• 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Devaka Cooray
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Knute Snortum
  • Bear Bibeault
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Ganesh Patekar
Bartenders:
  • Frits Walraven
  • Carey Brown
  • Tim Holloway

JAXB object and message mode

 
Ranch Hand
Posts: 1738
12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In MZ's notes, there is a quote "JAXB object may be used with any protocol binding in either message or message payload mode."
But according to Apache CXF, JAX-WS dispatch API documentation, it says "Message mode is not ideal when you wish to work with JAXB objects."

So, do the two statement contradict with each other about using message mode in dispatch API?
 
Creator of Enthuware JWS+ V6
Posts: 3288
296
Android Eclipse IDE Chrome
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
According to the specs it is allowed, but I don't have an example. By the way you have asked the same type of question here.

Did you give it a try?
 
Himai Minh
Ranch Hand
Posts: 1738
12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I tried that with Ivan's example and it did not work. I guess it is better to do this combination createDispatch (portName, Jaxbcontext, Service.Mode.PAYLOAD).

But I was surprise to see the statement that JAXB Object can be used with any protocol with message or payload mode. My example in the post a long time ago shows that it does not work.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!