I have done that. Every time i get this error. I have no idea why this is
thrown, and i don't know what he wants. Is there no librabry loaded for
parsing the jsf page? I have no idea.
On Mon, Mar 24, 2008 at 4:03 PM, Randy Burgess <[EMAIL PROTECTED]> wrote:
> I would take everything out of your JSF page and then start adding things
> in
> one by one until you find what is causing the missing the property editor
> error.
>
> Regards,
> Randy Burgess
> Sr. Web Applications Developer
> Nuvox Communications
>
>
>
> > From: Daniel <[EMAIL PROTECTED]>
> > Reply-To: Struts Users Mailing List <user@struts.apache.org>
> > Date: Sat, 22 Mar 2008 22:53:09 +0200
> > To: Struts Users Mailing List <user@struts.apache.org>
> > Subject: Re: struts 2 jsf plugin problem
> >
> > 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]
> >>
> >>
>
>
>
> This email and any attachments ("Message") may contain legally privileged
> and/or confidential information. If you are not the addressee, or if this
> Message has been addressed to you in error, you are not authorized to read,
> copy, or distribute it, and we ask that you please delete it (including all
> copies) and notify the sender by return email. Delivery of this Message to
> any person other than the intended recipient(s) shall not be deemed a waiver
> of confidentiality and/or a privilege.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
