Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-9013

Cannot deploy Seam Portlet Example to JBoss EPP 4.3

        Details

        • Steps to Reproduce:
          Hide

          1) download EPP 4.3 runtime http://download.devel.redhat.com/released/JBossEPP/4.3/GA/jboss-epp-4.3.GA.zip
          2) Create new EPP server
          3) make sure that in server deployment settings "Use the JBoss deploy folder" is selected
          4) Help -> Project Examples... -> Portlet -> JBoss Seam Portlet Example
          5) try to deploy to the server

          Show
          1) download EPP 4.3 runtime http://download.devel.redhat.com/released/JBossEPP/4.3/GA/jboss-epp-4.3.GA.zip 2) Create new EPP server 3) make sure that in server deployment settings "Use the JBoss deploy folder" is selected 4) Help -> Project Examples... -> Portlet -> JBoss Seam Portlet Example 5) try to deploy to the server

          Description

          See log attached.

            Gliffy Diagrams

            1. Text File
              server.log
              45 kB
              Pavol Srna
            2. File
              server.log2
              86 kB
              Pavol Srna
            3. File
              server.log3
              94 kB
              Pavol Srna
            4. File
              server.log4
              78 kB
              Libor Zoubek
            5. XML File
              testseamportlet-ds.xml
              0.5 kB
              Snjezana Peco
            1. jbide-9013.png
              96 kB
            2. portal.screen.png
              26 kB

              Activity

              Ascending order - Click to sort in descending order
              23 older comments
              Hide
              Permalink
              lzoubek Libor Zoubek added a comment -

              I was basically following Pavol's steps from description of this jira, so:
              I have gentoo linux, new workspace, JDK 1.6.0_27
              1. downloaded EPP 4.3.CP06
              2. uncommented admin=admin to enable JMX
              3. started JBossTools (latest 3.2.2M2 build)
              4. Added EPP runtime using runtime detector
              5. downloaded the example, in the meanwhile started EPP
              6. deployed datasource and example
              7. reached it in browser

              Show
              lzoubek Libor Zoubek added a comment - I was basically following Pavol's steps from description of this jira, so: I have gentoo linux, new workspace, JDK 1.6.0_27 1. downloaded EPP 4.3.CP06 2. uncommented admin=admin to enable JMX 3. started JBossTools (latest 3.2.2M2 build) 4. Added EPP runtime using runtime detector 5. downloaded the example, in the meanwhile started EPP 6. deployed datasource and example 7. reached it in browser
              Hide
              Permalink
              snjeza Snjezana Peco added a comment -

              Libor,

              Could you try to reproduce the issue using JBDS 4.1.1.CR1?

              Show
              snjeza Snjezana Peco added a comment - Libor, Could you try to reproduce the issue using JBDS 4.1.1.CR1?
              Hide
              Permalink
              lzoubek Libor Zoubek added a comment -

              I still reproduced it on 4.1.1.CR1, stacktrace is same as before - server.log4

              Show
              lzoubek Libor Zoubek added a comment - I still reproduced it on 4.1.1.CR1, stacktrace is same as before - server.log4
              Hide
              Permalink
              snjeza Snjezana Peco added a comment -

              There were two versions of richfaces libraries that were causing the problem (based on the error in the server.log4)
              Since the fix doesn't change the code, you can try to verify it using any JBDS. It is only necessary to import the project example again.

              There is only a problem related to the authentication. You can see this issue if you try to log in to the application.
              This is an upstream/runtime issue. There is already a jira for it - JBIDE-8289.

              Show
              snjeza Snjezana Peco added a comment - There were two versions of richfaces libraries that were causing the problem (based on the error in the server.log4) Since the fix doesn't change the code, you can try to verify it using any JBDS. It is only necessary to import the project example again. There is only a problem related to the authentication. You can see this issue if you try to log in to the application. This is an upstream/runtime issue. There is already a jira for it - JBIDE-8289 .
              Hide
              Permalink
              psrna Pavol Srna added a comment -

              Thanks Snjezana, now it works! Closing.

              Show
              psrna Pavol Srna added a comment - Thanks Snjezana, now it works! Closing.

                People

                • Assignee:
                  snjeza Snjezana Peco
                  Reporter:
                  psrna Pavol Srna
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Development