Hi Harald!
The tomcat samples are targeting a tomcat installation where OWB and the rest
is already installed in either ${catalina.home}/lib or in a shared.loader (see
conf/catalina.properties). They are also not very fancy in terms of style atm.
Sure a thing we can heavily improve...
LieGrue,
strub
----- Original Message -----
> From: Harald Wellmann <[email protected]>
> To: [email protected]
> Cc:
> Sent: Tuesday, July 24, 2012 9:24 PM
> Subject: Re: Servlet Injection on Jetty
>
> Am 24.07.2012 21:00, schrieb Mark Struberg:
>> No it does not yet. The main reason is that jetty6 was _really_
>> great, but 7 and 8 miss that level by far. We did hit so many bugs in
>> jetty 7 and 8 that we even moved to tomcat7 for internal development
>> and tomcat7-maven-plugin instead of jetty-embedded.
>>
>
> Ok, so that leads to the next question - how to run the tomcat7-sample?
>
> Running mvn tomcat:deploy, I get the following error in the Tomcat log:
>
> java.lang.NoClassDefFoundError: javax/enterprise/context/spi/Contextual
>
> which is not really surprising, as the atinject and jcdi dependencies are
> missing, or have provided scope only.
>
> And what about the openwebbeans-tomcat7 artifact? Isn't that the one that
> makes servlet injection work?
>
> Does the sample assume these libs to be present in ${catalina.home}/lib?
>
>
>> Thus we have not had sufficient need for adding this feature. If you
>> like to contribute such a feature, then we would of course highly
>> welcome this move! I've seen your name on quite a few ASF mailing
>> lists already. If you have fun hacking on ASF projects then we would
>> really welcome your contributions. Also feel free to ask questions -
>> every question asked is a chance to improve our rather bad
>> documentation ;)
>
> I'm currently working on combining CDI and OSGi in the Pax CDI [1] project,
> and the basic non-web functionality is coming along nicely. The next step
> will
> be web support, based on Pax Web which is built on Jetty. Tomcat does not
> even
> have OSGi support.
>
> So this may indeed lead up to implementing the missing links, but it's too
> early to tell...
>
> I'm currently hopping back and forth between OpenWebBeans and Weld whenever
> I hit a gap in the one or the other. Of course, the general idea is that Pax
> CDI
> should work with any CDI implementation and any OSGi web container, but at
> the
> moment, it's mainly about breaking ground.
>
> [1] http://team.ops4j.org/wiki/display/PAXCDI/
>
> Best regards,
> Harald
>
