[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1002) Have injection check for existing component
Christian Bauer (JIRA)
jira-events at lists.jboss.org
Mon Jan 28 01:09:21 EST 2008
[ http://jira.jboss.com/jira/browse/JBSEAM-1002?page=comments#action_12397120 ]
Christian Bauer commented on JBSEAM-1002:
-----------------------------------------
-1, I don't want Seam complaining about my @In foo just because I happen to set the context variable with Contexts.getEventContext().set("foo").
> Have injection check for existing component
> -------------------------------------------
>
> Key: JBSEAM-1002
> URL: http://jira.jboss.com/jira/browse/JBSEAM-1002
> Project: JBoss Seam
> Issue Type: Feature Request
> Components: Core
> Reporter: Chuck Adams
>
> Right now, if a component is injected from an unbound context variable, it is treated as if it were null. Consequently if a field/setter is misspelled or not renamed when a component is renamed, this results in errors at the time the component is injected or accessed. When components are first set up, there should be a warning logged if there are any injections detected for context variables that were never defined or outjected anywhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list