-
1. Re: JBoss Portal 2.6.2 + JBoss AS 4.2.2.GA = true?
theute Nov 14, 2007 9:20 AM (in response to viggo.navarsete)WSRP won't work out of the box with 4.2.2 because of the new version of JBossWS.
The coming JBoss Portal 2.6.3 (Dec 10th) will work out of the box on 4.2.2. -
2. Re: JBoss Portal 2.6.2 + JBoss AS 4.2.2.GA = true?
viggo.navarsete Nov 14, 2007 9:34 AM (in response to viggo.navarsete)I guess this is the kind of failure I that is the result of the new version of JBossWS:
2007-11-14 15:24:36,046 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing: --- Packages waiting for a deployer --- org.jboss.deployment.DeploymentInfo@67ccd552 { url=file:/opt/jboss-4.2.2.GA/server/dashboard/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse } deployer: null status: Starting state: INIT_WAITING_DEPLOYER watch: file:/opt/jboss-4.2.2.GA/server/dashboard/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse altDD: null lastDeployed: 1195050272552 lastModified: 1195050226000 mbeans:
But "everyting" else will work? I'm only interesting in deploying plain portlets spiced with a Richfaces and a JSF portletbridge -
3. Re: JBoss Portal 2.6.2 + JBoss AS 4.2.2.GA = true?
claprun Nov 14, 2007 12:01 PM (in response to viggo.navarsete)The problem with WSRP has been fixed in subversion and the rest works. For RichFaces support, you might want to wait for 2.6.3 though...
-
4. Re: JBoss Portal 2.6.2 + JBoss AS 4.2.2.GA = true?
viggo.navarsete Nov 14, 2007 3:39 PM (in response to viggo.navarsete)Any special reasons why Richfaces doesn't work with the current version of the JBoss Portal (2.6.2)?
-
5. Re: JBoss Portal 2.6.2 + JBoss AS 4.2.2.GA = true?
aalvarez Nov 23, 2007 9:23 AM (in response to viggo.navarsete)I had many problems trying to get Tomahawk to work with the extensions filter on this particular combination.
For example, sometimes while developing the Painlets I had to create a WEB-INF/lib2 folder or else a hidden JSF loader would crash. I also had massive classloading problems trying to install the filter on the web.xml of the Servlet Container. Using the portlet bridges didn't help very much either as there were rendering problems and the code had to be patched so much that it doesn't inspire any confidence to do any production with it.