[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
I don't know what you and Gavin did not like about static methods, but at least here
is one approach which will support all needs incl. my two scenarios. Why do you think it
will be easier/better to support system properties + class-availability ?
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