Bug 54965 - [f] web services client document literal causes error.
[f] web services client document literal causes error.
Product: webservices
Classification: Unclassified
Component: Code
PC Windows XP
: P4 (vote)
: 6.x
Assigned To: Milan Kuchtiak
Depends on:
  Show dependency treegraph
Reported: 2005-02-15 04:32 UTC by danjar
Modified: 2008-11-20 15:37 UTC (History)
0 users

See Also:
Issue Type: DEFECT

alexia wsdl from amazon (52.26 KB, text/plain)
2005-02-16 00:30 UTC, danjar

Note You need to log in before you can comment on or make changes to this bug.
Description danjar 2005-02-15 04:32:10 UTC
Whenever I create a web services client within a
web application where the clients wsdl uses
document/literal rather than rpc I get deployment
Comment 1 _ ludo 2005-02-15 05:02:33 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)
Comment 2 danjar 2005-02-16 00:30:54 UTC
Created attachment 20357 [details]
alexia wsdl from amazon
Comment 3 danjar 2005-02-16 00:40:33 UTC
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

Comment 4 _ pcw 2005-03-21 22:23:26 UTC
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".
Comment 5 _ pcw 2005-03-22 02:02:35 UTC
Need to get bugtraq number for JAXRPC bug.
Comment 6 _ pcw 2005-10-01 01:05:22 UTC
Reassigning to websvc since I am not working in this area anymore.
Comment 7 Lukas Jungmann 2005-12-01 01:28:08 UTC
got following exception while testing client for AWSAlexa.wsdl in the registry:

	at javax.swing.tree.DefaultMutableTreeNode.insert(DefaultMutableTreeNode.java:173)
	at javax.swing.tree.DefaultMutableTreeNode.add(DefaultMutableTreeNode.java:396)
Comment 8 m_wainamoinen 2006-03-10 20:46:12 UTC
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 ?
Comment 9 m_wainamoinen 2006-03-10 21:04:40 UTC
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.
Comment 10 Lukas Jungmann 2006-05-18 10:58:13 UTC
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
Comment 11 Lukas Jungmann 2008-04-14 17:17:22 UTC
moving opened issues where TM != dev to TM=TBD
Comment 12 Milan Kuchtiak 2008-11-20 15:37:44 UTC
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.

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo