[
https://jira.jboss.org/browse/WELD-644?page=com.atlassian.jira.plugin.sys...
]
Pete Muir closed WELD-644.
--------------------------
Resolution: Done
With the changes due to WELD-521, classloading for bean definition is now done inside
Weld, so we can catch these errors and log them.
Heiko, please test BETA1 (out Monday with luck) with your scenario, and let me know if you
still see any problems - it's possible I haven't protected all paths.
WeldDeployer should ignore classes which cause ClassNotFoundException
and NoClassDefFoundError
----------------------------------------------------------------------------------------------
Key: WELD-644
URL:
https://jira.jboss.org/browse/WELD-644
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Affects Versions: 1.0.1.Final
Reporter: Heiko Braun
Assignee: Pete Muir
Fix For: 1.1.0.BETA1
We are working on the GWT/CDI integration. If an application packages GWT client classes
that depend on gwt-user.jar and the weld deployer kicks in it chokes in classes that
import GWT client API. This happens because the usage of reflection to scan for annotation
meta data, loads all classes and forces all dependencies to be present.
These classes can be excluded from the web application packaging, but it's nothing
people usally do,
because they are required when running the GWT hosted mode.
So in order to simplify things, I would suggest we simply log and skip classes that
cannot be scanned due to CNFE and the like, instead of preventing the deployment at all.
--
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