You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by "Ivanov, Ivelin" <Iv...@bmc.com> on 2002/02/26 18:11:18 UTC
RE: XML-RPC and Cocoon (Was: How To map:generate XML that has bee
n retrieved from Java without using XSP)
I hope this doesn't sound OT, but this discussion
seemes to be leaning in a direction which
concerns the java Portlet-API:
http://www.theserverside.com/home/thread.jsp?thread_id=11976
http://www.theserverside.com/resources/article.jsp?l=Portlet_API
I was planning to raise this point and ask if Cocoon is planning to get
closer to this standard or stay independent? The teaser is that WebLogic 7
and IBM WebSphere already demonstrate support.
There is another thread going on the dev list about flow control.
Appears ti me that with tighter Web services integration (Axis?), the WSFL
(web services flow control) language can be leveraged.
-= Ivelin =-
>-----Original Message-----
>From: Matthew Langham [mailto:mlangham@s-und-n.de]
>Sent: Tuesday, February 26, 2002 11:01 AM
>To: cocoon-users@xml.apache.org; cocoon-dev@xml.apache.org
>Subject: XML-RPC and Cocoon (Was: How To map:generate XML that has been
>retrieved from Java without using XSP)
>
>
>Hi Kevin,
>
>>>
>Is there a way I can configure a reflection based action or
>generator to
>call an XML-RPC service by xml configuration utilizing request
>parameters?
><<
>a tough one. But then again maybe not.
>
>What you would need is a Transformer that can call an XML-RPC
>service based
>on request parameters it is passed - right?
>
>Something like:
>
><cocoon:call-xml-rpc>
> <target>http://myserver/xyzservice</target>
> <methodName>examples.getStateName</methodName>
> <params>
> <param>
> <value><i4>41</i4></value>
> </param>
> </params>
></cocoon:call-xml-rpc>
>
>The Transformer would then take this and call the service and pipe the
>response back into the pipeline.
>
>Is this something like what you were thinking?
>
>I think we should now move this over to cocoon-dev - because
>as yet there is
>no xml-rpc transformer or similar and I would love to hear what others
>think.
>
>That being said - we should implement something like this
>ASAP. Or is there
>something out there?
>
>Matthew
>
>--
>Open Source Group sunShine - Lighting up e:Business
>=================================================================
>Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
>Tel:+49-5251-1581-30 mlangham@s-und-n.de - http://www.s-und-n.de
> Weblogging at: http://www.need-a-cake.com
>=================================================================
>
>
>-----Original Message-----
>From: Kevin.Ross@bredex.com [mailto:Kevin.Ross@bredex.com]
>Sent: Tuesday, February 26, 2002 5:29 PM
>To: cocoon-users@xml.apache.org
>Subject: How To map:generate XML that has been retrieved from Java
>without using XSP
>
>
>Since I'm new to cocoon, this may be very easy, but I've read
>a great deal
>of documentation and haven't run across it.
>
>Without using XSP, how can I call on the generator to process
>xml that is
>dynamically retrieved by my java class? Would this be an action?
>
>
>
>Taking it a bit further:
>
>Is there a way I can configure a reflection based action or
>generator to
>call an XML-RPC service by xml configuration utilizing request
>parameters?
>
>
>
>Thanks in advance,
>
>Kevin
>
>
>---------------------------------------------------------------------
>Please check that your question has not already been answered in the
>FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
>To unsubscribe, e-mail: <co...@xml.apache.org>
>For additional commands, e-mail: <co...@xml.apache.org>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
RE: XML-RPC and Cocoon (Was: How To map:generate XML that has been retrieved from Java without using XSP)
Posted by Matthew Langham <ml...@s-und-n.de>.
>>
Ivanov,
<<
Sorry, I meant "Ivelin".
Matthew
-----Original Message-----
From: Matthew Langham [mailto:mlangham@s-und-n.de]
Sent: Tuesday, February 26, 2002 6:33 PM
To: cocoon-dev@xml.apache.org
Subject: RE: XML-RPC and Cocoon (Was: How To map:generate XML that has
been retrieved from Java without using XSP)
(limited to cocoon-dev so as not to scare off any users :-))
<rant mode>
Ivanov,
yes you are quite right. Cocoon should have a portal that is conformant to
the portlet-API and can integrate seamlessly into XML-RPC and SOAP using
WSRP. I think we may get there in about 4 years if we continue at this rate
:-).
Sorry to be a bit provocative and I do not mean to offend anyone. Discussion
and base-touching is GOOD. However we also need some form of practicality to
go with it.
Step 1 (as we see it) was the donation of the portal framework and
authentication last week. That may not be compatible to the portlet-api but
hey - it works and is tightly integrated into Cocoon. Pipelines that access
data such as moreover.com can be integrated as sunlets.
Step 2: If we can now build components that connect to exisiting web
services via XML-RPC and SOAP we would have the next step and open Cocoon as
an ideal web service client platform (including portal). To be honest I do
not care if we use Axis, Apache Soap or code everything by hand - but let's
do it! Sure, WSRP is a way to go but we need to take the first step .. well
.. first.
Step 3: Open up Cocoon as a _server_ platform for web services by providing
access via SOAP. Here it would be good if we can use Axis or something
similar to provide WSDL or similar representations of the hosted services.
This is obviously not as easy as the client side and will need more effort.
</rant mode>
Ok, so there you have the roadmap for CocoonWS :-)
Matthew
--
Open Source Group sunShine - Lighting up e:Business
=================================================================
Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
Tel:+49-5251-1581-30 mlangham@s-und-n.de - http://www.s-und-n.de
Weblogging at: http://www.need-a-cake.com
=================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: XML-RPC and Cocoon (Was: How To map:generate XML that has been retrieved from Java without using XSP)
Posted by Matthew Langham <ml...@s-und-n.de>.
(limited to cocoon-dev so as not to scare off any users :-))
<rant mode>
Ivanov,
yes you are quite right. Cocoon should have a portal that is conformant to
the portlet-API and can integrate seamlessly into XML-RPC and SOAP using
WSRP. I think we may get there in about 4 years if we continue at this rate
:-).
Sorry to be a bit provocative and I do not mean to offend anyone. Discussion
and base-touching is GOOD. However we also need some form of practicality to
go with it.
Step 1 (as we see it) was the donation of the portal framework and
authentication last week. That may not be compatible to the portlet-api but
hey - it works and is tightly integrated into Cocoon. Pipelines that access
data such as moreover.com can be integrated as sunlets.
Step 2: If we can now build components that connect to exisiting web
services via XML-RPC and SOAP we would have the next step and open Cocoon as
an ideal web service client platform (including portal). To be honest I do
not care if we use Axis, Apache Soap or code everything by hand - but let's
do it! Sure, WSRP is a way to go but we need to take the first step .. well
.. first.
Step 3: Open up Cocoon as a _server_ platform for web services by providing
access via SOAP. Here it would be good if we can use Axis or something
similar to provide WSDL or similar representations of the hosted services.
This is obviously not as easy as the client side and will need more effort.
</rant mode>
Ok, so there you have the roadmap for CocoonWS :-)
Matthew
--
Open Source Group sunShine - Lighting up e:Business
=================================================================
Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
Tel:+49-5251-1581-30 mlangham@s-und-n.de - http://www.s-und-n.de
Weblogging at: http://www.need-a-cake.com
=================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org