[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
Actually, I thought reusing beans.xml was what you wanted so that's why I went this
way in the proposal ? I have no strong opinion here, but since beans.xml is used by both
JEE and JSE (and in the future OSGI) it seems like a good place to place this.
Designing API's is always hard (especially in XML) so I am very interested to hear
other ideas. The include/exclude approach is both powerful and familiar and easy to
understand. The "if" and "unless" are the simplest way to do
conditions and the attributes are similar to what ANT uses for conditional targets. And
implementation wise also think this should be simple to support using java's build in
regular expressions.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL:
https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira