0

My issue began when I generated a web service client (in RAD 9.0.0) from a supplied WSDL. It ran as it was supposed to, but an UnsupportedNamespaceException was generated each time it ran. The namespace it objected to is won't let me post and after searching online I found a replacement in won't let me post. After modifying the WSDL, the UnsupportedNamespaceException was no longer generated; however, every time I publish the application I get "WSWS3770W: Warning: WSDL2Java does not support http://schemas.xmlsoap.org/ws/2004/09/policy ,http://schemas.xmlsoap.org/wsdl/soap12/ binding namespace." and a completely new package is generated whose classes contain a multitude of errors. While I was able to find a replacement (above) for the first namespace mentioned, I've been unable to find a replacement for the second one. Any ideas? Thanks!

Stuart Bessent
  • 1
  • 1
  • Are you able to post the WSDL? – dbreaux Mar 17 '17 at 14:29
  • It looks like you are generating a jax-rpc client. Wondering if a jax-ws client might work. – Bruce T. Mar 18 '17 at 13:23
  • @dbreaux - I don't see any way to post the WSDL. Maybe I'm not "experienced" enough. – Stuart Bessent Mar 20 '17 at 12:02
  • @Bruce T. - Every other web service in my WebSphere projects does use JAX-RPC, but I actually used JAX-WS for this one, as using JAX-RPC produced two separate packages with unusual classes. – Stuart Bessent Mar 20 '17 at 12:06
  • I wish I knew how to explain this, but when I started working on this today (Monday), all of the "bad behavior" just stopped. (No more unexpected new package and no more UnsupportedNamespaceException.) Thanks! – Stuart Bessent Mar 20 '17 at 13:44

0 Answers0