Re: UnsatisfiedResolutionException with qualifiers -- what am I doing wrong?

Hi Emmanuel, did you check your jar was not in the default excludes? (try renaming it "foo.jar" to test quickly) Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

Re: UnsatisfiedResolutionException with qualifiers -- what am I doing wrong?

Hello,     thank you for the answer! No, definitely it's not in the default excludes. Already injecting bunch of things from that JAR. Also, the interface is in a JAR, but the producer is in the main code of the app. And it's the producer which can't be found.     From your answer I take it

Re: UnsatisfiedResolutionException with qualifiers -- what am I doing wrong?

yes, try reproducing it in a sample maybe Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn |

UnsatisfiedResolutionException with qualifiers -- what am I doing wrong?

Hello,     I'm confused about a CDI error, I would expect this to work... What am I doing wrong? It's true otherwise that the interface is defined in another JAR than the producer but I wouldn't expect it to be a problem...     At runtime I get: 08-Mar-2018 12:27:57.287 SEVERE

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

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

velocityengine in cdi applicationscoped

TomEE 7.0.3 (i cannot upgrade to 7.0.4) i am trying to switch from using XSLT to using velocity templates. i noticed that velocity was included as a lib in TomEE if i declare VelocityEngine inside a CDI @ApplicationScoped try {             VelocityEngine velocityEngine = new VelocityEngine();

FTP trace level logging?

Hello, this seems simple enough but having difficulty in enabling FTP wire trace logging in TomEE; using org.apache.commons.net.ftp.FTPClient and would think I could either update logging.properties to include debug or trace level logging to that, or use a -D switch but cannot find anything.

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

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

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