[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-521:
--------------------------------
On Weld-SE it seems we will soon be able to work around this by using
a custom createDeployment
override that works on explicit mentioned classes but what about JavaEE?
It seems to me this would be a good way to prototype this. We can then migrate the support
into the core as it matures
Actually support this is easy enough. What is harder is defining a nice configuration
format. We should brainstorm that here. Any ideas?
I strongly need a way to exclude classes depending on environment
that will also work with JavaEE (and consequently
in glassfish and JBoss etc.). I also suspect this solution will need to arrive soon in
order to
have a chance to get included in upcomming glassfish 3.01
The cutoff for 3.0.1 has long gone. We can aim for GF 3.1
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