Repost from users list: Re: Axis/SOAP proposal for Struts

["V. Cekvenich" <vc...@basebeans.com>]

+1. And also XML RPC called via JavaScript from a browser w/o a submit. 
(To me, any time you call an "action" before a bean.... == Struts)

Already in 1.1 execute() signature is a bit different for tiles action 
then "Struts" action.

But maybe post on dev list for suggestions? (or even put sample 
implementation in bugzila). I am sure lots of good and bad ideas:
-Have struts work a bit more like JasperRepports - via Jelly ie: 
describe the JSP page in XML, so other projects can have code generators 
and IDE's. (like they have Eclipse plugin in fo JasperReport XML)
- a default action on dispatch action; dispatch action for tiles;
-ship Struts with JSTL via Maven;
-more interfaces?;
-deprecate some tags;
- make a DAO interface in Commons; (extends iterator?) people could 
implement many ways.
- more exotic JavaScript tags in Taglibs (Calendar, ....);
- some default actions with default behavior (ex: onExecuteSave() 
{formBean.save();};
-encapsulate req, resp, mapping, formbean into an event object so : 
execute(eventObject eo) { x= eo.getRequest(); .....] this allows for 
many action signatures to be replaced with one;
- add a testIt() abstract method to formBeans and the like (thus 
encouraging developers to unit test the bean patters before placing in 
Struts
- Styxx, Stuts Menu added in
- Should formBean extend collection and have a DAO property (makes 
master detail multi row trivial)
- indexed tag alternative having a concept of groped bands with nesting, 
like JasperReports (I have no Idea how to implement)

Oh yeah, maybe first let you ship 1.1 and get out of the way and thank 
you one more time for even having 1.1. (and then see the initiatives). 
Is there a new list of open bugs for 1.1 release?


.V





Mike Oliver wrote:
> Struts Users, 
> 
>  
> 
> I would like to propose that Struts be extended to support another entry
> point.  The ActionServlet would be augmented by an Axis/SOAP Web
> Services Interface to Struts.  FormBeans would be part of the payload
> for requests.  Responses would be generated by Forwards for SOAP.  This
> new Axis entry point would do the same work as ActionServlet with the
> only significant difference being the construction of the FormBean.
> Incoming SOAP Requests would be configured to call the same
> RequestHandlers and as far as the actions go they won't know that the
> source was an HTML Form or a serialized FormBean.  
> 
>  
> 
> I feel this will give a great deal of flexibility to Applications where
> they want a Web Browser User Interface as well as Web Services for the
> same Application Data Model and Business Logic.
> 
>  
> 
> I am planning on doing this anyway, and felt it applicable to this group
> and would offer to share it as a sub project and would welcome
> contributions of thought, expertise and code.
> 
>  
> 
> Michael Oliver
> Chief Technology Officer
> AppsAsPeers LLC
> 7391 S. Bullrider Ave.
> Tucson, AZ 85747
> 520.574.1150 Voice
> 520.844.1036 Fax
> 520.270.8862 Cell
> http://www.appsaspeers.com <http://www.appsaspeers.com/>  Home Page
> 5202708862@voicestream.net SMS
> http://www.ollie.ezpeer.net <http://www.ollie.ezpeer.net/>  Personal
> Home Page
> http://www.ollie.im-live.com/im-live/  Instant Chat
> MikeOliverAZ@hotmail.com MSN Messenger
> MikeOliverAZ@yahoo.com Yahoo Instant Messenger
> MikeOliverAZ Aol Instant Messenger
> 
> 
> 
>  
> 
> 



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>