[cdi-dev] [JBoss JIRA] (CDI-599) New lifecycle event to handle deployment/statup errors

[Mark Paluch (JIRA)]

     [ https://issues.jboss.org/browse/CDI-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Paluch updated CDI-599:
----------------------------
    Description: 
With CDI 1.2 the only way to react to deployment/validation errors is to fail on the container start.  Some exceptions could be handled/suppressed such as {{UnproxyableResolutionException}}. This ticket is to discuss a new lifecycle event which carries a deployment/validation error so a SPI developer can handle this problem. An example would be to allow unproxyable types in which case the error is reported, a portable extension tells the event to suppress the problem. This way the problem is handled and does not prevent the container start.

For the concrete example of allowing proxy

  was:With CDI 1.2 the only way to react to deployment/validation errors is to fail on the container start.  Some exceptions could be handled/suppressed such as {{UnproxyableResolutionException}}. This ticket is to discuss a new lifecycle event which carries a deployment/validation error so a SPI developer can handle this problem. An example would be to allow unproxyable types in which case the error is reported, a portable extension tells the event to suppress the problem. This way the problem is handled and does not prevent the container start.



> New lifecycle event to handle deployment/statup errors
> ------------------------------------------------------
>
>                 Key: CDI-599
>                 URL: https://issues.jboss.org/browse/CDI-599
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Events
>            Reporter: Mark Paluch
>
> With CDI 1.2 the only way to react to deployment/validation errors is to fail on the container start.  Some exceptions could be handled/suppressed such as {{UnproxyableResolutionException}}. This ticket is to discuss a new lifecycle event which carries a deployment/validation error so a SPI developer can handle this problem. An example would be to allow unproxyable types in which case the error is reported, a portable extension tells the event to suppress the problem. This way the problem is handled and does not prevent the container start.
> For the concrete example of allowing proxy



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)