[weld-issues] [JBoss JIRA] Updated: (WELD-836) WELD should try to resolve injection points in webapp's .jars

[Krzysztof Maslak (JIRA)]

     [ https://issues.jboss.org/browse/WELD-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Krzysztof Maslak updated WELD-836:
----------------------------------

    Description: 
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.
But it increases bootstrap so a concept of some filtering is required.

  was:
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.



> WELD should try to resolve injection points in webapp's .jars
> -------------------------------------------------------------
>
>                 Key: WELD-836
>                 URL: https://issues.jboss.org/browse/WELD-836
>             Project: Weld
>          Issue Type: Feature Request
>            Reporter: Krzysztof Maslak
>         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.
> But it increases bootstrap so a concept of some filtering is required.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira