12 Replies Latest reply on Aug 5, 2009 3:06 AM by Søren Hilmer

    JBoss 5 Integration

    Robert Brown III Newbie

      Folks:

      I am currently interested in using JBoss Portal for various sites that I want to create.

      Unfortunately, what has prevented me from using JBoss Portal is the fact that I have several pre- existing applications that are using JEE 5. It is my understanding that only JBoss 5 supports JEE 5.

      Is anyone planning on getting JBoss Portal to work on JBoss 5? If not, then I am going to have to stick with using Liferay/Sun Webspace...

      Could someone give some idea if and when a JBoss 5 supported version of JBoss Portal is coming?

      Thank you.

        • 2. Re: JBoss 5 Integration
          lucio piccoli Newbie

          just tried the wiki instructions

          JBoss_Portal_Branch_2_7_AS5 portal doesnt compile for me.

          [execmodules] C:\src\jbossportal\portal\wsrp\src\main\org\jboss\portal\wsrp\deployment\WSRPConsumerDeploymentImpl.java:67: cannot find symbol [execmodules] symbol : class WSRPProducerMetaData
          [execmodules] location: class org.jboss.portal.wsrp.deployment.WSRPConsumerDeploymentImpl
          [execmodules] for (WSRPProducerMetaData producer : deployments.getDeployments())

          i assume it is just a temp glitch cause i got no idea.

          i will try another co later.

          -lp

          • 3. Re: JBoss 5 Integration
            Andrew Dale Newbie

            Hi,

            I followed the instructions from the following page http://www.jboss.org/community/wiki/JBossPortalonAS5, but rather than using 5.1.0Beta1, I am using 5.1.0.GA.

            Both maven compiling steps went fine for me, but unfortunately the compiling of the JBoss_Portal_Branch_2_7_AS5 had i few issues. Here is the output:

            [javac] Compiling 249 source files to /commons/data/downloads/jboss/portal_as5/portal/wsrp/output/classes
             [javac] /commons/data/downloads/jboss/portal_as5/portal/wsrp/src/main/org/jboss/portal/test/wsrp/config/ProducerConfigurationTestCase.java:45: warning: [deprecation] org.jboss.xb.binding.XercesXsMarshaller in org.jboss.xb.binding has been deprecated
             [javac] import org.jboss.xb.binding.XercesXsMarshaller;
             [javac] ^
             [javac] /commons/data/downloads/jboss/portal_as5/portal/wsrp/src/main/org/jboss/portal/test/wsrp/deployment/DeploymentTestCase.java:33: package org.jboss.portal.metadata.wsrp.consumer does not exist
             [javac] import org.jboss.portal.metadata.wsrp.consumer.ConsumerDeploymentsMetaData;
             [javac] ^
             [javac] /commons/data/downloads/jboss/portal_as5/portal/wsrp/src/main/org/jboss/portal/test/wsrp/deployment/DeploymentTestCase.java:34: package org.jboss.portal.metadata.wsrp.consumer does not exist
             [javac] import org.jboss.portal.metadata.wsrp.consumer.WSRPProducerMetaData;
             [javac] ^
             [javac] /commons/data/downloads/jboss/portal_as5/portal/wsrp/src/main/org/jboss/portal/wsrp/WSRPResourceURL.java:30: warning: [deprecation] org.jboss.portal.common.util.MediaType in org.jboss.portal.common.util has been deprecated
            ..............
            I discovered that to resolve this build issue I had to add the jar create from the mvn install for the metadata (metadata-wsrp-trunk-SNAPSHOT.jar). This then leads to the following build problem:
            [javac] /commons/data/downloads/jboss/portal_as5/portal/wsrp/src/main/org/jboss/portal/wsrp/deployment/WSRPConsumerDeploymentImpl.java:43: package org.jboss.portal.deployer.wsrp.container does not exist
             [javac] public class WSRPConsumerDeploymentImpl implements org.jboss.portal.deployer.wsrp.container.WSRPDeployment
             [javac] ^
             [javac] /commons/data/downloads/jboss/portal_as5/portal/wsrp/src/main/org/jboss/portal/wsrp/deployment/WSRPConsumerDeploymentImpl.java:65: cannot find symbol
             [javac] symbol : class ConsumerDeploymentsMetaData
             [javac] location: class org.jboss.portal.wsrp.deployment.WSRPConsumerDeploymentImpl
             [javac] public void deployConsumer (ConsumerDeploymentsMetaData deployments)
             [javac] ^
            

            Adding the jar created from mvn package for the deployer fixes this build issue.

            This gives me the following structure in jboss server/all/deploy (NOTE, gif and png are removed from the output):

            [dalea@dalef9 deploy]$ tree jboss-portal/
            jboss-portal/
            |-- jboss-portal.sar
            | |-- META-INF
            | | |-- aliases.txt
            | | |-- default-object.xml
            | | |-- jboss-dependency.xml
            | | `-- jboss-service.xml
            | |-- conf
            | | |-- bundles
            | | | |-- Resource.properties
            | | | |-- Resource_fr.properties
            | | | |-- Resource_it.properties
            | | | |-- Resource_ja.properties
            | | | `-- Resource_pt.properties
            | | |-- config.xml
            | | |-- data
            | | |-- hibernate
            | | | |-- instance
            | | | | |-- domain.hbm.xml
            | | | | `-- hibernate.cfg.xml
            | | | |-- portal
            | | | | |-- domain.hbm.xml
            | | | | `-- hibernate.cfg.xml
            | | | |-- portlet
            | | | | |-- domain.hbm.xml
            | | | | `-- hibernate.cfg.xml
            | | | |-- user
            | | | | |-- domain.hbm.xml
            | | | | |-- hibernate.cfg.xml
            | | | | `-- setup.txt
            | | | `-- workflow
            | | | `-- hibernate.cfg.xml
            | | |-- identity
            | | | |-- identity-config.xml
            | | | |-- ldap_identity-config.xml
            | | | |-- profile-config.xml
            | | | `-- standardidentity-config.xml
            | | |-- login-config.xml
            | | |-- standardjboss-portlet.xml
            | | `-- theme
            | | `-- portal-layout.tld
            | |-- dtd
            | | |-- identity-config_2_6.dtd
            | | `-- profile-config_2_6.dtd
            | `-- lib
            | |-- commons-collections.jar
            | |-- commons-fileupload.jar
            | |-- commons-io.jar
            | |-- ehcache.jar
            | |-- freemarker.jar
            | |-- jboss-portlet-api-lib.jar
            | |-- jbpm-identity.jar
            | |-- jbpm-jpdl.jar
            | |-- portal-api-lib.jar
            | |-- portal-common-lib.jar
            | |-- portal-common-portal-lib.jar
            | |-- portal-core-lib.jar
            | |-- portal-identity-lib.jar
            | |-- portal-identity-sso-lib.jar
            | |-- portal-jems-lib.jar
            | |-- portal-portlet-bridge-lib.jar
            | |-- portal-portlet-controller-lib.jar
            | |-- portal-portlet-federation-lib.jar
            | |-- portal-portlet-lib.jar
            | |-- portal-portlet-management-lib.jar
            | |-- portal-portlet-server-lib.jar
            | |-- portal-registration-lib.jar
            | |-- portal-search-lib.jar
            | |-- portal-security-lib.jar
            | |-- portal-server-lib.jar
            | |-- portal-theme-lib.jar
            | |-- portal-web-lib.jar
            | |-- portal-workflow-lib.jar
            | |-- portals-bridges-common.jar
            | |-- portlet-api.jar
            | `-- tagsoup.jar
            |-- portal-ajax.war
            | |-- WEB-INF
            | | |-- jboss-web.xml
            | | `-- web.xml
            | `-- dyna
            | |-- builder.js
            | |-- controls.js
            | |-- dragdrop.js
            | |-- dyna.js
            | |-- effects.js
            | |-- prototype.js
            | |-- scriptaculous.js
            | |-- slider.js
            | |-- style.css
            | `-- unittest.js
            |-- portal-aop.xml
            |-- portal-core.war
            | |-- WEB-INF
            | | |-- classes
            | | | |-- Resource.properties
            | | | |-- Resource_de.properties
            | | | |-- Resource_fr.properties
            | | | |-- Resource_it.properties
            | | | |-- Resource_ja.properties
            | | | |-- Resource_pt_BR.properties
            | | | |-- nodesk
            | | | | |-- Modes.properties
            | | | | `-- WindowStates.properties
            | | | |-- phalanx
            | | | | |-- Modes.properties
            | | | | `-- WindowStates.properties
            | | | `-- templates
            | | | `-- user
            | | | |-- emailTemplate.tpl
            | | | `-- emailTemplate_fr.tpl
            | | |-- jboss-portal-app.xml
            | | |-- jboss-portlet.xml
            | | |-- jboss-web.xml
            | | |-- jsp
            | | | |-- content
            | | | | `-- portlet_editor.jsp
            | | | |-- error
            | | | | |-- page.jsp
            | | | | `-- portal.jsp
            | | | |-- header
            | | | | |-- header.jsp
            | | | | `-- tabs.jsp
            | | | `-- test
            | | | |-- testIf01.jsp
            | | | |-- testInclude01.jsp
            | | | |-- testInclude02.jsp
            | | | |-- testInclude03.jsp
            | | | |-- testIterate01.jsp
            | | | |-- testIterate02.jsp
            | | | |-- testIterate03.jsp
            | | | |-- testTaglib01.jsp
            | | | `-- testTaglib02.jsp
            | | |-- portal-layouts.xml
            | | |-- portal-lib.tld
            | | |-- portal-renderSet.xml
            | | |-- portal-themes.xml
            | | |-- portlet-instances.xml
            | | |-- portlet.xml
            | | |-- theme-basic-lib.tld
            | | `-- web.xml
            | |-- css
            | | |-- login.css
            | | `-- modal.css
            | |-- images
            | | |-- corners
            | | | |-- 7px
            | | | | |-- ....gif
            | | | `-- gray-header.gif
            | | |-- favicon.ico
            | | |-- logo-small-blue.gif
            | | |-- modal
            | | | |-- .....gif ...png
            | | `-- portletIcon_Default1.gif
            | |-- js
            | | |-- login.js
            | | |-- modal.js
            | | `-- tooltip
            | | |-- domLib.js
            | | |-- domTT.js
            | | |-- domTT_drag.js
            | | `-- fadomatic.js
            | |-- layouts
            | | |-- 1column
            | | | `-- index.jsp
            | | |-- 3columns
            | | | `-- index.jsp
            | | |-- common
            | | | |-- modal_body.jsp
            | | | `-- modal_head.jsp
            | | `-- generic
            | | |-- index.jsp
            | | `-- maximized.jsp
            | `-- themes
            | |-- common
            | | |-- common.css
            | | |-- portlet-editor.css
            | | `-- tooltip.css
            | |-- industrial
            | | |-- images
            | | | |-- .....gif
            | | | |-- Thumbs.db
            | | `-- portal_style.css
            | |-- maple
            | | |-- images
            | | | |-- Thumbs.db
            | | | |-- .....gif
            | | `-- portal_style.css
            | `-- renewal
            | |-- images
            | | |-- .......gif
            | `-- portal_style.css
            `-- portal-server.war
             |-- WEB-INF
             | |-- classes
             | | |-- Resource.properties
             | | |-- Resource_de.properties
             | | |-- Resource_fr.properties
             | | |-- Resource_it.properties
             | | |-- Resource_ja.properties
             | | `-- Resource_pt_BR.properties
             | |-- context.xml
             | |-- jboss-web.xml
             | `-- web.xml
             |-- images
             | |-- .........png
             `-- login.jsp
            
            56 directories, 323 files
            


            This gives me the following structure in jboss server/all/deployers:
            [dalea@dalef9 deployers]$ tree jboss-portal.deployer/
            jboss-portal.deployer/
            |-- META-INF
            | `-- deployer-jboss-beans.xml
            |-- conf
            | `-- standardjboss-portlet.xml
            |-- deployer-portal-trunk-SNAPSHOT.jar
            |-- deployer-portlet-trunk-SNAPSHOT.jar
            |-- deployer-theme-trunk-SNAPSHOT.jar
            |-- deployer-wsrp-trunk-SNAPSHOT.jar
            |-- dtd
            | |-- jboss-portal-app_2_6.dtd
            | |-- jboss-portlet_2_6.dtd
            | |-- jboss-wsrp-consumer_2_6.dtd
            | |-- jboss-wsrp-producer_2_6.dtd
            | |-- portal-layouts_2_7.dtd
            | |-- portal-object_2_6.dtd
            | |-- portal-renderset_2_7.dtd
            | |-- portal-theme_2_7.dtd
            | `-- portlet-instances_2_6.dtd
            |-- metadata-metadata-trunk-SNAPSHOT.jar
            |-- metadata-theme-trunk-SNAPSHOT.jar
            |-- metadata-wsrp-trunk-SNAPSHOT.jar
            |-- tld
            | |-- portal-layout.tld
            | |-- portlet.tld
            | `-- portlet_2_0.tld
            `-- xsd
             |-- jboss-wsrp-consumer_2_6.xsd
             |-- jboss-wsrp-producer_2_6.xsd
             `-- jboss-wsrp-producer_2_7.xsd
            
            5 directories, 24 files
            
            
            On deploy this gives me the following exception:
            
            
            13:27:52,889 INFO [TomcatDeployment] deploy, ctxPath=/admin-console
            13:27:52,944 INFO [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/admin-console'
            13:27:55,516 INFO [TomcatDeployment] deploy, ctxPath=/
            13:27:55,561 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
            13:27:55,610 INFO [TomcatDeployment] deploy, ctxPath=/portal-ajax
            13:27:55,682 INFO [TomcatDeployment] deploy, ctxPath=/portal
            13:27:55,881 ERROR [AbstractKernelController] Error installing to Installed: name=vfsfile:/usr/local/jboss-5.1.0.GA/server/all/deploy/jboss-portal/jboss-portal.sar/ state=Start mode=Manual requiredState=Installed
            org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/usr/local/jboss-5.1.0.GA/server/all/deploy/jboss-portal/jboss-portal.sar/
             at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
             at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177)
             at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
             at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
             at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
             at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
             at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
             at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
             at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
             at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
             at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
             at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
             at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
             at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
             at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
             at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
             at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
             at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
             at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
             at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
             at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
             at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
             at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
             at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
             at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
             at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
             at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
             at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
             at org.jboss.Main.boot(Main.java:221)
             at org.jboss.Main$1.run(Main.java:556)
             at java.lang.Thread.run(Thread.java:619)
            Caused by: java.lang.NullPointerException
             at org.jboss.portal.deployer.portlet.ObjectDeployer.internalDeploy(ObjectDeployer.java:64)
             at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
             at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
             ... 29 more
            13:27:55,896 WARN [DelegatingURLFactoryService] Unregistration of URL factory org.jboss.portal.core.controller.command.mapper.SignOutURLFactory@1bddffe failed because it is not registered
            13:27:56,054 INFO [ClientENCInjectionContainer] STOPPED CLIENT ENC CONTAINER: tagsoup
            13:27:56,082 INFO [ClientENCInjectionContainer] STOPPED CLIENT ENC CONTAINER: portal-server-lib
            13:27:56,115 INFO [ClientENCInjectionContainer] STOPPED CLIENT ENC CONTAINER: freemarker
            13:27:56,246 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
            
            DEPLOYMENTS MISSING DEPENDENCIES:
             Deployment "vfsfile:/usr/local/jboss-5.1.0.GA/server/all/deploy/jboss-portal/portal-core.war/" is missing the following dependencies:
             Dependency "portal:deployer=InstanceDeployment" (should be in state "Real", but is actually in state "** NOT FOUND Depends on 'portal:deployer=InstanceDeployment' **")
             Dependency "portal:deployer=ObjectDeployment" (should be in state "Real", but is actually in state "** NOT FOUND Depends on 'portal:deployer=ObjectDeployment' **")
             Dependency "portal:deployer=PortletDeployment" (should be in state "Real", but is actually in state "** NOT FOUND Depends on 'portal:deployer=PortletDeployment' **")
            
            
            Does anyone have any ideas what has gone wrong, or how to fix it ?
            
            Cheers,
            
            Andy
            


            • 4. Re: JBoss 5 Integration
              Matt Wringe Master

              Your compile issues are because you were not following the instructions (http://www.jboss.org/community/wiki/JBossPortalonAS5) it states what you need to do with the metadata and deployer modules before compiling the portal.

              As for the NPE issue you are having, I am not sure exactly what is causing this issue at this time. I not tested the code with JBoss 5.1.x

              Please note that we will not be going forward with this specific implementation, but AS5 support will be coming in another form.

              • 5. Re: JBoss 5 Integration
                Gregor Rosenauer Newbie

                mwringe, could you please elaborate more on the last paragraph?
                When and how does Red Hat plan to support Portal under JBoss 5?
                I hope it won't take as long as JBoss 5 itself,-)

                There is also currently no enterprise version of JBoss Portal that runs on JBoss 5, are there any plans, maybe to coincide with the release of EAP 5?

                • 6. Re: JBoss 5 Integration
                  Thomas Heute Master

                  EPP 4.3 runs on EAP 4.3 and embeds a derivated product from the community bits of JBoss Portal 2.7

                  There is no plan to ship a product from the community bits of JBoss Portal 2.7 with EAP 5 although we worked on the integration and the Wiki explain how to run this, but this is unmaintained.

                  As you may have seen we partnered with eXo platform for our next version of the project: http://blog.jboss-portal.org/2009/06/welcome-exo.html

                  All our efforts are going into that direction now and this will run under EAP 5. We aim at a preview release at the end of the month but some legal aspects are holding us down to share code for now :-/

                  • 7. Re: JBoss 5 Integration
                    Gregor Rosenauer Newbie

                    Thank you Thomas for your quick reply! This was very informative, and I'm looking forward to the integration of the two portal projects, must have missed that one... (blame my Vista RSS-gadget,-)

                    If the method in the howto is not supported (neither officially nor inofficially) it does not seem very feasible to go that route, better wait for the new version...

                    Does the eXo-merger also affect the Portlet-Bridge? I'd be happy to see improvements there, too, esp. regarding RichFaces-components (WAI-support?) and some other issues we are currently facing.

                    • 8. Re: JBoss 5 Integration
                      Thomas Heute Master

                      Portlet Bridge always improves (see the recent 2.0 Alpha release), it supports theorically any portlet container (it is based on the API) but is tested on the JBoss Portlet Container which is used by JBoss Portlet 2.7 and will be used in the merged project.

                      So yes, the JBoss Portlet Bridge project is a very important project on which we are investing. Help is always welcome :)

                      • 9. Re: JBoss 5 Integration
                        Gregor Rosenauer Newbie

                        Great to see cross-container-compatibility! Even if we use only JBoss for now, it's a big plus regarding standards-compliance and code quality.

                        Also good to hear the commitment to the portlet bridge, after a Google-esk beta-cycle,-)

                        Wink noted and directed to my colleague responsible for the portal project here,-) ("der Wink mit dem Zaunpfahl" wie wir Österreicher sagen, mir fällt es gerade nicht auf Schwyzerdytsch ein;)...

                        • 10. Re: JBoss 5 Integration
                          Thomas Heute Master

                          It is not a beta a-la Google, it's a Beta (partially) because the portlet bridge follows a spec that hasn't been finalized yet. (JSR-301 for the 1.0 version)

                          • 11. Re: JBoss 5 Integration
                            Fabio Cruz Newbie

                            Hello,

                            mvn deploy-all is getting the following error:

                            BUILD FAILED
                            C:\java\JBossPortal4JBoss5AS\portal\tools\etc\buildfragments\buildmagic.ent:273:
                            The following error occurred while executing this line:
                            C:\java\JBossPortal4JBoss5AS\portal\tools\etc\buildfragments\buildmagic.ent:395:
                            Compile failed; see the compiler error output for details.


                            Could someone put me on right direction in order to solve this?

                            Thanks,
                            Fábio

                            • 12. Re: JBoss 5 Integration
                              Søren Hilmer Newbie

                              This was very sad news indeed!

                              We have been using the explanation on the wiki for doing this, under the (obviously wrong) impression that this was the route forward ;-(

                              Now this announcement that 2.7 will never be supported on EAP5 literally pulls the carpet away under us.

                              So I have a few questions about this new product:

                              1) Will it be backwards compatible (feature wise) with 2.7?
                              2) We rely on stuff like setting up instances and objects in -object.xml and portlet-instances.xml. Will this be available?
                              3) Will partial content refresh be supported, we rely heavily on that?
                              4) Can the portal be customized using layouts and themes?
                              6) What about custom rendersets?

                              This is just from the top of my head, more questions might surface later.

                              I am really a bit shocked, that the old portal is discontinued like this.

                              --Soren