Hi Jochen,

... AND if javax.servlet.annotation is imported . Annotation scanning works
> now. That's why we use OSGi - to have more control, don't we?


yes, and that's why I alway use the maven-bundle-plugin to build all my
bundles (including war).
In that case those imports aren't forgotten :D

regards, Achim



2014-11-14 15:55 GMT+01:00 jochenw <[email protected]>:

> Hi Achim,
>
> ... AND if javax.servlet.annotation is imported . Annotation scanning works
> now. That's why we use OSGi - to have more control, don't we?
>
> Servlet as inner class - I don't know whether the scanner should support
> that, one can solve this easily. It's just a bit tricky to find out that it
> doesn't work that way.
>
> Regarding the resources: yes, there we need to do some refactoring.
> Starting
> with a "normal" war, one easily uses things like getBaseDirectory() to
> access images etc.
>
> Again thanks for the help - you brought me on the right track.
>
> Regards,
> Jochen
>
>
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/pax-web-war-stays-in-deploying-state-tp4036280p4036427.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>



-- 

Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>

Software Architect / Project Manager / Scrum Master

Reply via email to