JSC 2.1 not deploying to external Pluto 1.1.3
Okay, I hope I can explain this for everyone to understand.
I have a project using Java Server Faces. It is created and deployed correctly using JSC. What I have tried to do is move the war file over to an external version of Pluto. However, the problem is I get a Status Code 404 when I try to use http://localhost:8080/pluto/portal/
When I remove the project from pluto and now I am getting the same error.
I am hoping someone can provide me suggestions. I
# 1
The pluto-portal-driver-config.xml file must be purged of entries for the new portlet. This will get the pluto server back to its original state.
This leads me to believe the hot deployment is not making the changes to this file, so I did this by hand. This is where I am getting the 404 status code error to pluto's main portal page.
Does anyone have any suggestions?
Thank you for reading my post.
Message was edited by:
supercoder97
# 2
I want to point out JSC is not running the portlet through the Assembler for Pluto 1.1.3. This version of Pluto is injecting a Servlet and Servlet mapping element into the web.xml file. Because JSC hides the portlet from the user, I am wondering how a portlet project can be created from JSC and deployed in Pluto.
To me, this appears to break this handshake between JSC and Pluto. Does anyone see this differently?
Russ