You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Rich Feit (JIRA)" <be...@incubator.apache.org> on 2005/02/17 22:58:49 UTC

[jira] Resolved: (BEEHIVE-246) Struts merge feature doesn't set my actionmapping className attribute

     [ http://issues.apache.org/jira/browse/BEEHIVE-246?page=history ]
     
Rich Feit resolved BEEHIVE-246:
-------------------------------

     Assign To:     (was: Rich Feit)
    Resolution: Fixed

OK, I've changed this behavior (revision 154197).  The one thing to note is that your custom beans should extend ours (e.g., org.apache.beehive.netui.pageflow.config.PageFlowActionMapping), otherwise you'll get some weird behavior.  Let me know if you have any problems with it.

> Struts merge feature doesn't set my actionmapping className attribute
> ---------------------------------------------------------------------
>
>          Key: BEEHIVE-246
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-246
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Alpha
>  Environment: Windows, Beehive alpha V1
>     Reporter: Sunny Yee

>
> When an action method with a form parameter is specified in a JPF file, the generated <action> mapping's className attribute is always set to "org.apache.beehive.netui.pageflow.PageFlowRequestProcessor".  
> I'm using the Struts merge feature where I have a struts-config.xml that I used to merge its content with the generated struts-config.xml files.   I specifies my ActionMapping class for this action, but the generated struts-config.xml doesn't use my value, and always set it to "org.apache....PageFlowRequestProcessor".  I think the NetUI/Struts Merge code should set the className to my className value, unless one is not specified.
> Thanks.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira