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

[ https://jira.jboss.org/jira/browse/JBSEAM-3404?page=com.atlassian.jira.pl... ] Luis Tama commented on JBSEAM-3404: ----------------------------------- Hi Shane... I tested with the hibernate example as you did, and yes, it deployed fine... And, as you suggested, I compared the structures of the war files (please note "my" war file is a generated one, which is exploded BTW). I found the difference in the way they arrange the source code and the bin output folders. So let's see... AFAIK, JBoss Tools -> Create New Seam Web Project makes use of seam-gen tools, right? This seam-generated project creates these source folders: /src/action Here I have the Authenticator component, and my EntityHome classes, and everything related to actions / forms / conversations. Also my extended Identity component... The output folder is /WebContent/WEB-INF/dev, and is intended for incremental hot deployment during Seam development, as stated in section 2.8 in the docs. /src/model Here I must put the Entity classes, which will never be hot-deployable. The output folder is /build/classes, which is the default, and all the classes will be placed in /WEB-INF/classes at war generation. The BUG is the following: Initialization seems to not be properly scanning /WEB-INF/dev folder during seam application startup/deployment. So, a workaround could be to place these components in /src/model, but then they will not see hot deployable components inside /WEB-INF/dev (as stated in the docs). I already tested this workaround in my original app and it crashes because my Identity component and some other components depend on the ones in the hot deployable area, and even my pages don't render the data from these hot deployable beans/components, because they resolve to 'null' from the context they are in. I get this kind of exeptions in debug.seam: ... Exception during request processing: Caused by javax.el.PropertyNotFoundException with message: "Target Unreachable, identifier 'taskPlanificarArea' resolved to null" ... Evantually, in order to avoid all those errors, the final workaround is to change the output folder for the whole /src/action source folder, to be the default /build/classes -> WEB-INF/classes. This way my app works, but this turns off incremental hot deployment for all components... :-( I think this is a real bug, and I guess it's located in org.jboss.seam.init.Initialization.java (which has had some changes, specially in init(), redeploy() and createHotDeployment() methods... Maybe there are also some problems in org.jboss.seam.deployment.HotDeploymentStrategy.java Please test this scenario as I did, with a seam-generated app, or from a JBoss Tools Seam Web Project, not from the examples, because they don't have this hot deployable structure... Then you will reproduce the bug for sure... Hope this will be solved soon!! Thanks in advance!! -- 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