normal | wide

Signup for Training


More trainings...

INTALIO|BPMS WEBINARS


More Webinars...

Latest Posts


Show last 6 hrs - 24 hrs - 7 days

Forum RSS Feed

Top Posters

Last 30 days

  • Antoine (132)
  • gayatri.chandak (26)
  • gemor.roj (24)
  • juanjo.hernandez (22)
  • metabyte (20)
  • hellonico (15)
  • talita.pezzi (14)
  • danielandross (14)
  • liu.zhengyang (14)
  • Konstantin.Melnik (13)

All time

  • Antoine (2271)
  • Shivanand (1194)
  • cshekhar (933)
  • psq (797)
  • metabyte (411)
  • jag (393)
  • dfrench (358)
  • arnaud (328)
  • jalateras (325)
  • venkaiah.k (214)

Show last 4 hrs - 12 hrs - 24 hrs

POLL

We are looking for more information to tailor our training to better meet the needs of our customers. Please indicate all options that apply.

I would like to attend specialized training from Intalio on BPM as it relates to my application area:

I would like to attend specialized training from Intalio on BPM as it relates to my job function:

I would like to attend specialized training from Intalio on BPM as it relates to my industry:

Login

Who's online?

MAIN arrow FORUMS
Intalio|BPMS Community Edition Documentation Samples
I-Designer cannot resolve a referred to Namespace. (0 viewing) 
Go to bottom Post Reply Favoured: 1
TOPIC: I-Designer cannot resolve a referred to Namespace.
#15948
jnsunkersett (User)
Fresh Boarder
User Offline Click here to see the profile of this user
I-Designer cannot resolve a referred to Namespace. 10 Months ago Karma: 0  
Hi,

Following the WebServiceIntegration screencast I built my own project.
I want to use a custom developed service for which I have the WSDL and XSD.

But I-designer does not like the XSD.

In other words it is not able to resolve the XML Name space used ....
the error is:
    attribute 'arrayType@http://schemas.xmlsoap.org/soap/encoding/' not found


What can be done?
In case of Java development I know, I need to have a JAR in the classpath containing the referred XSD, but I could not find any concept of classpath with I-Designer.

myService.xsd is attached to this post
(please see line 5, 25 and 26. I-Designer cribs on line 25 and 26.


Code: :

 
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema 
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    targetNamespace="http://my.company.com.com/schemas/services/tickets"
    xmlns="http://my.company.com.com/schemas/services/tickets"
    xmlns:impl="http://my.company.com.com/schemas/services/tickets"
>

    <xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
    
    <xsd:complexType name="parameter">
        <xsd:sequence>
            <xsd:element name="name" type="xsd:string"/>
            <xsd:element name="type" type="xsd:string"/>
            <xsd:element name="required" type="xsd:boolean"/>
            <xsd:element name="isField" type="xsd:boolean"/>
            <xsd:element name="defaultValue" type="xsd:string"/>
        </xsd:sequence>
    </xsd:complexType>

    <xsd:complexType name="arrayOfParameter">
        <xsd:complexContent>
            <xsd:restriction base="soapenc:Array">
            <xsd:attribute ref="soapenc:arrayType" wsdl:arrayType="parameter[]" />
            </xsd:restriction>
        </xsd:complexContent>
    </xsd:complexType>

    <!-- and many more.... deleted for clarity -->
    
</xsd:schema>


~g1
File Attachment:
File Name: myService.xsd
File Size: 1168
 
Report to moderator   Logged Logged  
 
Last Edit: 2008/09/05 20:57 By jnsunkersett. Reason: The XSD pasted inside [code] got mangelled up.
  The administrator has disabled public write access.
#15953
Antoine (Admin)
Admin
User Offline Click here to see the profile of this user
Re:I-Designer cannot resolve a referred to Namespace. 10 Months ago Karma: 32  
Was that line in the XSD, or did you modify it ?

<strong><span style="color: #FF0000">xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/</span>"</strong>

I think you can remove the strong and span tags, that clearly seems invalid.
 
Report to moderator   Logged Logged  
 
Intalio, The Enterprise Cloud Company
www.intalio.com
  The administrator has disabled public write access.
#15955
jnsunkersett (User)
Fresh Boarder
User Offline Click here to see the profile of this user
Re:I-Designer cannot resolve a referred to Namespace. 10 Months ago Karma: 0  
Yes you r right, <span and <strong are invalid
I used cause it looked good in the preview.

Here is the exact (see Line 4, 23 and 24) I-designer cribs on 23 and 24.

Code: :

 

    <xsd:schema 
        xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
        xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
Line 4        xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" >

            targetNamespace="...my custom URI/ URL....."
            xmlns="...my custom URI/ URL....."
            xmlns:impl="...my custom URI/ URL.....">

            <xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
    
        <xsd:complexType name="parameter">
        <xsd:sequence>
            <xsd:element name="name" type="xsd:string"/>
            <xsd:element name="type" type="xsd:string"/>
            <xsd:element name="required" type="xsd:boolean"/>
            <xsd:element name="isField" type="xsd:boolean"/>
            <xsd:element name="defaultValue" type="xsd:string"/>
        </xsd:sequence>
        </xsd:complexType>

        <xsd:complexType name="arrayOfParameter">
            <xsd:complexContent>
Line 23            <xsd:restriction base="soapenc:Array">
Line 24                <xsd:attribute ref="soapenc:arrayType" wsdl:arrayType="parameter[]" />
                </xsd:restriction>
            </xsd:complexContent>
            </xsd:complexType>

 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
#15982
Antoine (Admin)
Admin
User Offline Click here to see the profile of this user
Re:I-Designer cannot resolve a referred to Namespace. 10 Months ago Karma: 32  
OK, then I'd like you to try something:

Download the SOAP XSD, place it next to yours, and refer to it locally:

<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" schemaLocation="soap.xsd"/>

Antoine
 
Report to moderator   Logged Logged  
 
Last Edit: 2008/09/07 07:05 By Antoine.
 
Intalio, The Enterprise Cloud Company
www.intalio.com
  The administrator has disabled public write access.
#16039
jnsunkersett (User)
Fresh Boarder
User Offline Click here to see the profile of this user
Re:I-Designer cannot resolve a referred to Namespace. 9 Months, 4 Weeks ago Karma: 0  
Thanks Antoine,

Downloading and referring to the XSD locally resolved that problem.

<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" schemaLocation="soap.xsd"/>

But in the Mapper view I still see something red which I cannot understand. (magnified picture attached in zip )



~g1
PS: I think I might be missing something and should revisit some fundamentals but unable to determine of what - intalio or webservices or ...
File Attachment:
File Name: mapper_view_full.zip
File Size: 30150
 
Report to moderator   Logged Logged  
 
Last Edit: 2008/09/10 01:12 By jnsunkersett.
  The administrator has disabled public write access.
#16046
Antoine (Admin)
Admin
User Offline Click here to see the profile of this user
Re:I-Designer cannot resolve a referred to Namespace. 9 Months, 4 Weeks ago Karma: 32  
You have an invalid variable, try remapping the messages on the task to recreate it properly. If that fails, try removing filters to see it in the diagram, and remove it directly.

Thanks,

Antoine
 
Report to moderator   Logged Logged  
 
Intalio, The Enterprise Cloud Company
www.intalio.com
  The administrator has disabled public write access.
Go to top Post Reply
get the latest posts directly to your desktop