Skip to main content

[javaee-spec issues] [JIRA] Commented: (JAVAEE_SPEC-8) Portable JNDI name for platform transaction manager

  • From: "arjan tijms (JIRA)" <jira-no-reply@...>
  • To: issues@...
  • Subject: [javaee-spec issues] [JIRA] Commented: (JAVAEE_SPEC-8) Portable JNDI name for platform transaction manager
  • Date: Thu, 24 Jan 2013 20:38:53 +0000 (GMT+00:00)
  • Auto-submitted: auto-generated


    [ 
http://java.net/jira/browse/JAVAEE_SPEC-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354296#action_354296
 ] 

arjan tijms commented on JAVAEE_SPEC-8:
---------------------------------------

Just wondering, what was the main objection? The fact that a transaction 
manager should not be accessible at all, or something else? Thanks!

> Portable JNDI name for platform transaction manager
> ---------------------------------------------------
>
>                 Key: JAVAEE_SPEC-8
>                 URL: http://java.net/jira/browse/JAVAEE_SPEC-8
>             Project: javaee-spec
>          Issue Type: Improvement
>            Reporter: arjan tijms
>
> Java EE mandates a (JTA) transaction manager to be present. There is 
> however no standardized portable JNDI defined for this. Currently a variety 
> of Java EE AS implementations use different names, e.g.:
> ||JNDI name || AS ||
> |java:jboss/TransactionManager | JBoss AS 7 |
> |java:/TransactionManager | JBoss AS 4 ~ 6, JRun4 |
> |java:comp/TransactionManager | Resin 3.x |
> |java:appserver/TransactionManager | Sun Glassfish | 
> |java:pm/TransactionManager | Borland, Sun |
> |javax.transaction.TransactionManager | BEA WebLogic |
> |java:comp/UserTransaction | Resin, Orion, JOnAS (JOTM) |
> _(list taken from Infinispan's GenericTransactionManagerLookup)_
> Some implementations (e.g. WebSphere), don't seem to register a transaction 
> manager in JNDI at all.
> For an end user this is troublesome, since various transactional products 
> (ORMs, Caching solutions) now need to bother the user with finding this 
> information for the particular AS the user is deploying that product on. 
> Generic solutions that scan well known locations may fail when the user 
> upgrades the AS or moves to another AS.
> To increase portability, I would like to request to introduce a portable 
> name for the platform transaction manager and mandate that this will be 
> available in all conforming implementations. E.g. 
> {{java:/TransactionManager}}.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://java.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[javaee-spec issues] [JIRA] Commented: (JAVAEE_SPEC-8) Portable JNDI name for platform transaction manager

ldemichiel (JIRA) 01/24/2013

<Possible follow-up(s)>

[javaee-spec issues] [JIRA] Commented: (JAVAEE_SPEC-8) Portable JNDI name for platform transaction manager

arjan tijms (JIRA) 01/24/2013

[javaee-spec issues] [JIRA] Commented: (JAVAEE_SPEC-8) Portable JNDI name for platform transaction manager

ldemichiel (JIRA) 01/24/2013

[javaee-spec issues] [JIRA] Commented: (JAVAEE_SPEC-8) Portable JNDI name for platform transaction manager

arjan tijms (JIRA) 01/24/2013

[javaee-spec issues] [JIRA] Commented: (JAVAEE_SPEC-8) Portable JNDI name for platform transaction manager

ldemichiel (JIRA) 01/24/2013

[javaee-spec issues] [JIRA] Commented: (JAVAEE_SPEC-8) Portable JNDI name for platform transaction manager

arjan tijms (JIRA) 01/24/2013
 
 
Close
loading
Please Confirm
Close