I have a Seam 2.2.0.GA application that is packaged in a war and deployed to a Tomcat 6 instance.
The web application depends on a jar that contains some Seam components (@Name annotated classes).
I have a requirement that these components need to be extensible at runtime. This means, it should be possible for implementors of my application (not known in advance) to define the same components with a higher precedence and deploy them in a jar in the lib directory of Tomcat.
I have made a small proof-of-concept, and if the jar is packaged in the WEB-INF/lib folder inside the war it works, but if it's deployed separately in Tomcat's lib it is not being picked up by Seam.
I have already checked that the jar contains an empty seam.properties file.
I suspect this is something related to Seam's deployment handler. Do you have any advice on what may be happening? Am I following the correct approach, or is there a better way to do this?
Thanks in advance,