[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3820) JEE5 booking example fails on deploy

Jozef Hartinger (JIRA) jira-events at lists.jboss.org
Thu Feb 5 08:59:44 EST 2009

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

Jozef Hartinger commented on JBSEAM-3820:

I am not sure if this example should even be deployed to JBoss 4.2. The problem is that the default target creates and archive that works on Glassfish and probably other application server but it does not work on JBoss 5 unless you manually modify persistence.xml. I suggest (I already have it, just waiting for approval) adding new target that handles correct persistence.xml for JBoss 5. Should this target or the Glassfish one be default?

> JEE5 booking example fails on deploy
> ------------------------------------
>                 Key: JBSEAM-3820
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3820
>             Project: Seam
>          Issue Type: Bug
>          Components: Examples
>    Affects Versions: 2.1.1.CR2
>         Environment: JDK 5
> JBoss AS 5.0.0.GA
>            Reporter: Jozef Hartinger
>            Assignee: Norman Richards
>             Fix For: 2.1.2.CR1
>         Attachments: jee5-as5-jdk5-login.txt, jee5-as5-jdk5.txt
> When the example is being deployed I can see errors in server log. Despite these errors the main page loads however when I try to login the application fails because it is not able to create an instance of authenticator component. See jee5-as5-jdk5.txt for deployment errors and jee5-as5-jdk5-login.txt for the exception during login attempt.

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


More information about the seam-issues mailing list