[ https://hibernate.onjira.com/browse/HHH-7012?page=com.atlassian.jira.plug... ] Jeff Cyre commented on HHH-7012: -------------------------------- There is a line of code in org.hinbernate.service.jndi.internal.JndiServiceImpl.locate(String jndiName). The line is <code>return initialContext.lookup( name );</code> Change it to <code>return initialContext.lookup( nametoString() );</code> I use Tomcat 6.0 and this solved it for me. This is essentially how previous version of Hibernate did it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HHH-7012?page=com.atlassian.jira.plug... ] Steve Ebersole commented on HHH-7012: ------------------------------------- Is this Tomcat's own JNDI implementation? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HHH-7012?page=com.atlassian.jira.plug... ] Steve Ebersole commented on HHH-7012: ------------------------------------- Even more boggling when you look at their impl: http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/naming/NamingCo... lookup(String) and lookup(Name) seem to equate to the same thing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HHH-7012?page=com.atlassian.jira.plug... ] Boris commented on HHH-7012: ---------------------------- I experience the same issue with WebLogic 12 as well as with Tomcat 5.5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HHH-7012?page=com.atlassian.jira.plug... ] Steve Ebersole commented on HHH-7012: ------------------------------------- Well we only ever need to use the {{Name}} variant when we have to perform binding. For just doing look ups, the {{String}} variant is fine. If multiple JNDI implementations have problems with their {{NameParser}} it might be better to switch back to the {{String}} variant for look ups. I just switched for consistency, but obviously a working solution that accounts for seeming bugs on various platforms trumps consistency :( If I had to guess, probably the NameParser returned from getNameParser( "" ) for the impls that fall down here are "rooted" at {{java:comp/env}} and does not recognize that as a prefix when passing in the full {{java:comp/env/jdbc/myCompDb}} string. Kind of retarded NameParser implementation if you ask me, but oh well. If that is the case, you should be able to name your datasource as {{jdbc/myCompDb}} to Hibernate and this code should then resolve correctly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HHH-7012?page=com.atlassian.jira.plug... ] Steve Ebersole commented on HHH-7012: ------------------------------------- WDYM Christian? Bitronix implemented the NameParser this same way? BTW you do know it is no longer a requirement to use JNDI for transaction object lookup right? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HHH-7012?page=com.atlassian.jira.plug... ] Steve Ebersole commented on HHH-7012: ------------------------------------- Same deal with datasource. No need for jndi if you dont want to. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HHH-7012?page=com.atlassian.jira.plug... ] Steve Ebersole commented on HHH-7012: ------------------------------------- Curious whether that actually worked for you with stock Hibernate after their change? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HHH-7012?page=com.atlassian.jira.plug... ] Matthew commented on HHH-7012: ------------------------------ I tested the latest Tomcat 7 trunk (7.0.26-dev) and I confirm that it now works with stock Hibernate, eliminating the need for workarounds. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HHH-7012?page=com.atlassian.jira.plug... ] Adam Buckley commented on HHH-7012: ----------------------------------- The persistence.xml fix ([comment 45915|/browse/HHH-7012?focusedCommentId=45915&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-45915]) is also confirmed to work with Tomcat 6.0.26 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira