• 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

WSDL, JAX-WS, WS-AT, Hibernate

 
Ranch Hand
Posts: 68
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am new to alot of this. As I peruse the internet, is it true that I can have a client running a Hibernate transaction against a database, and have a JAX-WS call that uses WS-AT which particpates in that parent transaction, and would rollback if the transaction were rolled back? That seems to be what the articles I am reading imply, but I don't seem to find a decent example showing a client test class running a transaction, calling a web service that participates. I misunderstood what JEST was, thinking it would do something like what I am after for REST services, but instead it seems to just be a scheme for managing transactions within a REST service.

So can someone set me straight on if I am going down the right path towards having transactional integrity while using web services? And maybe a pointer to a good example would be good.
 
You ought to ventilate your mind and let the cobwebs out of it. Use this cup to catch the tiny ads:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic