First of all, sorry for the delayed reply. I got stuck in urgent
issues and had to leave this aside.
Oh, I see. Well, I spent a few brain cycles on it, and I have to admit
that I'm not convinced that the Source/SWT way is the way to go. The
idea of a Source, to me, is that whatever I write to
Hi,
sorry for my late reply, I should have noted that I'm only subscribed to
dev-digest.
On Tuesday 27 July 2004 14:29, Daniel Fagerstrom wrote:
Christian Mayrhuber wrote:
On Monday 26 July 2004 16:12, Daniel Fagerstrom wrote:
Business logic:
As java beans or as stubs trough webservices|ejb.
On Monday 26 July 2004 16:12, Daniel Fagerstrom wrote:
Hi Morley,
I answer at Cocoon-dev as others might be interested.
AFAIK there are no current prefered method for calling web-services. I
and my colleagues, use the extended SourceWritingTransformer (SWT) and
On Mon, 26 Jul 2004 16:12:30 +0200, Daniel Fagerstrom
[EMAIL PROTECTED] wrote:
Hi Morley,
I answer at Cocoon-dev as others might be interested.
Yup, I am. We're currently facing the need of a tool that does XML
over HTTP for some webserviceish things that aren't actually SOAP
compliant (it's
Christian Mayrhuber wrote:
On Monday 26 July 2004 16:12, Daniel Fagerstrom wrote:
I'm currently writing a hand crafted stub for a remote object, that I can use
in both Flowscript and my custom generator. (The remote side has no wsdl)
If the remote site had a wsdl description you could use
On Tue, 27 Jul 2004 14:57:08 +0200, Daniel Fagerstrom
[EMAIL PROTECTED] wrote:
I was thinking about using SWT as well, but then I realized that SWT
doesn't offer a way of inserting the resulting XML in the original
stream: all it does is delete the XML inside the source:write/
element,
Hi Morley,
I answer at Cocoon-dev as others might be interested.
AFAIK there are no current prefered method for calling web-services. I
and my colleagues, use the extended SourceWritingTransformer (SWT) and
org.apache.excalibur.source.impl.HTTPClientSource that you can find in
