[
https://issues.jboss.org/browse/CDI-35?page=com.atlassian.jira.plugin.sys...
]
Mark Struberg commented on CDI-35:
----------------------------------
If the spec would specify that the classpath scanning also needs to work for
'unfinished classes' then we would be able to implement such a functionality as
portable extension. I got pointed to Seams @Required, but this is currently not working in
OWB because we throw a DeploymentException if we find a bean with an unresolved class
dependency.
add support for 'optional' beans
--------------------------------
Key: CDI-35
URL:
https://issues.jboss.org/browse/CDI-35
Project: CDI Specification Issues
Issue Type: Feature Request
Reporter: Mark Struberg
sometimes it's neat to mark a bean as @Optional depending if a specified class can
get loaded or not.
This is a simple way to implement deployment specific functionality.
An example would be a BvalSupportBean which only should become active if the JSR-303 bean
validation API can be found on the classpath.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira