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: | [f] web services client document literal causes error. | ||
---|---|---|---|
Product: | webservices | Reporter: | danjar <danjar> |
Component: | Code | Assignee: | Milan Kuchtiak <mkuchtiak> |
Status: | RESOLVED WORKSFORME | ||
Severity: | blocker | Keywords: | RELNOTE |
Priority: | P4 | ||
Version: | 4.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | alexia wsdl from amazon |
Description
danjar
2005-02-15 04:32:10 UTC
Which build? Which errors? Can you attach the wsdl? Or can you verify if it's correct? (hint: if downloaded via firefox or mozilla, it might contain errors) Thanks. Created attachment 20357 [details]
alexia wsdl from amazon
Sorry for the lack of information. I tested again with a wsdl file i obtained from amazon. And have attached the exact one that I used. I opened it straight into edit plus and saved it. The Build # is 041014 The error that I recieved in the Output window: Deployment Error -- Error while running ejbc -- Fatal Error from EJB Compiler -- jaxrpc compilation exception I also got this logged as INFO in the application servers logs. [failed to localize] Unable to locate jax-rpc mapping meta-data for wsdl operation UrlInfo in binding {http://webservices.amazon.com/AWSAlexa/2004-09-15}AWSAlexaBinding I forwarded this issue & WSDL to JAXRPC team. Here are their comments: "This is a known problem. This occurs when the WSDL operation qualifies for wrapper style and output part's element has more than one sub element. JAXRPC RI doesn't unwrap the output element in that case. This causes conflict with 109 spec." The workaround for this service is in project | properties | web service clients, for this service, enable the features "donotunwrap" and disable "strict". Need to get bugtraq number for JAXRPC bug. Reassigning to websvc since I am not working in this area anymore. got following exception while testing client for AWSAlexa.wsdl in the registry: java.lang.StackOverflowError at javax.swing.tree.DefaultMutableTreeNode.insert(DefaultMutableTreeNode.java:173) at javax.swing.tree.DefaultMutableTreeNode.add(DefaultMutableTreeNode.java:396) at org.netbeans.modules.websvc.registry.ui.TestWebServiceMethodDlg.traverseResultType(TestWebServiceMethodDlg.java:716) at org.netbeans.modules.websvc.registry.ui.TestWebServiceMethodDlg.traverseResultType(TestWebServiceMethodDlg.java:723) at org.netbeans.modules.websvc.registry.ui.TestWebServiceMethodDlg.traverseResultType(TestWebServiceMethodDlg.java:723) at org.netbeans.modules.websvc.registry.ui.TestWebServiceMethodDlg.traverseResultType(TestWebServiceMethodDlg.java:723) ... I read about the work-around but how can you do this, if I tell netbeans to create the client it does not ask me if I want the "strict" to be disabled and "dontwrap" enabled and it causes this error and does not give me a chance to say not "strict" and "dontwrap" ? how can you set these values before creating the client ? Doing it the hard-way, if manualy edited the file, nbproject/project.properties to exclude <some_line>features=strict this was during the client build process, so in the middle so to say. works fine when using JAX-WS in 5.5, althogh there are some minor issues in generated code (issue 76548, issue 76550); lowering to P4 moving opened issues where TM != dev to TM=TBD Tested both JAX-WS and JAX-RPC. In JAX-RPC, I've got 3 wscompile warnings : warning: unsupported XML Schema feature: "xsd:choice" in component {http://webservices.amazon.com/AWSAlexa/2004-09-15}CrawlType, mapping it to javax.xml.soap.SOAPElement warning: unsupported XML Schema feature: "xsd:choice" in component {http://webservices.amazon.com/AWSAlexa/2004-09-15}TimeRange, mapping it to javax.xml.soap.SOAPElement warning: unsupported XML Schema feature: "xsd:choice" in component {http://webservices.amazon.com/AWSAlexa/2004-09-15}TimeRangeType, mapping it to javax.xml.soap.SOAPElement Anyway, client artifacts were generated correctly. |