hibernate-issues

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-589) websphere 5.1 transaction manager lookup

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Tue, 30 Dec 2003 3:15 PM
       Body:
Please do - i guess it is just a another "try to look up class, if not availablet try the next option"
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-589


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-589
    Summary: websphere 5.1 transaction manager lookup
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1.1

   Assignee: 
   Reporter: Edina Pimp

    Created: Tue, 30 Dec 2003 1:38 PM
    Updated: Tue, 30 Dec 2003 3:15 PM
Environment: websphere 5.1

Description:
WebSphere 5.1 changed the name of the TransactionManagerFactory class.  Class is now:

  com.ibm.ws.Transaction.TransactionManagerFactory

As a result, the net.sf.hibernate.transaction.WebSphereTransactionManagerLookup strategy will need to be updated to look for this class.  I can provide working patch if needed.




---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-589) websphere 5.1 transaction manager lookup

[<leg...@at...>]

The following comment has been added to this issue:

     Author: CVS Notification Service
    Created: Tue, 20 Jan 2004 12:02 AM
       Body:
CVS COMMIT LOG: 
SUBJECT: [Hibernate-commits] Hibernate2/src/net/sf/hibernate/transaction WebSphereTransactionManagerLookup.java,1.5.2.5,1.5.2.6
HB-589 - changed package of Transaction Manager Factory (again).
This time for WAS 5.1
Tested against WAS 5.0 and 5.1
Patch from Edina Pimp


---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-589


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-589
    Summary: websphere 5.1 transaction manager lookup
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1.1

   Assignee: Daniel Bradby
   Reporter: Edina Pimp

    Created: Tue, 30 Dec 2003 1:38 PM
    Updated: Tue, 20 Jan 2004 12:02 AM
Environment: websphere 5.1

Description:
WebSphere 5.1 changed the name of the TransactionManagerFactory class.  Class is now:

  com.ibm.ws.Transaction.TransactionManagerFactory

As a result, the net.sf.hibernate.transaction.WebSphereTransactionManagerLookup strategy will need to be updated to look for this class.  I can provide working patch if needed.




---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-589) websphere 5.1 transaction manager lookup

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Rohit Singh
    Created: Fri, 30 Jan 2004 1:23 PM
       Body:
All Websphere package which start with com.ibm.ws are internal only package. That is they are not meant for external usage. If we use this package here it may work. work but create other problems later. Work but break in next release(like it did).

Is this the way to go ? Is this class required to be provided by a J2EE vendor. I cannot find where in J2EE docs it says that.

I longer run it may be better to use a public methodo not private, any issues in apps related to this will not be supported by IBM either.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-589


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-589
    Summary: websphere 5.1 transaction manager lookup
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1.1

   Assignee: Daniel Bradby
   Reporter: Edina Pimp

    Created: Tue, 30 Dec 2003 1:38 PM
    Updated: Fri, 30 Jan 2004 1:23 PM
Environment: websphere 5.1

Description:
WebSphere 5.1 changed the name of the TransactionManagerFactory class.  Class is now:

  com.ibm.ws.Transaction.TransactionManagerFactory

As a result, the net.sf.hibernate.transaction.WebSphereTransactionManagerLookup strategy will need to be updated to look for this class.  I can provide working patch if needed.




---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-589) websphere 5.1 transaction manager lookup

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Emmanuel Bernard
    Created: Sun, 1 Feb 2004 5:46 PM
       Body:
There is no standard way to find the application server transaction manager and each J2EE impelmentor do it differently even between versions.
I don't know other way than using internal classes.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-589


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-589
    Summary: websphere 5.1 transaction manager lookup
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1.1

   Assignee: Daniel Bradby
   Reporter: Edina Pimp

    Created: Tue, 30 Dec 2003 1:38 PM
    Updated: Sun, 1 Feb 2004 5:46 PM
Environment: websphere 5.1

Description:
WebSphere 5.1 changed the name of the TransactionManagerFactory class.  Class is now:

  com.ibm.ws.Transaction.TransactionManagerFactory

As a result, the net.sf.hibernate.transaction.WebSphereTransactionManagerLookup strategy will need to be updated to look for this class.  I can provide working patch if needed.




---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira