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.
Summary: | The bpel mapper does not generate Qualified name for local elements that have a element reference to global elements | ||
---|---|---|---|
Product: | soa | Reporter: | pvarghese <pvarghese> |
Component: | BPEL Mapper | Assignee: | Vladimir Yaroslavskiy <yaroslavskiy> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | alexeyyarmolenko |
Priority: | P1 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 93892 | ||
Attachments: |
the WSDL file containing the inline schema
the zip file of the composite App projec that was used to test this scenario, has bpel, java ee webservice and comp app project The bpel file that has the errorneous assignment statements |
Description
pvarghese
2007-01-31 20:19:04 UTC
Created attachment 37894 [details]
the WSDL file containing the inline schema
Created attachment 37895 [details]
the zip file of the composite App projec that was used to test this scenario, has bpel, java ee webservice and comp app project
Created attachment 37896 [details]
The bpel file that has the errorneous assignment statements
Hi, I don't understand how bpel mapper is involved. Please describe how to reproduce thebug by steps: 1) create new bpel project 2) open bpel file from attachment 3) bla-bla-bla Adding steps to reproduce: 1. Create a BPEL project using entrprise tools. 2. Use the attached wsdl to create a wsdl document in the project 3. Create a BPEL document(file). 4. Create partnerlink by importing the wsdl into the BPEL. 5. create two variables associated wiht the Message defined in the WSDL. 6. Add an assignment between the two variables and map at the leaf node level. the assignment generated would be as mentioned in the Description. Example: <bpws:assign name="Assign2"> <bpws:copy> <bpws:from>$IntPTOperOut.part1/intElem</bpws:from> <bpws:to>$ExtPTOperOut.part1/intElem</bpws:to> </bpws:copy> <bpws:copy> <bpws:from>$IntPTOperOut.part1/strElem</bpws:from> <bpws:to>$ExtPTOperOut.part1/strElem</bpws:to> </bpws:copy> </bpws:assign> the elements 'strElem' and 'intElem' are not qualified. They have to be qualified due to the reason mentioned in the Description. I don't know how the fix would be, but one way would be to import the schema and then qualify the elements by that prefix. Hope this helps The problem is that namespaces aren't added if an element is from inline schema stored in wsdl file. If schema is represented by schema file .xsd, it works fine. Related issue http://www.netbeans.org/issues/show_bug.cgi?id=95346 The rules have been implemented for qualifying element name: 1. Global element is always qualified. 2. If schema "elementFormDefault" is qualified, any element is qualified. 3. If schema "elementFormDefault" is unqualified: 3.1 if local element has qualified form, it is qualified. 3.2 if element is ElementReference, it is qualified. WinXP 070313 Mapper generate name with namespace prefix for this example |