[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3119) Multiple WAR in EAR verification, example, and document

Stuart Douglas (JIRA) jira-events at lists.jboss.org
Wed Apr 22 20:00:27 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBSEAM-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart Douglas updated JBSEAM-3119:
-----------------------------------

    Attachment: multi-war-wip.diff


I have attached a work in progress patch that attempts to resolve all the problems that stem from the use of the Lifecycle.application static. It involves some reasonably invasive changes, as every bit of code that calls these lifecycle methods now needs a reference to the application that they belong to.

There is still testing and some cleaning up to do, but I though I would post it here to get some feedback first to see if people agree with the approach I have taken.

Due to the API changes this is probably not going to be suitable for the 2.1 branch.

I did not do anything with the spring integration, it is still broken with respect to multiple war seam apps, I am not sure if this will even be possible to integrate multi war seam projects with spring properly.

> Multiple WAR in EAR verification, example, and document
> -------------------------------------------------------
>
>                 Key: JBSEAM-3119
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3119
>             Project: Seam
>          Issue Type: Feature Request
>          Components: Documentation Issues, Examples, Platform interoperability
>    Affects Versions: 2.1.0.A1
>            Reporter: Jay Balunas
>            Assignee: Shane Bryzak
>             Fix For: 2.2.0.CR1
>
>         Attachments: admin-dvdstore.diff, multi-war-wip.diff, multiple-wars.diff
>
>
> Create an example of two seam WAR applications inside of an EAR.  There has been quite a bit of forum traffic on the subject and it would be good to nail down an example and document.  There may also be errors and other issue that need to be worked out.
> An admin console type application to the standard booking application may be a good way to go.  It would be a real world/useful example.  

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