Performance problems in tomee 7.0.0

Hi, I don't know if I should report this or I should wait till final release. We are hitting performance problems with primefaces datatables with checkboxes in it listing eclipselink entities, 10 or 20 seconds to render a page. The problem is that a lot of exceptions (millions) are thrown

Re: Performance problems in tomee 7.0.0

Yep issue is primefaces validator usage which is not compatible with bval caching - strictly speaking both are right even if primefaces usage is surprising (they use an internal validator that they create and recreate without any config change from the quick code i saw). Le 23 déc. 2015 15:00,

Re: Performance problems in tomee 7.0.0

Interesting discussion. I am eclipselink and PrimeFaces user, currently using TomEE 1.7.3, and hope to use tomee 7.0.0 sometime in the future. On Dec 23, 2015 9:05 AM, "Romain Manni-Bucau" wrote: > Yep issue is primefaces validator usage which is not compatible with bval >

Re: Performance problems in tomee 7.0.0

hibernate-validator is an alternative for primefaces you can register in context .getExternalContext().getApplicationMap().put(APPLICATION_CONTEXT_KEY, myAppContext); myAppContext can be created in a ServletContextListener I think which would get the validator using @Inject Validator validator;

Re: Performance problems in tomee 7.0.0

On Dec 23, 2015 6:57 AM, "cocorossello" wrote: > > We are hitting performance problems with primefaces datatables with > checkboxes in it listing eclipselink entities, 10 or 20 seconds to render a > page. > May I ask which version of eclipselink are you using with tomee

Re: Performance problems in tomee 7.0.0

2.6.1 But the problem is not only with eclipselink, it just becomes more evident with it. -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/Performance-problems-in-tomee-7-0-0-tp4677292p4677296.html Sent from the TomEE Users mailing list archive at Nabble.com.

Re: Performance problems in tomee 7.0.0

I don't know how to use the container provided validator... Is there another validator besides bval? Do you think it's safe to use bval 0.5? -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/Performance-problems-in-tomee-7-0-0-tp4677292p4677298.html Sent from the

Re: Performance problems in tomee 7.0.0

I'll just use bval snapshot downloaded from jenkins, it works fine. -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/Performance-problems-in-tomee-7-0-0-tp4677292p4677300.html Sent from the TomEE Users mailing list archive at Nabble.com.

RE: [PRIVATE] ApplicationComposer 7.0.0 and @Jars

Ok, got it... But this is not really intuitive. We can't make a webapp with other modules ??? @Module @Classes( cdi = true, innerClassesAsBean = true, cdiInterceptors = {RequiredNewInterceptor.class, RequiredInterceptor.class}, value = {

Re: [PRIVATE] ApplicationComposer 7.0.0 and @Jars

@Descriptor(s) should allow you to setup JPA and keep it a simple webapp (single module) Romain Manni-Bucau @rmannibucau | Blog | Github | LinkedIn |

Re: [PRIVATE] ApplicationComposer 7.0.0 and @Jars

you can make an ear (so N webapps with N persistence modules and N ejbmodules) but this needs more wiring and I'm not sure all the annotations are 100% compatible with ear for CDI without producing an AppModule. We can definitively enhance it since in this case we know we have a single module !=

RE: [PRIVATE] ApplicationComposer 7.0.0 and @Jars

@Descriptor(s) work only if the descriptor is directly in the project. When I want to have a separate module for JPA for exemple, it doesn't work. I just retested. -Original Message- From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] Sent: mercredi 23 décembre 2015 18:39 To:

Re: [PRIVATE] ApplicationComposer 7.0.0 and @Jars

you can locate it, @Descriptor(name="persistence.xml", path="../jpa/src/main/resources/META-INF/persistence.xml") alternative would be to use @PersistenceUnitDefinition in a scanned bean (in value):

Re: [PRIVATE] ApplicationComposer 7.0.0 and @Jars

Thank you very much for the sample project made it easy to fix: https://issues.apache.org/jira/browse/TOMEE-1685 Romain Manni-Bucau @rmannibucau | Blog | Github | LinkedIn

Re: Performance problems in tomee 7.0.0

Hi yes it is the right moment to report it, fixed it for next release: https://issues.apache.org/jira/browse/BVAL-143 A fix could be to use the container provided Validator in org.primefaces.context.ApplicationContext (ie integrate primefaces with bean validation from EE since by default it