Hi Henrik,

I think It shouldn't be necessary to prepare the web.xml manually. There is a deployment ant script available for 3.6.1 which does the necessary web.xml alterations and the deployment itself

http://www.liferay.com/web/guest/documentation/development/hot_deploy#2

I guess the mentioned example was just the predeployment variant hence the missing entries.

HTH,
Tanju

----- Original Message ----- From: Henrik Bentel
To: MyFaces Discussion
Sent: Tuesday, October 04, 2005 12:41 AM
Subject: Re: JSF, Portlets and URLs


I found my problem, or rather, I found an easy way to get it to work.

I hadn't assigned a servlet mapping to the FacesServlet in web.xml.
I started my JSF portlet app on the "sample_jsf_myfaces_portlet" example that comes with liferay, and this example didn't have the mapping set.
I guess the assumption was that everything goes through the portal.

After I assigned the servlet mapping to the faces servlet, my tree2 component renders just fine with all images, etc. It also solved my problem with a popup which displays "non-portal" content pulled from the same webapp.

-Henrik

Reply via email to