[weld-issues] [JBoss JIRA] Commented: (WELD-469) Exception in normal mode for incompletly annotated custom scopes.
[
https://jira.jboss.org/jira/browse/WELD-469?page=com.atlassian.jira.plugi...
]
Wolfgang Frech commented on WELD-469:
-------------------------------------
A bit more on suggestion c)
Of course it is not within the scope of Weld itself to develop an Eclipse plugin or an
extension to any other IDE. On the other hand, the container implementor must implement
the error detection logic anyway. Why not implement the error detection in a way that can
be run without the real container in a checking tool, may it be command line based (Maven,
Ant) or interactive in Eclipse or Netbeans? The community will use that and develop the
wrappers for the various environments.
Exception in normal mode for incompletly annotated custom scopes.
-----------------------------------------------------------------
Key: WELD-469
URL: https://jira.jboss.org/jira/browse/WELD-469
Project: Weld
Issue Type: Bug
Affects Versions: 1.0.1.Final
Environment: n/a
Reporter: Wolfgang Frech
If a custom scope is incomplete, say without the target annotation for field and type,
but without method, Weld now
- logs a warning
- uses the context for that scope
- marks the scope as invalid
- returns only Java, not ClientProxy refs for Beans.
According to the spec,the container must detect the missing annotation.
It should not complete the initialization.
In addition to that behavior, it may treat it on a best-effort basis, but only in
development mode.
In normal mode, the container should throw an exception that cannot be missed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira