[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3404) Extended Identity component is not being loaded during Initialization process

[Shane Bryzak (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBSEAM-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12430101#action_12430101 ] 

Shane Bryzak commented on JBSEAM-3404:
--------------------------------------

I tested this again in trunk, dropping your extended Identity class directly into the hibernate example (which is a war project also).  It deployed as expected:

07:51:53,671 INFO  [Component] Component: org.jboss.seam.security.identity, scope: SESSION, type: JAVA_BEAN, class: org.
ostion.siplacad2.session.Identity

I suggest that you compare the structure of your war file to that of the hibernate example.

> Extended Identity component is not being loaded during Initialization process
> -----------------------------------------------------------------------------
>
>                 Key: JBSEAM-3404
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3404
>             Project: Seam
>          Issue Type: Bug
>          Components: Core, Security
>    Affects Versions: 2.1.0.BETA1
>         Environment: Windows XP SP2, JDK 1.5.0_16, JBoss AS 4.2.2.GA, Eclipse JEE Europa Winter (3.3.2), JBoss Tools 2.1.2.GA, JBoss Seam 2.1.0.BETA1 and 2.1.0-SNAPSHOT # 309
>            Reporter: Luis Tama
>            Assignee: Shane Bryzak
>         Attachments: home.page.xml, Identity.java
>
>
> I have this Extended Identity component, which lets me render different home pages according to the user roles:
> @Name("org.jboss.seam.security.identity")
> @Scope(ScopeType.SESSION)
> @Install(precedence = Install.APPLICATION)
> @BypassInterceptors
> @Startup
> public class Identity extends org.jboss.seam.security.Identity {
> 	private static final String DEFAULT_HOME_PAGE = "/home/home.xhtml";
> 	private String homePage = DEFAULT_HOME_PAGE;
> 	// getter and setter for homePage, and business logic
> 	// and some other important properties related to my business model...
> }
> In Seam 2.1.0.BETA1, it works fine:
> ...
> 21:53:16,159 INFO  [Initialization] Installing components...
> ...
> 21:53:16,921 INFO  [Component] Component: org.jboss.seam.security.identity, scope: SESSION, type: JAVA_BEAN, class: org.ostion.siplacad.session.Identity
> ...
> In Seam 2.1.0-SNAPSHOT # 303, it's not being loaded:
> ...
> 21:55:54,125 INFO  [Initialization] Installing components...
> ...
> 21:55:55,500 INFO  [Component] Component: org.jboss.seam.security.identity, scope: SESSION, type: JAVA_BEAN, class: org.jboss.seam.security.Identity
> ...
> 21:55:56,765 INFO  [Initialization] two components with same name, higher precedence wins: org.jboss.seam.security.identity
> ...
> So I can't access identity.homePage from my webapp. I can see this exception in debug.seam:
> Exception during request processing:
> Caused by javax.el.MethodNotFoundException with message: "Method not found: org.jboss.seam.security.Identity at 9527ee.renderHomePage()"
> ...
> I will not post the full stack trace, because the obvious reason for the problem is that the extended component is not being loaded by Seam.
> I checked Seam source code, comparing versions BETA1 and SNAPSHOT # 303:
> Class org.jboss.seam.Component has no changes between versions.
> Class org.jboss.seam.security.Identity has changed, but i don't think there is a problem there.
> Class org.jboss.seam.init.Initialization does have some changes, specially regarding hotDeploymentStrategy. I guess there is a problem is with the hacks over there.
> Please check this. I must tell I switched to the SNAPSHOT to not have the "NPE with hot Redeployment" issue, but now I can't even see my webapp!!

-- 
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