[jboss-jira] [JBoss JIRA] Commented: (JBAS-7032) Getting invalid deployment on what appears to be valid, a webbeans ear file.

[John Ament (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-7032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12475142#action_12475142 ] 

John Ament commented on JBAS-7032:
----------------------------------

It's funny that this got brought back up, I was about to update this as well.  After some playing with it, if I configure the server to enter a clustered environment, I can get it (admin-console.war) to deploy correctly but attempting to access it results in a no active conversation exception.  I've only been able to reproduce this with a webbeans deployment, I'm not sure about you.  From what I can tell, the fact that it's deploying is apparently a bug w/ the current webbeans ri which doesn't seem to work correctly in a clustered environment.  The no active conversation is a result of the webbeans deployer and filter taking higher precedence over the seam deployment (I verified by looking at the stack trace and seeing that the seam request was running through the webbeans filter, rather than the seam filter).  If you believe it's relevant, I'll post that stacktrace tomorrow.

> Getting invalid deployment on what appears to be valid, a webbeans ear file.
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-7032
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7032
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Deployers
>         Environment: JBoss AS 5.1
> JDK 1.6 u 13
> OpenSuSe 11.1 / SLES 10.2
>            Reporter: John Ament
>            Assignee: Shelly McGowan
>            Priority: Blocker
>             Fix For: JBossAS-5.2.0.Beta1
>
>         Attachments: WhatUpDawg.ear
>
>
> The best description I can give is from the forum.
> Basically, I have an EAR that appears to be completely valid, it's 2 war's and 1 ejb module.  It's built using web beans.  I get the described stack trace when either deploying via the UI or just dropping the EAR file in deploy.  However, I get different results.  When I drop the ear in and restart, it loads perfectly (my app) but embedded jopr fails.

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