Hi
I have a JSF portlet (running on Liferay) where I'm trying to use the tree2 component.
It's a very simple tree with only a few nodes. I can get this tree
compoenent to display fine in a regular JSF webapp but when
running as a portlet, it seems that URLs are treated very differently.
So I ha
I was trying tree2 on Liferay too. But then I realize
myfaces (TOMAHAWK components) are NOT portlet
compliant yet. There are quite a few bugs filed for
that in JIRA. I'm waiting for the team to support
portlet before I can use it. The other problem you'll
run into is ClassCastException as TOMAHWAK
Henrik Bentel wrote:
> Hi
>
> I have a JSF portlet (running on Liferay) where I'm trying to use the
> tree2 component.
> It's a very simple tree with only a few nodes. I can get this tree
> compoenent to display fine in a regular JSF webapp but when
> running as a portlet, it seems that URLs are
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 as
s 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 t
Correct, I've used that script before. Though not anymore, as it adds a
faces-context-factory to faces-config.xml which doesn't play nice.
The liferay deployment ant script just puts in the neccesary liferay
hooks (like the Liferay context listener entry), etc. It doesn't add
missing not-liferay-r
6 matches
Mail list logo