Okay I don't know if this a Pluto issue or not, but I wanted to post it here in hopes other developers could shed some light on this issue. May at least ways to debug through some of the deployment issues one faces when testing with Pluto 1.1.3.
What I have done is built a Portlet using Sun's Java Studio Creator 2.1. I have exported the project to a war file so I can use it within an external version of Pluto (1.1.3). I have also edited the pluto-portal-driver-config.xml using an earlier example that worked. My goal is to create a separate page with the new portlet on it. The portlet is using Java Server Faces. When I drop the war file in the webapps directory the first time, I can see from the log files all the things are working for pluto. The hot-deployment is exploding the war file. This is where the problems begin. What I try an accomplish next is log into Pluto using the standard URL: http://localhost:8080/pluto/portal This is where I receive a HTTP Status Code of 404 in my browser. I see no errors in the logs files. No errors are showing up in the command window either. When I backout the war file and change to the xml file, everything is working correctly. Does someone have any suggestion? Is there a way to turn on logging for the the hot deployment so we can ensure no errors exist in the deployment? Is there a way to turn on schema validation to ensure XMLs are created properly? Thank you very much for taking the time to read my post. Russ -- View this message in context: http://www.nabble.com/Java-Studio-Creator-2.1-created-Portel-not-deploying-to-Pluto-1.1.3-tf3985303.html#a11315372 Sent from the Pluto - User mailing list archive at Nabble.com.
