At first i have tried to make the portlet only with JSF. Unfortunately Weblogic has some problems , many problems, it's the first time when i use weblogic and it's not worthing it's money. After i failed making the portlet with pure JSF i said to make a try with struts 2 and jsf plugin. Using this method i have reached far than using pure JSF. I will try more to see if there is any hope with this solution.
On Fri, Mar 21, 2008 at 5:55 PM, Nils-Helge Garli Hegvik <[EMAIL PROTECTED]> wrote: > Sorry, no clue. As I said, I have no idea if this combination will > work at all. Maybe someone with JSF experience can point out what's > wrong. At least it looks like the portlet dispatcher has been able to > execute the action, but it's failing with the JSF result. > > You might want to consider creating your portlet with either JSF or > Struts 2 instead of combining them both. > > Nils-H > > On Fri, Mar 21, 2008 at 1:55 PM, Daniel <[EMAIL PROTECTED]> wrote: > > I've done what you have said, unfortunately without results. I still > > receive index.jsp:16:26: No property editor found for the bean " > > javax.el.ValueExpression". > > > > Any other ideas? > > > > > > On Thu, Mar 20, 2008 at 12:43 PM, Nils-Helge Garli Hegvik < > [EMAIL PROTECTED]> > > wrote: > > > > > > > > > First of all, I'm not even sure if it's possible to use the portlet > > > and the jsf plugin at the same time. I have not tried, but there > might > > > be issues with it if they try to do conflicting things in the > > > interceptors and the results. > > > > > > > struts.xml > > > > > > > > <package name="default" extends="portlet-jsf-default" > > > namespace="/view"> > > > > > > > > <action name="index" class="com.mycompany.HelloAction"> > > > > <interceptor-ref name="basicStack"/> > > > > <interceptor-ref name="jsfStack"/> > > > > <result name="success" type="jsf"/> > > > > <result>/WEB-INF/jsp/view/index.jsp</result> > > > > </action> > > > > </package> > > > > > > > > > > A couple of things here. You're extending portlet-jsf-default, which > > > still has the jsfStack as the default interceptor ref. Since you have > > > defined a "jsf" package that extends "portlet-jsf-default", you > should > > > probably extend the "jsf" package instead. However, it's probably > just > > > as easy configuring the correct interceptor stack and default > > > interceptor ref right there in the "portlet-jsf-default" package. In > > > addition, you're overriding the default interceptor stack in your > > > action definition, so it's not really using the portletDefaultStack, > > > even if you had configured your default interceptor stack correctly. > > > Unless you need to use different interceptors in your action, there's > > > no need configuring those interceptor-refs there. > > > > > > You could also try swapping the order of the portletDefaultStack and > > > the jsfStack and see if that makes a difference. > > > > > > Nils-H > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
