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.
The XML Schema import capability is removed. You can import XML schema later on on the <types> element. But the real problem is that any types defined in the XML schema cannot be chosen when creating a <message> element of WSDL. It really diminish the usefulness of WSDL designer given that you cannot select any element/type defined in the imported XML schema. The only work-around is copy and paste the XML schema definitions from the XML schema file into the WSDL's type definition using source editor, which is a real kludge.
You should be able to select the elements from the part element or type chooser in the abstract configuration step. Can you provide the steps, which project type(java, bpel etc) are you using?
More info from the reporter (Sang): XML schema import is automatically done when creating WSDL under BPEL project but in other project types - Web app or Java app, even if you imported the XML schema, the types from that schema cannot be selected.
Fixed. Changeset 142832
I'm not clear on the scenario for this issue to verify the fix. Is this related to issue 166945 ?
See issue 166945 for problems see when testing this bug fix with GFESB 2.2.
Created attachment 92160 [details] user can specify Pre-Decode and Post-Encode charsets at the top encoding node
sorry put attachment into wrong ticket also mistakenly changed the status, all because this wacky netbeans issue tracking problem where modifying and saving a ticket redirect you to another ticket by random :(