Elliot: Thank you for your help. For us to automate this action involving ANT, we need the ANT-Task definition located in a jar file. I have search the web site for Pluto and I do not see the jar file in any of the src dowloads files. Is it located somewhere else or was the name changed? I see others have looked for the jar file too, but were unable to locate it.
Russ Elliot Metsger wrote: > > Russ, > > Pluto doesn't have hot deployment per se. > > First, you need to make sure you've installed Pluto properly [0]. After > Pluto is installed, then you can deploy your portlet war file (I'd > highly recommend downloading the pluto-current-bundle distribution which > comes with a pre-configured Tomcat, with Pluto already installed). > > Your portlet war file needs to be assembled by a manual process > (assembly is distinct from deployment in the servlet container): either > by hand (not recommended), by an ant task [1], or by the Pluto Maven 2 > plugin. > > After assembling your war file, then you can drop the assembled war into > tomcat's webapps directory. After starting Tomcat, you should then be > able to publish the portlet by either using the Pluto Admin tool or by > hand-editing pluto-portal-driver-config.xml. > > > HTH, > Elliot > > [0] http://portals.apache.org/pluto/v11/getting-started.html > [1] http://portals.apache.org/pluto/pluto-ant-tasks/getting-started.html > > russ_2007 wrote: >> From what I can gleam from the documentation >> (http://portals.apache.org/pluto/v11/deploying.html) involving deploying >> Portlets to Pluto Portal, the hot deployment is not injecting the servlet >> and servlet mappings to the deployment descriptor (web.xml). When I put >> the >> elements in the web.xml file (a guess on my part what they are), it is >> still >> giving me a HTTP Status Code 404. The other thing I want to point out is >> JSC is using its own portlet and hides the portlet implementation. from >> the >> user. >> >> >> >> russ_2007 wrote: >>> 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#a11345901 Sent from the Pluto - User mailing list archive at Nabble.com.
