Re: Does tomee plus support ValidatingManagedConnectionFactory?
I dont know this one but. You can still pre init it in a singleton startup but you are right that's weird. Le 11 janv. 2013 02:51, "Anthony Fryer" a écrit : > Is there a reason for that design? If connection creation is expensive, > then > you're paying the cost and have to wait when you get the first connection, > with the client blocking until the connection is created. > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Does-tomee-plus-support-ValidatingManagedConnectionFactory-tp4660187p4660233.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
Re: Secure EJBs testing with Arquillian
typically you should look a bit upper in the logs to find the real reason,
it is logged in warning or severe level.
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/1/10 Luca Merolla
> Yes I have added users.properties and groups.properties and now the
> authorization is working.
>
> I have still problems with "sub-dependencies". For example, if I create a
> CountryBeanTest with arquillian and CountryBean looks like that:
>
> public class CountryBean implements CountryBeanLocal {
> @EJB
> private CountryEAOLocal countryEAO;
>
> public List getAllCountries() {
> return countryEAO.getAllCountries();
> }
> }
>
> Arquillian test inject countryBean, but I get NPE
> on countryEAO.getAllCountries() because the CountryEAOLocal is not
> injected.
>
> In the ShrinkWrap of my CountryBeanTest I
> have .addClasses(CountryBean.class, CountryBeanLocal.class), but if I
> add .addClasses(CountryBean.class,
> CountryBeanLocal.class, CountryEAO.class, CountryEAOLocal.class) I get:
>
> SEVERE: Unable to deploy collapsed ear in war
>
> StandardEngine[Tomcat].StandardHost[localhost].StandardContext[/application2]
> org.apache.openejb.config.ValidationFailedException: Module failed
> validation. AppModule(name=application2)
>
>
>
> On Thu, Jan 10, 2013 at 1:55 AM, Romain Manni-Bucau
> wrote:
>
> > yep, did you set the jaas system property?
> >
> > *Romain Manni-Bucau*
> > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > *Blog: **http://rmannibucau.wordpress.com/*<
> > http://rmannibucau.wordpress.com/>
> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > *Github: https://github.com/rmannibucau*
> >
> >
> >
> > 2013/1/10 Luca Merolla
> >
> > > I have added INITIAL_CONTEXT_FACTORY and now I get:
> > >
> > > javax.security.auth.login.FailedLoginException: User does not exist
> > >
> > > while before I was getting : javax.ejb.EJBAccessException: Unauthorized
> > > Access by Principal Denied
> > >
> > > I guess now I need to configure some sort of users.properties file with
> > > users and password.
> > >
> > >
> > > On Thu, Jan 10, 2013 at 1:12 AM, Romain Manni-Bucau
> > > wrote:
> > >
> > > > it basically does the same
> > > >
> > > > maybe you'll need to specify Context.INITAL_CONTEXT_FACTORY (normally
> > no
> > > > but depend how you run the test)
> > > >
> > > > *Romain Manni-Bucau*
> > > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > > > *Blog: **http://rmannibucau.wordpress.com/*<
> > > > http://rmannibucau.wordpress.com/>
> > > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > > > *Github: https://github.com/rmannibucau*
> > > >
> > > >
> > > >
> > > > 2013/1/10 Luca Merolla
> > > >
> > > > > I was actually trying something similar already, basically the
> > previous
> > > > > "login" method was the following
> > > > >
> > > > > Properties properties = new Properties();
> > > > > properties.put(Context.SECURITY_PRINCIPAL, username);
> > > > > properties.put(Context.SECURITY_CREDENTIALS, password);
> > > > >
> > > > > final Context context = new InitialContext(properties);
> > > > >
> > > > > but the access was not authorized, then I found the previous
> example
> > > and
> > > > I
> > > > > thought there was a need of having this ArquillianContext class
> > > > >
> > > > > On Thu, Jan 10, 2013 at 12:44 AM, Romain Manni-Bucau
> > > > > wrote:
> > > > >
> > > > > > new InitialContext
> > > > >
> > > >
> > >
> > >
> > >
> >
>
Re: TomEE 1.5.1-SNAPSHOT: strange JPA behavior
Thanks for the report! Here the fix: https://issues.apache.org/jira/browse/TOMEE-720 Using commons dbcp instead of tomcat jdbc you shouldn't get this behavior *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/10 diuis > Hi Romain, > Hi all, > finally I wrote a little sample to reproduce the strange JPA behavior. > > Please, download it from github: > > git clone https://github.com/diuis/test-jpa-tx.git > > change directory: > > cd test-jpa-tx/ > > and run TomEE 1.5.1: > > mvn package tomee:run > > I wrote a simple REST service; you could open these urls: > > http://localhost:8080/test-jpa-tx-0.0.1-SNAPSHOT/start/tx1 > The 'tx1 service' open a connection to the first persistence unit (PUBLIC > is > the CATALOG and sa1 the username). > > http://localhost:8080/test-jpa-tx-0.0.1-SNAPSHOT/start/tx2 > The 'tx2 service' open a connection to the second persistence unit (PUBLIC > is the CATALOG and sa2 the username). > > http://localhost:8080/test-jpa-tx-0.0.1-SNAPSHOT/start/tx > The 'tx service' uses both the persistence units, but first, in the same > ejb > transaction, and after in two different transactions. > When the transaction is the same, I guess that the second entity manager > takes the already opened db connection, instead of the connection of the > datasource configured in the persistence.xml. > > I have not used the XA jdbc driver in this test, but I used it in my real > application, where I have two different databases (MySQL and H2) and the > result is the same. > > Thank for the support, > Demis Gallisto > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/TomEE-1-5-1-SNAPSHOT-strange-JPA-behavior-tp4658500p4660225.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
Re: Secure EJBs testing with Arquillian
yep, did you set the jaas system property? *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/10 Luca Merolla > I have added INITIAL_CONTEXT_FACTORY and now I get: > > javax.security.auth.login.FailedLoginException: User does not exist > > while before I was getting : javax.ejb.EJBAccessException: Unauthorized > Access by Principal Denied > > I guess now I need to configure some sort of users.properties file with > users and password. > > > On Thu, Jan 10, 2013 at 1:12 AM, Romain Manni-Bucau > wrote: > > > it basically does the same > > > > maybe you'll need to specify Context.INITAL_CONTEXT_FACTORY (normally no > > but depend how you run the test) > > > > *Romain Manni-Bucau* > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > *Blog: **http://rmannibucau.wordpress.com/*< > > http://rmannibucau.wordpress.com/> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > *Github: https://github.com/rmannibucau* > > > > > > > > 2013/1/10 Luca Merolla > > > > > I was actually trying something similar already, basically the previous > > > "login" method was the following > > > > > > Properties properties = new Properties(); > > > properties.put(Context.SECURITY_PRINCIPAL, username); > > > properties.put(Context.SECURITY_CREDENTIALS, password); > > > > > > final Context context = new InitialContext(properties); > > > > > > but the access was not authorized, then I found the previous example > and > > I > > > thought there was a need of having this ArquillianContext class > > > > > > On Thu, Jan 10, 2013 at 12:44 AM, Romain Manni-Bucau > > > wrote: > > > > > > > new InitialContext > > > > > > > > > -- > *Luca Merolla* > Management, Business & Technology Consultant > > > <http://maps.google.com/maps?q=&hl=en> *Mobile:* +393774569974 > *Email:* l...@merollaconsulting.com > *www.linkedin.com/in/lucamerolla* > *Website <http://www.merollaconsulting.com>* > > > Merolla Consulting Limited >
Re: Secure EJBs testing with Arquillian
it basically does the same maybe you'll need to specify Context.INITAL_CONTEXT_FACTORY (normally no but depend how you run the test) *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/10 Luca Merolla > I was actually trying something similar already, basically the previous > "login" method was the following > > Properties properties = new Properties(); > properties.put(Context.SECURITY_PRINCIPAL, username); > properties.put(Context.SECURITY_CREDENTIALS, password); > > final Context context = new InitialContext(properties); > > but the access was not authorized, then I found the previous example and I > thought there was a need of having this ArquillianContext class > > On Thu, Jan 10, 2013 at 12:44 AM, Romain Manni-Bucau > wrote: > > > new InitialContext >
Re: Secure EJBs testing with Arquillian
why not creating an initial context?
new InitialContext instead of arquillianContext?
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/1/10 Luca Merolla
> I have some EJBs which are secured with @RolesAllowed("admin")
>
> And I'm trying to perform an authentication in the unit test otherwise it
> fails because I'm not allowed.
> Basically the method in the example is using this method:
>
> private Context login(final String username, final String password) {
> // Precondition checks
> assert username != null : "username must be supplied";
> assert password != null : "password must be supplied";
>
> // Log in and create a context
> final Map namingContextProps = new HashMap Object>();
> namingContextProps.put(Context.SECURITY_PRINCIPAL, username);
> namingContextProps.put(Context.SECURITY_CREDENTIALS, password);
> final Context context = arquillianContext.get(Context.class,
> namingContextProps);
>
> // Return
> return context;
> }
>
>
> On Thu, Jan 10, 2013 at 12:35 AM, Romain Manni-Bucau
> wrote:
>
> > sorry i didn't get your question
> >
> > maybe cause i don't know ArquillianContext but it doesn't look an
> upstream
> > change.
> >
> > what's the really issue (why you need it)?
> >
> > *Romain Manni-Bucau*
> > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > *Blog: **http://rmannibucau.wordpress.com/*<
> > http://rmannibucau.wordpress.com/>
> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > *Github: https://github.com/rmannibucau*
> >
> >
> >
> > 2013/1/10 Luca Merolla
> >
> > > Hi everyone,
> > >
> > > I'm trying to get Arquillian up and running with some secured EJBs.
> > >
> > > I have followed this example which is using the class ArquillianContext
> > >
> > >
> > >
> >
> https://github.com/ALRubinger/oreilly-ejb-6thedition-book-examples/blob/master/ch15-secureschool/src/test/java/org/jboss/ejb3/examples/ch15/secureschool/SecureSchoolIntegrationTest.java
> > >
> > > these are my maven test dependencies
> > >
> > >
> > >
> > > junit
> > > junit
> > > ${junit.version}
> > > test
> > >
> > >
> > > org.apache.openejb
> > > tomee-embedded
> > > ${tomee.version}
> > > test
> > >
> > >
> > > org.apache.openejb
> > > arquillian-tomee-embedded
> > > ${tomee.version}
> > > test
> > >
> > >
> > > org.jboss.arquillian.junit
> > > arquillian-junit-container
> > >
> > >
> > > org.jboss.arquillian.protocol
> > > arquillian-protocol-servlet
> > > test
> > >
> > >
> > > org.jboss.shrinkwrap.resolver
> > > shrinkwrap-resolver-depchain
> > > 2.0.0-alpha-6
> > > pom
> > >
> > >
> > > however, I think ArquillianContext is in this one
> > >
> > >
> > > org.jboss.arquillian.container
> > > arquillian-openejb-embedded-3.1
> > > 1.0.0.Alpha5
> > > test
> > >
> > >
> > > but when I add arquillian-openejb-embedded-3.1 I get the following
> error
> > > when I'm running the junit test:
> > >
> > > Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: Api
> > type
> > > [org.jboss.arquillian.prototyping.context.api.ArquillianContext] is not
> > > found with the qualifiers
> > > Qualifiers: [@javax.enterprise.inject.Default()]
> > >
> > > I'm using TomEE 1.5.1. Is there a different approach to solve this
> > problem,
> > > or it's my configuration that is wrong?
> > >
> > > Thanks in advance,
> > > LM
> > >
> >
>
Re: Secure EJBs testing with Arquillian
sorry i didn't get your question
maybe cause i don't know ArquillianContext but it doesn't look an upstream
change.
what's the really issue (why you need it)?
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/1/10 Luca Merolla
> Hi everyone,
>
> I'm trying to get Arquillian up and running with some secured EJBs.
>
> I have followed this example which is using the class ArquillianContext
>
>
> https://github.com/ALRubinger/oreilly-ejb-6thedition-book-examples/blob/master/ch15-secureschool/src/test/java/org/jboss/ejb3/examples/ch15/secureschool/SecureSchoolIntegrationTest.java
>
> these are my maven test dependencies
>
>
>
> junit
> junit
> ${junit.version}
> test
>
>
> org.apache.openejb
> tomee-embedded
> ${tomee.version}
> test
>
>
> org.apache.openejb
> arquillian-tomee-embedded
> ${tomee.version}
> test
>
>
> org.jboss.arquillian.junit
> arquillian-junit-container
>
>
> org.jboss.arquillian.protocol
> arquillian-protocol-servlet
> test
>
>
> org.jboss.shrinkwrap.resolver
> shrinkwrap-resolver-depchain
> 2.0.0-alpha-6
> pom
>
>
> however, I think ArquillianContext is in this one
>
>
> org.jboss.arquillian.container
> arquillian-openejb-embedded-3.1
> 1.0.0.Alpha5
> test
>
>
> but when I add arquillian-openejb-embedded-3.1 I get the following error
> when I'm running the junit test:
>
> Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: Api type
> [org.jboss.arquillian.prototyping.context.api.ArquillianContext] is not
> found with the qualifiers
> Qualifiers: [@javax.enterprise.inject.Default()]
>
> I'm using TomEE 1.5.1. Is there a different approach to solve this problem,
> or it's my configuration that is wrong?
>
> Thanks in advance,
> LM
>
Re: Configuring Apache CXF in TomEE
ok so first put it in WEB-INF, it is looked up here for sure then mea culpa, i said but it is *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/9 > Just tried to put files with no effect in: > /META-INF > /WEB-INF > /WEB-INF/classes/META-INF > > > > -Ursprüngliche Nachricht- > Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] > Gesendet: Mittwoch, 9. Januar 2013 17:16 > An: users@openejb.apache.org > Betreff: Re: Configuring Apache CXF in TomEE > > try to put files in WEB-INF > > *Romain Manni-Bucau* > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > *Blog: **http://rmannibucau.wordpress.com/*< > http://rmannibucau.wordpress.com/> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > *Github: https://github.com/rmannibucau* > > > > 2013/1/9 > > > Just tried proposed configuration: > > https://github.com/eiskonzept/tomee-jaxrs/blob/master/src/main/resourc > > es/META-INF/ Still not working. I have checked in debugger that > > JsonService.setDropRootElement(true) is called, but then another > > instance of JsonService is used for marshaling. pojo-deployment tag in > > openejb-jar.xml seems not working correctly. > > > > > > My openejb-jar.xml: > > http://www.openejb.org/openejb-jar/1.1";> > > > > > > cxf.jaxrs.providers = json > > > > > > > > > > My resources.xml: > > > > > class-name="org.apache.cxf.jaxrs.provider.json.JSONProvider"> > > dropRootElement = true > > supportUnwrapped = true > > > > > > > > -Ursprüngliche Nachricht- > > Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] > > Gesendet: Mittwoch, 9. Januar 2013 16:11 > > An: users@openejb.apache.org > > Betreff: Re: Configuring Apache CXF in TomEE > > > > jaxrs-application is for tomee >= 1.5.2 (to be released) > > > > you can do: > > > > > > > > > > cxf.jaxrs.providers = json > > > > > > > > > > > class-name="org.apache.cxf.jaxrs.provider.json.JSONProvider"> > > dropRootElement = true > > # etc... > > > > > > supportUnwrapped=true,dropRootElement=true > > > > > > 2013/1/9 > > > > > > > > > > > cxf.jaxrs.properties = supportUnwrapped=true,dropRootElement=true > > > > > > > > > > > > > > > > > *Romain Manni-Bucau* > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > *Blog: **http://rmannibucau.wordpress.com/*< > > http://rmannibucau.wordpress.com/> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > *Github: https://github.com/rmannibucau* > > >
Re: Configuring Apache CXF in TomEE
try to put files in WEB-INF *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/9 > Just tried proposed configuration: > https://github.com/eiskonzept/tomee-jaxrs/blob/master/src/main/resources/META-INF/ > Still not working. I have checked in debugger that > JsonService.setDropRootElement(true) is called, but then another instance > of JsonService is used for marshaling. pojo-deployment tag in > openejb-jar.xml seems not working correctly. > > > My openejb-jar.xml: > http://www.openejb.org/openejb-jar/1.1";> > > > cxf.jaxrs.providers = json > > > > > My resources.xml: > > class-name="org.apache.cxf.jaxrs.provider.json.JSONProvider"> > dropRootElement = true > supportUnwrapped = true > > > > -Ursprüngliche Nachricht- > Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] > Gesendet: Mittwoch, 9. Januar 2013 16:11 > An: users@openejb.apache.org > Betreff: Re: Configuring Apache CXF in TomEE > > jaxrs-application is for tomee >= 1.5.2 (to be released) > > you can do: > > > > > cxf.jaxrs.providers = json > > > > > class-name="org.apache.cxf.jaxrs.provider.json.JSONProvider"> > dropRootElement = true > # etc... > > > supportUnwrapped=true,dropRootElement=true > > > 2013/1/9 > > > > > > > cxf.jaxrs.properties = supportUnwrapped=true,dropRootElement=true > > > > > > > > > > *Romain Manni-Bucau* > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > *Blog: **http://rmannibucau.wordpress.com/*< > http://rmannibucau.wordpress.com/> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > *Github: https://github.com/rmannibucau* >
Re: TomEE maven plugin reload app
right and define a synchro block but thing you want to synch. Note: for jar it was a bit complicated so i decided to allow source and target being files this way you update the file (not perfect but to start it is enough) *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/9 José Luis Cetina > Yeah im using, 1.5.2-Snapshot for tomeeVersion and 1.0.1 for plugin, the > plugin still recognized my changes (it prints Updating) but the changes are > not reflecting in the application, i need to try your new commit for this?? > > > 2013/1/8 Romain Manni-Bucau > > > sure > > > > before it was the default (1.5.1), now no more so the plugin was updated > > but you mixed both versions right? > > > > *Romain Manni-Bucau* > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > *Blog: **http://rmannibucau.wordpress.com/*< > > http://rmannibucau.wordpress.com/> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > *Github: https://github.com/rmannibucau* > > > > > > > > 2013/1/8 José Luis Cetina > > > > > Yes i have, i updated now, i will test right now. > > > > > > Before try the new update, I just noticed something, when i dont add > the > > > src/main/tomee/conf to my project my ear and run tomee:run tomee runs > ok, > > > my ear file drops in apps folder but never get unwrapped, then if i add > > the > > > mentioned folder with my configurations files my ear is unwrapped, > could > > be > > > because in my tomee.xml i have: Deployments dir="apps/" > > > > > > > > > 2013/1/8 Romain Manni-Bucau > > > > > > > https://issues.apache.org/jira/browse/TOMEE-715 > > > > > > > > i know you have the sources on your computer ( ;) ) so you can now > > > update > > > > (from svn) + compile maven/tomee-maven-plugin and use 1.5.2-SNAPSHOT > > > > version > > > > > > > > *Romain Manni-Bucau* > > > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > > > *Blog: **http://rmannibucau.wordpress.com/*< > > > > http://rmannibucau.wordpress.com/> > > > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > > > *Github: https://github.com/rmannibucau* > > > > > > > > > > > > > > > > 2013/1/8 Romain Manni-Bucau > > > > > > > > > oh ok, > > > > > > > > > > basically you have to: > > > > > 1) do the change (== compile if you observe target/classes) > > > > > 2) wait the max of all update intervals (for now a single one but > > soon > > > > > multiples) to let the app be reloaded > > > > > > > > > > *Romain Manni-Bucau* > > > > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > > > > *Blog: **http://rmannibucau.wordpress.com/*< > > > > http://rmannibucau.wordpress.com/> > > > > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > > > > *Github: https://github.com/rmannibucau* > > > > > > > > > > > > > > > > > > > > 2013/1/8 José Luis Cetina > > > > > > > > > >> Ok, for now im setting > resourcesDir,targetResourcesDir,binariesDir > > > and > > > > >> targetBinariesDir to fixed values for onlye one module. I like the > > > idea > > > > >> where i cand add each module manually. > > > > >> > > > > >> But i still asking me, do i have to do something extra before do > > some > > > > >> change and wait 5 seconds for see my changes do i have to run > > mvn > > > > >> compile? or something? > > > > >> > > > > >> 2013/1/8 Romain Manni-Bucau > > > > >> > > > > >> > sychronization > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > --- > > > *SCJA. José Luis Cetina* > > > --- > > > > > > > > > -- > --- > *SCJA. José Luis Cetina* > --- >
Re: Configuring Apache CXF in TomEE
jaxrs-application is for tomee >= 1.5.2 (to be released) you can do: cxf.jaxrs.providers = json dropRootElement = true # etc... supportUnwrapped=true,dropRootElement=true 2013/1/9 > > > cxf.jaxrs.properties = supportUnwrapped=true,dropRootElement=true > > > *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau*
Re: TomEE maven plugin
give a try on the snapshot (either build it from sources or wait tomorrow
for a new deployment) it should be fixed
another way to do so is to skip current project (a tag in the plugin) then
define the war as a context in a provided server.xml. In this
definition set reloadable to true.
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/1/9 Schmitt, Markus
> Hello,
>
> like discussed with "rmannibucau" I'll send again my comment of page
> http://rmannibucau.wordpress.com/2012/10/16/tomee-maven-plugin-reload-your-app-automatically/
>
>
>org.apache.openejb.maven
>tomee-maven-plugin
>1.0.1
>
>
>
>
> .class
>.tml
>
>
> true
>
> 1.5.1
> plus
>
> -Djava.naming.factory.initial=org.apache.openejb.client.LocalInitialContextFactory
> -Djava.naming.factory.url.pkgs=org.apache.openejb.core.ivm.naming
> ${project.basedir}/conf
>
>
>
> mysql:mysql-connector-java:5.1.21
>
>
>
>
> Unfortunately I am not allowed to send any project resources...
> Here is my question:
>
> After updating a class the output says: reloading...
> But the change of the class is not deployed.
> Maybe you can give me a hint ?
>
> Thanks and best regards,
> Markus
>
>
>
>
> Geschäftsführer: Wolf Kunisch
> Aufsichtsratsvorsitzender: Christophe Duquenne
> Sitz der Gesellschaft: Frankfurt/Main
> Handelsregister: Frankfurt/Main HRB 40 417
>
> * * * * * * * * L E G A LD I S C L A I M E R * * * * * * * *
> This e-mail and the documents attached are confidential and intended
> solely for the addressee; it may also be privileged. If you receive this
> e-mail by error, please notify the sender immediately and destroy it. As
> its integrity cannot be secured on the internet, the Atos group liability
> cannot be triggered for the message content. Although the sender endeavors
> to maintain a computer virus-free network, the sender does not warrant that
> this transmission is virus-free and shall not be liable for any damages
> resulting from any virus transmitted.
> * * * * * * * * L E G A LD I S C L A I M E R * * * * * * * *
>
Re: How to tell openejb to use only supplied orm over generated for CMP2.1
yeah open a jira and you can attach a patch to it (granting it to Apache) then we'll apply it after a review bugtracker is issues.apache.org/jira/browse/TOMEE *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/9 BKumar > Is it possible to get a fix for this soon. Do I need to create JIRA for > this? Actually I am new to this forum. > > Thanks, > Bibhuti > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/How-to-tell-openejb-to-use-only-supplied-orm-over-generated-for-CMP2-1-tp4660196p4660201.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
Re: Does tomee plus support ValidatingManagedConnectionFactory?
first you can't use tomee.xml for war provided resources (tomee.xml resources are created at startup before any deployment so the classes are not here at all). You can use resources.xml (in WEB-INF) - same syntax then the type (or more exactly for you class-name attribute) is the managedconnectionfactory one and not Resource (which is not the java type you want) That said it should be deployed by default normally and you have the name in the logs *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/9 Anthony Fryer > Yes i'll definately test it. > > I have a question around the configuration of the pooling parameters. Now > I'm deploying the ra in the war file, i was trying to use tomee.xml to > configure values like poolMinSize, poolMaxSize etc. > > I tried variations like this... > > > poolMinSize = 7 > poolMaxSize = 10 > > > But this always errors because the type is not supported. > > The only way i have succeeded in configuring the pool is by adding these > lines to the system.properties file... > > eis/sabre/91.poolMinSize = 2 > eis/sabre/91.poolMaxSize = 10 > > Is it possible to configure the pool in tomee.xml and if so, what value > should i use for the type attribute? > > > > > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Does-tomee-plus-support-ValidatingManagedConnectionFactory-tp4660187p4660198.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
Re: How do i deploy a ManagedConnectionFactory in a war file?
Thought to it too but then thought today rar were rar and not jar. Btw i didnt test but connector 1.6 allows to use annotations and we scan them so maybe you can use it directly Le 9 janv. 2013 03:52, "Anthony Fryer" a écrit : > Just thinking about the spec, i wonder if .rar files could be replaced with > just a .jar file with a META-INF/ra.xml. That would make sense to me. > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/How-do-i-deploy-a-ManagedConnectionFactory-in-a-war-file-tp4659993p4660185.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
Re: TomEE maven plugin reload app
sure before it was the default (1.5.1), now no more so the plugin was updated but you mixed both versions right? *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/8 José Luis Cetina > Yes i have, i updated now, i will test right now. > > Before try the new update, I just noticed something, when i dont add the > src/main/tomee/conf to my project my ear and run tomee:run tomee runs ok, > my ear file drops in apps folder but never get unwrapped, then if i add the > mentioned folder with my configurations files my ear is unwrapped, could be > because in my tomee.xml i have: Deployments dir="apps/" > > > 2013/1/8 Romain Manni-Bucau > > > https://issues.apache.org/jira/browse/TOMEE-715 > > > > i know you have the sources on your computer ( ;) ) so you can now > update > > (from svn) + compile maven/tomee-maven-plugin and use 1.5.2-SNAPSHOT > > version > > > > *Romain Manni-Bucau* > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > *Blog: **http://rmannibucau.wordpress.com/*< > > http://rmannibucau.wordpress.com/> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > *Github: https://github.com/rmannibucau* > > > > > > > > 2013/1/8 Romain Manni-Bucau > > > > > oh ok, > > > > > > basically you have to: > > > 1) do the change (== compile if you observe target/classes) > > > 2) wait the max of all update intervals (for now a single one but soon > > > multiples) to let the app be reloaded > > > > > > *Romain Manni-Bucau* > > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > > *Blog: **http://rmannibucau.wordpress.com/*< > > http://rmannibucau.wordpress.com/> > > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > > *Github: https://github.com/rmannibucau* > > > > > > > > > > > > 2013/1/8 José Luis Cetina > > > > > >> Ok, for now im setting resourcesDir,targetResourcesDir,binariesDir > and > > >> targetBinariesDir to fixed values for onlye one module. I like the > idea > > >> where i cand add each module manually. > > >> > > >> But i still asking me, do i have to do something extra before do some > > >> change and wait 5 seconds for see my changes do i have to run mvn > > >> compile? or something? > > >> > > >> 2013/1/8 Romain Manni-Bucau > > >> > > >> > sychronization > > >> > > > > > > > > > > > > -- > --- > *SCJA. José Luis Cetina* > --- >
Re: TomEE maven plugin reload app
https://issues.apache.org/jira/browse/TOMEE-715 i know you have the sources on your computer ( ;) ) so you can now update (from svn) + compile maven/tomee-maven-plugin and use 1.5.2-SNAPSHOT version *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/8 Romain Manni-Bucau > oh ok, > > basically you have to: > 1) do the change (== compile if you observe target/classes) > 2) wait the max of all update intervals (for now a single one but soon > multiples) to let the app be reloaded > > *Romain Manni-Bucau* > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > *Github: https://github.com/rmannibucau* > > > > 2013/1/8 José Luis Cetina > >> Ok, for now im setting resourcesDir,targetResourcesDir,binariesDir and >> targetBinariesDir to fixed values for onlye one module. I like the idea >> where i cand add each module manually. >> >> But i still asking me, do i have to do something extra before do some >> change and wait 5 seconds for see my changes do i have to run mvn >> compile? or something? >> >> 2013/1/8 Romain Manni-Bucau >> >> > sychronization >> > >
Re: TomEE maven plugin reload app
oh ok, basically you have to: 1) do the change (== compile if you observe target/classes) 2) wait the max of all update intervals (for now a single one but soon multiples) to let the app be reloaded *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/8 José Luis Cetina > Ok, for now im setting resourcesDir,targetResourcesDir,binariesDir and > targetBinariesDir to fixed values for onlye one module. I like the idea > where i cand add each module manually. > > But i still asking me, do i have to do something extra before do some > change and wait 5 seconds for see my changes do i have to run mvn > compile? or something? > > 2013/1/8 Romain Manni-Bucau > > > sychronization >
Re: TomEE maven plugin reload app
kind of i'll add a new block where you can put block inside. the main difference will be this once will not be configured by default (you have to define you modules manually for webapp it will be fine IMO, for jar i still wonder *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/8 José Luis Cetina > Ok, then i dont need to use reloadOnUpdate (or set to false) because im > using an ear. > > But i can see the update happend but is not reflecting when in the app when > i refresh the page, that's what you mean when you sayed "so only a good way > to update file is to find"??? > > > > > 2013/1/8 Romain Manni-Bucau > > > mea culpa just said a wrong thing > > > > it is implemented for ear too > > > > so only a good way to update file is to find > > > > *Romain Manni-Bucau* > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > *Blog: **http://rmannibucau.wordpress.com/*< > > http://rmannibucau.wordpress.com/> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > *Github: https://github.com/rmannibucau* > > > > > > > > 2013/1/8 Romain Manni-Bucau > > > > > let me explain a bit more: > > > > > > here the words are maybe wrong (think that's only clear for tomcat dev > ;) > > > > > > reload is a method on tomcat context (= webapp). It is just a shortcut > to > > > stop/start a webapp. In openejb (ear) we don't have it so we could > doing > > > stop/start but it is not mapped ATM. > > > > > > Once the config issue (how to define it) is fixed, i'll update the > plugin > > > > > > we can talk on irc if you want > > > > > > *Romain Manni-Bucau* > > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > > *Blog: **http://rmannibucau.wordpress.com/*< > > http://rmannibucau.wordpress.com/> > > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > > *Github: https://github.com/rmannibucau* > > > > > > > > > > > > 2013/1/8 José Luis Cetina > > > > > >> I dont understand, the plugin is for reload the app automatically, the > > >> plugin detect my changes and print [Updating]... > > >> > > >> If those changes are updating (replacing the old files for new files) > > why > > >> are not reflecting in the webapp when i press F5 (reload the page)??? > > >> > > >> The problem is the ear again?? > > >> > > >> Im confused. > > >> > > >> > > >> 2013/1/8 Romain Manni-Bucau > > >> > > >> > ATM > > >> > > >> > > >> > > >> > > >> -- > > >> --- > > >> *SCJA. José Luis Cetina* > > >> --- > > >> > > > > > > > > > > > > -- > --- > *SCJA. José Luis Cetina* > --- >
Re: TomEE maven plugin reload app
mea culpa just said a wrong thing it is implemented for ear too so only a good way to update file is to find *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/8 Romain Manni-Bucau > let me explain a bit more: > > here the words are maybe wrong (think that's only clear for tomcat dev ;) > > reload is a method on tomcat context (= webapp). It is just a shortcut to > stop/start a webapp. In openejb (ear) we don't have it so we could doing > stop/start but it is not mapped ATM. > > Once the config issue (how to define it) is fixed, i'll update the plugin > > we can talk on irc if you want > > *Romain Manni-Bucau* > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > *Github: https://github.com/rmannibucau* > > > > 2013/1/8 José Luis Cetina > >> I dont understand, the plugin is for reload the app automatically, the >> plugin detect my changes and print [Updating]... >> >> If those changes are updating (replacing the old files for new files) why >> are not reflecting in the webapp when i press F5 (reload the page)??? >> >> The problem is the ear again?? >> >> Im confused. >> >> >> 2013/1/8 Romain Manni-Bucau >> >> > ATM >> >> >> >> >> -- >> --- >> *SCJA. José Luis Cetina* >> --- >> > >
Re: TomEE maven plugin reload app
let me explain a bit more: here the words are maybe wrong (think that's only clear for tomcat dev ;) reload is a method on tomcat context (= webapp). It is just a shortcut to stop/start a webapp. In openejb (ear) we don't have it so we could doing stop/start but it is not mapped ATM. Once the config issue (how to define it) is fixed, i'll update the plugin we can talk on irc if you want *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/8 José Luis Cetina > I dont understand, the plugin is for reload the app automatically, the > plugin detect my changes and print [Updating]... > > If those changes are updating (replacing the old files for new files) why > are not reflecting in the webapp when i press F5 (reload the page)??? > > The problem is the ear again?? > > Im confused. > > > 2013/1/8 Romain Manni-Bucau > > > ATM > > > > > -- > --- > *SCJA. José Luis Cetina* > --- >
Re: TomEE maven plugin reload app
to be honest "reload" part of the tag was totally related to tomcat and not to openejb so the plugin needs to be updated open to idea here, i'm not really sure of the best solution ATM *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/8 José Luis Cetina > Hi Romain, i just set the resourcesDir,targetResourcesDir,binariesDir and > targetBinariesDir to fixed values that point to my webapplication in ear > and apps folder, my changes are detected but the app is not reloading. > > Im getting this when i do some change in my webapp (that is inside of my > ear) [Updating] /here/a/directory to /the/target/directory, but im not > getting the Reloading message (i look up to UpdatableTomEEMojo.java). > > I have set reloadOnUpdate to true. > > Do i have to do another step after doing some modifications? > > > > 2013/1/8 José Luis Cetina > > > mmm i have exactly that problem, i don't want to treat each application > > alone, because they depend of the same ejb modules and i will have > problems > > with duplicate id's for ejbs and so on. > > > > I will be appreciated if the plugin can be enhancement for "support" > ears. > > > > What do you think? > > > > > > -- > --- > *SCJA. José Luis Cetina* > --- >
Re: clean install of openejb 4.5.1 is not working
Hi,
I thin kit is a tracked issue
try to set in conf/system.properties the property openejb.system.apps=true
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/1/8 AlanHeath
> I did the following
> 1. download 4.5.1 version of openejb
> 2. Installed it onto a windows 7 C:\programs
> 3. In a command window cd C:\programs\apache-openejb-4.5.1\bin
> 4. openejb start
> Everything seems ok The logfile looks ok ejbd
> Jan 08, 2013 4:09:06 PM org.apache.openejb.server.SimpleServiceManager
> printRow
> INFO: ejbd 127.0.0.1 4201
> 5. Open another command window, cd C:\programs\apache-openejb-4.5.1\bin
> 6. In the second command window openejb properties
>Jan 08, 2013 4:09:42 PM org.apache.openejb.client.EventLogger log
>INFO: RemoteInitialContextCreated{providerUri=ejbd://localhost:4201}
>Jan 08, 2013 4:09:42 PM org.apache.openejb.client.EventLogger log
>INFO: ConnectionOpened{uri=ejbd://localhost:4201}
>Jan 08, 2013 4:09:42 PM org.apache.openejb.client.EventLogger log
>INFO: ServerAdded{server=ejbds://127.0.0.1:4203}
> ClusterMetaDataUpdated{provider
>=ejbd://localhost:4201, version=1357661341934, uris=2}
>Jan 08, 2013 4:09:42 PM org.apache.openejb.client.EventLogger log
>INFO: ServerAdded{server=ejbd://127.0.0.1:4201}
> ClusterMetaDataUpdated{provider=
>ejbd://localhost:4201, version=1357661341934, uris=2}
>Jan 08, 2013 4:09:42 PM org.apache.openejb.client.EventLogger log
>INFO: ServerRemoved{server=ejbd://localhost:4201}
>ClusterMetaDataUpdated{provider=ejbd://localhost:4201,
> version=1357661341934, uris=2}
>ConfigurationInfo does not exist in server 'ejbd://localhost:4201',
> check
> the server logs to ensure it
>exists and has not been removed.
>
>
> Now looking in the log file I get the following
> Jan 08, 2013 4:09:06 PM org.apache.openejb.server.SimpleServiceManager
> start
> INFO: Ready!
> Jan 08, 2013 4:09:42 PM org.apache.openejb.client.EventLogger log
> INFO: RemoteInitialContextCreated{providerUri=ejbd://localhost:4201}
> Jan 08, 2013 4:09:42 PM org.apache.openejb.client.EventLogger log
> INFO: ConnectionOpened{uri=ejbd://localhost:4201}
> Jan 08, 2013 4:09:42 PM org.apache.openejb.client.EventLogger log
> INFO: ServerAdded{server=ejbds://127.0.0.1:4203}
> ClusterMetaDataUpdated{provider=ejbd://localhost:4201,
> version=1357661341934, uris=2}
> Jan 08, 2013 4:09:42 PM org.apache.openejb.client.EventLogger log
> INFO: ServerAdded{server=ejbd://127.0.0.1:4201}
> ClusterMetaDataUpdated{provider=ejbd://localhost:4201,
> version=1357661341934, uris=2}
> Jan 08, 2013 4:09:42 PM org.apache.openejb.client.EventLogger log
> INFO: ServerRemoved{server=ejbd://localhost:4201}
> ClusterMetaDataUpdated{provider=ejbd://localhost:4201,
> version=1357661341934, uris=2}
>
> Looks like the server ejbd shut down for some reason.
>
> I used netstat -a to check non of the ports are being used
>
> Does anyone know why this is happening?
> By the way my knowledge of EJB's is limited but I have not got to the step
> of deploying an EJB yet.
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/clean-install-of-openejb-4-5-1-is-not-working-tp4660165.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
Re: TomEE maven plugin reload app
changes will be detected this way but not copied in the right place (see the end of http://openejb.apache.org/tomee-maven-plugin.html) if you don't want to work by part on your app i fear we need to update the plugin to support a better config *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/8 José Luis Cetina > Ok, what advice can you give me, i have this scenario: > > I have and ear "project" where i have 1 ejb module + 2 webapps > i have a single maven project where i have the tomee maven plugin for run > tomee and deploy on it. > > If i want to use the reload on update option, i have to define the entire > tomee plugin in the webapp where i want to reload? if yes, then i cant use > a external project (as i do) for only run tomee?? > > > 2013/1/8 Romain Manni-Bucau > > > Hi, > > > > currently you can sync only one war or a jar at a time > > > > *Romain Manni-Bucau* > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > *Blog: **http://rmannibucau.wordpress.com/*< > > http://rmannibucau.wordpress.com/> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > *Github: https://github.com/rmannibucau* > > > > > > > > 2013/1/8 José Luis Cetina > > > > > Hi Romain, im reading (again) your post about TomEE plugin for > reloading > > > the app: > > > > > > > > > http://rmannibucau.wordpress.com/2012/10/16/tomee-maven-plugin-reload-your-app-automatically/ > > > > > > > > > I was wondering how this can work in an ear project, i mean in the > > > synchronization block i have to set for example the > > > resourcesDir,targetBinariesDir etc... but i have 2 wars, 1 ejb module > an > > a > > > ear. Do i have to add the plugin for every war, ejb, ear??. > > > > > > Its possible to use with an ear project? > > > > > > > > > -- > --- > *SCJA. José Luis Cetina* > --- >
Re: TomEE maven plugin reload app
Hi, currently you can sync only one war or a jar at a time *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/8 José Luis Cetina > Hi Romain, im reading (again) your post about TomEE plugin for reloading > the app: > > http://rmannibucau.wordpress.com/2012/10/16/tomee-maven-plugin-reload-your-app-automatically/ > > > I was wondering how this can work in an ear project, i mean in the > synchronization block i have to set for example the > resourcesDir,targetBinariesDir etc... but i have 2 wars, 1 ejb module an a > ear. Do i have to add the plugin for every war, ejb, ear??. > > Its possible to use with an ear project? >
Re: JDBC connection pool memory leak
Great! thanks for the feedback. That's really appreciated. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/8 Bjorn Danielsson : > compiledICHolderKlass
Re: TomEE + CDI + Wicket = no suitable constructor for injection
not sure it is related, think it is log just for info because it tends to be an issue (that's not a common usage) - that's how i understand it looking the code Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/7 Bertrand Guay-Paquet : > As far as I can see it works, yes. > > However, I do have a suspicious eye towards warnings which I don't > understand. Also, I thought maybe this was somehow related to the crash I > get if I uncomment the "seam-conversation-owb" dependency in the pom. > > Bertrand > > > On 07/01/2013 4:18 PM, Romain Manni-Bucau wrote: >> >> BTW guys, >> >> it works then no? just warnings at startup no? >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> >> 2013/1/7 Bertrand Guay-Paquet : >>> >>> Harald, >>> >>> Thanks for jumping in! I think you are much better informed regarding >>> this >>> issue than I am. >>> >>> Regarding the UnmanagedObject class, you are right. I meant "unmanaged" >>> in >>> the sense that wicket does not inject it automatically, but via a method >>> call in the constructor. Since this test project could be referenced >>> elsewhere, I'll add a comment to that effect. >>> >>> Regards, >>> Bertrand >>> >>> >>> On 07/01/2013 4:03 PM, Harald Wellmann wrote: >>>> >>>> wicket-cdi does not define beans, they define injection targets which >>>> OpenWebBeans (IMHO incorrectly) treats as managed beans, hence the >>>> confusing >>>> messages. >>>> >>>> I've started a new thread [1] on the OWB user list for this issue. >>>> >>>> I've tested Bertrand's sample without problems on GlassFish/Weld, and >>>> the >>>> Weld implementation code for InjectionTargets looks a good deal cleaner >>>> to >>>> me. >>>> >>>> Bertrand: By the way, the UnmanagedObject in your sample is in fact a >>>> managed bean - not adding a @XXXScoped qualifier does not make it >>>> unmanaged, >>>> it's a managed bean with @Dependant scope. >>>> >>>> [1] http://comments.gmane.org/gmane.comp.java.openwebbeans.user/369 >>>> >>>> Best regards, >>>> Harald >>>> >>>> Am 07.01.2013 07:44, schrieb Romain Manni-Bucau: >>>>> >>>>> wicket-cdi defines beans with constructor params without @Inject on >>>>> the constructor so it is not a cdi bean for cdi >>>>> >>>>> >>>>> then not sure how they use it but the issue is in wicket-cdi >>>>> >>>>> >>>>> if it is a false cdi bean (manage by wicket) it should be annotated >>>>> Typed(), if not the constructor should be annotated @Inject >>>>> >>>>> >
Re: TomEE + CDI + Wicket = no suitable constructor for injection
BTW guys, it works then no? just warnings at startup no? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/7 Bertrand Guay-Paquet : > Harald, > > Thanks for jumping in! I think you are much better informed regarding this > issue than I am. > > Regarding the UnmanagedObject class, you are right. I meant "unmanaged" in > the sense that wicket does not inject it automatically, but via a method > call in the constructor. Since this test project could be referenced > elsewhere, I'll add a comment to that effect. > > Regards, > Bertrand > > > On 07/01/2013 4:03 PM, Harald Wellmann wrote: >> >> wicket-cdi does not define beans, they define injection targets which >> OpenWebBeans (IMHO incorrectly) treats as managed beans, hence the confusing >> messages. >> >> I've started a new thread [1] on the OWB user list for this issue. >> >> I've tested Bertrand's sample without problems on GlassFish/Weld, and the >> Weld implementation code for InjectionTargets looks a good deal cleaner to >> me. >> >> Bertrand: By the way, the UnmanagedObject in your sample is in fact a >> managed bean - not adding a @XXXScoped qualifier does not make it unmanaged, >> it's a managed bean with @Dependant scope. >> >> [1] http://comments.gmane.org/gmane.comp.java.openwebbeans.user/369 >> >> Best regards, >> Harald >> >> Am 07.01.2013 07:44, schrieb Romain Manni-Bucau: >>> >>> wicket-cdi defines beans with constructor params without @Inject on >>> the constructor so it is not a cdi bean for cdi >>> >>> >>> then not sure how they use it but the issue is in wicket-cdi >>> >>> >>> if it is a false cdi bean (manage by wicket) it should be annotated >>> Typed(), if not the constructor should be annotated @Inject >>> >>> >> >
Re: Apache TomEE Plugin - TomEE Version
here the diff: https://gist.github.com/e3255c2d34677c7ea3b6 works fine Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/7 José Luis Cetina : > I dont know what i was doing wrong. > > But what i did is create a new maven project. In my pom.xml i add the maven > plugin with inherited set to false and i create src/main/conf with my own > server.xml, tomcat-users.xml and tomee.xml now the ear is deployed and > unwrapped when i run tomee:run > > > 2013/1/7 José Luis Cetina > >> Another question, why if i use tomee:run the ear is copied to apps folder >> but is not "unwrapped" ??? >> >> >> 2013/1/7 José Luis Cetina >> >>> Can you give a try to my example: >>> https://github.com/maxtorzito/tomee-tests >>> >>> >>> >>> >>> 2013/1/7 José Luis Cetina >>> >>>> mmm i dont know what could be wrong >>>> >>>> >>>> 2013/1/7 José Luis Cetina >>>> >>>>> >>>>> >>>>> >>>>> org.apache.openejb.maven >>>>> tomee-maven-plugin >>>>> 1.0.1 >>>>> false >>>>> >>>>> 1.5.2-SNAPSHOT >>>>> 8080 >>>>> 8005 >>>>> false >>>>> 5005 >>>>> -XX:MaxPermSize=256M >>>>> -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled >>>>> >>>>> >>>>> com.grupokx:kx-apps-ear:1.0-SNAPSHOT:ear >>>>> >>>>> >>>>> mysql:mysql-connector-java:5.1.19 >>>>> com.grupokx:kx-security:1.0 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> 2013/1/7 Romain Manni-Bucau >>>>> >>>>>> version >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> --- >>>>> *SCJA. José Luis Cetina* >>>>> --- >>>>> >>>> >>>> >>>> >>>> -- >>>> --- >>>> *SCJA. José Luis Cetina* >>>> --- >>>> >>> >>> >>> >>> -- >>> --- >>> *SCJA. José Luis Cetina* >>> --- >>> >> >> >> >> -- >> --- >> *SCJA. José Luis Cetina* >> --- >> > > > > -- > --- > *SCJA. José Luis Cetina* > ---
Re: Apache TomEE Plugin - TomEE Version
Weird, never saw this behavior Did you align plugin version? Maybe share your project if with snapshot versions it doesnt work Le 7 janv. 2013 19:11, "José Luis Cetina" a écrit : > Yes, i ran it where is defined. > > If i comment inherited tag i have the same port occupied issue > > If i use tomee:run i dont have this error but the ear isnt deployed. > > > 2013/1/7 José Luis Cetina > > > Whe i add inherited like this: > > > > > > > > org.apache.openejb.maven > > tomee-maven-plugin > > 1.0.1 > > false > > > > 1.5.2-SNAPSHOT > > 8080 > > 8005 > > false > > 5005 > > -XX:MaxPermSize=256M > > -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled > > > > > com.grupokx:kx-apps-ear:1.0-SNAPSHOT:ear > > > > > > mysql:mysql-connector-java:5.1.19 > > com.grupokx:kx-security:1.0 > > > > > > > > > > > > > > > > I get no plugin prefix > > > > > > No plugin found for prefix 'tomee' in the current project and in the > > plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available > from > > the repositories [local (/home/maxtorzito/.m2/repository), central ( > > http://repo.maven.apache.org/maven2)] -> [Help 1] > > > > > > 2013/1/7 Romain Manni-Bucau > > > >> yes > >> > >> not perfect but works > >> > >> or define it only in your child and run it from here > >> > >> Romain Manni-Bucau > >> Twitter: @rmannibucau > >> Blog: http://rmannibucau.wordpress.com/ > >> LinkedIn: http://fr.linkedin.com/in/rmannibucau > >> Github: https://github.com/rmannibucau > >> > >> > >> > >> 2013/1/7 José Luis Cetina : > >> > Do you mean the tag? > >> > > >> > > >> > 2013/1/7 José Luis Cetina > >> > > >> >> > >> >> I use parent tag for my ejb module and my web module, what do you > mean > >> >> with inherited to false?? and run with -N?? > >> >> > >> >> > >> >> > >> >> 2013/1/7 Romain Manni-Bucau > >> >> > >> >>> N > >> >> > >> >> > >> >> > >> >> > >> > > >> > > >> > -- > >> > --- > >> > *SCJA. José Luis Cetina* > >> > --- > >> > > > > > > > > -- > > --- > > *SCJA. José Luis Cetina* > > --- > > > > > > -- > --- > *SCJA. José Luis Cetina* > --- >
Re: Apache TomEE Plugin - TomEE Version
Do you run it from the pom where it is defined? Well the easier is to define it in the pom defining the ear and not in others then cd myear && mvn package tomee:run Le 7 janv. 2013 18:33, "José Luis Cetina" a écrit : > Whe i add inherited like this: > > > > org.apache.openejb.maven > tomee-maven-plugin > 1.0.1 > false > > 1.5.2-SNAPSHOT > 8080 > 8005 > false > 5005 > -XX:MaxPermSize=256M > -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled > > com.grupokx:kx-apps-ear:1.0-SNAPSHOT:ear > > > mysql:mysql-connector-java:5.1.19 > com.grupokx:kx-security:1.0 > > > > > > > > I get no plugin prefix > > > No plugin found for prefix 'tomee' in the current project and in the plugin > groups [org.apache.maven.plugins, org.codehaus.mojo] available from the > repositories [local (/home/maxtorzito/.m2/repository), central ( > http://repo.maven.apache.org/maven2)] -> [Help 1] > > > 2013/1/7 Romain Manni-Bucau > > > yes > > > > not perfect but works > > > > or define it only in your child and run it from here > > > > Romain Manni-Bucau > > Twitter: @rmannibucau > > Blog: http://rmannibucau.wordpress.com/ > > LinkedIn: http://fr.linkedin.com/in/rmannibucau > > Github: https://github.com/rmannibucau > > > > > > > > 2013/1/7 José Luis Cetina : > > > Do you mean the tag? > > > > > > > > > 2013/1/7 José Luis Cetina > > > > > >> > > >> I use parent tag for my ejb module and my web module, what do you mean > > >> with inherited to false?? and run with -N?? > > >> > > >> > > >> > > >> 2013/1/7 Romain Manni-Bucau > > >> > > >>> N > > >> > > >> > > >> > > >> > > > > > > > > > -- > > > --- > > > *SCJA. José Luis Cetina* > > > --- > > > > > > -- > --- > *SCJA. José Luis Cetina* > --- >
Re: Apache TomEE Plugin - TomEE Version
yes not perfect but works or define it only in your child and run it from here Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/7 José Luis Cetina : > Do you mean the tag? > > > 2013/1/7 José Luis Cetina > >> >> I use parent tag for my ejb module and my web module, what do you mean >> with inherited to false?? and run with -N?? >> >> >> >> 2013/1/7 Romain Manni-Bucau >> >>> N >> >> >> >> > > > -- > --- > *SCJA. José Luis Cetina* > ---
Re: Apache TomEE Plugin - TomEE Version
so add inherited to false in the parent and run with -N Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/7 José Luis Cetina : > I just want to deploy my ear file as normal (deploy in apps). > > > 2013/1/7 Romain Manni-Bucau > >> not sure i get it >> >> you want to start it by module? if yes just provide a different config for >> ports >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> >> 2013/1/7 José Luis Cetina : >> > Yes, as i can see it starts for each submodule as you said, but how can i >> > prevent the port in use? >> > >> > >> > 2013/1/7 Romain Manni-Bucau >> > >> >> start on a multimodule project runs start on all submodules, isnt it >> your >> >> issue? >> >> >> >> Romain Manni-Bucau >> >> Twitter: @rmannibucau >> >> Blog: http://rmannibucau.wordpress.com/ >> >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> >> Github: https://github.com/rmannibucau >> >> >> >> >> >> >> >> 2013/1/7 José Luis Cetina : >> >> > I have a problem, i dont know what im doing wrong. >> >> > >> >> > If i try to use tomee:start apparently it try to run more than 1 time >> the >> >> > tomee server and i get a PORT IN USE, im trying to use with an ear >> file. >> >> > >> >> > Here is my plugin dependency: >> >> > >> >> > >> >> > >> >> > >> >> > org.apache.openejb.maven >> >> > tomee-maven-plugin >> >> > 1.0.1 >> >> > >> >> > 1.5.2-SNAPSHOT >> >> > 8080 >> >> > 8005 >> >> > false >> >> > 5005 >> >> > -XX:MaxPermSize=256M >> >> > -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled >> >> > >> >> > >> >> com.grupokx:kx-apps-ear:1.0-SNAPSHOT:ear >> >> > >> >> > >> >> > mysql:mysql-connector-java:5.1.19 >> >> > com.grupokx:kx-security:1.0 >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > Here is the log: >> >> > >> >> > >> >> >> > Building kx-apps 1.0-SNAPSHOT >> >> > >> >> >> > >> >> > [tomee:start] >> >> > TomEE was unzipped in >> >> > '/home/maxtorzito/NetBeansProjects/kx-apps/target/apache-tomee' >> >> > Removed not mandatory default webapps >> >> > Copied 'mysql:mysql-connector-java:5.1.19' in >> >> > >> >> >> '/home/maxtorzito/NetBeansProjects/kx-apps/target/apache-tomee/lib/mysql-connector-java-5.1.19.jar >> >> > Copied 'com.grupokx:kx-security:1.0' in >> >> > >> >> >> '/home/maxtorzito/NetBeansProjects/kx-apps/target/apache-tomee/lib/kx-security-1.0.jar >> >> > Copied 'com.grupokx:kx-apps-ear:1.0-SNAPSHOT:ear' in >> >> > >> >> >> '/home/maxtorzito/NetBeansProjects/kx-apps/target/apache-tomee/apps/kx-apps-ear-1.0-SNAPSHOT.ear >> >> > Running 'start'. Configured TomEE in plugin is localhost:8080 (plugin >> >> > shutdown port is 8005) >> >> > Please use CMSClassUnloadingEnabled in place of >> CMSPermGenSweepingEnabled >> >> > in the future >> >> > >> >> > >> >> >> > Building kx-apps-ejb 1.0-SNAPSHOT >> >> > >> --
Re: Apache TomEE Plugin - TomEE Version
not sure i get it you want to start it by module? if yes just provide a different config for ports Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/7 José Luis Cetina : > Yes, as i can see it starts for each submodule as you said, but how can i > prevent the port in use? > > > 2013/1/7 Romain Manni-Bucau > >> start on a multimodule project runs start on all submodules, isnt it your >> issue? >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> >> 2013/1/7 José Luis Cetina : >> > I have a problem, i dont know what im doing wrong. >> > >> > If i try to use tomee:start apparently it try to run more than 1 time the >> > tomee server and i get a PORT IN USE, im trying to use with an ear file. >> > >> > Here is my plugin dependency: >> > >> > >> > >> > >> > org.apache.openejb.maven >> > tomee-maven-plugin >> > 1.0.1 >> > >> > 1.5.2-SNAPSHOT >> > 8080 >> > 8005 >> > false >> > 5005 >> > -XX:MaxPermSize=256M >> > -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled >> > >> > >> com.grupokx:kx-apps-ear:1.0-SNAPSHOT:ear >> > >> > >> > mysql:mysql-connector-java:5.1.19 >> > com.grupokx:kx-security:1.0 >> > >> > >> > >> > >> > >> > >> > >> > Here is the log: >> > >> > >> > Building kx-apps 1.0-SNAPSHOT >> > >> > >> > [tomee:start] >> > TomEE was unzipped in >> > '/home/maxtorzito/NetBeansProjects/kx-apps/target/apache-tomee' >> > Removed not mandatory default webapps >> > Copied 'mysql:mysql-connector-java:5.1.19' in >> > >> '/home/maxtorzito/NetBeansProjects/kx-apps/target/apache-tomee/lib/mysql-connector-java-5.1.19.jar >> > Copied 'com.grupokx:kx-security:1.0' in >> > >> '/home/maxtorzito/NetBeansProjects/kx-apps/target/apache-tomee/lib/kx-security-1.0.jar >> > Copied 'com.grupokx:kx-apps-ear:1.0-SNAPSHOT:ear' in >> > >> '/home/maxtorzito/NetBeansProjects/kx-apps/target/apache-tomee/apps/kx-apps-ear-1.0-SNAPSHOT.ear >> > Running 'start'. Configured TomEE in plugin is localhost:8080 (plugin >> > shutdown port is 8005) >> > Please use CMSClassUnloadingEnabled in place of CMSPermGenSweepingEnabled >> > in the future >> > >> > >> > Building kx-apps-ejb 1.0-SNAPSHOT >> > >> > >> > [tomee:start] >> > Jan 07, 2013 10:05:03 AM org.apache.catalina.core.AprLifecycleListener >> init >> > INFO: The APR based Apache Tomcat Native library which allows optimal >> > performance in production environments was not found on the >> > java.library.path: >> > >> /usr/lib/jvm/jdk1.7.0_09/jre/lib/amd64:/usr/lib/jvm/jdk1.7.0_09/jre/lib/i386::/usr/java/packages/lib/i386:/lib:/usr/lib >> > TomEE was unzipped in >> > >> '/home/maxtorzito/NetBeansProjects/kx-apps/kx-apps-ejb/target/apache-tomee' >> > Removed not mandatory default webapps >> > Copied 'mysql:mysql-connector-java:5.1.19' in >> > >> '/home/maxtorzito/NetBeansProjects/kx-apps/kx-apps-ejb/target/apache-tomee/lib/mysql-connector-java-5.1.19.jar >> > Copied 'com.grupokx:kx-security:1.0' in >> > >> '/home/maxtorzito/NetBeansProjects/kx-apps/kx-apps-ejb/target/apache-tomee/lib/kx-security-1.0.jar >> > Copied 'com.grupokx:kx-apps-ear:1.0-SNAPSHOT:ear' in >> > >> '/home/maxtorzito/NetBeansProjects/kx-apps/kx-apps-ejb/target/apac
Re: Apache TomEE Plugin - TomEE Version
start on a multimodule project runs start on all submodules, isnt it your issue? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/7 José Luis Cetina : > I have a problem, i dont know what im doing wrong. > > If i try to use tomee:start apparently it try to run more than 1 time the > tomee server and i get a PORT IN USE, im trying to use with an ear file. > > Here is my plugin dependency: > > > > > org.apache.openejb.maven > tomee-maven-plugin > 1.0.1 > > 1.5.2-SNAPSHOT > 8080 > 8005 > false > 5005 > -XX:MaxPermSize=256M > -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled > > com.grupokx:kx-apps-ear:1.0-SNAPSHOT:ear > > > mysql:mysql-connector-java:5.1.19 > com.grupokx:kx-security:1.0 > > > > > > > > Here is the log: > > > Building kx-apps 1.0-SNAPSHOT > > > [tomee:start] > TomEE was unzipped in > '/home/maxtorzito/NetBeansProjects/kx-apps/target/apache-tomee' > Removed not mandatory default webapps > Copied 'mysql:mysql-connector-java:5.1.19' in > '/home/maxtorzito/NetBeansProjects/kx-apps/target/apache-tomee/lib/mysql-connector-java-5.1.19.jar > Copied 'com.grupokx:kx-security:1.0' in > '/home/maxtorzito/NetBeansProjects/kx-apps/target/apache-tomee/lib/kx-security-1.0.jar > Copied 'com.grupokx:kx-apps-ear:1.0-SNAPSHOT:ear' in > '/home/maxtorzito/NetBeansProjects/kx-apps/target/apache-tomee/apps/kx-apps-ear-1.0-SNAPSHOT.ear > Running 'start'. Configured TomEE in plugin is localhost:8080 (plugin > shutdown port is 8005) > Please use CMSClassUnloadingEnabled in place of CMSPermGenSweepingEnabled > in the future > > > Building kx-apps-ejb 1.0-SNAPSHOT > > > [tomee:start] > Jan 07, 2013 10:05:03 AM org.apache.catalina.core.AprLifecycleListener init > INFO: The APR based Apache Tomcat Native library which allows optimal > performance in production environments was not found on the > java.library.path: > /usr/lib/jvm/jdk1.7.0_09/jre/lib/amd64:/usr/lib/jvm/jdk1.7.0_09/jre/lib/i386::/usr/java/packages/lib/i386:/lib:/usr/lib > TomEE was unzipped in > '/home/maxtorzito/NetBeansProjects/kx-apps/kx-apps-ejb/target/apache-tomee' > Removed not mandatory default webapps > Copied 'mysql:mysql-connector-java:5.1.19' in > '/home/maxtorzito/NetBeansProjects/kx-apps/kx-apps-ejb/target/apache-tomee/lib/mysql-connector-java-5.1.19.jar > Copied 'com.grupokx:kx-security:1.0' in > '/home/maxtorzito/NetBeansProjects/kx-apps/kx-apps-ejb/target/apache-tomee/lib/kx-security-1.0.jar > Copied 'com.grupokx:kx-apps-ear:1.0-SNAPSHOT:ear' in > '/home/maxtorzito/NetBeansProjects/kx-apps/kx-apps-ejb/target/apache-tomee/apps/kx-apps-ear-1.0-SNAPSHOT.ear > '/home/maxtorzito/NetBeansProjects/kx-apps/kx-apps-ejb/target/kx-apps-ejb-1.0-SNAPSHOT.ejb' > doesn't exist, ignoring (maybe run mvn package before this plugin) > Running 'start'. Configured TomEE in plugin is localhost:8080 (plugin > shutdown port is 8005) > > > Building kx-apps-mailing 1.0-SNAPSHOT > > Please use CMSClassUnloadingEnabled in place of CMSPermGenSweepingEnabled > in the future > Jan 07, 2013 10:05:04 AM org.apache.coyote.AbstractProtocol init > INFO: Initializing ProtocolHandler ["http-bio-8080"] > Jan 07, 2013 10:05:04 AM org.apache.coyote.AbstractProtocol init > INFO: Initializing ProtocolHandler ["ajp-bio-8009"] > The artifact org.apache.commons:commons-io:jar:1.3.2 has been relocated to > commons-io:commons-io:jar:1.3.2 > > [tomee:start] > TomEE was unzipped in > '/home/maxtorzito/NetBeansProjects/kx-apps/kx-apps-mailing/target/apache-tomee' > Removed not mandatory default webapps > Copied 'mysql:mysql-connector-java:5.1
Re: How do i deploy a ManagedConnectionFactory in a war file?
didn't try with eclipse but worked for hazelcast resource adapter with tomee mvn plugin: https://issues.apache.org/jira/browse/TOMEE-710 Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/7 Anthony Fryer : > I initially specified the wrong link. When i edited it, it didn't resend the > email. The correct link is > http://java.net/projects/javaee-spec/lists/users/archive/2012-09/message/9 > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/How-do-i-deploy-a-ManagedConnectionFactory-in-a-war-file-tp4659993p4660118.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Apache TomEE Plugin - TomEE Version
Just try to use 1.5.2-SNAPSHOT version of plugin, it should be far enough IMO and shouldn't bother you since you already rely on the snapshot, no? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/7 José Luis Cetina : > Im testing tomee plugin, because i want to use it for deploy my ear and > before that use the tomee plugin that detects changes in code (like > JRebel). But im learning how to use it. > > I ask for version because you fix some CODI issue's in 1.5.2-SNAPSHOT. > > > > > 2013/1/7 Romain Manni-Bucau > >> 1.5.2-SNAPSHOT > > > > > -- > --- > *SCJA. José Luis Cetina* > ---
Re: Apache TomEE Plugin - TomEE Version
Hi, if you ask i guess you have an issue? typically you can use tomee maven plugin in version 1.5.2-SNAPSHOT (we aligned it with tomee version yesterday) but 1.0.1 should work Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/7 José Luis Cetina : > Hi it is possible to use the tomee snapshot in tomee maven plugin?? > > > org.apache.openejb.maven > tomee-maven-plugin > 1.0.1 > > 1.5.2-SNAPSHOT > . > . > . > . > . > .
Re: How do i deploy a ManagedConnectionFactory in a war file?
I see "The mailing list us...@javaee-spec.java.net does not have any messages in its archive." following your link, not sure why tw i don't see anything blocking technically to support it. If it doesn't break tck we should be able to do it. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/7 Anthony Fryer : > Which spec defines the collapsed ear packaging? I'm looking > javaee-platform-6_0-fr-spec.pdf but can't see mention of 'collapsed ear' > anywhere. > > Anyhow, is only ejb lite supported in a collapsed ear? I found a > conversation thread where David wanted to be able to deploy rars in wars. > Would be really nice to be able to do that... > > http://java.net/projects/javaee-spec/lists/users/archive/2012-09/message/91 > > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/How-do-i-deploy-a-ManagedConnectionFactory-in-a-war-file-tp4659993p4660116.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: How do i deploy a ManagedConnectionFactory in a war file?
...but was changed by the spec Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/7 Jean-Louis MONTEIRO : > The collapsed EAR (not fully compatible with what it really is nowadays) > was an OpenEJB feature. > With Java EE 6, we pushed that feature to the spec so that now it's fully > standard. > > Jean-Louis > > > 2013/1/6 Anthony Fryer > >> If the collapsed ear concept is a "tomee' specific idea and not part of the >> spec, could I request that a resource adapter could also be deployed in a >> war file, similarly to ejbs? >> >> >> >> -- >> View this message in context: >> http://openejb.979440.n4.nabble.com/How-do-i-deploy-a-ManagedConnectionFactory-in-a-war-file-tp4659993p4660105.html >> Sent from the OpenEJB User mailing list archive at Nabble.com. >> > > > > -- > Jean-Louis
Re: TomEE + CDI + Wicket = no suitable constructor for injection
wicket-cdi defines beans with constructor params without @Inject on the constructor so it is not a cdi bean for cdi then not sure how they use it but the issue is in wicket-cdi if it is a false cdi bean (manage by wicket) it should be annotated Typed(), if not the constructor should be annotated @Inject Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/7 Bertrand Guay-Paquet : > Here you go: > https://github.com/berniegp/test-wicket-cdi > > > On 04/01/2013 5:13 PM, Romain Manni-Bucau wrote: >> >> Share it on github if possible >> Le 4 janv. 2013 20:49, "Bertrand Guay-Paquet" a >> écrit : >> >>> Hi, >>> >>> Howard: I already had a look at these messages and others from the Wicket >>> mailing list. They were indeed helpful in getting me to where I am now. >>> >>> From what I understand, Harald is right and wicket-cdi is not specific >>> to >>> Weld. @RequestScoped, @SessionScoped and @ApplicationScoped all work fine >>> in my limited tests. However, I'm not able to get @ConversionScoped >>> working >>> with the owb seam connector (seam-conversation-owb) for an unknown >>> reason; >>> but this is not related to my prior questions. >>> >>> Romain: Where should I send a small sample app which demonstrates the >>> issue? >>> >>> Also, am I "swimming against the current" by trying to use cdi instead of >>> jndi lookups for connecting my EJB tier to the web tier (Wicket)? I >>> currently, have jndi lookups working correctly and wanted to benefit from >>> the cdi goodies but I'm starting to think it's not worth the trouble >>> right >>> now. >>> >>> Regards, >>> Bertrand >>> >>> On 04/01/2013 2:13 PM, Romain Manni-Bucau wrote: >>> >>>> if you have a sample i'll will give it a try this week end but looking >>>> quickly not sure it is implemented to be portable >>>> >>>> >>>> Romain Manni-Bucau >>>> Twitter: @rmannibucau >>>> Blog: >>>> http://rmannibucau.wordpress.**com/<http://rmannibucau.wordpress.com/> >>>> LinkedIn: >>>> http://fr.linkedin.com/in/**rmannibucau<http://fr.linkedin.com/in/rmannibucau> >>>> >>>> Github: https://github.com/rmannibucau >>>> >>>> >>>> >>>> 2013/1/4 Harald Wellmann : >>>> >>>>> I don't think that's the point. >>>>> >>>>> wicket-cdi [1] only depends on the CDI API, not on Weld. The Seam >>>>> dependency >>>>> is optional in fact. So it should work with OWB (but I haven't tried). >>>>> >>>>> The message means that DetachEventEmitter is being considered as an >>>>> injection target but does not have a default constructor. >>>>> >>>>> The question is why this class is considered at all. >>>>> >>>>> I suppose you have a WAR with a WEB-INF/beans.xml descriptor to enable >>>>> CDI >>>>> and wicket-cdi in WEB-INF/lib/ >>>>> >>>>> It might be that OpenWebBeans scans all JARs in WEB-INF/lib even if the >>>>> individual libs don't contain a beans.xml marker (and wicket-cdi has no >>>>> beans.xml, nor is it a CDI extension). >>>>> >>>>> (I remember a discussion about Bean Deployment Archives being handled >>>>> differently in Weld and OWB and people arguing the CDI 1.0 spec to be >>>>> somewhat broken in this respect.) >>>>> >>>>> [1] >>>>> http://search.maven.org/**remotecontent?filepath=org/** >>>>> >>>>> apache/wicket/wicket-cdi/6.1.**1/wicket-cdi-6.1.1.pom<http://search.maven.org/remotecontent?filepath=org/apache/wicket/wicket-cdi/6.1.1/wicket-cdi-6.1.1.pom> >>>>> >>>>> >>>>> Best regards, >>>>> Harald >>>>> >>>>> >>>>> Am 04.01.2013 19:33, schrieb Romain Manni-Bucau: >>>>> >>>>> wicket-cdi is for weld not for cdi if it is the one i'm thinking >>>>>> >>>>>> about. So this is not portable >>>>>> >>>>>> Romain Manni-Bucau >>>>>> Twitter: @rmannibucau >>>>>> Blog: >>>>>> http://rmannibucau.wordpress.**com/<http://rmannibucau.wordpress.com/> >>>>>> LinkedIn: >>>>>> http://fr.linkedin.com/in/**rmannibucau<http://fr.linkedin.com/in/rmannibucau> >>>>>> >>>>>> Github: https://github.com/rmannibucau >>>>>> >>>>>> >>>>>> >>>>>> 2013/1/4 Bertrand Guay-Paquet : >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> When running Wicket with its wicket-cdi module which provides CDI >>>>>>> injection >>>>>>> of Wicket components, I get a ton of info/warnings of this sort: >>>>>>> org.apache.webbeans.component.**creation.** >>>>>>> >>>>>>> AnnotatedTypeBeanCreatorImpl >>>>>>> defineConstructor >>>>>>> INFO: No suitable constructor found for injection target class : >>>>>>> [class >>>>>>> org.apache.wicket.cdi.**DetachEventEmitter]. produce() method does >>>>>>> not >>>>>>> >>>>>>> work! >>>>>>> >>>>>>> I'm new to CDI so I searched online but couldn't find out what these >>>>>>> mean... >>>>>>> Are they problematic? What do they mean? Apparently, wicket + weld >>>>>>> doesn't >>>>>>> produce these messages. >>>>>>> >>>>>>> Regards, >>>>>>> Bertrand >>>>>>> >
Re: JDBC connection pool memory leak
ok, with https://issues.apache.org/jira/browse/TOMEE-703 (available tomorrow on snapshot) + DataSourceCreator tomcat JdbcDriver com.mysql.jdbc.Driver JdbcUrl jdbc:mysql://localhost:3306/poolbugtest ValidationQuery SELECT * FROM MYTABLE JtaManaged true jdbcInterceptors = StatementFinalizer it should be better can you check it please? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/4 Howard W. Smith, Jr. : > Is this possibly related to the following discussion (which was > coincidentally discussed today as well on tomcat user list) ? > > http://tomcat.10.n6.nabble.com/jdbc-pool-Transaction-left-open-by-the-connection-validation-mechanism-td4991758.html
Re: How do i deploy a ManagedConnectionFactory in a war file?
Currently i dont think but if you dont develop the rar you can configure it in tomee.xml then simply dev your war in eclipse Le 3 janv. 2013 23:40, "Anthony Fryer" a écrit : > 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 that way i can use eclipse wtp > to automatically deploy the war to tomee and quickly develop and debug my > application. Is it possible to setup eclipse wtp to automatically publish > ear files to tomee? > > I have no idea what the specification says about war files and resource > adapters but it would be really nice if i could do this with tomee. > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/How-do-i-deploy-a-ManagedConnectionFactory-in-a-war-file-tp4659993p4660058.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
Re: TomEE + CDI + Wicket = no suitable constructor for injection
Share it on github if possible Le 4 janv. 2013 20:49, "Bertrand Guay-Paquet" a écrit : > Hi, > > Howard: I already had a look at these messages and others from the Wicket > mailing list. They were indeed helpful in getting me to where I am now. > > From what I understand, Harald is right and wicket-cdi is not specific to > Weld. @RequestScoped, @SessionScoped and @ApplicationScoped all work fine > in my limited tests. However, I'm not able to get @ConversionScoped working > with the owb seam connector (seam-conversation-owb) for an unknown reason; > but this is not related to my prior questions. > > Romain: Where should I send a small sample app which demonstrates the > issue? > > Also, am I "swimming against the current" by trying to use cdi instead of > jndi lookups for connecting my EJB tier to the web tier (Wicket)? I > currently, have jndi lookups working correctly and wanted to benefit from > the cdi goodies but I'm starting to think it's not worth the trouble right > now. > > Regards, > Bertrand > > On 04/01/2013 2:13 PM, Romain Manni-Bucau wrote: > >> if you have a sample i'll will give it a try this week end but looking >> quickly not sure it is implemented to be portable >> >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.**com/<http://rmannibucau.wordpress.com/> >> LinkedIn: >> http://fr.linkedin.com/in/**rmannibucau<http://fr.linkedin.com/in/rmannibucau> >> Github: https://github.com/rmannibucau >> >> >> >> 2013/1/4 Harald Wellmann : >> >>> I don't think that's the point. >>> >>> wicket-cdi [1] only depends on the CDI API, not on Weld. The Seam >>> dependency >>> is optional in fact. So it should work with OWB (but I haven't tried). >>> >>> The message means that DetachEventEmitter is being considered as an >>> injection target but does not have a default constructor. >>> >>> The question is why this class is considered at all. >>> >>> I suppose you have a WAR with a WEB-INF/beans.xml descriptor to enable >>> CDI >>> and wicket-cdi in WEB-INF/lib/ >>> >>> It might be that OpenWebBeans scans all JARs in WEB-INF/lib even if the >>> individual libs don't contain a beans.xml marker (and wicket-cdi has no >>> beans.xml, nor is it a CDI extension). >>> >>> (I remember a discussion about Bean Deployment Archives being handled >>> differently in Weld and OWB and people arguing the CDI 1.0 spec to be >>> somewhat broken in this respect.) >>> >>> [1] >>> http://search.maven.org/**remotecontent?filepath=org/** >>> apache/wicket/wicket-cdi/6.1.**1/wicket-cdi-6.1.1.pom<http://search.maven.org/remotecontent?filepath=org/apache/wicket/wicket-cdi/6.1.1/wicket-cdi-6.1.1.pom> >>> >>> Best regards, >>> Harald >>> >>> >>> Am 04.01.2013 19:33, schrieb Romain Manni-Bucau: >>> >>> wicket-cdi is for weld not for cdi if it is the one i'm thinking >>>> about. So this is not portable >>>> >>>> Romain Manni-Bucau >>>> Twitter: @rmannibucau >>>> Blog: >>>> http://rmannibucau.wordpress.**com/<http://rmannibucau.wordpress.com/> >>>> LinkedIn: >>>> http://fr.linkedin.com/in/**rmannibucau<http://fr.linkedin.com/in/rmannibucau> >>>> Github: https://github.com/rmannibucau >>>> >>>> >>>> >>>> 2013/1/4 Bertrand Guay-Paquet : >>>> >>>>> Hello, >>>>> >>>>> When running Wicket with its wicket-cdi module which provides CDI >>>>> injection >>>>> of Wicket components, I get a ton of info/warnings of this sort: >>>>> org.apache.webbeans.component.**creation.** >>>>> AnnotatedTypeBeanCreatorImpl >>>>> defineConstructor >>>>> INFO: No suitable constructor found for injection target class : [class >>>>> org.apache.wicket.cdi.**DetachEventEmitter]. produce() method does not >>>>> work! >>>>> >>>>> I'm new to CDI so I searched online but couldn't find out what these >>>>> mean... >>>>> Are they problematic? What do they mean? Apparently, wicket + weld >>>>> doesn't >>>>> produce these messages. >>>>> >>>>> Regards, >>>>> Bertrand >>>>> >>>> >>> >
Re: TomEE + CDI + Wicket = no suitable constructor for injection
if you have a sample i'll will give it a try this week end but looking quickly not sure it is implemented to be portable Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/4 Harald Wellmann : > I don't think that's the point. > > wicket-cdi [1] only depends on the CDI API, not on Weld. The Seam dependency > is optional in fact. So it should work with OWB (but I haven't tried). > > The message means that DetachEventEmitter is being considered as an > injection target but does not have a default constructor. > > The question is why this class is considered at all. > > I suppose you have a WAR with a WEB-INF/beans.xml descriptor to enable CDI > and wicket-cdi in WEB-INF/lib/ > > It might be that OpenWebBeans scans all JARs in WEB-INF/lib even if the > individual libs don't contain a beans.xml marker (and wicket-cdi has no > beans.xml, nor is it a CDI extension). > > (I remember a discussion about Bean Deployment Archives being handled > differently in Weld and OWB and people arguing the CDI 1.0 spec to be > somewhat broken in this respect.) > > [1] > http://search.maven.org/remotecontent?filepath=org/apache/wicket/wicket-cdi/6.1.1/wicket-cdi-6.1.1.pom > > Best regards, > Harald > > > Am 04.01.2013 19:33, schrieb Romain Manni-Bucau: > >> wicket-cdi is for weld not for cdi if it is the one i'm thinking >> about. So this is not portable >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> >> 2013/1/4 Bertrand Guay-Paquet : >>> >>> Hello, >>> >>> When running Wicket with its wicket-cdi module which provides CDI >>> injection >>> of Wicket components, I get a ton of info/warnings of this sort: >>> org.apache.webbeans.component.creation.AnnotatedTypeBeanCreatorImpl >>> defineConstructor >>> INFO: No suitable constructor found for injection target class : [class >>> org.apache.wicket.cdi.DetachEventEmitter]. produce() method does not >>> work! >>> >>> I'm new to CDI so I searched online but couldn't find out what these >>> mean... >>> Are they problematic? What do they mean? Apparently, wicket + weld >>> doesn't >>> produce these messages. >>> >>> Regards, >>> Bertrand > >
Re: EAR+CODI doesnt work
well i just triggered a deployment (should be online in some minutes) i managed to make your test.xhtml working this morning hope nothing was broken this afternoon Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/4 José Luis Cetina : > i build tome form trunk, after that i get this exceptions: > > Jan 04, 2013 12:46:01 PM org.apache.myfaces.shared.util.ClassUtils > buildApplicationObject > SEVERE: null > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:525) > at > org.apache.myfaces.shared.util.ClassUtils.buildApplicationObject(ClassUtils.java:561) > at > org.apache.myfaces.config.FacesConfigurator.configureApplication(FacesConfigurator.java:532) > at > org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:419) > at > org.apache.myfaces.webapp.AbstractFacesInitializer.buildConfiguration(AbstractFacesInitializer.java:370) > at > org.apache.myfaces.webapp.Jsp21FacesInitializer.initContainerIntegration(Jsp21FacesInitializer.java:73) > at > org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:143) > at > org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:119) > at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4791) > at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > Caused by: java.lang.IllegalStateException: no > org.apache.myfaces.extensions.cdi.core.api.provider.BeanManagerProvider in > place! Please ensure that you configured the CDI implementation of your > choice properly. If your setup is correct, please clear all caches and > compiled artifacts. If there is still a problem, try one of the controlled > bootstrapping add-ons for the CDI implementation you are using. > at > org.apache.myfaces.extensions.cdi.core.api.provider.BeanManagerProvider.getInstance(BeanManagerProvider.java:83) > at > org.apache.myfaces.extensions.cdi.core.impl.util.CodiUtils.getContextualReferenceByClass(CodiUtils.java:124) > at > org.apache.myfaces.extensions.cdi.jsf2.impl.navigation.CodiNavigationHandler.isAddViewConfigsAsNavigationCaseActivated(CodiNavigationHandler.java:200) > at > org.apache.myfaces.extensions.cdi.jsf2.impl.navigation.CodiNavigationHandler.(CodiNavigationHandler.java:65) > ... 21 more > > Jan 04, 2013 12:46:01 PM org.apache.myfaces.webapp.AbstractFacesInitializer > initFaces > SEVERE: An error occured while initializing MyFaces: > java.lang.reflect.InvocationTargetException > javax.faces.FacesException: java.lang.reflect.InvocationTargetException > at > org.apache.myfaces.shared.util.ClassUtils.buildApplicationObject(ClassUtils.java:576) > at > org.apache.myfaces.config.FacesConfigurator.configureApplication(FacesConfigurator.java:532) > at > org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:419) > at > org.apache.myfaces.webapp.AbstractFacesInitializer.buildConfiguration(AbstractFacesInitializer.java:370) > at > org.apache.myfaces.webapp.Jsp21FacesInitializer.initContainerIntegration(Jsp21FacesInitializer.java:73) > at > org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:143) > at > org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:119) > at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4791) > at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) > at > org.apache.c
Re: TomEE + CDI + Wicket = no suitable constructor for injection
wicket-cdi is for weld not for cdi if it is the one i'm thinking about. So this is not portable Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/4 Bertrand Guay-Paquet : > Hello, > > When running Wicket with its wicket-cdi module which provides CDI injection > of Wicket components, I get a ton of info/warnings of this sort: > org.apache.webbeans.component.creation.AnnotatedTypeBeanCreatorImpl > defineConstructor > INFO: No suitable constructor found for injection target class : [class > org.apache.wicket.cdi.DetachEventEmitter]. produce() method does not work! > > I'm new to CDI so I searched online but couldn't find out what these mean... > Are they problematic? What do they mean? Apparently, wicket + weld doesn't > produce these messages. > > Regards, > Bertrand
Re: WARNING: WebAppInfo not found.
probably because the injection type doesn't have all info (@webserviceclient?) that's said i didn't understand your "not in wtpwebapps" answer. apps folder is configured in tomee.xml () Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/4 avrono : > further to that, I can get the .create working but not via injection > @WebServiceRef(wsdlLocation = "http://localhost:8080/Calculator?wsdl";) > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/WARNING-WebAppInfo-not-found-tp4660077p4660084.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: EAR+CODI doesnt work
think the snapshot is not up to date (== doesnt contain the fix) Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/4 José Luis Cetina : > I've just tested and i still with the same problem. > > > Im using: apache-tomee-1.5.2-20130104.041348-22-webprofile.zip > > java.lang.IllegalStateException: Could not find beans for Type=class > com.grupokx.MyEJBBean and qualifiers:[] > > org.apache.myfaces.extensions.cdi.core.api.provider.BeanManagerProvider.getContextualReference(BeanManagerProvider.java:172) > > com.grupokx.managedbean.MyManagedBeanTest.myPostConstruct(MyManagedBeanTest.java:31) > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > java.lang.reflect.Method.invoke(Method.java:601) > > org.apache.webbeans.intercept.InvocationContextImpl.proceedCommonAnnots(InvocationContextImpl.java:381) > > org.apache.webbeans.intercept.InvocationContextImpl.proceed(InvocationContextImpl.java:185) > > org.apache.webbeans.component.AbstractInjectionTargetBean.postConstructDefault(AbstractInjectionTargetBean.java:259) > > org.apache.webbeans.component.AbstractInjectionTargetBean.postConstruct(AbstractInjectionTargetBean.java:237) > > org.apache.webbeans.portable.creation.InjectionTargetProducer.postConstruct(InjectionTargetProducer.java:122) > > org.apache.webbeans.component.InjectionTargetWrapper.postConstruct(InjectionTargetWrapper.java:87) > > org.apache.webbeans.component.AbstractOwbBean.create(AbstractOwbBean.java:182) > > org.apache.webbeans.container.SerializableBean.create(SerializableBean.java:119) > > org.apache.myfaces.extensions.cdi.core.impl.util.CodiUtils.createNewInstanceOfBean(CodiUtils.java:69) > > org.apache.myfaces.extensions.cdi.jsf.impl.scope.conversation.AbstractConversationBeanEntry.createNewBeanInstance(AbstractConversationBeanEntry.java:139) > > org.apache.myfaces.extensions.cdi.jsf.impl.scope.conversation.AbstractConversationBeanEntry.getBeanInstance(AbstractConversationBeanEntry.java:84) > > org.apache.myfaces.extensions.cdi.core.impl.scope.conversation.AbstractGroupedConversationContext.create(AbstractGroupedConversationContext.java:100) > > org.apache.myfaces.extensions.cdi.core.impl.scope.conversation.ConversationContextAdapter.get(ConversationContextAdapter.java:81) > > org.apache.webbeans.context.CustomContextImpl.get(CustomContextImpl.java:43) > > org.apache.webbeans.context.CustomPassivatingContextImpl.get(CustomPassivatingContextImpl.java:42) > > org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.getContextualInstance(NormalScopedBeanInterceptorHandler.java:154) > > org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.invoke(NormalScopedBeanInterceptorHandler.java:114) > > org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.invoke(NormalScopedBeanInterceptorHandler.java:108) > > com.grupokx.managedbean.MyManagedBeanTest_$$_javassist_27.getName(MyManagedBeanTest_$$_javassist_27.java) > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > java.lang.reflect.Method.invoke(Method.java:601) > javax.el.BeanELResolver.getValue(BeanELResolver.java:64) > javax.el.CompositeELResolver.getValue(CompositeELResolver.java:58) > > org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:179) > org.apache.el.parser.AstValue.getValue(AstValue.java:183) > > org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:185) > > org.apache.webbeans.el.WrappedValueExpression.getValue(WrappedValueExpression.java:68) > > org.apache.webbeans.el.WrappedValueExpression.getValue(WrappedValueExpression.java:68) > > org.apache.myfaces.view.facelets.el.ELText$ELTextVariable.writeText(ELText.java:219) > > org.apache.myfaces.view.facelets.el.ELText$ELTextComposite.writeText(ELText.java:131) > > org.apache.myfaces.view.facelets.compiler.TextInstruction.write(TextInstruction.java:45) > > org.apache.myfaces.vie
Re: WARNING: WebAppInfo not found.
Hi,
webapps folder is for webapp ATM, try to put the jar in /apps
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/1/4 avrono :
> Hi,
>
> I am having a problem deploying and using the webservice in this
> http://openejb.apache.org/examples-trunk/simple-webservice/
> <http://openejb.apache.org/examples-trunk/simple-webservice/> example
>
> Any ideas how to resolve the "WARNING: WebAppInfo not found." error/warning
> ?
>
> I have copied the .jar to the Webapps folder of my TomEE installation and I
> am trying to run the JUnit test from another project. The test fails with a
> ServiceConstructionException
>
> Below is the server startup log (relevant part)
>
>
> 04-Jan-2013 14:11:41 org.apache.openejb.config.ConfigurationFactory
> configureApplication
> INFO: Configuring enterprise application:
> /home/avrono/TomEE/apache-tomee-plus-1.5.0/webapps/simple-webservice-1.1.0-SNAPSHOT.jar
> 04-Jan-2013 14:11:41 org.apache.openejb.config.InitEjbDeployments deploy
> INFO: Auto-deploying ejb Calculator: EjbDeployment(deployment-id=Calculator)
> 04-Jan-2013 14:11:41 org.apache.openejb.config.AppInfoBuilder build
> INFO: Enterprise application
> "/home/avrono/TomEE/apache-tomee-plus-1.5.0/webapps/simple-webservice-1.1.0-SNAPSHOT.jar"
> loaded.
> 04-Jan-2013 14:11:41 org.apache.openejb.assembler.classic.Assembler
> createApplication
> INFO: Assembling app:
> /home/avrono/TomEE/apache-tomee-plus-1.5.0/webapps/simple-webservice-1.1.0-SNAPSHOT.jar
> 04-Jan-2013 14:11:41 org.apache.openejb.cdi.CdiBuilder initSingleton
> INFO: Existing thread singleton service in SystemInstance()
> org.apache.openejb.cdi.ThreadSingletonServiceImpl@5da37c
> 04-Jan-2013 14:11:41 org.apache.openejb.cdi.OpenEJBLifecycle
> startApplication
> INFO: OpenWebBeans Container is starting...
> 04-Jan-2013 14:11:41 org.apache.webbeans.plugins.PluginLoader startUp
> INFO: Adding OpenWebBeansPlugin : [CdiPlugin]
> 04-Jan-2013 14:11:41 org.apache.webbeans.plugins.PluginLoader startUp
> INFO: Adding OpenWebBeansPlugin : [OpenWebBeansJsfPlugin]
> 04-Jan-2013 14:11:41 org.apache.openejb.cdi.BeansDeployer
> validateInjectionPoints
> INFO: All injection points are validated successfully.
> 04-Jan-2013 14:11:41 org.apache.openejb.cdi.OpenEJBLifecycle
> startApplication
> INFO: OpenWebBeans Container has started, it took 4 ms.
> 04-Jan-2013 14:11:41 org.apache.openejb.assembler.classic.Assembler
> createApplication
> INFO: Created Ejb(deployment-id=Calculator, ejb-name=Calculator,
> container=My Stateless Container)
> 04-Jan-2013 14:11:41 org.apache.openejb.assembler.classic.Assembler
> createApplication
> INFO: Started Ejb(deployment-id=Calculator, ejb-name=Calculator,
> container=My Stateless Container)
> 04-Jan-2013 14:11:41 org.apache.openejb.assembler.classic.Assembler
> createApplication
> INFO: Deployed
> Application(path=/home/avrono/TomEE/apache-tomee-plus-1.5.0/webapps/simple-webservice-1.1.0-SNAPSHOT.jar)
> 04-Jan-2013 14:11:41
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean
> buildServiceFromClass
> INFO: Creating Service {http://superbiz.org/wsdl}CalculatorService from
> class org.superbiz.calculator.ws.CalculatorWs
> 04-Jan-2013 14:11:42 org.apache.cxf.endpoint.ServerImpl initDestination
> INFO: Setting the server's publish address to be http://nopath:80
> 04-Jan-2013 14:11:42 org.apache.tomee.catalina.TomcatWebAppBuilder init
> INFO: -
> TomcatWebAppBuilder.init /Calculator
> 04-Jan-2013 14:11:42 org.apache.tomee.catalina.OpenEJBContextConfig
> processAnnotationsUrl
> WARNING: WebAppInfo not found.
> StandardContextInfo{standardContext=StandardEngine[Catalina].StandardHost[localhost].StandardContext[/Calculator]}
> 04-Jan-2013 14:11:42 org.apache.tomee.catalina.OpenEJBContextConfig
> processAnnotationsUrl
> WARNING: WebAppInfo not found.
> StandardContextInfo{standardContext=StandardEngine[Catalina].StandardHost[localhost].StandardContext[/Calculator]}
> 04-Jan-2013 14:11:43 org.apache.tomee.catalina.OpenEJBContextConfig
> processAnnotationsUrl
> WARNING: WebAppInfo not found.
> StandardContextInfo{standardContext=StandardEngine[Catalina].StandardHost[localhost].StandardContext[/Calculator]}
> java.lang.NullPointerException
> at
> org.apache.tomee.catalina.TomcatJndiBuilder.mergeJava(TomcatJndiBuilder.java:247)
> at
> org.apache.tomee.catalina.TomcatJavaJndiBinder.lifecycleEvent(TomcatJavaJndiBinder.java:30)
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
> at
> org.apache.catalina.util.LifecycleB
Re: AW: Passivation capable CDI beans replication across cluster does not work
this issue should be fixed on trunk + it should work without the wrapper property now Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/4 : > Just tested with snapshot 1.5.2-20130104.041348-22: > -Dtomee.session-context.wrapper=http only - no effect > both -Dtomee.session-context.wrapper=http and -Dopenejb.session-context=http > - got exception: > > java.lang.ClassCastException: java.lang.String cannot be cast to > javax.enterprise.context.spi.Contextual > > org.apache.tomee.catalina.cdi.SessionContextBackedByHttpSession.key(SessionContextBackedByHttpSession.java:62) > > org.apache.tomee.catalina.cdi.SessionContextBackedByHttpSession.access$000(SessionContextBackedByHttpSession.java:21) > > org.apache.tomee.catalina.cdi.SessionContextBackedByHttpSession$HttpSessionMap.get(SessionContextBackedByHttpSession.java:223) > > org.apache.tomee.catalina.cdi.SessionContextBackedByHttpSession$HttpSessionMap.putIfAbsent(SessionContextBackedByHttpSession.java:249) > > org.apache.tomee.catalina.cdi.SessionContextBackedByHttpSession$HttpSessionMap.putIfAbsent(SessionContextBackedByHttpSession.java:164) > > org.apache.webbeans.context.AbstractContext.createContextualBag(AbstractContext.java:82) > > org.apache.webbeans.context.AbstractContext.initContextualBag(AbstractContext.java:72) > > org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.initiateBeanBag(NormalScopedBeanInterceptorHandler.java:73) > > org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.(NormalScopedBeanInterceptorHandler.java:62) > > org.apache.webbeans.proxy.ProxyFactory.createInterceptorHandler(ProxyFactory.java:282) > > org.apache.webbeans.proxy.ProxyFactory.createNormalScopedBeanProxy(ProxyFactory.java:225) > > org.apache.webbeans.container.BeanManagerImpl.getReference(BeanManagerImpl.java:850) > > org.apache.webbeans.container.InjectableBeanManager.getReference(InjectableBeanManager.java:135) > > org.apache.myfaces.extensions.cdi.core.api.provider.BeanManagerProvider.getReference(BeanManagerProvider.java:216) > > org.apache.myfaces.extensions.cdi.core.api.provider.BeanManagerProvider.getContextualReference(BeanManagerProvider.java:176) > > org.apache.myfaces.extensions.cdi.jsf2.impl.listener.phase.CodiLifecycleWrapper.broadcastBeforeFacesRequestEvent(CodiLifecycleWrapper.java:157) > > org.apache.myfaces.extensions.cdi.jsf2.impl.listener.phase.CodiLifecycleWrapper.execute(CodiLifecycleWrapper.java:81) > javax.faces.webapp.FacesServlet.service(FacesServlet.java:197) > > -Ursprüngliche Nachricht- > Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] > Gesendet: Freitag, 4. Januar 2013 14:00 > An: users@openejb.apache.org > Betreff: Re: AW: Passivation capable CDI beans replication across cluster > does not work > > did you try adding: > > -Dtomee.session-context.wrapper=http? > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > > 2013/1/4 : >> But Apache CODI uses session to save its Conversation and Window Scopes (and >> I can see relevant attributes in session of first node which are not >> replicated to second node). >> Furthermore CODI scopes are replicated in another application servers which >> uses same technology stack(like IBM Websphere 8). >> >> -Ursprüngliche Nachricht- >> Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] >> Gesendet: Donnerstag, 3. Januar 2013 21:41 >> An: users@openejb.apache.org >> Betreff: Re: AW: Passivation capable CDI beans replication across >> cluster does not work >> >> 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/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 node1 >>> mvn clean package tomee:start -P node2 2. Open index.xhtml in >>> test application context: >>> http://lo
Re: EAR Hot deploy
works fine for me, here my config: $ cat conf/system.properties # /tmp/unpack needs to exist, can be work dir too tomee.unpack.dir=/tmp/unpack openejb.system.apps = false $ cat conf/tomee.xml Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/4 José Luis Cetina : > 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. >> > >> >> 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é Luis Cetina >> >> wrote: >> >> >> >>> Well, this could unpack my ear file (which cotains ejb module + webapp >> >>> modules) dropping my ear file to apps but im getting a >> >>> DuplicateDeploymentIdException. >> >>> >> >>> SEVERE: Unable to deploy collapsed ear in war >> >>> >> >> >> StandardEngine[Catalina].StandardHost[localhost_ear].StandardContext[/myenterprise-ear-1.0-SNAPSHOT] >> >>> org.apache.openejb.DuplicateDeploymentIdException: Application cannot >> be >> >>> deployed as it contains deployment-ids which are in use: app: >> >> >> >> Yeah, definitely don't do that. There's an issue that needs to be fixes >> >> with regards to putting EARs in the webapps/ directory (or any Tomcat >> >> appbase). Once the EAR is unpacked, Tomcat will try to deploy the >> unpacked >> >> EAR as a webapp and this essentially get deployed twice. >> >> >> >> I've done some work in this area, so there are two options: >> >> >> >> 1. [Recommended] In the tomee.xml edit `` to >> be >> >> `` >> >> 2. Use `webapps`, but unpack to a different location by setting the >> >> `tomee.unpack.dir` system property to `work` >> >> >> >> >> >> -David >> >> >> >> >> > >> > >> > -- >> > --- >> > *SCJA. José Luis Cetina* >> > --- >> >>
Re: JDBC connection pool memory leak
ok so can you share a sample reproducing the issue please? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/4 Bjorn Danielsson : > Romain Manni-Bucau wrote: >> >> just to be sure to understand: >> >> in a plain tomcat does StatementFinalizer replace stmt.close() to make >> the leak going away? > > Yes. > > -- > Bjorn Danielsson > Cuspy Code AB
Re: EAR+CODI doesnt work
done -> https://issues.apache.org/jira/browse/TOMEE-701 can you give it another try please? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/4 José Luis Cetina : > 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. >>> > >>> > 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.class); >>> > >>> > I get this error: >>> > >>> > SEVERE: An error occurred while executing [@PostConstruct.] >>> > java.lang.IllegalStateException: Could not find beans for Type=class >>> > com.grupokx.mailing.ejbs.MailingsEnviadosFacade and qualifiers:[] >>> > >>> > This webapp works without problem if i deploy it as a war, im having all >>> > this issues with an ear file. >>> > >>> > What could be? >>> > >>> > >>> > 2012/12/31 Romain Manni-Bucau >>> > >>> > > Forget it >>> > > >>> > > Veto in cdi means ignore the bean in cdi context...that was normal, >>> codi >>> > > manages it itself >>> > > Le 1 janv. 2013 00:28, "José Luis Cetina" a >>> > écrit : >>> > > >>> > > > I will give a try. What do you mean with vetoed? I dont >>> understand. >>> > > > Thanks. >>> > > > El dic 31, 2012 6:29 AM, "Romain Manni-Bucau" < >>> rmannibu...@gmail.com> >>> > > > escribió: >>> > > > >>> > > > > hope https://issues.apache.org/jira/browse/TOMEE-689 will help >>> with >>> > > your >>> > > > > issue >>> > > > > >>> > > > > Romain Manni-Bucau >>> > > > > Twitter: @rmannibucau >>> > > > > Blog: http://rmannibucau.wordpress.com/ >>> > > > > LinkedIn: http://fr.linkedin.com/in/rmannibucau >>> > > > > Github: https://github.com/rmannibucau >>> > > > > >>> > > > > >>> > > > > >>> > > > > 2012/12/31 Romain Manni-Bucau : >>> > > > > > hmm >>> > > > > > >>> > > > > > i looked quickly in codi and it seems jsfphaselistener are >>> vetoed >>> > > > > > >>> > > > > >>> > > > >>> > > >>> > >>> (org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.PhaseListenerExtension#filterJsfPhaseListeners) >>> > > > > > >>> > > > > > so then when trying to create the >>> JsfRequestLifecyclePhaseListener >>> > > > > > using the bean manager to inject fields it is not found (which >>> is >>> > > > > > normal since it is vetoed) >>> > > > > > >>> > > > > > not sure where the issue is here... >>> > > > > > >>> > > > > > Romain Manni-Bucau >>> > > > > > Twitter: @rmannibucau >>> > > > > > Blog: http://rmannibucau.wordpress.com/ >>> > > > > > LinkedIn: http://fr.linkedin.com/in/rmannibucau >>> > > > > > Github: https://github.com/rmannibucau >>> > > > > > >>> > > > > > >>> > > > > > >>> > > > > > 2012/12/28 José Luis Cetina : >>> > > > > >> Well, now TomEE can start, but when you try to use CODI the >>> webapp >>> > > > > >> breakdown. >>> > > > > >> >>> > > > > >> Im only try to use the @ViewAccessScoped a
Re: AW: Passivation capable CDI beans replication across cluster does not work
did you try adding: -Dtomee.session-context.wrapper=http? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/4 : > But Apache CODI uses session to save its Conversation and Window Scopes (and > I can see relevant attributes in session of first node which are not > replicated to second node). > Furthermore CODI scopes are replicated in another application servers which > uses same technology stack(like IBM Websphere 8). > > -Ursprüngliche Nachricht- > Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] > Gesendet: Donnerstag, 3. Januar 2013 21:41 > An: users@openejb.apache.org > Betreff: Re: AW: Passivation capable CDI beans replication across cluster > does not work > > 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/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 node1 >> mvn clean package tomee:start -P node2 2. Open index.xhtml in >> test application context: >> http://localhost:8080/tomee_replication-1.0/index.xhtml >> 3. Check created session in manager application of first node: >> http://localhost:8080/manager/html/sessions >> >> There is parameter with something like this in its name: >> "org.apache.myfaces.extensions.cdi.jsf.impl.scope.conversation.EditableWindowContextManagerProxy" >> 4. Check replicated session in manager application of second node: >> http://localhost:8081/manager/html/sessions >> >> There is no such parameter. >> >> >> >> -Ursprüngliche Nachricht- >> Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] >> Gesendet: Donnerstag, 3. Januar 2013 15:38 >> An: users@openejb.apache.org >> Betreff: Re: Passivation capable CDI beans replication across cluster >> does not work >> >> Hi, >> >> is it possible for you to share a project reproducing it? >> >> the best would be a maven project with the tomee maven plugin >> configured >> >> about failoverservice it is off by default and can be configured on >> trunk ( >> https://issues.apache.org/jira/browse/TOMEE-698) >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> >> 2013/1/2 : >> > cannot load the class >>
Re: JDBC connection pool memory leak
Hi,
great progress!
just to be sure to understand:
in a plain tomcat does StatementFinalizer replace stmt.close() to make
the leak going away?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/1/4 Bjorn Danielsson :
> I just reproduced the memory leak in a plain Tomcat 7.0.34,
> using only JDBC and a Mysql datasource:
>
> InitialContext ctx = new InitialContext();
> DataSource ds = (DataSource) ctx.lookup("java:/comp/env/jdbc/test");
> Connection conn = ds.getConnection();
> PreparedStatement stmt = conn.prepareStatement("SELECT * FROM MYTABLE");
> ResultSet rs = stmt.executeQuery();
> conn.close();
>
> I put the above code in a JSP file, then after each request I
> did "jmap -histo:live 4711 | grep com.mysql.jdbc.JDBC4".
> The numbers increment steadily.
>
> Adding stmt.close() before conn.close() makes the leak go away.
>
> Using jdbcInterceptors="StatementFinalizer" in the pool helps.
> This seems to be the documented way to deal with this. However
> when I tried "StatementFinalizer" in TomEE it had no effect.
> The attribute was recognized, because if I misspelled the value
> I got an error message in TomEE's catalina.out.
>
> With Tomcat and commons-dbcp (the default) it was impossible
> to reproduce the memory leak even when I neglected to close
> the Connection proxy.
>
> I can provide an isolated TomEE example that reproduces the
> problem, but I need to disentangle it from my main project
> code first.
>
> --
> Bjorn Danielsson
> Cuspy Code AB
>
>
> Romain Manni-Bucau wrote:
>> 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 Manni-Bucau
>> Twitter: @rmannibucau
>> Blog: http://rmannibucau.wordpress.com/
>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> Github: https://github.com/rmannibucau
>>
>>
>>
>> 2013/1/3 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 working fine for me, but I think I'm experiencing memory
>>> leaks that are possibly caused by Google Calendar API's use of
>>> threadlocal/etc... No need to discuss that here in this thread.
>>>
>>>
>>> On Thu, Jan 3, 2013 at 1:54 PM, Bjorn Danielsson <
>>> bjorn-apa...@lists.cuspycode.com> wrote:
>>>
>>>> It doesn't matter if I use Eclipselink instead of OpenJPA.
>>>>
>>>> But the memory leak goes away if I change the database from Mysql
>>>> to embedded Derby, so I assume there is some quirkiness in the
>>>> Mysql driver that is involved.
>>>>
Re: Fatal error configuring enricher
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 > 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 adding the enricher (tomee.xml attached) > > ** ** > > INFO: Enterprise application "openejb" loaded. > > 04/01/2013 10:25:36 AM org.apache.openejb.assembler.classic.Assembler > createRecipe > > INFO: Creating Service(id=enricher) > > 04/01/2013 10:25:36 AM org.apache.openejb.util.OpenEJBErrorHandler > handleUnknownError > > SEVERE: FATAL ERROR: Unknown error in Assembler. Please send the > following stack trace and this message to users@openejb.apache.org : > > org.apache.xbean.recipe.ConstructionException: Type class could not be > found: > org.apache.openejb.assembler.classic.AdditionalLibClassLoaderEnricherObserver > > > at > org.apache.xbean.recipe.ObjectRecipe.getType(ObjectRecipe.java:355) > > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:266) > > > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) > > at > org.apache.openejb.assembler.classic.Assembler.createService(Assembler.java:1635) > > > at > org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:407) > > > at > org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:344)** > ** > > at > org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:144) > > at org.apache.openejb.OpenEJB.init(OpenEJB.java:290) > > at > org.apache.tomee.catalina.TomcatLoader.initialize(TomcatLoader.java:233)** > ** > > at > org.apache.tomee.catalina.TomcatLoader.init(TomcatLoader.java:130) > > at > org.apache.tomee.catalina.ServerListener.lifecycleEvent(ServerListener.java:121) > > > at > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) > > > at > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) > > > at > org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402) > > > at > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:110) > > at > org.apache.catalina.startup.Catalina.load(Catalina.java:633) > > at > org.apache.catalina.startup.Catalina.load(Catalina.java:658) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > > at java.lang.reflect.Method.invoke(Method.java:616) > > at > org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:281) > > at > org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:450) > > ** ** > > Thanks, > > ** ** > > Sally MacFarlane > > ** ** > > Application Engineer, > > Enterprise Applications, > > ICT Services, > > *University of Southern Queensland* > > +617 4631 2080 > > ** ** > -- > This email (including any attached files) is confidential and is for the > intended recipient(s) only. If you received this email by mistake, please, > as a courtesy, tell the sender, then delete this email. > > The views and opinions are the originator's and do not necessarily reflect > those of the University of Southern Queensland. Although all reasonable > precautions were taken to ensure that this email contained no viruses at > the time it was sent we accept no liability for any losses arising from its > receipt. > > The University of Southern Queensland is a registered provider of > education with the Australian Government. > (CRICOS Institution Code QLD 00244B / NSW 02225M, TEQSA PRV12081 ) >
Re: JDBC connection pool memory leak
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 Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/3 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 working fine for me, but I think I'm experiencing memory > leaks that are possibly caused by Google Calendar API's use of > threadlocal/etc... No need to discuss that here in this thread. > > > On Thu, Jan 3, 2013 at 1:54 PM, Bjorn Danielsson < > bjorn-apa...@lists.cuspycode.com> wrote: > >> It doesn't matter if I use Eclipselink instead of OpenJPA. >> >> But the memory leak goes away if I change the database from Mysql >> to embedded Derby, so I assume there is some quirkiness in the >> Mysql driver that is involved. >>
Re: AW: Passivation capable CDI beans replication across cluster does not work
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/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 node1 > mvn clean package tomee:start -P node2 > 2. Open index.xhtml in test application context: > http://localhost:8080/tomee_replication-1.0/index.xhtml > 3. Check created session in manager application of first node: > http://localhost:8080/manager/html/sessions > > There is parameter with something like this in its name: > "org.apache.myfaces.extensions.cdi.jsf.impl.scope.conversation.EditableWindowContextManagerProxy" > 4. Check replicated session in manager application of second node: > http://localhost:8081/manager/html/sessions > > There is no such parameter. > > > > -Ursprüngliche Nachricht- > Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] > Gesendet: Donnerstag, 3. Januar 2013 15:38 > An: users@openejb.apache.org > Betreff: Re: Passivation capable CDI beans replication across cluster does > not work > > Hi, > > is it possible for you to share a project reproducing it? > > the best would be a maven project with the tomee maven plugin configured > > about failoverservice it is off by default and can be configured on trunk ( > https://issues.apache.org/jira/browse/TOMEE-698) > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > > 2013/1/2 : > > cannot load the class >
Re: EAR+CODI doesnt work
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 this: > > facade = > > BeanManagerProvider.getInstance().getContextualReference(MailingsEnviadosFacade.class); > > I get this error: > > SEVERE: An error occurred while executing [@PostConstruct.] > java.lang.IllegalStateException: Could not find beans for Type=class > com.grupokx.mailing.ejbs.MailingsEnviadosFacade and qualifiers:[] > > This webapp works without problem if i deploy it as a war, im having all > this issues with an ear file. > > What could be? > > > 2012/12/31 Romain Manni-Bucau > > > Forget it > > > > Veto in cdi means ignore the bean in cdi context...that was normal, codi > > manages it itself > > Le 1 janv. 2013 00:28, "José Luis Cetina" a > écrit : > > > > > I will give a try. What do you mean with vetoed? I dont understand. > > > Thanks. > > > El dic 31, 2012 6:29 AM, "Romain Manni-Bucau" > > > escribió: > > > > > > > hope https://issues.apache.org/jira/browse/TOMEE-689 will help with > > your > > > > issue > > > > > > > > Romain Manni-Bucau > > > > Twitter: @rmannibucau > > > > Blog: http://rmannibucau.wordpress.com/ > > > > LinkedIn: http://fr.linkedin.com/in/rmannibucau > > > > Github: https://github.com/rmannibucau > > > > > > > > > > > > > > > > 2012/12/31 Romain Manni-Bucau : > > > > > hmm > > > > > > > > > > i looked quickly in codi and it seems jsfphaselistener are vetoed > > > > > > > > > > > > > > > (org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.PhaseListenerExtension#filterJsfPhaseListeners) > > > > > > > > > > so then when trying to create the JsfRequestLifecyclePhaseListener > > > > > using the bean manager to inject fields it is not found (which is > > > > > normal since it is vetoed) > > > > > > > > > > not sure where the issue is here... > > > > > > > > > > Romain Manni-Bucau > > > > > Twitter: @rmannibucau > > > > > Blog: http://rmannibucau.wordpress.com/ > > > > > LinkedIn: http://fr.linkedin.com/in/rmannibucau > > > > > Github: https://github.com/rmannibucau > > > > > > > > > > > > > > > > > > > > 2012/12/28 José Luis Cetina : > > > > >> Well, now TomEE can start, but when you try to use CODI the webapp > > > > >> breakdown. > > > > >> > > > > >> Im only try to use the @ViewAccessScoped annotation and i get the > > > > following > > > > >> error: > > > > >> > > > > >> javax.servlet.ServletException: No bean found for type: > > > > >> > > > > > > > > > > org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster > > > > >> and name jsfRequestLifecycleBroadcaster > > > > >> javax.faces.webapp.FacesServlet.service(FacesServlet.java:229) > > > > >> root cause > > > > >> > > > > >> java.lang.IllegalStateException: No bean found for type: > > > > >> > > > > > > > > > > org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster > > > > >> and name jsfRequestLifecycleBroadcaster > > > > >> > > > > > > > > > > org.apache.myfaces.extensions.cdi.core.impl.util.CodiUtils.getContextualReferenceByName(CodiUtils.java:109) > > > > >> > > > > > > > > > > org.apache.myfaces.extensions.cdi.core.impl.util.CodiUtils.getContextualReferenceByName(CodiUtils.java:83) > > > > >> > > > > > > > > > > org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener.resolveBroadcaster(JsfRequestLifecyclePhaseListener.java:70) > > > > >> > > > > > > > > > > org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener.beforePhase(JsfRequestLifecyclePhaseListener.java:56) > > > > &g
Re: How to package an EJB3.1 WebService in an EAR
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: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/3 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: > http://openejb.979440.n4.nabble.com/How-to-package-an-EJB3-1-WebService-in-an-EAR-tp4659793p4660042.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: tomee+ 1.5.1 : datasource creation failed with an empty UserName
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.com/rmannibucau 2013/1/3 Simon Renard : > DataSourceProxy
Re: JAX-RS webservices do not work on TomEE if webapp context is "/"
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.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/2 zeeman : > Somehow github was not getting latest pom.xml > > Could you please sync my test project https://github.com/z00 and try again. > I can reproduce the issue with snapshot. > > I configure Tomee snapshot in pom.xml from tomee maven plugin. > > Thanks! > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/JAX-RS-webservices-do-not-work-on-TomEE-if-webapp-context-is-tp4659047p4660024.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: JAX-RS webservices do not work on TomEE if webapp context is "/"
I wasnt with 1.5.2 snapshot Le 2 janv. 2013 10:27, "zeeman" a écrit : > I have already updated it https://github.com/z00 > You should be able to reproduce it with 1.5.1 release. > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/JAX-RS-webservices-do-not-work-on-TomEE-if-webapp-context-is-tp4659047p4660008.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
Re: JAX-RS webservices do not work on TomEE if webapp context is "/"
With your sample i get issues with seam, can you update it please? I have an idea of the issue, will look tomorrow Le 2 janv. 2013 00:21, "zeeman" a écrit : > Thanks for looking into this. I have same kept the same Eclipse (3.7). If I > use Tomee 1.5.1 or snapshot I get "can't find path under current webapp > deployment" error. If I revert to Tomee 1.5.0 everything works fine. > > The only variable that changed here is Tomee, not eclipse. > > If I can take the war, deploy it outside of Eclipse in Tomee, it works > fine. > So there is something between Eclipse and Tomee 1.5.1 that's causing this. > Latest stack trace is below: > > > SEVERE: A child container failed during start > java.util.concurrent.ExecutionException: > org.apache.catalina.LifecycleException: Failed to start component > [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]] > at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source) > at java.util.concurrent.FutureTask.get(Unknown Source) > at > > org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1123) > at > org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:800) > at > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at > > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) > at > > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549) > at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) > at java.util.concurrent.FutureTask.run(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown > Source) > at java.lang.Thread.run(Unknown Source) > Caused by: org.apache.catalina.LifecycleException: Failed to start > component > [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]] > at > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) > ... 7 more > Caused by: java.lang.IllegalArgumentException: can't find path under > current > webapp deployment [] > at > > org.apache.tomee.catalina.OpenEJBContextConfig.processAnnotationsUrl(OpenEJBContextConfig.java:297) > at > > org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1306) > at > > org.apache.tomee.catalina.OpenEJBContextConfig.webConfig(OpenEJBContextConfig.java:188) > at > > org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878) > at > > org.apache.tomee.catalina.OpenEJBContextConfig.configureStart(OpenEJBContextConfig.java:76) > at > > org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:369) > at > > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) > at > > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) > at > > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5173) > at > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > ... 7 more > Jan 1, 2013 7:15:15 PM org.apache.catalina.core.ContainerBase startInternal > SEVERE: A child container failed during start > java.util.concurrent.ExecutionException: > org.apache.catalina.LifecycleException: Failed to start component > [StandardEngine[Catalina].StandardHost[localhost]] > at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source) > at java.util.concurrent.FutureTask.get(Unknown Source) > at > > org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1123) > at > > org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:302) > at > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at > > org.apache.catalina.core.StandardService.startInternal(StandardService.java:443) > at > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at > > org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:732) > at > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at org.apache.catalina.startup.Catalina.start(Catalina.java:684) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:322) > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:451) > Caused by: org.apache.catalina.LifecycleException: Failed to start > component > [StandardEngine[Catalina].StandardHost[localhost]] > at > org.apache.catalina.util.LifecycleBase.start(Lifec
Re: JAX-RS webservices do not work on TomEE if webapp context is "/"
did you read https://bugs.eclipse.org/bugs/show_bug.cgi?id=145701? seems a kind of bug in wtp Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/31 zeeman : > Whenver I remove webapps/ROOT, eclipse recreate is when I publish. ROOT only > has an empty WEB-INF/web.xml in it. Do I need to turn that off somewhere? I > don't know why eclipse is creating it. > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/JAX-RS-webservices-do-not-work-on-TomEE-if-webapp-context-is-tp4659047p4659989.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: How do i deploy a ManagedConnectionFactory in a war file?
Hi, Did you try to put it in an ear instead of war directly? Le 1 janv. 2013 00:46, "Anthony Fryer" a écrit : > I have a jar file that contains all the JCA implementation classes > including > ResourceAdapter and ManagedConnectionFactory implementation classes. In > that jar file project, when i run my test cases with tomee, i get the > following printed out to the console that shows the classes being detected > by tomee and resources being created... > > INFO - Found ConnectorModule in classpath: > > d:\users\anthony\documents\dev\sabreresourceadapter\sabre-resource-adapter\sabre-ra-jca\target\test-classes > INFO - Beginning load: > > d:\users\anthony\documents\dev\sabreresourceadapter\sabre-resource-adapter\sabre-ra-jca\target\test-classes > INFO - Configuring enterprise application: > > D:\Users\Anthony\Documents\DEV\SabreResourceAdapter\sabre-resource-adapter\sabre-ra-jca > WARNING - Method 'lookup' is not available for 'javax.annotation.Resource'. > Probably using an older Runtime. > INFO - Configuring Service(id=Default Managed Container, type=Container, > provider-id=Default Managed Container) > INFO - Auto-creating a container for bean > com.virginaustralia.sabre.jca.MultiUserConnectionPoolTest: > Container(type=MANAGED, id=Default Managed Container) > INFO - Creating Container(id=Default Managed Container) > INFO - Using directory D:\Users\Anthony\AppData\Local\Temp for stateful > session passivation > INFO - Auto-linking resource-ref 'java:comp/env/eis/sabre/91' in bean > com.virginaustralia.sabre.jca.MultiUserConnectionPoolTest to > Resource(id=eis/sabre/91) > INFO - Dumping Generated ra.xml to: > D:\Users\Anthony\AppData\Local\Temp\ra-9057826138595557674sabre-ra-jca.xml > INFO - Configuring Service(id=sabre-ra-jcaRA, type=Resource, > provider-id=sabre-ra-jcaRA) > INFO - Configuring Service(id=eis/sabre/91, type=Resource, > provider-id=eis/sabre/91) > > In my webapp, i have that jar as a dependency and have created a ra.xml > file > and put it in the WEB-INF folder. When I startup tomee for the webapp i > don't see any log messages in the console that indicate the ResourceAdapter > and ManagedConnectionFactory have been found and created by tomee. How > exactly should i package this resource adapter up in my war file? Should I > be putting a .rar file in WEB-INF/lib instead of just the .jar file? Where > should i put the ra.xml file? > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/How-do-i-deploy-a-ManagedConnectionFactory-in-a-war-file-tp4659993.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
Re: EAR+CODI doesnt work
Forget it Veto in cdi means ignore the bean in cdi context...that was normal, codi manages it itself Le 1 janv. 2013 00:28, "José Luis Cetina" a écrit : > I will give a try. What do you mean with vetoed? I dont understand. > Thanks. > El dic 31, 2012 6:29 AM, "Romain Manni-Bucau" > escribió: > > > hope https://issues.apache.org/jira/browse/TOMEE-689 will help with your > > issue > > > > Romain Manni-Bucau > > Twitter: @rmannibucau > > Blog: http://rmannibucau.wordpress.com/ > > LinkedIn: http://fr.linkedin.com/in/rmannibucau > > Github: https://github.com/rmannibucau > > > > > > > > 2012/12/31 Romain Manni-Bucau : > > > hmm > > > > > > i looked quickly in codi and it seems jsfphaselistener are vetoed > > > > > > (org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.PhaseListenerExtension#filterJsfPhaseListeners) > > > > > > so then when trying to create the JsfRequestLifecyclePhaseListener > > > using the bean manager to inject fields it is not found (which is > > > normal since it is vetoed) > > > > > > not sure where the issue is here... > > > > > > Romain Manni-Bucau > > > Twitter: @rmannibucau > > > Blog: http://rmannibucau.wordpress.com/ > > > LinkedIn: http://fr.linkedin.com/in/rmannibucau > > > Github: https://github.com/rmannibucau > > > > > > > > > > > > 2012/12/28 José Luis Cetina : > > >> Well, now TomEE can start, but when you try to use CODI the webapp > > >> breakdown. > > >> > > >> Im only try to use the @ViewAccessScoped annotation and i get the > > following > > >> error: > > >> > > >> javax.servlet.ServletException: No bean found for type: > > >> > > > org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster > > >> and name jsfRequestLifecycleBroadcaster > > >> javax.faces.webapp.FacesServlet.service(FacesServlet.java:229) > > >> root cause > > >> > > >> java.lang.IllegalStateException: No bean found for type: > > >> > > > org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster > > >> and name jsfRequestLifecycleBroadcaster > > >> > > > org.apache.myfaces.extensions.cdi.core.impl.util.CodiUtils.getContextualReferenceByName(CodiUtils.java:109) > > >> > > > org.apache.myfaces.extensions.cdi.core.impl.util.CodiUtils.getContextualReferenceByName(CodiUtils.java:83) > > >> > > > org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener.resolveBroadcaster(JsfRequestLifecyclePhaseListener.java:70) > > >> > > > org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener.beforePhase(JsfRequestLifecyclePhaseListener.java:56) > > >> > > > org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersBefore(PhaseListenerManager.java:77) > > >> > > > org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:158) > > >> > > > org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) > > >> > > > org.apache.myfaces.extensions.cdi.jsf2.impl.listener.phase.CodiLifecycleWrapper.execute(CodiLifecycleWrapper.java:95) > > >> javax.faces.webapp.FacesServlet.service(FacesServlet.java:197 > > >> > > >> > > >> You can get the update of the project from > > >> https://github.com/maxtorzito/tomee-tests > > >> > > >> > > >> > > >> > > >> 2012/12/28 José Luis Cetina > > >> > > >>> Now it works. Thanks Romain > > >>> > > >>> > > >>> 2012/12/23 José Luis Cetina > > >>> > > >>>> Ok. I will try tomorrow and let you know rhe results. Thanks > > >>>> El dic 23, 2012 9:30 AM, "Romain Manni-Bucau" < > rmannibu...@gmail.com> > > >>>> escribió: > > >>>> > > >>>> yes: > > >>>>> > > >>>>> $ ls > > >>>>> > > > apps/myenterprise-ear-1.0-SNAPSHOT/myenterprise-web-1.0-SNAPSHOT/WEB-INF/lib/ > > >>>>> myfaces-extcdi-core-api-1.0.5.jar > > >>>>> myfaces-extcdi-jsf20-module-api-1.0.5.jar > > >>>>> myfaces-extcdi-message
Re: EAR+CODI doesnt work
hope https://issues.apache.org/jira/browse/TOMEE-689 will help with your issue Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/31 Romain Manni-Bucau : > hmm > > i looked quickly in codi and it seems jsfphaselistener are vetoed > (org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.PhaseListenerExtension#filterJsfPhaseListeners) > > so then when trying to create the JsfRequestLifecyclePhaseListener > using the bean manager to inject fields it is not found (which is > normal since it is vetoed) > > not sure where the issue is here... > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > > 2012/12/28 José Luis Cetina : >> Well, now TomEE can start, but when you try to use CODI the webapp >> breakdown. >> >> Im only try to use the @ViewAccessScoped annotation and i get the following >> error: >> >> javax.servlet.ServletException: No bean found for type: >> org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster >> and name jsfRequestLifecycleBroadcaster >> javax.faces.webapp.FacesServlet.service(FacesServlet.java:229) >> root cause >> >> java.lang.IllegalStateException: No bean found for type: >> org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster >> and name jsfRequestLifecycleBroadcaster >> org.apache.myfaces.extensions.cdi.core.impl.util.CodiUtils.getContextualReferenceByName(CodiUtils.java:109) >> org.apache.myfaces.extensions.cdi.core.impl.util.CodiUtils.getContextualReferenceByName(CodiUtils.java:83) >> org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener.resolveBroadcaster(JsfRequestLifecyclePhaseListener.java:70) >> org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener.beforePhase(JsfRequestLifecyclePhaseListener.java:56) >> org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersBefore(PhaseListenerManager.java:77) >> org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:158) >> org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) >> org.apache.myfaces.extensions.cdi.jsf2.impl.listener.phase.CodiLifecycleWrapper.execute(CodiLifecycleWrapper.java:95) >> javax.faces.webapp.FacesServlet.service(FacesServlet.java:197 >> >> >> You can get the update of the project from >> https://github.com/maxtorzito/tomee-tests >> >> >> >> >> 2012/12/28 José Luis Cetina >> >>> Now it works. Thanks Romain >>> >>> >>> 2012/12/23 José Luis Cetina >>> >>>> Ok. I will try tomorrow and let you know rhe results. Thanks >>>> El dic 23, 2012 9:30 AM, "Romain Manni-Bucau" >>>> escribió: >>>> >>>> yes: >>>>> >>>>> $ ls >>>>> apps/myenterprise-ear-1.0-SNAPSHOT/myenterprise-web-1.0-SNAPSHOT/WEB-INF/lib/ >>>>> myfaces-extcdi-core-api-1.0.5.jar >>>>> myfaces-extcdi-jsf20-module-api-1.0.5.jar >>>>> myfaces-extcdi-message-module-api-1.0.5.jar >>>>> myfaces-extcdi-core-impl-1.0.5.jar >>>>> myfaces-extcdi-jsf20-module-impl-1.0.5.jar >>>>> myfaces-extcdi-message-module-impl-1.0.5.jar >>>>> >>>>> Romain Manni-Bucau >>>>> Twitter: @rmannibucau >>>>> Blog: http://rmannibucau.wordpress.com/ >>>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau >>>>> Github: https://github.com/rmannibucau >>>>> >>>>> >>>>> >>>>> 2012/12/22 José Luis Cetina : >>>>> > Do you uncomment the codi dependencies lines in pom.xml? >>>>> > El dic 22, 2012 12:37 PM, "Romain Manni-Bucau" >>>>> > escribió: >>>>> > >>>>> >> Hi José, >>>>> >> >>>>> >> just tested again on trunk and it starts without issues for me >>>>> >> >>>>> >> did you try the snapshot (on apache repo), think it is deployed now. >>>>> >> >>>>> >> Romain Manni-Bucau >>>>> >> Twitter: @rmannibucau >>>>> >> Blog: http://rmannibucau.wordpress.com/ >
Re: EAR+CODI doesnt work
hmm i looked quickly in codi and it seems jsfphaselistener are vetoed (org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.PhaseListenerExtension#filterJsfPhaseListeners) so then when trying to create the JsfRequestLifecyclePhaseListener using the bean manager to inject fields it is not found (which is normal since it is vetoed) not sure where the issue is here... Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/28 José Luis Cetina : > Well, now TomEE can start, but when you try to use CODI the webapp > breakdown. > > Im only try to use the @ViewAccessScoped annotation and i get the following > error: > > javax.servlet.ServletException: No bean found for type: > org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster > and name jsfRequestLifecycleBroadcaster > javax.faces.webapp.FacesServlet.service(FacesServlet.java:229) > root cause > > java.lang.IllegalStateException: No bean found for type: > org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster > and name jsfRequestLifecycleBroadcaster > org.apache.myfaces.extensions.cdi.core.impl.util.CodiUtils.getContextualReferenceByName(CodiUtils.java:109) > org.apache.myfaces.extensions.cdi.core.impl.util.CodiUtils.getContextualReferenceByName(CodiUtils.java:83) > org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener.resolveBroadcaster(JsfRequestLifecyclePhaseListener.java:70) > org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener.beforePhase(JsfRequestLifecyclePhaseListener.java:56) > org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersBefore(PhaseListenerManager.java:77) > org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:158) > org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) > org.apache.myfaces.extensions.cdi.jsf2.impl.listener.phase.CodiLifecycleWrapper.execute(CodiLifecycleWrapper.java:95) > javax.faces.webapp.FacesServlet.service(FacesServlet.java:197 > > > You can get the update of the project from > https://github.com/maxtorzito/tomee-tests > > > > > 2012/12/28 José Luis Cetina > >> Now it works. Thanks Romain >> >> >> 2012/12/23 José Luis Cetina >> >>> Ok. I will try tomorrow and let you know rhe results. Thanks >>> El dic 23, 2012 9:30 AM, "Romain Manni-Bucau" >>> escribió: >>> >>> yes: >>>> >>>> $ ls >>>> apps/myenterprise-ear-1.0-SNAPSHOT/myenterprise-web-1.0-SNAPSHOT/WEB-INF/lib/ >>>> myfaces-extcdi-core-api-1.0.5.jar >>>> myfaces-extcdi-jsf20-module-api-1.0.5.jar >>>> myfaces-extcdi-message-module-api-1.0.5.jar >>>> myfaces-extcdi-core-impl-1.0.5.jar >>>> myfaces-extcdi-jsf20-module-impl-1.0.5.jar >>>> myfaces-extcdi-message-module-impl-1.0.5.jar >>>> >>>> Romain Manni-Bucau >>>> Twitter: @rmannibucau >>>> Blog: http://rmannibucau.wordpress.com/ >>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau >>>> Github: https://github.com/rmannibucau >>>> >>>> >>>> >>>> 2012/12/22 José Luis Cetina : >>>> > Do you uncomment the codi dependencies lines in pom.xml? >>>> > El dic 22, 2012 12:37 PM, "Romain Manni-Bucau" >>>> > escribió: >>>> > >>>> >> Hi José, >>>> >> >>>> >> just tested again on trunk and it starts without issues for me >>>> >> >>>> >> did you try the snapshot (on apache repo), think it is deployed now. >>>> >> >>>> >> Romain Manni-Bucau >>>> >> Twitter: @rmannibucau >>>> >> Blog: http://rmannibucau.wordpress.com/ >>>> >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >>>> >> Github: https://github.com/rmannibucau >>>> >> >>>> >> >>>> >> >>>> >> 2012/12/20 José Luis Cetina : >>>> >> > If you create an ear file with an ejb module + web app module (with >>>> CODI >>>> >> > dependencies) it doesnt work. >>>> >> > >>>> >> > Here is the sample: >>>> >> > https://github.com/maxtorzito/tomee-tests/tree/master/myenterprise >>>> >> > >>>> >> > >>>> >> > In the sample i
Re: JAX-RS webservices do not work on TomEE if webapp context is "/"
can you try removing root please? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/31 zeeman : > Yes, in webapps. I have 2 folders under webapps, ROOT and sportivity. From > Eclipse, I sat context path to / > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/JAX-RS-webservices-do-not-work-on-TomEE-if-webapp-context-is-tp4659047p4659967.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Is TomEE 1.5.2 SNAPSHOT persistence across restarts working as designed?
Oh got it Depend on the conf but AFAIK thats not linked to start stop but more to time (see passivation) Le 30 déc. 2012 22:03, "Howard W. Smith, Jr." a écrit : > Interesting, okay, thanks for the clarification. > > I attempted to use @Stateful in this manner, because i remember, a while > ago, while using 1.5.1 SNAPSHOT, @Stateful bean would persist across > restarts, as it was the first time I attempted to use @Stateful, but I > think I don't see that same behavior in 1.5.2 SNAPSHOT, so I can change my > implementation and not rely on @Stateful. > > Thanks. :) > > > On Sun, Dec 30, 2012 at 4:59 PM, Romain Manni-Bucau > wrote: > > > No more =no more than that (dont expect more) > > > > @sessionscoped. Stateful are different and can even be requestscoped so > why > > saving them by default? > > >
Re: JAX-RS webservices do not work on TomEE if webapp context is "/"
Just to be sure: did you keep root app in webapps/? Le 28 déc. 2012 07:39, "zeeman" a écrit : > Update: > > I updated Eclipse and plugins and using / context root from Eclipse still > does not work with 1.5.1 and the snapshot. > > The sample project link above should let you reproduce it. > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/JAX-RS-webservices-do-not-work-on-TomEE-if-webapp-context-is-tp4659047p4659912.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
Re: Is TomEE 1.5.2 SNAPSHOT persistence across restarts working as designed?
No more =no more than that (dont expect more) @sessionscoped. Stateful are different and can even be requestscoped so why saving them by default? Le 30 déc. 2012 21:57, "Howard W. Smith, Jr." a écrit : > but no more = no longer a feature of TomEE > > sessionscoped beans = @SessionScoped or @Stateful, or both? > > On Sun, Dec 30, 2012 at 4:49 PM, Romain Manni-Bucau > wrote: > > > Basically only tomcat session is persisted. Now sessionscoped beans > should > > be too when existing but no more > > >
Re: Is TomEE 1.5.2 SNAPSHOT persistence across restarts working as designed?
Basically only tomcat session is persisted. Now sessionscoped beans should
be too when existing but no more
Le 30 déc. 2012 16:30, "Howard W. Smith, Jr." a
écrit :
> Is TomEE 1.5.2 SNAPSHOT persistence across restarts working as designed? I
> know this is a Tomcat7 feature, but maybe I'm missing something in my code.
> My CDI @ApplicationScoped bean references @Stateful EJB in @PostConstruct
> and @Predestroy to read and write data. The @PreDestroy code works as
> designed, but the @PostConstruct code never executes or shows up in the
> log. What am I missing? Please see below.
>
> Below is code in CDI @ApplicationScoped @PostConstruct and @PreDestroy
>
> @PostConstruct
> public void init() {
> tripDatesInQueueForGoogleCalendarUpdate = null;
> if
>
> (applicationStatefulSessionBean.getTripDatesInQueueForGoogleCalendarUpdate()
> != null &&
>
>
> !applicationStatefulSessionBean.getTripDatesInQueueForGoogleCalendarUpdate().isEmpty())
> {
>
> tripDatesInQueueForGoogleCalendarUpdate =
> applicationStatefulSessionBean.
>
> getTripDatesInQueueForGoogleCalendarUpdate();
> log("ApplicationScopeBean.init():
> tripDatesInQueueForGoogleCalendarUpdate = " +
>
>
> "applicationStatefulSessionBean.getTripDatesInQueueForGoogleCalendarUpdate()
> completed; " +
> "tripDatesInQueueForGoogleCalendarUpdate.size() = " +
> tripDatesInQueueForGoogleCalendarUpdate.size());
> }
>
> }
>
> @PreDestroy
> private void destroy() {
> log("ApplicationScopeBean.destroy() invoked");
> if (tripDatesInQueueForGoogleCalendarUpdate != null &&
> !tripDatesInQueueForGoogleCalendarUpdate.isEmpty()) {
> String queue = "";
> for (Date d : tripDatesInQueueForGoogleCalendarUpdate) {
> if (queue.length() > 0) {
> queue += ", ";
> }
> queue += new DateTime(d).toString("MM/dd/");
> }
> log("ApplicationScopeBean.destroy():
> tripDatesInQueueForGoogleCalendarUpdate include " + queue);
>
> applicationStatefulSessionBean.
>
>
> setTripDatesInQueueForGoogleCalendarUpdate(tripDatesInQueueForGoogleCalendarUpdate);
>
> log("ApplicationScopeBean.destroy():
> applicationStatefulSessionBean." +
>
>
> "setTripDatesInQueueForGoogleCalendarUpdate(tripDatesInQueueForGoogleCalendarUpdate)
> " +
> "completed; tripDatesInQueueForGoogleCalendarUpdate.size()
> = " +
> tripDatesInQueueForGoogleCalendarUpdate.size());
> }
> }
>
>
>
> Below is the @Stateful bean
>
> /*
> * To change this template, choose Tools | Templates
> * and open the template in the editor.
> */
> package pf;
>
> import java.io.Serializable;
>
> import java.util.Date;
> import java.util.List;
>
> import javax.ejb.Stateful;
>
> /**
> *
> * @author Administrator
> *
> *
>
> http://stackoverflow.com/questions/5387267/persisting-session-of-tomcat-server-application-between-re-deploymets-from-myecl
> *
>
> http://tomcat.apache.org/tomcat-7.0-doc/config/manager.html#Persistence_Across_Restarts
> */
> @Stateful
> public class ApplicationStatefulSessionBean implements Serializable {
>
> private List tripDatesInQueueForGoogleCalendarUpdate;
>
> public List getTripDatesInQueueForGoogleCalendarUpdate() {
> return tripDatesInQueueForGoogleCalendarUpdate;
> }
>
> public void setTripDatesInQueueForGoogleCalendarUpdate(List
> tripDatesInQueueForGoogleCalendarUpdate) {
> this.tripDatesInQueueForGoogleCalendarUpdate =
> tripDatesInQueueForGoogleCalendarUpdate;
> }
>
> }
>
Re: JAX-RS webservices do not work on TomEE if webapp context is "/"
Tomee webapp can be removed with another attribute (cant remember the exact name right now). Le 27 déc. 2012 13:27, "zeeman" a écrit : > I tried with the 1.5.2 snapshot. Still the same exact error. If I don't > use / > as root context things work fine from eclipse. > > So it looks like something broke it in 1.5.1 release and forward when it > comes to using / as context root. > > If I revert things work fine, so must be something must have changed. > > I update my test project https://github.com/z00 > > you can get Tomee by running the plugin and test with / > > BTW, mvn plugin no longer deletes tomee folder under webapps. I have > removeDefaultWebapps = true. > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/JAX-RS-webservices-do-not-work-on-TomEE-if-webapp-context-is-tp4659047p4659905.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
Re: JAX-RS webservices do not work on TomEE if webapp context is "/"
Hi, Well please try the snapshot to be sure it wasnt fixed then if it doesnt work please share something reproducing it since it worked last time i tried so thats hard to work on it for us Le 27 déc. 2012 05:44, "zeeman" a écrit : > Hi Romain, > > I have the same exact issue with 1.5.1 release (final one). I downloaded > today. I cannot start Tomee from Eclipse. > > In my Eclipse server.xml: > > source="org.eclipse.jst.jee.server:sportivity"/> > > With 1.5.0 it used to work fine with Eclipse. I'm blocked on this, > otherwise, I have to revert to old one. > > Thanks! > Z > > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/JAX-RS-webservices-do-not-work-on-TomEE-if-webapp-context-is-tp4659047p4659897.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
Re: naming conventions
IIRC wicket application can be seens as a kind of page factory so with deltaspike that s easy to integrate both (a bit like pax did for blueprint) Le 25 déc. 2012 01:28, "Ron Smits" a écrit : > That will be the next part currently I am using > http://jeff-schwartz.blogspot.nl/2011/03/java-ee6-wicket.html just to see > how much change I have to make to make it work. > Also wicket-cdi is weld based.. > > I Haven't Lost My Mind - It's Backed Up On Disk Somewhere > > > On Tue, Dec 25, 2012 at 1:26 AM, Romain Manni-Bucau > wrote: > > > +1 > > > > That said i'd use wicket cdi instead of an ejb integration > > > > Wdyt? > > Le 24 déc. 2012 22:22, "John D. Ament" a écrit > : > > > > > EJB 3.1 introduced standardized naming conventions. The best one to > use > > is > > > the one that matches: > > > > > > > > > java:global[/]//# > > > > > > > > > On Mon, Dec 24, 2012 at 3:15 PM, Ron Smits > wrote: > > > > > > > Evening > > > > > > > > Been playing with tomee and wicket. I had quite a hard time getting > > > wicket > > > > to play nice with EJB's because it could not use the right naming > > > strategy. > > > > Apparently tomee publishes EJB's with two names: > > > > -- > > > > HelloEJB!ejb.HelloEJB > > > > org.apache.openejb.core.ivm.naming.BusinessLocalBeanReference > > > > HelloEJB > org.apache.openejb.core.ivm.naming.BusinessLocalBeanReference > > > > > > > > they are available from "java:global/tomee" context where tomee is > the > > > name > > > > of the project I am working on. there is an easy solution for with > the > > > > wicket javaee-inject module. but what would be the best jndi name to > > use? > > > > My 'guess' would be the first one as it is likely to be more unique. > > > > > > > > comments? > > > > > > > > Ron > > > > I Haven't Lost My Mind - It's Backed Up On Disk Somewhere > > > > > > > > > >
Re: naming conventions
+1 That said i'd use wicket cdi instead of an ejb integration Wdyt? Le 24 déc. 2012 22:22, "John D. Ament" a écrit : > EJB 3.1 introduced standardized naming conventions. The best one to use is > the one that matches: > > java:global[/]//# > > > On Mon, Dec 24, 2012 at 3:15 PM, Ron Smits wrote: > > > Evening > > > > Been playing with tomee and wicket. I had quite a hard time getting > wicket > > to play nice with EJB's because it could not use the right naming > strategy. > > Apparently tomee publishes EJB's with two names: > > -- > > HelloEJB!ejb.HelloEJB > > org.apache.openejb.core.ivm.naming.BusinessLocalBeanReference > > HelloEJB org.apache.openejb.core.ivm.naming.BusinessLocalBeanReference > > > > they are available from "java:global/tomee" context where tomee is the > name > > of the project I am working on. there is an easy solution for with the > > wicket javaee-inject module. but what would be the best jndi name to use? > > My 'guess' would be the first one as it is likely to be more unique. > > > > comments? > > > > Ron > > I Haven't Lost My Mind - It's Backed Up On Disk Somewhere > > >
Re: TomEE doesn't persist @SessionScoped beans?
FYI: openejb.session-context=http will make it active on trunk: https://issues.apache.org/jira/browse/TOMEE-676 Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/19 Romain Manni-Bucau : > remove the correctly and we agree ;) (joking) > > well JBoss persists stateful with extended entitymanagers too...no > exception but it doesn't work... > > maybe open a jira on issues.apache.org, will be easier to track this feature > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > > 2012/12/19 bibhas : >> Thanks Romain, for the clarification. >> >> By the way, if this matters to anyone, I tested out with JBoss AS 7. It >> correctly persists session scoped CDI managed beans, once persistence is >> enabled for Tomcat. >> >> >> >> -- >> View this message in context: >> http://openejb.979440.n4.nabble.com/TomEE-doesn-t-persist-SessionScoped-beans-tp4659814p4659830.html >> Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: EAR+CODI doesnt work
yes: $ ls apps/myenterprise-ear-1.0-SNAPSHOT/myenterprise-web-1.0-SNAPSHOT/WEB-INF/lib/ myfaces-extcdi-core-api-1.0.5.jar myfaces-extcdi-jsf20-module-api-1.0.5.jar myfaces-extcdi-message-module-api-1.0.5.jar myfaces-extcdi-core-impl-1.0.5.jar myfaces-extcdi-jsf20-module-impl-1.0.5.jar myfaces-extcdi-message-module-impl-1.0.5.jar Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/22 José Luis Cetina : > Do you uncomment the codi dependencies lines in pom.xml? > El dic 22, 2012 12:37 PM, "Romain Manni-Bucau" > escribió: > >> Hi José, >> >> just tested again on trunk and it starts without issues for me >> >> did you try the snapshot (on apache repo), think it is deployed now. >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> >> 2012/12/20 José Luis Cetina : >> > If you create an ear file with an ejb module + web app module (with CODI >> > dependencies) it doesnt work. >> > >> > Here is the sample: >> > https://github.com/maxtorzito/tomee-tests/tree/master/myenterprise >> > >> > >> > In the sample if you deploy the ear in apps folder it runs, but if you >> > uncomment the CODI dependencies it wont deploy. >> > >> > I tried with the last snapshot (today) and i build a new TomEE from trunk >> > as Romain suggest me, but i have the same problem. >> > >> > >> > Log file: >> > >> > SEVERE: CDI Beans module deployment failed >> > javax.enterprise.inject.UnsatisfiedResolutionException: Api type >> > >> [org.apache.myfaces.extensions.cdi.jsf.impl.security.spi.SecurityStrategy] >> > is not found with the qualifiers >> > Qualifiers: [@javax.enterprise.inject.Default()] >> > for injection into Field Injection Point, field name : securityStrategy, >> > Bean Owner : [SecurityInterceptor, Name:null, WebBeans Type:MANAGED, API >> > >> Types:[org.apache.myfaces.extensions.cdi.jsf.impl.security.SecurityInterceptor,java.lang.Object,java.io.Serializable], >> > Qualifiers:[javax.enterprise.inject.Any,javax.enterprise.inject.Default]] >> > at >> > >> org.apache.webbeans.util.InjectionExceptionUtils.throwUnsatisfiedResolutionException(InjectionExceptionUtils.java:77) >> > at >> > >> org.apache.webbeans.container.InjectionResolver.checkInjectionPoints(InjectionResolver.java:193) >> > at >> > >> org.apache.webbeans.container.BeanManagerImpl.validate(BeanManagerImpl.java:1034) >> > at >> > >> org.apache.openejb.cdi.WebappBeanManager.validate(WebappBeanManager.java:207) >> > at org.apache.openejb.cdi.BeansDeployer.validate(BeansDeployer.java:269) >> > at >> > >> org.apache.openejb.cdi.BeansDeployer.validateInjectionPoints(BeansDeployer.java:215) >> > at >> > >> org.apache.openejb.cdi.OpenEJBLifecycle.startApplication(OpenEJBLifecycle.java:280) >> > at >> > >> org.apache.openejb.cdi.ThreadSingletonServiceImpl.initialize(ThreadSingletonServiceImpl.java:150) >> > at org.apache.openejb.cdi.CdiBuilder.build(CdiBuilder.java:61) >> > at >> > >> org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1134) >> > at >> > >> org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:938) >> > at >> > >> org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:124) >> > at >> > >> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) >> > at >> > >> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) >> > at >> > >> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5173) >> > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) >> > at >> > >> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) >> > at >> > >> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549) >> > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) >> > at java.util.concurrent.FutureTask.run(FutureTask.java:166) >> > at >> > >> java.util.concurrent.ThreadPo
Re: TomEE Embedded for JAX-RS and Plus?
Hi, Did you try tomee-webservices and tomee-jaxrs? FYI we have a setup to test against all tomee (embedded or not) here http://svn.apache.org/repos/asf/openejb/trunk/openejb/arquillian/arquillian-tomee-tests/ Le 23 déc. 2012 12:13, "Harald Wellmann" a écrit : > Assuming that tomee-embedded is an embedded representation of the TomEE > Web Profile, what about embedded usage of the TomEE JAX-RS and TomEE Plus > profiles? > > Are there separate embedded artifacts for these profiles, or is it enough > to add some extra libraries to the classpath - if so, which ones? > > Thanks, > Harald >
Re: EAR+CODI doesnt work
Hi José, just tested again on trunk and it starts without issues for me did you try the snapshot (on apache repo), think it is deployed now. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/20 José Luis Cetina : > If you create an ear file with an ejb module + web app module (with CODI > dependencies) it doesnt work. > > Here is the sample: > https://github.com/maxtorzito/tomee-tests/tree/master/myenterprise > > > In the sample if you deploy the ear in apps folder it runs, but if you > uncomment the CODI dependencies it wont deploy. > > I tried with the last snapshot (today) and i build a new TomEE from trunk > as Romain suggest me, but i have the same problem. > > > Log file: > > SEVERE: CDI Beans module deployment failed > javax.enterprise.inject.UnsatisfiedResolutionException: Api type > [org.apache.myfaces.extensions.cdi.jsf.impl.security.spi.SecurityStrategy] > is not found with the qualifiers > Qualifiers: [@javax.enterprise.inject.Default()] > for injection into Field Injection Point, field name : securityStrategy, > Bean Owner : [SecurityInterceptor, Name:null, WebBeans Type:MANAGED, API > Types:[org.apache.myfaces.extensions.cdi.jsf.impl.security.SecurityInterceptor,java.lang.Object,java.io.Serializable], > Qualifiers:[javax.enterprise.inject.Any,javax.enterprise.inject.Default]] > at > org.apache.webbeans.util.InjectionExceptionUtils.throwUnsatisfiedResolutionException(InjectionExceptionUtils.java:77) > at > org.apache.webbeans.container.InjectionResolver.checkInjectionPoints(InjectionResolver.java:193) > at > org.apache.webbeans.container.BeanManagerImpl.validate(BeanManagerImpl.java:1034) > at > org.apache.openejb.cdi.WebappBeanManager.validate(WebappBeanManager.java:207) > at org.apache.openejb.cdi.BeansDeployer.validate(BeansDeployer.java:269) > at > org.apache.openejb.cdi.BeansDeployer.validateInjectionPoints(BeansDeployer.java:215) > at > org.apache.openejb.cdi.OpenEJBLifecycle.startApplication(OpenEJBLifecycle.java:280) > at > org.apache.openejb.cdi.ThreadSingletonServiceImpl.initialize(ThreadSingletonServiceImpl.java:150) > at org.apache.openejb.cdi.CdiBuilder.build(CdiBuilder.java:61) > at > org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1134) > at > org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:938) > at > org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:124) > at > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) > at > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) > at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5173) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > > Dec 20, 2012 12:17:36 PM org.apache.tomee.catalina.TomcatWebAppBuilder > startInternal > SEVERE: Error merging Java EE JNDI entries in to war /myenterprise-web: > Exception: couldn't start owb context > org.apache.openejb.OpenEJBRuntimeException: couldn't start owb context > at > org.apache.openejb.cdi.ThreadSingletonServiceImpl.initialize(ThreadSingletonServiceImpl.java:152) > at org.apache.openejb.cdi.CdiBuilder.build(CdiBuilder.java:61) > at > org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1134) > at > org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:938) > at > org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:124) > at > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) > at > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) > at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5173) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBa
Re: Help with JPA Entity Persist
You probably miss a transaction. Use an ejb for instance (@stateless)
Le 20 déc. 2012 22:28, "avrono" a écrit :
> Hi All,
>
> Newbie trying to experiment with JPA2 (openjpa - TomEE). I would appreciate
> any pointers on where I might be going wrong with the example below
>
> I can read data from my Persistence-unit, but cannot write data (and no
> error is generated) and I cannot see any generated SQL
>
> The only log output I get is as follows:
> =
>
> 25019 PRSX TRACE [http-bio-8080-exec-5] openjpa.jdbc.SQL - conn 20981618> executing prepstmnt 19451103 SELECT t0.bidEndDate,
> t0.bidStartDate, t0.createdDate, t0.initialPrice, t0.name FROM item t0
> WHERE
> t0.id = ? [params=?]
> 25020 PRSX TRACE [http-bio-8080-exec-5] openjpa.jdbc.SQL - conn 20981618> [1 ms] spent
> 25023 PRSX TRACE [http-bio-8080-exec-5] openjpa.jdbc.SQL - conn 8418899> executing prepstmnt 30955499 SELECT t0.credit_rating,
> t0.user_id FROM bidder t0 WHERE t0.id = ? [params=?]
> 25023 PRSX TRACE [http-bio-8080-exec-5] openjpa.jdbc.SQL - conn 8418899> [0 ms] spent
> In add Bid : id = 0 bidStartDate = Thu Dec 20 21:12:24 GMT 2012 Initial
> Price = 0.0 item_id = 0 item id from item is = 0 bidder_id = 1
> Trying to persist !
> 20-Dec-2012 21:12:24 org.apache.myfaces.renderkit.html.HtmlLabelRenderer
> encodeBegin
> WARNING: Attribute 'for' of label component with id j_id_3:j_id_5 is not
> defined
>
>
> My persistence.xml:
> ===
>
> http://java.sun.com/xml/ns/persistence"; version="1.0">
>
>
> jdbc/testDB
> com.prsx.dao.item.Item
>
>
>
>
> value="buildSchema(ForeignKeys=true)"/>
>
>
>
>
>
>
> ManagedBean:
> =
>
>
>
> @ManagedBean(name = "itemAdderBean")
> @RequestScoped
> //@TransactionManagement(TransactionManagementType.BEAN)
> public class ItemAdderBean {
>
> @Resource
> private UserTransaction userTransaction;
>
> @PersistenceUnit(unitName="PRSX")
> private EntityManagerFactory entityManagerFactory;
>
> /*
> @PersistenceContext(unitName = "PRSX", type =
> PersistenceContextType.TRANSACTION)
> private EntityManagerFactory entityManagerFactory;
> */
> @PersistenceContext
> private EntityManager entityManager;
>
> private int id =0;
> private Date bidDate = null;
> private double bidPrice = 0;
> private int item_id = 0;
> private int bidder_id = 0;
>
> @SuppressWarnings("unused")
> private List list;
> private Item item;
>
>
>
> public ItemAdderBean() {
> System.out.println("Constructor of ItemAdderBean Called
> !");
> item = new Item();
>
> }
>
> @SuppressWarnings("unchecked")
> public List getList() throws Exception {
> System.out.println("GetList of ItemAdderBean Called !");
> Query query = entityManager.createQuery("Select i from
> Item i");
> System.out.println("GetList of ItemAdderBean Called -
> returning !");
> return query.getResultList();
> }
>
> public Item getItem() {
> return item;
> }
>
> public void setItem(Item item) {
> this.item = item;
> }
>
> /* Getter / Setter */
> public int getId() {
> return this.id;
> }
>
> public void setId(int id) {
> this.id = id;
> }
>
> public Date getBidDate() {
> return this.bidDate;
> }
>
> public void setBidDate(Date bidDate) {
> this.bidDate = bidDate;
> }
>
> public double getBidPrice() {
> return this.bidPrice;
> }
>
> public void setBidPrice(double bidPrice) {
> this.bidPrice = bidPrice;
> }
>
> public int getItem_id() {
> return this.item_id;
> }
>
> public void setItem_id(int item_id) {
> this.item_id = item_id;
> }
>
> public int getBidder_id() {
> return this.bidder_id;
> }
>
> public void setBidder_id(int bidder_id) {
> this.bidder_id = bidder_id;
> }
>
>
>
> public String addBid() {
>
> System.out.println("Add Called !");
>
> Bid bids = new Bid();
> bids.setId(this.id);
> bids.setBidDate(this.bidDate);
> bids.setBidPrice(this.bidPrice);
>
> Item theItem = entityManager.find(Item.class,
> this.item_id);
> bids.setItem(theItem);
>
> /* Just set bidder to 0 */
> Bidder theBidder = entityManager.find(Bidder.class, 1);
> bids.setBidder(theBidder);
>
> String output = "In add Bid : id = " + this.id +
>
Re: EntityManagerFactory injection
The webpage is not a javaee component (not a servlet, listener...). You
would need to update wicket application impl to manage injections in pages
to support it. Not sure it exists out of the box.
Le 20 déc. 2012 17:45, "Lucio Crusca" a écrit :
> Hello *,
>
> this document
>
> http://docs.oracle.com/javaee/5/tutorial/doc/bnbrm.html
>
> states that "resource injection using annotations can only be used with
> classes that are managed by a Java EE compliant container [...] One
> exception
> is a request-scoped JavaServer Faces managed bean".
>
> Then it specifies that "You can still use resource injection in a web
> application that is not a JavaServer Faces application if you can do it in
> an
> object that is managed by the container. These objects include servlets and
> ServletContextListener objects"
>
> My application is a Wicket app, not JSF, but I'm deploying in Tomee+. As I
> understand it, my container should be J2EE compliant, right? However, in:
>
> @Stateless
> public class MyPage extends org.apache.wicket.markup.html.WebPage
> {
> @PersistenceUnit
> private EntityManagerFactory emf;
> ...
>
> emf is always null.
>
> Here is my persistence.xml
>
>
> xmlns="http://java.sun.com/xml/ns/persistence";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
>http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd";>
>
>
> org.hibernate.ejb.HibernatePersistence
> mercatinoDatabase
> mercatinoDatabaseUnmanaged
>
>
>
>/>
>
>name="hibernate.dialect">org.hibernate.dialect.MySQLDialect
>name="hibernate.connection.driver_class">com.mysql.jdbc.Driver
>
> name="hibernate.connection.url">jdbc:mysql://localhost:3306/mydb?zeroDateTimeBehavior=convertToNull&autoReconnect=true
> myuser
> secret
>
>
>
>
>
>
>
>
>
>
> What am I doing wrong?
>
Re: How to package an EJB3.1 WebService in an EAR
yeah got the same with a jar deployment (not an ear) think it should be fixed on trunk now Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/20 ymaraner : > I got the latest 1.5.2 snapshot and tested the fix. It works great as long as > there is only one @WebService EJB in the module. As soon as I added a second > one I got the following exception: > > 'WebServiceEJBs' is the name of the EJB Module. > > I updated the project on GitHub > <https://github.com/ymaraner/EJBWebServiceInEar> to demonstrate this > issue. > > > > - > - Tim > -- > View this message in context: > http://openejb.979440.n4.nabble.com/How-to-package-an-EJB3-1-WebService-in-an-EAR-tp4659793p4659859.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Debugging null openjpa.jdbc.JDBC
the existing table doesn't match the describe one (size) it is configurable normally Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/20 avrono : > I just solved the problem, a total pot shot ... I had a table called Group > which seems to have been messing things up (since it is reserved in Mysql) > > > Any idea what these warnings mean ? > > INFO: Using dictionary class "org.apache.openjpa.jdbc.sql.MySQLDictionary". > 20-Dec-2012 11:05:06 null openjpa.jdbc.Schema > WARNING: Existing column "name" on table "item" is incompatible with the > same column in the given schema definition. Existing column: > Full Name: item.name > Type: varchar > Size: 256 > Default: null > Not Null: true > Given column: > Full Name: item.name > Type: varchar > Size: 255 > Default: null > Not Null: false > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Debugging-null-openjpa-jdbc-JDBC-tp4659845p4659849.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Debugging null openjpa.jdbc.JDBC
you debug in LoggingConnectionDecorator you'll get the raw exception and it origin. are you sure you use the right driver? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/20 avrono : > LoggingConnectionDecorator
Re: Failed to execute goal
well the issue you have are not linked to tomee ;) you probably miss some repo, check on these lib websites Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/19 Lucio Crusca : > José Luis Cetina wrote: >> I use this dependency: >> >> >> org.apache.openejb >> apache-tomee >> 1.5.0 >> webprofile >> zip >> provided >> > > Unfortunately this didn't solve my problem (besides, it broke my javax.ejb.* > references). > > Romain Manni-Bucau wrote: >> it doesn't come from us >> >> can you check with a mvn dependency:tree please? > > Not sure it will help much, however here's to you: > > $ mvn dependency:tree > [INFO] Scanning for projects... > [INFO] > [INFO] > > [INFO] Building SalixWeb 1.0-SNAPSHOT > [INFO] > > Downloading: > https://repository.apache.org/content/repositories/snapshots/com/jgoodies/JGoodies/b2.5- > c1.2.1-f1.4.2-l2.4.2-v2.3.2/JGoodies-b2.5-c1.2.1-f1.4.2-l2.4.2-v2.3.2.pom > [WARNING] The POM for com.jgoodies:JGoodies:jar:b2.5-c1.2.1-f1.4.2-l2.4.2- > v2.3.2 is missing, no dependency information available > Downloading: > https://repository.apache.org/content/repositories/snapshots/com/db4o/db4o/7.12.243.16079- > all-java5/db4o-7.12.243.16079-all-java5.pom > [WARNING] The POM for com.db4o:db4o:jar:7.12.243.16079-all-java5 is missing, > no dependency information available > [WARNING] The POM for unknown.binary:mysql-connector-java-5.1.18- > bin:jar:SNAPSHOT is missing, no dependency information available > Downloading: > https://repository.apache.org/content/repositories/snapshots/javax/transaction/jta/1.0.1B/jta-1.0.1B.jar > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 12.335s > [INFO] Finished at: Wed Dec 19 22:05:06 CET 2012 > [INFO] Final Memory: 11M/35M > [INFO] > > [ERROR] Failed to execute goal on project SalixWeb: Could not resolve > dependencies for project com.virtual_bit.salix.web:SalixWeb:war:1.0-SNAPSHOT: > Could not find artifact javax.transaction:jta:jar:1.0.1B in Apache Nexus > (https://repository.apache.org/content/repositories/snapshots/) -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
Re: Failed to execute goal
Hi, it doesn't come from us can you check with a mvn dependency:tree please? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/19 José Luis Cetina : > I use this dependency: > > > org.apache.openejb > apache-tomee > 1.5.0 > webprofile > zip > provided > > > > > Hope it helps > > > 2012/12/19 Lucio Crusca > >> SNAPSHOT > > > > > -- > --- > *SCJA. José Luis Cetina* > ---
Re: EJB Module Lookup
discussed on IRC but just to log something here: the issue was due to OpenJPA enhancing wich, trying to enhance openejb, was creating a cycle in classloading you openened a JIRA and it is now fixed on trunk normally Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/19 José Luis Cetina : > Yes it is, the only difference that i add a persistence.xml, anyway here is > the link of the sample: http://www.mediafire.com/?rkz3m0moq9p4580 > > > 2012/12/19 Howard W. Smith, Jr. > >> I need to signup somewhere, so I am notified of releases, because I always >> want the latest and greatest. :) >> >> On Wed, Dec 19, 2012 at 12:12 PM, José Luis Cetina > >wrote: >> >> > Im using: apache-tomee-1.5.2-20121219.041507-6-webprofile.zip >> > >> > > > > -- > --- > *SCJA. José Luis Cetina* > ---
Re: How to package an EJB3.1 WebService in an EAR
ok, reproduced and fixed on trunk thanks for the sample, it helps a lot :) Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/19 ymaraner : > A very simple example can be found here: > https://github.com/ymaraner/EJBWebServiceInEar > <https://github.com/ymaraner/EJBWebServiceInEar> > It has a single HelloWorld webservice that is packaged inside of an EAR > file. It has the same issue when I deploy it to TomEE (by placing it in the > apps folder) > > I am new to Git and Maven, so hopefully everything you need is there. It was > created in Eclipse, converted to Maven, and then placed in GIT. > > > > - > - Tim > -- > View this message in context: > http://openejb.979440.n4.nabble.com/How-to-package-an-EJB3-1-WebService-in-an-EAR-tp4659793p4659832.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: TomEE doesn't persist @SessionScoped beans?
remove the correctly and we agree ;) (joking) well JBoss persists stateful with extended entitymanagers too...no exception but it doesn't work... maybe open a jira on issues.apache.org, will be easier to track this feature Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/19 bibhas : > Thanks Romain, for the clarification. > > By the way, if this matters to anyone, I tested out with JBoss AS 7. It > correctly persists session scoped CDI managed beans, once persistence is > enabled for Tomcat. > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/TomEE-doesn-t-persist-SessionScoped-beans-tp4659814p4659830.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: EJB Module Lookup
is it still on your test app? if yes can you share it please? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/19 José Luis Cetina : > Im using: apache-tomee-1.5.2-20121219.041507-6-webprofile.zip > > > 2012/12/19 José Luis Cetina > >> Hi Romain the lookup now is working from webapp to ejbmodule. >> >> As you told me i have to use 1.5.2-SNAPSHOT for this. >> >> When i deploy my ebjmodule in apps folder i always see this: >> >> INFO: OpenWebBeans Container is starting... >> Dec 19, 2012 11:06:26 AM org.apache.openejb.assembler.classic.Assembler >> destroyApplication >> INFO: Undeploying app: >> /home/maxtorzito/tomee/apache-tomee-webprofile-1.5.2-SNAPSHOT_19-12-2012/apps/myejbmodule-1.0-SNAPSHOT.jar >> Dec 19, 2012 11:06:26 AM org.apache.openejb.assembler.classic.Assembler >> buildContainerSystem >> SEVERE: Application could not be deployed: >> >> /home/maxtorzito/tomee/apache-tomee-webprofile-1.5.2-SNAPSHOT_19-12-2012/apps/myejbmodule-1.0-SNAPSHOT.jar >> org.apache.openejb.OpenEJBException: Creating application failed: >> /home/maxtorzito/tomee/apache-tomee-webprofile-1.5.2-SNAPSHOT_19-12-2012/apps/myejbmodule-1.0-SNAPSHOT.jar: >> loader (instance of org/apache/catalina/loader/StandardClassLoader): >> attempted duplicate class definition for name: >> "org/apache/openejb/cdi/CdiPlugin" >> at >> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:823) >> at >> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:534) >> at >> org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:433) >> at org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:341) >> at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:144) >> at org.apache.openejb.OpenEJB.init(OpenEJB.java:290) >> at >> org.apache.tomee.catalina.TomcatLoader.initialize(TomcatLoader.java:233) >> at org.apache.tomee.catalina.TomcatLoader.init(TomcatLoader.java:130) >> at >> org.apache.tomee.catalina.ServerListener.lifecycleEvent(ServerListener.java:121) >> at >> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) >> at >> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) >> at >> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402) >> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:110) >> at org.apache.catalina.startup.Catalina.load(Catalina.java:633) >> at org.apache.catalina.startup.Catalina.load(Catalina.java:658) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:601) >> at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:281) >> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:450) >> Caused by: java.lang.LinkageError: loader (instance of >> org/apache/catalina/loader/StandardClassLoader): attempted duplicate >> class definition for name: "org/apache/openejb/cdi/CdiPlugin" >> at java.lang.ClassLoader.defineClass1(Native Method) >> at java.lang.ClassLoader.defineClass(ClassLoader.java:791) >> at >> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) >> at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) >> at java.net.URLClassLoader.access$100(URLClassLoader.java:71) >> at java.net.URLClassLoader$1.run(URLClassLoader.java:361) >> at java.net.URLClassLoader$1.run(URLClassLoader.java:355) >> at java.security.AccessController.doPrivileged(Native Method) >> at java.net.URLClassLoader.findClass(URLClassLoader.java:354) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:423) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:410) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:356) >> at >> org.apache.openejb.cdi.OptimizedLoaderService.loadWebBeansPlugins(OptimizedLoaderService.java:87) >> at >> org.apache.openejb.cdi.OptimizedLoaderService.load(OptimizedLoaderService.java:57) >> at >> org.apache.openejb.cdi.OptimizedLoaderService.load(OptimizedLoaderService.java:51) >> at org.apache.webbeans.plugins.PluginLoader.startUp(PluginLoader.java:75) >> at >> org.apache.openejb.cdi.OpenEJB
Re: TomEE doesn't persist @SessionScoped beans?
well the point is today you can configure session strategy, stateful
one but not CDI one. There is no global persist option.
clearly something we'll need to have a look (probably next year ;)
the best solution today is to store it in the session
that's said i just looked the code and 2 points:
1) when you shutdown a tomee the application is destroyed so beans too
2) the main point is the implementation of SessionContext whch doesn't
use the session today (that's in OpenWebBeans more than TomEE/OpenEJB)
Nothing important to implement but the point is then it will slow down
your app at runtime...
if you want to try to contribute just hack
org.apache.openejb.cdi.CdiAppContextsService#initSessionContext and
replace the line currentSessionContext = new SessionContext(); by a
session context using the http session
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2012/12/19 bibhas :
> Hi Romain,
>
> Let me explain more. In Tomcat session objects can be persisted on disk so
> that they survive application or server restart. This is configured in
> context.xml by setting a path name:
>
>
>
> Persistence can be disabled by setting an empty path name. But, by default,
> persistence is enabled in Tomcat and TomEE.
>
>> that's probably not the default everybody expect.
>
> If someone doesn't want session persistence, they can easily disable that.
>
>> then the point is mainly with stateful beans
>
> I am not talking about EJB here. I am talking about plain POJO JavaBeans
> that are managed by CDI. I am not using any entity manager from this bean.
>
> @Named
> @SessionScoped
> public class MyBean implements Serializable {
> ...
> }
>
> I agree that trying to persist a session EJB that uses entity manager can be
> tricky. I won't even try something like that. What I am trying to do is
> persist plain JavaBeans that are in CDI session scope.
>
> The issue that I am trying to point out is that TomEE is being inconsistent.
> When persistence is enabled, regular session objects are persisted but not
> CDI beans. This is causing unnecessary headache for my application, nothing
> that can not be worked around with a bit of code. But, I will like to avoid
> this if possible.
>
> What do I need to do to persist CDI managed JavaBeans that are in session or
> conversation scope?
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/TomEE-doesn-t-persist-SessionScoped-beans-tp4659814p4659823.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: TomEE doesn't persist @SessionScoped beans?
well why should it be done ;)? that's not the case because that's probably not the default everybody expect. but i think you are right if we say it can be desired. then the poin tis mainly with stateful beans (which can be sessionscoped): if you have an extended em you'll be tempted to serialize it and even if it can work it is broken (you loose entity state etc). So it shouldn't be done at all IMO Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/19 bibhas : > My question is, if Tomcat persists all session objects on disk, shouldn't > session scoped CDI beans also be persisted? Why is that not the case? What's > the point in implementing Serializable then? > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/TomEE-doesn-t-persist-SessionScoped-beans-tp4659814p4659821.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: EAR multiple persistence.xml
yep that's the idea Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/18 José Luis Cetina : > Ok, then what you propose is create and ejb module with the content of the > webapp. > With this i have to isolate all the ejb's from webapps and create them as > ejbmodule, am i correct? > > Doing this is not a limitation to me. > > > > 2012/12/18 Romain Manni-Bucau > >> basically: >> >> ear >> | >> ejb.jar >> ejb2.jar <- ejb of the webmodule + persistence.xml of the webmodule >> web.war <- without ejb2 content >> >> >> Side note: next trunk should be better for your need even without >> respecting this hierarchy >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> >> 2012/12/18 José Luis Cetina : >> > You mean that i have to create a jar (like ejb module, but not being an >> ejb >> > module itself, i said this because i have to drop it in ear/lib folder >> and >> > not in ear)? >> > >> > >> > 2012/12/18 Romain Manni-Bucau >> > >> >> basically the idea was: >> >> >> >> take all ejb stuff from the webapp and put it in a jar in lib part of >> >> the ear (even the META-INF/persistence.xml) >> >> >> >> Romain Manni-Bucau >> >> Twitter: @rmannibucau >> >> Blog: http://rmannibucau.wordpress.com/ >> >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> >> Github: https://github.com/rmannibucau >> >> >> >> >> >> >> >> 2012/12/18 José Luis Cetina : >> >> > No, i didn't. >> >> > >> >> > Do you mean, that i have to move the persistence of my webapp to >> where?? >> >> > >> >> > Where i move was the ejb.jar from ear root to ear/lib >> >> > >> >> > >> >> > >> >> > 2012/12/18 Romain Manni-Bucau >> >> > >> >> >> sorry not sure i understood >> >> >> >> >> >> did you move the persistence.xml which was in >> WEB-INF/classes/META-INF >> >> >> in the ejb.jar too? >> >> >> >> >> >> Romain Manni-Bucau >> >> >> Twitter: @rmannibucau >> >> >> Blog: http://rmannibucau.wordpress.com/ >> >> >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> >> >> Github: https://github.com/rmannibucau >> >> >> >> >> >> >> >> >> >> >> >> 2012/12/18 José Luis Cetina : >> >> >> > Yes. >> >> >> > >> >> >> > I have 2 persistences 1 in ejb module and the other in the webapp. >> >> >> > >> >> >> > My ear look like this: >> >> >> > >> >> >> > -ear >> >> >> > .lib >> >> >> > .myejb.jar >> >> >> >META-INF/persistence.xml >> >> >> > >> >> >> > >> >> >> > ..META-INF >> >> >> > ..mywebapp.war >> >> >> > >> >> >> > >> >> >> > I move my ejb from ear/ejb.jar to ear/lib folder, then the >> >> >> persistence.xml >> >> >> > is inside of the jar itself. >> >> >> > >> >> >> > >> >> >> > 2012/12/18 Romain Manni-Bucau >> >> >> > >> >> >> >> did you move the persistence.xml as well? >> >> >> >> >> >> >> >> Romain Manni-Bucau >> >> >> >> Twitter: @rmannibucau >> >> >> >> Blog: http://rmannibucau.wordpress.com/ >> >> >> >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> >> >> >> Github: https://github.com/rmannibucau >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> 2012/12/18 José Luis Cetina : >> >> >> >> > I moved my ejb module to lib (ear) folder, but i still having >> issue >> >> >> with >> >> >> >> > the persistence unit. >> >> >> >> > >> >> >> >> > I just move my ejb jar to lib an in application.xml i add the >> >> >> following: >> >> >> >> > >> >> >> >> > >> >> >> >> > lib/myejb.jar >> >> >> >> > >> >> >> >> > >> >> >> >> > 2012/12/18 Romain Manni-Bucau >> >> >> >> > >> >> >> >> >> ear >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > -- >> >> >> >> > >> --- >> >> >> >> > *SCJA. José Luis Cetina* >> >> >> >> > >> --- >> >> >> >> >> >> >> > >> >> >> > >> >> >> > >> >> >> > -- >> >> >> > --- >> >> >> > *SCJA. José Luis Cetina* >> >> >> > --- >> >> >> >> >> > >> >> > >> >> > >> >> > -- >> >> > --- >> >> > *SCJA. José Luis Cetina* >> >> > --- >> >> >> > >> > >> > >> > -- >> > --- >> > *SCJA. José Luis Cetina* >> > --- >> > > > > -- > --- > *SCJA. José Luis Cetina* > ---
Re: EAR multiple persistence.xml
basically: ear | ejb.jar ejb2.jar <- ejb of the webmodule + persistence.xml of the webmodule web.war <- without ejb2 content Side note: next trunk should be better for your need even without respecting this hierarchy Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/18 José Luis Cetina : > You mean that i have to create a jar (like ejb module, but not being an ejb > module itself, i said this because i have to drop it in ear/lib folder and > not in ear)? > > > 2012/12/18 Romain Manni-Bucau > >> basically the idea was: >> >> take all ejb stuff from the webapp and put it in a jar in lib part of >> the ear (even the META-INF/persistence.xml) >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> >> 2012/12/18 José Luis Cetina : >> > No, i didn't. >> > >> > Do you mean, that i have to move the persistence of my webapp to where?? >> > >> > Where i move was the ejb.jar from ear root to ear/lib >> > >> > >> > >> > 2012/12/18 Romain Manni-Bucau >> > >> >> sorry not sure i understood >> >> >> >> did you move the persistence.xml which was in WEB-INF/classes/META-INF >> >> in the ejb.jar too? >> >> >> >> Romain Manni-Bucau >> >> Twitter: @rmannibucau >> >> Blog: http://rmannibucau.wordpress.com/ >> >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> >> Github: https://github.com/rmannibucau >> >> >> >> >> >> >> >> 2012/12/18 José Luis Cetina : >> >> > Yes. >> >> > >> >> > I have 2 persistences 1 in ejb module and the other in the webapp. >> >> > >> >> > My ear look like this: >> >> > >> >> > -ear >> >> > .lib >> >> > .myejb.jar >> >> >META-INF/persistence.xml >> >> > >> >> > >> >> > ..META-INF >> >> > ..mywebapp.war >> >> > >> >> > >> >> > I move my ejb from ear/ejb.jar to ear/lib folder, then the >> >> persistence.xml >> >> > is inside of the jar itself. >> >> > >> >> > >> >> > 2012/12/18 Romain Manni-Bucau >> >> > >> >> >> did you move the persistence.xml as well? >> >> >> >> >> >> Romain Manni-Bucau >> >> >> Twitter: @rmannibucau >> >> >> Blog: http://rmannibucau.wordpress.com/ >> >> >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> >> >> Github: https://github.com/rmannibucau >> >> >> >> >> >> >> >> >> >> >> >> 2012/12/18 José Luis Cetina : >> >> >> > I moved my ejb module to lib (ear) folder, but i still having issue >> >> with >> >> >> > the persistence unit. >> >> >> > >> >> >> > I just move my ejb jar to lib an in application.xml i add the >> >> following: >> >> >> > >> >> >> > >> >> >> > lib/myejb.jar >> >> >> > >> >> >> > >> >> >> > 2012/12/18 Romain Manni-Bucau >> >> >> > >> >> >> >> ear >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > -- >> >> >> > --- >> >> >> > *SCJA. José Luis Cetina* >> >> >> > --- >> >> >> >> >> > >> >> > >> >> > >> >> > -- >> >> > --- >> >> > *SCJA. José Luis Cetina* >> >> > --- >> >> >> > >> > >> > >> > -- >> > --- >> > *SCJA. José Luis Cetina* >> > --- >> > > > > -- > --- > *SCJA. José Luis Cetina* > ---
Re: EAR multiple persistence.xml
basically the idea was: take all ejb stuff from the webapp and put it in a jar in lib part of the ear (even the META-INF/persistence.xml) Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/18 José Luis Cetina : > No, i didn't. > > Do you mean, that i have to move the persistence of my webapp to where?? > > Where i move was the ejb.jar from ear root to ear/lib > > > > 2012/12/18 Romain Manni-Bucau > >> sorry not sure i understood >> >> did you move the persistence.xml which was in WEB-INF/classes/META-INF >> in the ejb.jar too? >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> >> 2012/12/18 José Luis Cetina : >> > Yes. >> > >> > I have 2 persistences 1 in ejb module and the other in the webapp. >> > >> > My ear look like this: >> > >> > -ear >> > .lib >> > .myejb.jar >> >META-INF/persistence.xml >> > >> > >> > ..META-INF >> > ..mywebapp.war >> > >> > >> > I move my ejb from ear/ejb.jar to ear/lib folder, then the >> persistence.xml >> > is inside of the jar itself. >> > >> > >> > 2012/12/18 Romain Manni-Bucau >> > >> >> did you move the persistence.xml as well? >> >> >> >> Romain Manni-Bucau >> >> Twitter: @rmannibucau >> >> Blog: http://rmannibucau.wordpress.com/ >> >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> >> Github: https://github.com/rmannibucau >> >> >> >> >> >> >> >> 2012/12/18 José Luis Cetina : >> >> > I moved my ejb module to lib (ear) folder, but i still having issue >> with >> >> > the persistence unit. >> >> > >> >> > I just move my ejb jar to lib an in application.xml i add the >> following: >> >> > >> >> > >> >> > lib/myejb.jar >> >> > >> >> > >> >> > 2012/12/18 Romain Manni-Bucau >> >> > >> >> >> ear >> >> > >> >> > >> >> > >> >> > >> >> > -- >> >> > --- >> >> > *SCJA. José Luis Cetina* >> >> > --- >> >> >> > >> > >> > >> > -- >> > --- >> > *SCJA. José Luis Cetina* >> > --- >> > > > > -- > --- > *SCJA. José Luis Cetina* > ---
Re: EAR multiple persistence.xml
sorry not sure i understood did you move the persistence.xml which was in WEB-INF/classes/META-INF in the ejb.jar too? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/18 José Luis Cetina : > Yes. > > I have 2 persistences 1 in ejb module and the other in the webapp. > > My ear look like this: > > -ear > .lib > .myejb.jar >META-INF/persistence.xml > > > ..META-INF > ..mywebapp.war > > > I move my ejb from ear/ejb.jar to ear/lib folder, then the persistence.xml > is inside of the jar itself. > > > 2012/12/18 Romain Manni-Bucau > >> did you move the persistence.xml as well? >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> >> 2012/12/18 José Luis Cetina : >> > I moved my ejb module to lib (ear) folder, but i still having issue with >> > the persistence unit. >> > >> > I just move my ejb jar to lib an in application.xml i add the following: >> > >> > >> > lib/myejb.jar >> > >> > >> > 2012/12/18 Romain Manni-Bucau >> > >> >> ear >> > >> > >> > >> > >> > -- >> > --- >> > *SCJA. José Luis Cetina* >> > --- >> > > > > -- > --- > *SCJA. José Luis Cetina* > ---
