beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlin Rogers (JIRA)" <>
Subject [jira] Updated: (BEEHIVE-1151) Cannot find PropertyDescriptor exception when using AnyBeanActionForm
Date Tue, 12 Dec 2006 18:09:21 GMT
     [ ]

Carlin Rogers updated BEEHIVE-1151:

          Component/s: Documentation
                           (was: NetUI)
        Fix Version/s: V.Next
    Affects Version/s: 1.0.2
             Priority: Minor  (was: Major)

Yes, this isn't real clear. I'm going to change this to a documentation bug. I think this
is by design but certainly some documentation on this will help.

In the case that an AnyBeanActionForm is used, there is a public getBean() method to allow
you to get at the actual form bean object. In the example in this bug, the EL would be...


> Cannot find PropertyDescriptor exception when using AnyBeanActionForm
> ---------------------------------------------------------------------
>                 Key: BEEHIVE-1151
>                 URL:
>             Project: Beehive
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 1.0.1, 1.0.2, V.Next
>         Environment: WebLogic 9.2 beta, Windows XP
>            Reporter: Jean-Baptiste Nizet
>            Priority: Minor
>             Fix For: V.Next
>         Attachments:
> When using an ActionForm that just implements Serializable, and does not extend ActionForm
or FormData, I can't access objects stored in the ActionForm (by the action) anymore: I get
this exception:
> javax.servlet.jsp.el.ELException: Cannot find PropertyDescriptor for 'result' for bean
'class org.apache.beehive.netui.pageflow.internal.AnyBeanActionForm'
> The result object is an instance of a simple JavaBean containing a result String property,
that the controller creates and stores in the form bean before the JSP is rendered.
> The JSP tries to render the result using the following EL expression :
> ${bugForm.result.result}
> If the ActionForm extends ActionForm or FormData, the bug disappears.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message