This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 138597 - UI/Compiler error: "incorrect message type" when using multiple wsdls sharing same namespace
Summary: UI/Compiler error: "incorrect message type" when using multiple wsdls sharing...
Status: NEW
Alias: None
Product: xml
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@xml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-30 10:38 UTC by babram
Modified: 2008-11-19 19:29 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments
Sample project to illustrate issue (look at Test.bpel) (16.21 KB, text/plain)
2008-06-30 10:43 UTC, babram
Details
Sample project to illustrate issue (look at Test.bpel) (16.21 KB, application/x-compressed)
2008-06-30 10:44 UTC, babram
Details

Note You need to log in before you can comment on or make changes to this bug.
Description babram 2008-06-30 10:38:21 UTC
Environment
===========

Product Version: NetBeans IDE 6.1 (Build 200804211638 & 200806240008)
Java: 1.5.0_10; Java HotSpot(TM) Client VM 1.5.0_10-b03
System: Windows XP version 5.1 running on x86; Cp1252; en_GB (nb)


Problem description
===================

When using multiple WSDLs in a BPEL process that share the same namespace "incorrect message type" errors will occur
when associating variables to invoke actions.

Rationale for using multiple WSDLs with the same namespace is when using multiple (OSS/j) JSR-264 compliant services in
a process for example.


Steps to Duplicate
==================

1. Create a BPEL process that uses two WSDLs using the same namespace
2. Create two invoke actions that uses each of the WSDLs
3. Create variables for the actions

4. Build the project and the following error would occur:

ERROR: When the optional inputVariable and outputVariable attributes are being used in an <invoke> activity, the
variables referenced by inputVariable and outputVariable must be messageType variables whose QName matches the QName of
the input and output message type used in the operation, respectively.

 (Note that there might be another error occurring first, regarding problems with the portType - not sure if this is a
bug but the portType can safely be removed from the invoke action as the partnerLinkType will define the portType)

5. Further inconsistencies can be found when going back to edit one of the invoke actions:

   i)   For a variable Click "Browse..."
   ii)  Make sure the checkbox "show variables with appropriate types only" is checked
   iii) Pick one of the variables previously created and click OK
   iv)  An error message will appear: "The variable with incorrect type was chosen!"
Comment 1 babram 2008-06-30 10:43:45 UTC
Created attachment 63668 [details]
Sample project to illustrate issue (look at Test.bpel)
Comment 2 babram 2008-06-30 10:44:52 UTC
Created attachment 63669 [details]
Sample project to illustrate issue (look at Test.bpel)
Comment 3 babram 2008-06-30 13:42:45 UTC
A solution might be to "wrap" the WSDL(s) in a new WSDL with unique namespace... Will investigate 
Comment 4 Sergey Lunegov 2008-10-01 14:24:57 UTC
Kirill, looks like we already investigated this problem please provide comments.
Comment 5 Kirill Sorokin 2008-10-02 23:06:52 UTC
Yes, we did. A loong time ago we'd stumbled upon the very same issue. We had some ideas of how to avoid this, but then
did not produce any concrete plan. I'll try to recollect the ideas when I'm back from vacation. Meanwhile, I believe
switching the Allow build with errors checkbox in project's properties will help.
Comment 6 Kirill Sorokin 2008-11-19 19:29:57 UTC
This actually happens due to XML support lacking a certain feature.. Namely the impossibility to treat several WSDLs
with the same namespace as a single logical entity. Whenever we try to look for the given type, we end up in wrong file.

Transferring as a P2 enhancement to XML to evaluate.