• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • paul wheaton
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
  • Himai Minh
Bartenders:

Doubt about import statement in RMH

 
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi
Can anyone explain the following about import in rmh
"It is important to note that you cannot use the xml schema import statement to import an xml schema directly from the types element of some other wsdl document".
This statement is the last statement in 5.2.4 (rmh).
regards
vasugi
 
Ranch Hand
Posts: 228
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
C

an anyone explain the following about import in rmh
"It is important to note that you cannot use the xml schema import statement to import an xml schema directly from the types element of some other wsdl document".
This statement is the last statement in 5.2.4 (rmh).
regards



1. import statement can be used to import schema and also wsdl definitions from other wsdl file (Refer example of WSDL Specifications)
2. The above thing is a constraint placed by BasicProfile. not to refer to the schema types created in a wsdl from other wsdl

Example
Let us have parent.wsdl
you have defined a type called contactinfo inside the types definition in parent.wsdl
<types>
<xsd:schema targetNamespace="http://parentcontact/">....
<xsd:complexType name="contactinfo">
....</xsd:complexType>
</xsd:schema></types>


Now you shouldnt refer the contactinfo in another wsdl child.wsdl
using the targetnamespace.

I guess,they would have kept it for modularity and encapsulation. Not sure why the constraint was kept.

Can anybody throw more light on that and correct me if i am wrong.

Regards
 
vasu venki
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi
Thanks karthik,but can you be more specific on the constraint.or can anyone help me.
 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
My interpretation:

Schema import Syntax:

<import namespace=".." schemaLocation="...xsd"/>

schemaLocation must point to a ".xsd" file only.

(This import could happen within an XSD file or in the types section of a wsdl file)
reply
    Bookmark Topic Watch Topic
  • New Topic