AW: [EXVAL] InformationProviderBean not cached

2011-12-21 Thread Dreher, Markus
Hi gerhard, i created issue EXTVAL-139 [1]. Right now we workaround that problem by storing the InformationProviderBean in application scope by ourselves in an StartupListener, as we now we don't have a custom one. markus [1] https://issues.apache.org/jira/browse/EXTVAL-139 -Ursprünglic

[SOLVED] Jetty 8, MyFaces 2.1.5, Jersey 1.11 -> anyone got this to work?

2011-12-21 Thread Stephen Connolly
On 21 December 2011 14:59, Stephen Connolly wrote: > On 21 December 2011 13:50, Stephen Connolly > wrote: >> Ok, >> >> first side peeve is that I have to use >> >>   >>     >> org.apache.myfaces.webapp.StartupServletContextListener >>   >> >> with jetty 8... > > Ok, not my main problem, but the i

Re: Jetty 8, MyFaces 2.1.5, Jersey 1.11 -> anyone got this to work?

2011-12-21 Thread Stephen Connolly
On 21 December 2011 13:50, Stephen Connolly wrote: > Ok, > > first side peeve is that I have to use > >   >     > org.apache.myfaces.webapp.StartupServletContextListener >   > > with jetty 8... Ok, not my main problem, but the issue with the above is that for some reason Jetty is initializing the

Jetty 8, MyFaces 2.1.5, Jersey 1.11 -> anyone got this to work?

2011-12-21 Thread Stephen Connolly
Ok, first side peeve is that I have to use org.apache.myfaces.webapp.StartupServletContextListener with jetty 8... but that is not my issue (though it could be related) my issue is that as soon as com.sun.jersey.server.impl.container.servlet.JerseyServletContainerInitializer is on t

Re: [EXVAL] InformationProviderBean not cached

2011-12-21 Thread Gerhard Petracek
hi markus, if i remember correctly, it was done due to an issue with mojarra. please file a jira issue. regards, gerhard Am 21. Dezember 2011 13:41 schrieb Dreher, Markus : > Hi all, > > > > we use extVal 1.2.4. > > During performance tests we recognized that the synchronized Method > ExtValC

[EXVAL] InformationProviderBean not cached

2011-12-21 Thread Dreher, Markus
Hi all, we use extVal 1.2.4. During performance tests we recognized that the synchronized Method ExtValContextInternals.initInformationProviderBean is called many times for each client request. We don't configured a custom InformationProviderBean. In line 71 the created "default" InformationP