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
To comment on this issue (including whether it should be
accepted), please follow-up to this announcement on the
wsbpel@lists.oasis-open.org list (replying to this message should
automatically send your message to that list), or ensure
the subject line as you send it starts "Issue - 174 -
[anything]" or is a reply
to such a message. If you want to formally propose a resolution to an
open issue, please start the subject line "Issue - 174 - Proposed
resolution", without any Re: or similar.
To add a new issue, see the issues procedures document (but the
address for new issue submission is the sender of this announcement).
Choreology Anti virus scan completed