• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Java EE doesnot support Encoded binding

 
Ranch Hand
Posts: 268
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I tried making wsdl using wsgen tool. The SEI was annotated using the SOAPBinding annotation :



wsgen threw error saying "The fromjava.server.AddNumbersImpl class has invalid SOAPBinding annotation. rpc/encoded SOAPBinding is not supported"

J2EE 1.4 supported ENCODED binding . Does it mean that ENCODED binding cannot be used with Java EE.
 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Sim Kim:
Does it mean that ENCODED binding cannot be used with Java EE.



Correct - RPC/encoded is not supported (which I did mention to you here) as a messaging mode and the "encoded" encoding style isn't supported at all, only the "literal" encoding style is supported under JAX-WS.

Basically SOAP 1.1 section 5 encoding was too ambiguous to be implemented consistently and some platforms couldn't even support it. RPC/encoded was a the root of many "interoperation nightmares".
[ November 20, 2008: Message edited by: Peer Reynders ]
reply
    Bookmark Topic Watch Topic
  • New Topic