[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
My needs are:
1) Support running environments: JEE, JSE, OSGI (but I don't think this can be
auto-detected - I think only the application will be able to know what the environment is,
which is why a static method is good).
2) Support different versions of the same software - f.x. "standard",
"professionel", "enterprise".
Both these needs affect the classpath and what classes/packages should be scanned (f.x. my
app's OSGI specific classes will simply not resolve if running as JSE and maybe not
under JEE) . Normally, in Java this is not a problem because the Java standard has lazy
loading of classes.... But since the weld scanner loads everything, this will cause
applications to "blow up" unless we have a way to customize where to look.
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