OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsbpel] Issue - 174 - Are multiple imports with the same namespaceallowed?


Hi,

In general there are no restrictions that all definitions that go in a target Namespace be defined in a single fille (or be available from the same location) etc., hence IMO it is perfectly legal to import the same namespace more than once.  However, I have seen people run into issues with this as the spec is not very clear on this. The schemaLocation is just a hint as to where to find a schema for a given namespace. If the system thinks it already has a schema for that namespace, some systems assume that it's another copy of the same schema, and do not do the actual import. To get around this people assemble a complete schema for a namespace using
xs:include, and then import the assembled schema.

Having said that I think we should not preclude multiple imports of the same namespace (Schema, WSDL etc.).

Regards, Prasad

------- Original Message --------
Subject: Re: [wsbpel] Issue - 174 - Are multiple imports with the same namespace allowed?
Date: Sat, 23 Oct 2004 17:58:10 -0700
From: Alex Yiu <alex.yiu@oracle.com>
To: wsbpel@lists.oasis-open.org
CC: Alex Yiu <alex.yiu@oracle.com>
References: <200410231745.i9NHjTZ2019000@agminet04.oracle.com>

Hi, all,

I just would like to point out that the <bpel:import> construct of BPEL can import both WSDL and XSD.

It is legal to import multiple XSD of the same TNS from different locations using <xsd:import> within a schema location.

Therefore, I think <bpel:import> construct should allow importing multiple XSD of the same TNS also.

Thus, I tend to think a similar semantics should be carried over to allow importing multiple WSDL of the same TNS from different location as well. I would like to hear more WSDL experts to confirm this usage situation will not create problems.

Thanks!


Regards,
Alex Yiu

ws-bpel issues list editor wrote:

This issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if the TC accepts it as identifying a bug in the spec or decides it should be accepted specially. Otherwise it will be closed without further consideration (but will be marked as "Revisitable")

The issues list is posted as a Technical Committee document to the OASIS WSBPEL TC pages on a regular basis. The current edition, as a TC document, is the most recent version of the document entitled in the "Issues" folder of the WSBPEL TC document list - the next posting as a TC document will include this issue. The list editor's working copy, which will normally include an issue when it is announced, is available at this constant URL.

Issue - 174 - Are multiple imports with the same namespace allowed?

Status: received
Date added: 23 Oct 2004
Categories: Related standards
Date submitted: 27 September 2004
Submitter: Jim Clune
Description: Is it legal to have a BPEL process with two BPEL import elements each pointing to WSDLs of the same namespace, but different locations? The Document Linking section of the spec does not explicitly disallow this. One might interpret this situation as legal, and one might further interpret references to WSDL elements within such a process as resolving so long as each element resolves to one of the imported WSDLs for that namespace.

The text should be clear.
Changes: 23 Oct 2004 - new issue





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]