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" a
écrit :
> I’m using TomEE 1.5.1 and attempted to configure a class loader enricher
> according to
> htt
Could you tested?
El ene 3, 2013 11:39 AM, "José Luis Cetina" escribió:
> Its updated now.
>
>
>
>
> 2013/1/3 Romain Manni-Bucau
>
>> Can you update your sample?
>> Le 3 janv. 2013 17:51, "José Luis Cetina" a écrit
>> :
>>
>> > OK, now i can use CODI stuff but i have a problem with one of them.
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 than
Sorry for not be specific. I have the same problem, Duplicate id when try
to deploy
El ene 3, 2013 4:46 PM, "David Blevins" escribió:
>
> On Jan 3, 2013, at 8:34 AM, José Luis Cetina wrote:
>
> > I tried to use your recommended option (# 1) and im still having
> deployment
> > id issues.
> >
>
>
On Jan 3, 2013, at 8:34 AM, José Luis Cetina wrote:
> I tried to use your recommended option (# 1) and im still having deployment
> id issues.
>
If you have any details on what doesn't work, that'd be great.
-David
> 2012/12/29 David Blevins
>
>>
>> On Dec 28, 2012, at 10:54 AM, José Lui
I have tried using an EAR file and I think it works but have come across
other issues that i'll try to resolve with deploying a singleton in a war
file contained in an EAR.
Even if the ear option does work, i'd still much prefer to be able to deploy
the resource adapter in the war file because tha
Hi,
did you try to reproduce it with tomcat-jdbc (in a simple test without
tomee or any other framework)?
i wonder if it is linked to tomee or tomcat-jdbc directly (or mysql
since derby seems fine)
any more info or even a test reproducing the issue (in a reasonnable
time) would be great.
Romain
Only the sessionscoped beans are replicated through tomcat session...other
scoped are not (depend on the impl which probably doesnt use the session to
store instances)
Le 3 janv. 2013 19:49, a écrit :
> Hi,
>
> I have just uploaded test project reproducing the problem:
> https://github.com/eiskon
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 w
Hi people,
I get memory leaks from the built-in TomEE JDBC connection pool,
using the default container-managed persistence and transactions.
I have some code in a Singleton EJB that does, essentially, this:
@PersistenceUnit(unitName = "MyApp")
EntityManagerFactory emf;
@Schedule(se
Hi,
I have just uploaded test project reproducing the problem:
https://github.com/eiskonzept/tomee/
I have not reproduced exception, but WindowScoped beans are not
replicated(without exception)
To reproduce the problem:
1. Start two tomee instances:
mvn clean package tomee:start -P
Its updated now.
2013/1/3 Romain Manni-Bucau
> Can you update your sample?
> Le 3 janv. 2013 17:51, "José Luis Cetina" 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
> > clas
Can you update your sample?
Le 3 janv. 2013 17:51, "José Luis Cetina" 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.
>
> When i use thi
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.
When i use this:
facade =
BeanManagerProvider.getInstance().getContextualReference(MailingsEnviadosFacade
I tried to use your recommended option (# 1) and im still having deployment
id issues.
Im using apache-tomee-1.5.2-20130103.040941-21-webprofile
2012/12/29 David Blevins
>
> On Dec 28, 2012, at 10:54 AM, José Luis Cetina
> wrote:
>
> > Well, this could unpack my ear file (which cotains ejb m
there is a jira: main one is TOMEE-668
and this commit (just tracked on TOMEE-699):
http://mail-archives.apache.org/mod_mbox/openejb-commits/201212.mbox/%3c20121220162549.78b792388...@eris.apache.org%3E
since the 1.5.2 is the update of the 1.5.1 it will be in 1.5.2
Romain Manni-Bucau
Twitter: @r
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:
http://openejb.979440.n4.nabble.com/How-to-package-an-EJB3-1-WebService-in-an-EAR-tp4659793p4660042.htm
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 a
Hello Romain,
Thanks for the answer and the fix.
Would there be any other bypass than using dbcp ?
Is there a ETA for official release of 1.5.2 ?
--
View this message in context:
http://openejb.979440.n4.nabble.com/tomee-1-5-1-datasource-creation-failed-with-an-empty-UserName-tp4660030p46
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
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: https://github.c
On Thu, Jan 3, 2013 at 9:08 AM, Simon Renard 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 in '' and ""
hmm
still the same issue
btw i tested on a project from my own using @WebXXX in eclipse and it seems fine
if you still encouter github issues maybe create another repo to push
the project
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linked
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
24 matches
Mail list logo
