Re: JSPs on Axis Best Practice for accessing server code?

[Bill Keese]

I've been wondering about this myself.  People always talk about 
separating the presentation layer from the application layer (business 
logic), sometimes even running them on separate machines and 
communicating via EJB, although I've never personally heard of anyone 
connecting them via SOAP.  Is that what you are talking about?

Of course, marshalling and unmarshalling to XML will slow down your 
application, so your other option is to have the JSP's call your SOAP 
server classes (the SoapBindingImplementation) directly.

Bill
Robert Simmons Jr. wrote:
I currently have the need to deploy some code as both a web service 
and a web application. The JSPs will allow a user to configure their 
subscription and the Web Services will then allow the user to get 
updates to their subscription remotely.

What I want to know is what is the best practice for the srever side 
stuff. I can quite easily call my implementation classes directly 
without going through Axis by merely putting the JSPs in the Axis 
webapp. However, is that reccommended or should I be going through the 
web service whenever I want to contact the services?

Please advise what the best practice should be.
-- Robert