True. But somehow, to leverage what struts really is, you would need to communicate some kind of instructions from the server side controller.
I think the core of what I am saying is that Axis does *not* provide a view. And therefore you would have controller functions on the other side of the web service. So you dupliate what Struts does, you would need to bridge communications between the two controllers. That is where I see the problem. Simple XML-RPC of "view/model" objects with Struts doesn't leverage core Struts features to the client controller. So you either dumb down the server app, or beef up the client controller. On Fri, 2003-01-24 at 17:31, [EMAIL PROTECTED] wrote: > > > > > > ** You may find more utility in creating set of client side proxys for > > Struts server side controller contructs. In other words, RPC the > > selected controller components. ActionForms would be user defined, but > > the ActionForward, ActionErrors, etc ... could be proxy objects. > > I like this idea - but doesn't this assume that the client is Java? > > > > --------------------------------------------------------------------------- > This e-mail message (including attachments, if any) is intended for the use > of the individual or entity to which it is addressed and may contain > information that is privileged, proprietary , confidential and exempt from > disclosure. If you are not the intended recipient, you are notified that > any dissemination, distribution or copying of this communication is > strictly prohibited. If you have received this communication in error, > please notify the sender and erase this e-mail message immediately. > --------------------------------------------------------------------------- > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
