I'm following the current web service related discusions. I was just hoping someone could answer a few specific questions on the design of the axis block. Thanks for the pointers though.
Btw, [2, 3] is IMO basically just a avalon component wrapper around the org.apache.axis.server.AxisServer class. The AxisRPCReader has the same role as the axis AxisServlet class by providing the necesarry context for [2,3] from the request. Using the SoapServerImpl directly is not a intended option IMO. On 6/29/05, Jan Hinzmann <[EMAIL PROTECTED]> wrote: > Hi, > > if you search the mailing list on "WebServices", "Cocoon and Axis", "Cocoon > and WebServices" you'll find some discussion on this. > > also you may want to have a look at: > > [1] http://wiki.apache.org/cocoon/WebServiceServer > [2] > http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/components/axis/SoapServer.html > [3] > http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/components/axis/SoapServerImpl.html > [4] http://webservices.xml.com/pub/a/ws/2003/03/18/cocoon.html > > greet, jan > On Wednesday 29 June 2005 20:55, Stefan Podkowinski wrote: > > Hi Cocoon Users > > > > Could someone answer me some questions on the axis block who has > > probably some experience with it? > > > > I had a closer look on it as I needed to implement some web services > > to be served by my cocoon app. > > > > The block has very little documentation so I had to study the source > > directly. But even after thinking about it over and over again I could > > gasp the concept of this block. "Why is it there?" > > > > * Whats the point in using the RPC Reader from the Axis block instead > > of using the Axis Servlet directly > > * Does a reader that does also send a direct response to the peer fit > > into the cocoon concept of cocoons component pipelines? > > * How can I deploy my services using the axis block? Do I need to > > configure it in cocoon.xconf? > > > > Another problem that stroke me with the axis block was that apparently > > it is not possible to bind a services to a url endpoint. The samples > > did only specify "rpcrouter" as the endpoint which leaves the question > > open how the "router" would recognize which service I intend to > > consume. I found out that the router will get this information from > > the http header. So I checked the specs and found out that this is > > only optional (and http transport specific) and services are supposed > > to be found by their url endpoint. So I'm even more confused.. > > > > > > Steve > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- > Gruß, Jan > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
