[ https://issues.apache.org/jira/browse/DELTASPIKE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855122#comment-13855122 ]
Romain Manni-Bucau commented on DELTASPIKE-472: ----------------------------------------------- Hi I don't get it too, we agreed to add xml config, is it this? BTW module.xml is a bad name IMO and can conflict with some containers. apache-deltaspike-xxx.xml would be better IMO (xxx=cdi or config surely). > Implement portable extensions that install custom beans when not running > inside a WAR file. > ------------------------------------------------------------------------------------------- > > Key: DELTASPIKE-472 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-472 > Project: DeltaSpike > Issue Type: Improvement > Components: Core > Reporter: John D. Ament > Assignee: John D. Ament > Fix For: 0.6 > > > In many cases, when you deploy with CDI you're using a self contained WAR > that has everything in it. However, in certain deployment models you can > reference external classpath entries that could be available to you, but not > scanned based on CDI scanning rules. > To work with these more efficiently, we need to implement some extensions > that do very basic things, mostly installing custom beans at runtime to the > destination applications. > I'll go through the application and identify cases where we need to install a > bean, ignoring things that obviously don't belong, e.g. @Typed classes which > are understood to not be installed. At a minimum we should create extensions > that encompass our primary features, where they don't already exist - for > example, Partial Bean is already an extension and needs no other work, Bean > Validation doesn't need an extension since it can be configured, Servlet > simply needs to be registered. Most of this work seems to be in Core. -- This message was sent by Atlassian JIRA (v6.1.5#6160)