glassfish_at_javadesktop.org wrote:
> Hi,
>
> Thanx for reply.
>
> I saw all your screencast, very usefull.
> Sounds like your the master and I'm the padawan :)
>
> I just wanted to know more about configuring WS-AT in my web services.
> Do I need to code transactions commit/rollback events or WS-AT manage the end of the web service ?
>
> Do I simply need to check "Required" in WSIT panel for my operation ?
>
> I have a last question, I need to make a call from wsA service to wsB service in a transactionnal way.
> What do I need to do ? Does the wsA need to be "Required" and wsB "Supported" ?
> I'm quite lots on that point.
>
Simply enabling "Required" on the wsA and wsB methods is sufficient.
When wsA invocation is made w/o a current transactional context,
(JTATxnMgr.getTransaction() returns null), the container will create
transaction
to make invocation with and will commit/rollback on return. (Just like
invoking an EJB 3.0 Required method works.)
One problem that we have noted is personal firewalls can stealthy block
lookups from the runtime to the __wstx_service, effectively
disabling WS-AT. If this is happening, you will see a warning in the
server.log.
WSTX-WS2004-5000: WSTX service for 2004
WS-Coordination/WS-AtomicTransaction is unavailable
or
WSTX-CLIENT-1001: WS-TX service is not available. Unable to flow a
WS-Atomic Transaction Context for web service invocation of operation
''{0}'' from current container
Configuring your firewall to allow access to the port that WS-TX service
is running on will address these issues.
******
You did not provide version info with your issue. There is a known
regression that occurred in glassfish b50 and was fixed in b51. See
https://glassfish.dev.java.net/issues/show_bug.cgi?id=3181. If you are
using b50, you would also see the behavior that you are reporting along
with the above warnings in the server.log.
-Joe
> Thanx in advance.
> [Message sent by forum member 'jgresse' (jgresse)]
>
> http://forums.java.net/jive/thread.jspa?messageID=223006
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>