JWSDP 2.0 with JBoss 4.0.4 ?

[hamptont]

When using JBoss 4.0.3SP1 I used JWSDP 2.0 to generate the ties for my webservice. I would like to upgrade to using JBoss 4.0.4.

When I deploy this same web service built, using JWSDP to JBoss 4.0.4, I get the following WARNINGS. The web service works, but these warnings concern me.

17:47:27,822 WARN [PortComponentMetaData] <wsdl-port> element in webservices.xml not namespace qualified: MyWSPort
17:47:29,593 WARN [WSDL11Reader] Encoding style 'http://schemas.xmlsoap.org/soap/encoding/' not supported for: {http://myws.my.com/}getDBList
17:47:29,594 WARN [WSDL11Reader] Encoding style 'http://schemas.xmlsoap.org/soap/encoding/' not supported for: {http://myws.my.com/}processBlastJob

Do I need to stop using JWSDP and use the wstool that comes with JBoss ?

[jason.greene]

We don't support soap encoding. We recommend using our tool, but if you prefer to stick with wscompile thats fine. Just make sure you are using rpcliteral or documentliteral.

-Jason

[tomstrummer]

We don't support soap encoding. We recommend using our tool, but if you prefer to stick with wscompile thats fine. Just make sure you are using rpcliteral or documentliteral.

-Jason

Hi Jason -- sorry to resurrect an old thread but I'm seeing a similar problem.

I am consuming a web service that I don't have control over (I think it's a .NET WS). First I tried using Apache CXF's wsdl2java to generate the client stubs, which complained about soapenc:Array in the WSDL (I don't remember the exact error). Googling suggested I needed an XML-RPC client, which JBossWS supports.

So the JBossWS' wsconsume tool generates my stubs and jaxrpc-mapping.xml file correctly, and I can even create and call the web service. But I see this same warning about soap encoding. I am a WS noob -- what should I do?

Thanks in advance.