[
https://issues.jboss.org/browse/WELD-836?page=com.atlassian.jira.plugin.s...
]
Pete Muir closed WELD-836.
--------------------------
Assignee: Pete Muir
Resolution: Won't Fix
Closing as won't fix. The Weld Servlet support only targets JBoss AS 5 (EAP 5),
Tomcat, Jetty and GAE.
As Ales mentions, we plan proper integration (actually Stuart has most of it done) for AS7
Beta1 (the next milestone) so far better to concentrate on helping out with that work than
hacking the Servlet module to work!
Comment back if you want to help with that, Stuart can get you started.
WELD should try to resolve injection points in webapp's jar
files
-----------------------------------------------------------------
Key: WELD-836
URL:
https://issues.jboss.org/browse/WELD-836
Project: Weld
Issue Type: Feature Request
Reporter: Krzysztof Maslak
Assignee: Pete Muir
Attachments: WEB-INF_lib__jar_scanner.patch
Having following example scenario:
webapp.war
- /WEB-INF/lib/jar-with-some-nice-business-logic.jar - contains some injection points
( i.e. ICacheManager ) and using DefaultBean shipped with SeamSolder a default
implementation ( as the injection points have to be satisfied )
- /WEB-INF/lib/caching-solution-provider.jar - provides CacheManagerImpl
Having this simple example I would like to have this injection point satisfied by this
caching-solution-provider.jar. With such solution I would be able to change my
caching-solution-provider.jar without any code modification just by changing dependency in
pom.xml for another cache provider which would be able to satisfy my contract.
Then my development process would be similar to development in OSGi and blueprint as DI
provider. I would care only about fulfilling the contracts by various artefacts.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira