You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by Lazar Kirchev <la...@gmail.com> on 2017/02/03 09:00:09 UTC
Re: Separating the SystemInstance initialization from the
TomcatLoader initialization
Hello Romain,
It seems the commit
https://github.com/apache/tomee/commit/ed37f9ee3995812ae91a19cf36a85d534787cefa
does not fix the issue in TOMEE-1875. It is in the TomcatWebAppBuilder's
constructor and it tries to get the ConfigurationFactory if already
created, but this gets executed before the call to Assembler.init method
which creates correctly the custom configuration factory configured in the
openejb.configurator property. Could you check this?
Regards,
Lazar
On Mon, Jul 18, 2016 at 2:45 PM, Romain Manni-Bucau <rm...@gmail.com>
wrote:
> Ok get it now, opened https://issues.apache.org/jira/browse/TOMEE-1875
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/
> rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2016-07-18 13:28 GMT+02:00 Svetlin Zarev <svetlin.angelov.zarev@gmail.com
> >:
>
> > > 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: Separating the SystemInstance initialization from the
TomcatLoader initialization
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Well yes but the ticket was to allow to change the impl which it does since
you can set another instance either programmatically or using the component
type qualified name = impl in system properties
Le 3 févr. 2017 10:00, "Lazar Kirchev" <la...@gmail.com> a écrit :
> Hello Romain,
>
> It seems the commit
> https://github.com/apache/tomee/commit/ed37f9ee3995812ae91a19cf36a85d
> 534787cefa
> does not fix the issue in TOMEE-1875. It is in the TomcatWebAppBuilder's
> constructor and it tries to get the ConfigurationFactory if already
> created, but this gets executed before the call to Assembler.init method
> which creates correctly the custom configuration factory configured in the
> openejb.configurator property. Could you check this?
>
> Regards,
> Lazar
>
> On Mon, Jul 18, 2016 at 2:45 PM, Romain Manni-Bucau <rmannibucau@gmail.com
> >
> wrote:
>
> > Ok get it now, opened https://issues.apache.org/jira/browse/TOMEE-1875
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> | Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > <http://www.tomitribe.com> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
> > 2016-07-18 13:28 GMT+02:00 Svetlin Zarev <svetlin.angelov.zarev@gmail.
> com
> > >:
> >
> > > > 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.
> > >
> >
>