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.
XSLT editor does not support messages defined on simple or built-in types steps to reproduce. 1. Define a wsdl document that has a message defined on a built in data type ex: <wsdl:message name="InOutMsg"> <wsdl:part name="InOutPart" element="xsd:String"/> </wsdl:message> A sample wsdl is available with the project zip attached to this ticket. 2. create a new Request-Reply Service type by selecting this wsdl and pointing to the request-response operation 3. Observe that the wsdl editor opens up and the mapper view does not have any message structure shown. Netbeans build used is : ide-gavotte-070220_6.zip from http://balui.sfbay.sun.com/kits/oriondev/gavotte/Build070220_6/
Created attachment 38795 [details] The project file containing the test case
Not stopper for Beta. Will be addressed by FCS.
<wsdl:part name="InOutPart" element="xsd:String"/> Is not a valid declaration. Should be <wsdl:part name="InOutPart" type="xsd:string"/> Please try to run Validate XML on your WSDL files, you will get an error: C:/Documents and Settings/Alexey/XsltModule32/src/po2la.wsdl:14,8 Error: In part "part1", attribute element's value "xsd:String" is not a valid xml schema element available in this wsdl file. : Specify a valid schema element value for element attribute. C:/Documents and Settings/Alexey/XsltModule32/src/po2la.wsdl:17,8 Error: In part "part1", attribute element's value "xsd:String" is not a valid xml schema element available in this wsdl file. : Specify a valid schema element value for element attribute. Support for type=".." declarations for message parts will be implemented in FCS.
My apologies Steps to reproduce point 1 in the description was a typo error it should have actually been <wsdl:message name="InOutMsg"> <wsdl:part name="InOutPart" type="xsd:String"/> </wsdl:message> However if you had opened the attached project zip "XsltModule1.zip" and looked at the wsdl file InOut.wsdl you would see the message definition as <message name="message1"> <wsdl:part name="part1" type="xsd:string"/> </message>
Removed Beta EP551_WAIVER_APPROVED keyword - we are going forward to FCS.
To fix this problem, "source document" tree should be seriously re-worked. Currently, nodes in this tree is 1-to-1 corrlates with element in AXI model. And a lot of functions are implemented based on this fact. To add support for type="..." definitions, we should add "virtual" node for root elements (virtual means that they not exists in schema). And all this functions should be re-written or modified. So, the fix becomes too risky to implement it now.
*** Issue 95058 has been marked as a duplicate of this issue. ***
Guys, Any update on this P1 ?
Work in progress. However there is non zero probability will fix it after Beta1.
*** Issue 121114 has been marked as a duplicate of this issue. ***
there is no warning to user in the wizard or elsewhere about it ? wouldn't it be that wizard should not complete if this bug situation happens. in my case, I just kept pressing next in wizard; I realize real user would know more about how to really do it, but seems like still should be warning now due to this issue ? (rather than mysterious warning on design panel) ken.frank@sun.com
will there be relnote for this ? I'm adding that keyword; please remove it if not needed. My view is from just a user getting started who would go thru the wizards without customizing the wsdl file yet, but then they would run into this issue and it could be confusing for them to see the err msg. ken.frank@sun.com
The XSLT will be on update center so decreasing priority.
waived
This is related to graphical part of XSLT editor which should reimplemented totally. Marked as WONTFIX.
The Design View of the XSLT Editor has been removed indefinitely. Issues related to the former Design View view are no longer applicable. GFESB (20090105-0707) does not have the Design View. Marking this issue as Verified.