Re: Separating the SystemInstance initialization from the TomcatLoader initialization

HI, >what's your use case? I want to use a customized TomcatWebAppBuilder. I can simply do "SystemInstance.get().setComponent(WebAppBuilder.class, webAppBuilder);" before the TomcatLoader isinitialized and it will pick my instance instead of creating its own. But currently the SystemInstance is re

Re: Separating the SystemInstance initialization from the TomcatLoader initialization

2016-07-18 9:09 GMT+02:00 Svetlin Zarev : > HI, > > >what's your use case? > I want to use a customized TomcatWebAppBuilder. I can simply do > "SystemInstance.get().setComponent(WebAppBuilder.class, webAppBuilder);" > before the TomcatLoader isinitialized and it will pick my instance instead > of

Re: Separating the SystemInstance initialization from the TomcatLoader initialization

> org.apache.openejb.assembler.classic.WebAppBuilder=foo.MyImpl Thanks, that will do it. > if you need to capture things before a tomcat listener does the work. I wanted to use the SystemInstance from a tomcat listener, but it's unusable because it's not initialized, but if I initialize it - then

Re: Separating the SystemInstance initialization from the TomcatLoader initialization

2016-07-18 10:23 GMT+02:00 Svetlin Zarev : > > org.apache.openejb.assembler.classic.WebAppBuilder=foo.MyImpl > Thanks, that will do it. > > > if you need to capture things before a tomcat listener does the work. > I wanted to use the SystemInstance from a tomcat listener, but it's > unusable beca

Re: Separating the SystemInstance initialization from the TomcatLoader initialization

> You can still init then reset it, not perfect but works well. Bu then the components I set on the SystemInstance will not be accessible to the TomcatLoader or other components after the reset. > Or if you want to go this way your use case would be amisusage then. Currently it is, but if the init

Re: Separating the SystemInstance initialization from the TomcatLoader initialization

2016-07-18 11:32 GMT+02:00 Svetlin Zarev : > > You can still init then reset it, not perfect but works well. > Bu then the components I set on the SystemInstance will not be accessible > to the TomcatLoader or other components after the reset. > > Then I'd use org.apache.openejb.assembler.classic.

Re: Integrate ActiveMQ web console with TomEE Plus

Hi , Could you please let me know where to configure in TomEE+ ? Please share the configuration as well. I have a query , ActiveMQ jars has both the TomEE+ /lib and ActiveMQ Web Console war /lib , which one should be take for ActiveMQ. I am Confusing. Please help me. Thanks -- View this mess

Re: Integrate ActiveMQ web console with TomEE Plus

Could you please let me know where to configure in TomEE+ ? -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/Integrate-ActiveMQ-web-console-with-TomEE-Plus-tp4679322p4679367.html Sent from the TomEE Users mailing list archive at Nabble.com.

Re: Separating the SystemInstance initialization from the TomcatLoader initialization

> openejb.configurator property allows to change ConfigurationFactory This is exactly what I'm looking for, but unfortunately it does not work. The TomcatWebAppBuilder creates a ConfigurationFactory instance regardless of that property and the one from the property is ignored.

Re: Integrate ActiveMQ web console with TomEE Plus

Set the system property webconsole.type to invm or the context classifier you want in webconsole/WEB-INF ( see webconsole-*.xml in https://github.com/apache/activemq/tree/master/activemq-web-console/src/main/webapp/WEB-INF ) Romain Manni-Bucau @rmannibucau | Bl

Re: Separating the SystemInstance initialization from the TomcatLoader initialization

Ok get it now, opened https://issues.apache.org/jira/browse/TOMEE-1875 Romain Manni-Bucau @rmannibucau | Blog | Old Wordpress Blog | Github | LinkedIn

Connection pool exception after upgrading to 7.0.1

Hi, After upgrading from 1.7.2 to 7.0.1 I saw some connection exceptions on the log like this: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet successfully received from the server was 35.540.502 milliseconds ago. The last packet sent success

Re: Connection pool exception after upgrading to 7.0.1

Hi by default tomcat-jdbc but switching to DataSourceCreator=dbcp you will use dbcp (in datasource properties). If you run both servers in parallel don't you have the same exceptions? (= can't be it some issues with MySQL at the moment) Romain Manni-Bucau @rmannibucau

TomEE 7.0.1, problem with path

Hi, My production TomEE 7.0.1 is installed under /home/ec2-user/apache-tomee-plus-7.0.1. I have a symbolic link for this folder: apache-tomee-plus -> apache-tomee-plus-7.0.1/ I noticed this on the log: 17-Jul-2016 04:01:28.227 INFO [localhost-startStop-1] org.apache.openejb.assembler.classic.As

Re: TomEE 7.0.1, problem with path

can be both, I would first check *.loader in conf/catalina.properties before saying it is a bug (did you misconfigure the common.loader to be very concrete?) Romain Manni-Bucau @rmannibucau | Blog | Old Wordpress Blog

Re: TomEE 7.0.1, problem with path

I'm using the default catalina.properties Loaders config: common.loader="${catalina.base}/lib","${catalina.base}/lib/*.jar","${catalina.home}/lib","${catalina.home}/lib/*.jar" server.loader= shared.loader= 2016-07-18 15:45 GMT-03:00 Romain Manni-Bucau : > can be both, I would first check *.lo

Re: TomEE 7.0.1, problem with path

Is that hard to test the same setup and naming with a plain tomcat? Stack should only imply tomcat code but im surprised issue wasnt identified already if present Le 18 juil. 2016 21:03, "Felipe Jaekel" a écrit : > I'm using the default catalina.properties > > Loaders config: > > > common.loade