Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-3119

Multiple WAR in EAR verification, example, and document

    Details

    • Similar Issues:
      Show 10 results 

      Description

      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.

        Gliffy Diagrams

        1. admin-dvdstore.diff
          51 kB
          Stuart Douglas
        2. multiple-wars.diff
          2 kB
          Stuart Douglas
        3. multi-war-appname1.diff
          81 kB
          Stuart Douglas
        4. multi-war-wip.diff
          43 kB
          Stuart Douglas
        5. multi-war-wip-v2.diff
          46 kB
          Stuart Douglas
        6. seam-multi-war-2009-06-14.diff
          9 kB
          Stuart Douglas

          Issue Links

            Activity

            Hide
            pmuir Pete Muir added a comment -

            All issues reported here should be fixed. I've created WBRI-284 to create tests for this for Seam 3.

            Show
            pmuir Pete Muir added a comment - All issues reported here should be fixed. I've created WBRI-284 to create tests for this for Seam 3.
            Hide
            pmuir Pete Muir added a comment -

            All sub issues, closed, so closing.

            Show
            pmuir Pete Muir added a comment - All sub issues, closed, so closing.
            Hide
            reind Reind D added a comment -

            I tried out Stuart's earlier patch which looked to resolve JBSEAM-3849 (I could have been mistaken), but that I can confirm that that bug is still occurring in the latest Seam_2_2 branch.

            Looking at the new diff, I don't see anything that would resolve it directly.

            Show
            reind Reind D added a comment - I tried out Stuart's earlier patch which looked to resolve JBSEAM-3849 (I could have been mistaken), but that I can confirm that that bug is still occurring in the latest Seam_2_2 branch. Looking at the new diff, I don't see anything that would resolve it directly.
            Hide
            salvati Andre Salvati added a comment -

            This issue is closed but there is no changes on dvdstore example (Seam 2.2 trunk).

            Show
            salvati Andre Salvati added a comment - This issue is closed but there is no changes on dvdstore example (Seam 2.2 trunk).
            Hide
            susnet Susanne Jarl added a comment -

            This is working fine in Seam 2.2.0.GA except for one thing - the seam graphicImageStore. It is only working in the first loaded war and in the second war I get the following exception when trying to view an image using the s:graphicImage tag:

            javax.servlet.ServletException: java.lang.IllegalArgumentException: value of context variable is not an instance of the component bound to the context variable: org.jboss.seam.ui.graphicImage.graphicImageStore. If you are using hot deploy, you may have attempted to hot deploy a session or application-scoped component definition while using an old instance in the session.
            at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:74)
            at org.jboss.seam.ui.graphicImage.GraphicImageResource.getResource(GraphicImageResource.java:46)
            at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
            ...

            If I only deploy the second war, so there is only one war in the ear, I get no exception and the images shows up. So I guess this must be a bug. This worked fine in Seam 2.1.0.

            Show
            susnet Susanne Jarl added a comment - This is working fine in Seam 2.2.0.GA except for one thing - the seam graphicImageStore. It is only working in the first loaded war and in the second war I get the following exception when trying to view an image using the s:graphicImage tag: javax.servlet.ServletException: java.lang.IllegalArgumentException: value of context variable is not an instance of the component bound to the context variable: org.jboss.seam.ui.graphicImage.graphicImageStore. If you are using hot deploy, you may have attempted to hot deploy a session or application-scoped component definition while using an old instance in the session. at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:74) at org.jboss.seam.ui.graphicImage.GraphicImageResource.getResource(GraphicImageResource.java:46) at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) ... If I only deploy the second war, so there is only one war in the ear, I get no exception and the images shows up. So I guess this must be a bug. This worked fine in Seam 2.1.0.

              People

              • Assignee:
                pmuir Pete Muir
                Reporter:
                jbalunas Jay Balunas
              • Votes:
                33 Vote for this issue
                Watchers:
                25 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development