Here Here...
<rant and frustration mode from hours of reading and experimentation with
no answers...>
I agree with Matthew. I am a Cocoon newbie, but I will step up and do the
first hokey implementation (#2). I know little (other than the docs) and I
haven't really used cocoon yet since our system is based on soap services
( in the pattern sense ), but I'm willing to make something happen.
With that said, something is better than nothing and getting xml from a
java classes shouldn't be too hard. It won't be ready for the cvs main
trunk, but, it'll work.
Kevin
"Matthew
Langham" To: <[EMAIL PROTECTED]>
<mlangham@s-un cc:
d-n.de> Subject: RE: XML-RPC and Cocoon (Was: How
To map:generate XML that has been retrieved from Java
without using XSP)
02/26/2002
11:38 AM
Please respond
to cocoon-dev
>>
Ivanov,
<<
Sorry, I meant "Ivelin".
Matthew
-----Original Message-----
From: Matthew Langham [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 26, 2002 6:33 PM
To: [EMAIL PROTECTED]
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 [EMAIL PROTECTED] - http://www.s-und-n.de
Weblogging at: http://www.need-a-cake.com
=================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
