[ https://jira.jboss.org/jira/browse/JBSEAM-3757?page=com.atlassian.jira.pl... ] Denis Forveille commented on JBSEAM-3757: ----------------------------------------- Could be related/similar to JBSEAM-3618 ? -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3757?page=com.atlassian.jira.pl... ] Pete Muir updated JBSEAM-3757: ------------------------------ Fix Version/s: 2.1.1.CR2 -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3757?page=com.atlassian.jira.pl... ] Denis Forveille updated JBSEAM-3757: ------------------------------------ Attachment: traces_ComponentDeploymentHandler.txt components.xml Dan, you were right, this is org.jboss.seam.transaction.EjbSynchronizations that is the problem, an no, there is no "<transaction:ejb-transaction>" in our component.xml I uploaded the trace and our component.xml thanks -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3757?page=com.atlassian.jira.pl... ] Dan Allen reassigned JBSEAM-3757: --------------------------------- Assignee: Dan Allen -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3757?page=com.atlassian.jira.pl... ] Dan Allen commented on JBSEAM-3757: ----------------------------------- Very interesting findings that have resulted from this issue. So here's the story. If you use any of the annotation inspection methods on a Class (i.e, getAnnotations(), getAnnotation(), isAnnotationPresent()) with the IBM JVM and any of the annotations present is not available on the classpath, the JVM craps out. So the search for the @Install on the component class after the scan is where it failed. That begs the question, why was EjbSynchronizations class even able to load at all. Well, as it turns out, the javax.ejb.SessionSynchronization interface is available in the EJB 2 API, which must be on your classpath. Thus, the class is loading, but the first time you inspect its annotations things fail. What I have done is added a call to getAnnotations() immediately after loading a class. If we cannot inspect the annotations, then it is the equivalent of the class not loading successfully. This isn't the only place this error will crop up, but it is the only place within Seam. For instance, if you define a component in components.xml that points to a class containing an annotation that is not available on the classpath, then Seam will fail to start. But then again, you shouldn't be defining the component anyway, so it because a debate of who's responsibility it is for the defensive programming. If it is a problem, it is a separate issue. -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3757?page=com.atlassian.jira.pl... ] Dan Allen resolved JBSEAM-3757. ------------------------------- Resolution: Done -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3757?page=com.atlassian.jira.pl... ] Pete Muir commented on JBSEAM-3757: ----------------------------------- Seam scans all classes in an application e.g. for Seam annotations... -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3757?page=com.atlassian.jira.pl... ] Dan Allen commented on JBSEAM-3757: ----------------------------------- Sorry, I should have said "Seam scans all classes with the @Name annotation in a classpath entry containing a seam.properties file, META/seam.properties file, or components.xml file", but you knew that, right? -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3757?page=com.atlassian.jira.pl... ] Denis Forveille commented on JBSEAM-3757: ----------------------------------------- Thanks for the explanation (and the fix!). Our app with Seam v2.1.1 CR1 now starts with the fix in WAS v6.1.0.17 in POJOs mode... About the annotation thing, maybe you coudl have a look at JBSEAM-3726. This is another JIRA I opened but this time with WebSphere v7.0 (JEE5+EJB3 as we are trying to move our app to this version of WAS and get the benefits of EJB3 and seam....) This *may* be another example of handling differently annotations between servers/jdk, even if I think that JBSEAM-3726 is more about a different implementation/interpreation of the JEE5 API in WAS than a difference in the JDKs . -- 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