I do see the action in the generated xml file but I'm still getting a
pageflow action when I try to execute the method:

Could not find matching action method for action=*showAttachment*, form=*
[none]*.

From the generated xml:
<action validate="false" scope="request" type="BaseController"
path="/showAttachment">
     <forward className="
com.bea.wlw.netui.pageflow.config.PageFlowActionForward" path="currentPage"
name="attachRemoved">
       <set-property value="true" property="returnToPage"/>
     </forward>

On 5/24/06, Eddie O'Neil <[EMAIL PROTECTED]> wrote:

Kevin--

  I assume it does -- the processing of metadata and compilation of a
Page Flow into a .class file and struts-config.xml file is a build
time thing and should be independent of the application server.

  One way to diagnose the problem further would be to look at the
generated struts-config file for PageFlowController B and see if it
has declarations for the actions defined in A.

Eddie



On 5/24/06, Kevin Conaway <[EMAIL PROTECTED]> wrote:
> Eddie,
>
> Thanks for responding.  I don't suppose you know if this works on
WebLogic?
>
> Kevin
>
> On 5/24/06, Eddie O'Neil <[EMAIL PROTECTED]> wrote:
> >
> > Kevin--
> >
> >   Yes, this is possible -- make sure that PageFlowController A has the
> > @Jpf.Controller annotation which is used to process metadata defined
> > in that class.  More information can be found here:
> >
> >   http://beehive.apache.org/docs/1.0.1/netui/pageFlowInheritance.html
> >
> > It's not out of the question that there would be a bug in this code
> > (it changed a lot at one point); if you think you see one, please file
> > a JIRA issue:
> >
> >   http://issues.apache.org/jira/browse/BEEHIVE
> >
> > Eddie
> >
> >
> >
> > On 5/24/06, Kevin Conaway <[EMAIL PROTECTED]> wrote:
> > > Is it possible to use pageflow actions through inheritance? If I
> > > PageFlowController B that inherits from PageFlowController A, I
can't
> > seem
> > > to call an action defined on A from B.
> > >
> > > Is there any way to do this?
> > >
> > > Thanks,
> > >
> > > Kevin
> > >
> > >
> >
>
>

Reply via email to