On 11/3/05, Pollähne. Ullrich <[EMAIL PROTECTED]> wrote:
No, there seems to be a bug in Tomcat 5.5.12 that is causing issues with how pluto contexts are configured. Once one of us looks into this further and verifies that it truly is a tomcat issue (which I'm pretty sure of at this point), we will file a bug with Tomcat.
Tomcat 5.5.9 works fine.
Yes, this is the same error that others have seen.
That's the issue, context configurations aren't getting picked up properly in .12 (or the approach has intentionally changed, which I doubt).
Ooops, the testsuite should exclude this dependency. I updated the portal a couple of days ago to do so, but must have missed the jsp-api dep in testsuite. I'll do it now.
Actually, the most current docs (not published) indicated cd pluto-util.
Also, the new parameters name has changed to -DinstallDir.
The deploy task knows based on the -DinstallDir.
Make sure you do it from pluto-util
Hi,
is Pluto 1.1 (as of today noon) supposed to run in tomcat 5.5.12?
No, there seems to be a bug in Tomcat 5.5.12 that is causing issues with how pluto contexts are configured. Once one of us looks into this further and verifies that it truly is a tomcat issue (which I'm pretty sure of at this point), we will file a bug with Tomcat.
Tomcat 5.5.9 works fine.
I checked out everything from the svn repository, built the stuff, installed pluto and have the following in webapps after starting tomcat:
pluto-portal/
ROOT/
pluto-testsuite/
tomcat-docs/
pluto-portal.war
pluto-testsuite.war
After re-starting tomcat and directing my browser to http://localhost:8080/pluto-portal I see the following exptions instead of the portlets:
org.apache.pluto.PortletContainerRuntimeException: Error creating portlet invoker for portlet TestPortlet1. Unable to locate context /testsuite. Check your portlet configuration and ensure cross context dispatching is enabled.
Well, there is no context /testsuite but a context /pluto-testsuite.
Tomcat complains about the following:
WARNUNG: A docBase C:\Programme\Tomcat 5.5\webapps\pluto-testsuite.war inside the host appBase has been specified, and will be ignored
Yes, this is the same error that others have seen.
So it seems that this is reason for the nonexistent /testsuite context. But was this different in tomcat 5.5.9?
That's the issue, context configurations aren't getting picked up properly in .12 (or the approach has intentionally changed, which I doubt).
If I rename pluto-portal* to pluto* and pluto-testsuite* to testsuite* then I get the portal site but only after removing testsuite/WEB-INF/lib/jsp-api-2.0.jar I am able to use the testsuite since tomcat already has a jsp-api.jar in it's path.
Ooops, the testsuite should exclude this dependency. I updated the portal a couple of days ago to do so, but must have missed the jsp-api dep in testsuite. I'll do it now.
Another question:
The readme states that I should do the following to install my portlet:
Step 1: 'cd pluto-install'
Step 2: 'maven pluto:assemble -Dmaven.deploy.deployment=<path to war>
Step 1: 'cd pluto-install'
Step 2: 'maven pluto:deploy -Dmaven.deploy.deployment= <path to war>
Actually, the most current docs (not published) indicated cd pluto-util.
Also, the new parameters name has changed to -DinstallDir.
I have not tried it yet since this page http://portals.apache.org/pluto/1.1/getting-started.html tells to go to pluto-util for the assemble task and in addition I do not know how the deploy task does know where to deploy to.
The deploy task knows based on the -DinstallDir.
Ok I dared to execute the assemble task (in pluto-util) and got the following:
BUILD FAILED
Goal "pluto:assemble" does not exist in this project.
Make sure you do it from pluto-util
Ullrich.
