[
http://jira.jboss.com/jira/browse/JBSEAM-1588?page=comments#action_12368818 ]
Anthony Whitford commented on JBSEAM-1588:
------------------------------------------
The lack of qualification for the component name presents this risk. Why not make it best
practice to qualify the component name? So built-in components are
"org.jboss.seam.Session", and my own objects would be
"com.domain.project.Session". I know it seems verbose, but it just seems
practical for large projects.
Seam Component name "session" reserved keyword
----------------------------------------------
Key: JBSEAM-1588
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1588
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.BETA1
Reporter: Christoph Aigner
Assigned To: Gavin King
Priority: Blocker
Fix For: 2.0.0.CR1
Original Estimate: 1 hour
Remaining Estimate: 1 hour
after migrating from 1.2 to 2.0 Seam throws the following error:
java.lang.IllegalArgumentException: value of context variable is not an instance of the
component bound to the context variable: session
the error occurs when I try to inject a class:
@Name("session")
@Scope(ScopeType.SESSION)
public class Session implements java.io.Serializable {
..
in:
@Stateless
@Name("remoting_desktop")
public class Desktop implements DesktopInterface {
@In(create=true,required=false) Session session;
..
worked with 1.2 as "session" is reserved
--
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