tomee+ 1.5.1 : datasource creation failed with an empty UserName

2013-01-03 Thread Simon Renard
Hello, I've deployed a web application that uses a local derby database that does not have any authentication necessary. Since Tomee+ is defaulting the UserName to sa I registered the datasource like shown bellow. This used to work in 1.5.0 but is now failing in 1.5.1. Please see stack bellow.

Re: tomee+ 1.5.1 : datasource creation failed with an empty UserName

2013-01-03 Thread Howard W. Smith, Jr.
On Thu, Jan 3, 2013 at 9:08 AM, Simon Renard simon.ren...@3ds.com wrote: I've deployed a web application that uses a local derby database that does not have any authentication necessary. Am I missing something or is it a bug in 1.5.1 ? I've also tried to set UserName to '' or but it results

Re: tomee+ 1.5.1 : datasource creation failed with an empty UserName

2013-01-03 Thread Romain Manni-Bucau
Hi, that's a bug of 1.5.1 - https://issues.apache.org/jira/browse/TOMEE-697 it only affects tomcat-jdbc connection pooling (not commons-dbcp) Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github:

Re: tomee+ 1.5.1 : datasource creation failed with an empty UserName

2013-01-03 Thread Simon Renard
Note that it's working when using the Apache Commons DBCP by using DataSourceCreator dbcp -- View this message in context: http://openejb.979440.n4.nabble.com/tomee-1-5-1-datasource-creation-failed-with-an-empty-UserName-tp4660030p4660034.html Sent from the OpenEJB User mailing list archive

Re: tomee+ 1.5.1 : datasource creation failed with an empty UserName

2013-01-03 Thread Simon Renard
Ok thanks. BTW what are the consequences of using commons-dbcp rather that tomcat-jdbc ? -- View this message in context: http://openejb.979440.n4.nabble.com/tomee-1-5-1-datasource-creation-failed-with-an-empty-UserName-tp4660030p4660038.html Sent from the OpenEJB User mailing list archive

Re: How to package an EJB3.1 WebService in an EAR

2013-01-03 Thread ymaraner
Are these issues also going to be fixed in an update to 1.5.1 or just 1.5.2? Also, is there a JIRA or two associated with this fix? Thanks again - - Tim -- View this message in context:

Re: EAR+CODI doesnt work

2013-01-03 Thread Romain Manni-Bucau
Can you update your sample? Le 3 janv. 2013 17:51, José Luis Cetina maxtorz...@gmail.com a écrit : OK, now i can use CODI stuff but i have a problem with one of them. CODI have a method for inject beans, i use this method in converters and classes where i can inject using @EJB or @Inject.

Re: JDBC connection pool memory leak

2013-01-03 Thread Howard W. Smith, Jr.
Very interesting info here, thanks for sharing. I have been using TomEE since 1.5.1-SNAPSHOT and now 1.5.2-SNAPSHOT. Also, I'm using Apache Derby 10.9.1.0 and Eclipse 2.3.2, and JDBC configured in tomee.xml. Can you share your JDBC config from your tomee.xml and/or context.xml? Apache Derby is

Fatal error configuring enricher

2013-01-03 Thread Sally MacFarlane
I'm using TomEE 1.5.1 and attempted to configure a class loader enricher according to http://rmannibucau.wordpress.com/2012/09/23/add-the-same-jar-to-all-your-war-without-including-them-thanks-to-tomee/ Have reproduced the below error on server startup with no config changes to TomEE other

Re: EAR+CODI doesnt work

2013-01-03 Thread José Luis Cetina
Could you tested? El ene 3, 2013 11:39 AM, José Luis Cetina maxtorz...@gmail.com escribió: Its updated now. 2013/1/3 Romain Manni-Bucau rmannibu...@gmail.com Can you update your sample? Le 3 janv. 2013 17:51, José Luis Cetina maxtorz...@gmail.com a écrit : OK, now i can use CODI

Re: Fatal error configuring enricher

2013-01-03 Thread Romain Manni-Bucau
Hi, Just updated the article Now the enricher moved under enricher package because we have another one (thats the risk to write on trunk feature ;) Le 4 janv. 2013 02:48, Sally MacFarlane sally.macfarl...@usq.edu.au a écrit : I’m using TomEE 1.5.1 and attempted to configure a class loader