• 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

Webservice implementing Provider<Source>: no difference with service mode MESSAGE or PAYLOAD

 
Greenhorn
Posts: 15
Oracle VI Editor Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi everybody,

i am new to jax-ws and noticed that my webservice which implements interface Provider<Source> (Annotation WebServiceProvider) behaves the same
regardless of the chosen servicemode. In both cases (PAYLOAD or MESSAGE) the method invoke gets an object of type StAXSource which holds the entire SOAP-Message
(beginning with <?xml .... <S:Envelope ....). Using payload-mode i expected only the contents of the soap-body , but i always get the whole soap-message.
(i am using glassfish 2.1.1, java 5)

the j2ee 5 doc says:
Service mode. PAYLOAD indicates that the Provider implementation wishes to work with protocol message payloads only. MESSAGE indicates that the Provider implementation wishes to work with entire protocol messages
( see http://download.oracle.com/javaee/5/api/javax/xml/ws/ServiceMode.html )

maybe this behaviour is specific to glassfish ?

thanks in advance
ulli





 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic