Re: velocityengine in cdi applicationscoped

Means the bean is vetoed, probably cause the class cannot be loaded surprisingly. Le 8 mars 2018 21:58, "Matthew Broadhead" a écrit : > i didn't add velocity in my app i was trying to use the TomEE one. i moved > the code out of the @ApplicationScoped and into a

Re: velocityengine in cdi applicationscoped

i didn't add velocity in my app i was trying to use the TomEE one. i moved the code out of the @ApplicationScoped and into a @Named and the container started but then the @Named bean resolved to null javax.el.PropertyNotFoundException: Target Unreachable, identifier 'eventsBean' resolved to

Re: velocityengine in cdi applicationscoped

Then you can use the force-load option if you have velocity in your app or remove it from here to use tomee one That said tomee should only need velocity in embedded mode and not others so maybe a dependency leak to fix if not already. Le 8 mars 2018 19:21, "Matthew Broadhead"

Re: velocityengine in cdi applicationscoped

btw is there some way to define VelocityEngine as a Resource in tomee.xml so it doesn't have to be loaded each time? On 08/03/2018 19:15, Romain Manni-Bucau wrote: Hi If you keep the bean and remove velocity you will probably get the same error until its classloader is not correctly set and

Re: velocityengine in cdi applicationscoped

if i remove velocity from NoteDao then TomEE starts fine On 08/03/2018 19:15, Romain Manni-Bucau wrote: Hi If you keep the bean and remove velocity you will probably get the same error until its classloader is not correctly set and you have extensions in your webapp but it should fail at

Re: velocityengine in cdi applicationscoped

Hi If you keep the bean and remove velocity you will probably get the same error until its classloader is not correctly set and you have extensions in your webapp but it should fail at runtime. Le 8 mars 2018 18:48, "Matthew Broadhead" a écrit : > TomEE 7.0.3