You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Stefan Podkowinski <sp...@gmail.com> on 2005/06/29 20:55:04 UTC
Questions on Axis Block
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: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Questions on Axis Block
Posted by Stefan Podkowinski <sp...@gmail.com>.
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 <ja...@geeksonly.de> 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: users-unsubscribe@cocoon.apache.org
> > For additional commands, e-mail: users-help@cocoon.apache.org
> >
> >
>
> --
> Gruß, Jan
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Questions on Axis Block
Posted by Jan Hinzmann <ja...@geeksonly.de>.
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: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
--
Gruß, Jan
Re: Questions on Axis Block
Posted by Sebastien Arbogast <se...@gmail.com>.
2005/6/29, Stefan Podkowinski <sp...@gmail.com>:
> Sebastien, the second approach described by you in the wiki may work
> well. However, I think you are doing alot of the stuff that would
> already be handled by the Axis Servlet and Axis Server. If you just
> have to integrate the axis rpc call result into your pipeline (as
> suggested by the adapt() function) you could propably use the Web
> Service Proxy Generator and a "classic" axis service (theres also
> spring support for that..).
Yes I guess it should be possible. I didn't have time to dig on that
but it might be possible. If you find a way to do so, it would be
great if you could enrich this wiki page.
--
Sébastien Arbogast
WebCV : http://www.sebastien-arbogast.com
The Epseelon Project : http://www.epseelon.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Questions on Axis Block
Posted by Stefan Podkowinski <sp...@gmail.com>.
Sebastien, the second approach described by you in the wiki may work
well. However, I think you are doing alot of the stuff that would
already be handled by the Axis Servlet and Axis Server. If you just
have to integrate the axis rpc call result into your pipeline (as
suggested by the adapt() function) you could propably use the Web
Service Proxy Generator and a "classic" axis service (theres also
spring support for that..).
On 6/29/05, Sebastien Arbogast <se...@gmail.com> wrote:
> 2005/6/29, Stefan Podkowinski <sp...@gmail.com>:
> > 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..
>
> Apparently the WebServiceServer feature begins to be a source of
> interest. Maybe it will trigger a new move to improve and specify
> that. Have a look at http://wiki.apache.org/cocoon/WebServiceServer ,
> it's likely to answer your questions.
> From what I was told before trying to make that, the Axis block just
> provides a WebService proxy for Cocoon to consume WebServices.
> In the wiki page, I've tried to integrate Axis possibiliities as much
> as I could but I'm sure it could be improved by using Axis handlers.
> The problem is that I don't know how to do that.
> But for now that code works and I think it's generic enough to fit
> most of the situations.
>
> --
> Sébastien Arbogast
>
> WebCV : http://www.sebastien-arbogast.com
> The Epseelon Project : http://www.epseelon.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Questions on Axis Block
Posted by Sebastien Arbogast <se...@gmail.com>.
2005/6/29, Stefan Podkowinski <sp...@gmail.com>:
> 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..
Apparently the WebServiceServer feature begins to be a source of
interest. Maybe it will trigger a new move to improve and specify
that. Have a look at http://wiki.apache.org/cocoon/WebServiceServer ,
it's likely to answer your questions.
>From what I was told before trying to make that, the Axis block just
provides a WebService proxy for Cocoon to consume WebServices.
In the wiki page, I've tried to integrate Axis possibiliities as much
as I could but I'm sure it could be improved by using Axis handlers.
The problem is that I don't know how to do that.
But for now that code works and I think it's generic enough to fit
most of the situations.
--
Sébastien Arbogast
WebCV : http://www.sebastien-arbogast.com
The Epseelon Project : http://www.epseelon.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org