No worries James, thanks for the quick turnaround!
On Thu, Jul 26, 2012 at 1:12 PM, James Page <email address hidden> wrote:
> John - thanks for your help on the test case for this SRU - very much
> appreciated.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1012794
>
> Title:
> [SRU] DataSource JNDI lookup with javax.naming.Name failed
>
> Status in “tomcat7” package in Ubuntu:
> Fix Released
> Status in “tomcat7” source package in Precise:
> Fix Released
>
> Bug description:
> [Impact]
> Users of tomcat7 are unable to deploy applications which use Name instead of String to complete JNDI lookups. This includes applications which make use of the most recent version of the popular hibernate ORM framework.
>
> [Test Case]
> sudo apt-get install tomcat7 libhsqldb-java
> sudo ln -s /usr/share/hsqldb.jar /usr/share/tomcat7/lib/hsqldb.jar
> sudo wget "https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1012794/+attachment/3221552/+files/ubuntu-test.war" -O /var/lib/tomcat7/webapps/ubuntu-test.war
> sudo service tomcat7 restart
>
> goto : http://localhost:8080/ubuntu-test
> >> Big stack trace including "javax.naming.NamingException: This context must be accessed through a java: URL"
>
> when fixed:
>
> "Message Test
>
> Hello, world!
> It's Alive!!!"
>
>
> [Regression Potential]
> Minimal - the change is isolated to JNDI lookups by Name and is in later versions of tomcat7.
>
> >> Original Bug Report <<
> I realize that Tomcat was just upgraded to 7.0.26, but there are a few fixes in Tomcat 7.0.27, specifically issue 52830 (https://issues.apache.org/bugzilla/show_bug.cgi?id=52830) which causes a big problem for people, like me, who are trying to use the Tomcat connection pool with Hibernate 4.x, which fails without this fix.
>
> Currently I updated my deployment by hand, but I would much rather
> have a proper package. I can't find a PPA, and my skill set is nil in
> terms of the ability to create my own PPA for this. Many thanks!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1012794/+subscriptions
No worries James, thanks for the quick turnaround!
On Thu, Jul 26, 2012 at 1:12 PM, James Page <email address hidden> wrote: /bugs.launchpad .net/bugs/ 1012794 hsqldb. jar /usr/share/ tomcat7/ lib/hsqldb. jar /bugs.launchpad .net/ubuntu/ +source/ tomcat7/ +bug/1012794/ +attachment/ 3221552/ +files/ ubuntu- test.war" -O /var/lib/ tomcat7/ webapps/ ubuntu- test.war localhost: 8080/ubuntu- test naming. NamingException : This context must be accessed through a java: URL" /issues. apache. org/bugzilla/ show_bug. cgi?id= 52830) which causes a big problem for people, like me, who are trying to use the Tomcat connection pool with Hibernate 4.x, which fails without this fix. /bugs.launchpad .net/ubuntu/ +source/ tomcat7/ +bug/1012794/ +subscriptions
> John - thanks for your help on the test case for this SRU - very much
> appreciated.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> [SRU] DataSource JNDI lookup with javax.naming.Name failed
>
> Status in “tomcat7” package in Ubuntu:
> Fix Released
> Status in “tomcat7” source package in Precise:
> Fix Released
>
> Bug description:
> [Impact]
> Users of tomcat7 are unable to deploy applications which use Name instead of String to complete JNDI lookups. This includes applications which make use of the most recent version of the popular hibernate ORM framework.
>
> [Test Case]
> sudo apt-get install tomcat7 libhsqldb-java
> sudo ln -s /usr/share/
> sudo wget "https:/
> sudo service tomcat7 restart
>
> goto : http://
> >> Big stack trace including "javax.
>
> when fixed:
>
> "Message Test
>
> Hello, world!
> It's Alive!!!"
>
>
> [Regression Potential]
> Minimal - the change is isolated to JNDI lookups by Name and is in later versions of tomcat7.
>
> >> Original Bug Report <<
> I realize that Tomcat was just upgraded to 7.0.26, but there are a few fixes in Tomcat 7.0.27, specifically issue 52830 (https:/
>
> Currently I updated my deployment by hand, but I would much rather
> have a proper package. I can't find a PPA, and my skill set is nil in
> terms of the ability to create my own PPA for this. Many thanks!
>
> To manage notifications about this bug go to:
> https:/