On Thu, 25 Sep 2003, Steve Raeburn wrote: <snip /> > Shouldn't you be exposing your business objects as web services, not > Struts actions or forms? Struts deals with controlling the user > interface (currently Servlet specific) so any business tier / web > services tier code would be outside of the Struts domain.
I'm not suggesting this type of functionality be in Struts core, as I agree with you Struts is focused on controlling the user interface. However, I can imagine the following situation: using struts-chain, define an action that takes parameters, uses the context to determine authorization, checks for a web context to perform servlet-specific things, pulls data from the business facade and sticks it in the request. I would want to expose that both to Struts and as a web service without any extra code, save perhaps an Axis WSDD. While of course it isn't too hard to write an interface layer to expose business objects/facades via web services, since Actions are already only a few lines, I'd rather not write a whole other set of classes. And of course, I'd like to take the same actions and expose them to portlet code. struts-chain does a great job of remaining agnostic of implementation and let you mix and match just about anything. Don > > Steve > > > > > Don > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
