[jbossws-issues] [JBoss JIRA] Commented: (JBWS-1947) Metro clients require jnpserver.jar
Alessio Soldano (JIRA)
jira-events at lists.jboss.org
Fri May 23 09:49:45 EDT 2008
[ http://jira.jboss.com/jira/browse/JBWS-1947?page=comments#action_12414007 ]
Alessio Soldano commented on JBWS-1947:
---------------------------------------
jnpserver.jar is actually needed since the metro client code checks whether the transactions are enabled when creating the pipes. This check for ws-atomic transactions includes a JNDI lookup for "java:appserver/TransactionManager" (which is btw Sun App Server specific) and that's the reason for the need of jnpserver.jar library.
> Metro clients require jnpserver.jar
> -----------------------------------
>
> Key: JBWS-1947
> URL: http://jira.jboss.com/jira/browse/JBWS-1947
> Project: JBoss Web Services
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: jbossws-metro
> Affects Versions: jbossws-metro-3.0.0
> Reporter: Heiko Braun
> Assigned To: Alessio Soldano
> Priority: Minor
> Fix For: jbossws-metro-3.0.2
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> For some reason (ws-tx) metro clients require jnpserver.jar to be in classpath. It shouldn't be like this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossws-issues
mailing list