> I can see the appeal of exposing the web application's code as web
services
> using Axis. It seems like exposing Action classes directly as web
services
> will be more trouble than it's worth. It would seem better to move the
code
> in the Action class into another class (not tied to Struts/Web) which
will
> be used by the Action class and exposed directly as a web service running
> inside the same web application.
At least as a first pass, I think that using the HTTP post into the Action
servlet as the entry point into Struts (same entry point as other Struts
invocations) is the best approach.
o It's the simplest to build and begin testing with.
o It ensures that changes to Struts won't require changes in the
axis4struts 'middleware'.
o It provides the option (but the not the *requirement*) that Axis and
Struts be in the same webapp.
Once an initial app is out and has been tested, it's pssobiel that the
connection you're describing may evolve one way or another...
-- Kevin
---------------------------------------------------------------------------
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]>
