I think what Anne wanted to say was not so much that it is not
/possible/ to use SOAP to exchange Swing components (I see no general
problem with that), but that it frankly is against the idea of Web
Services to mis-use it like a distributed object middleware. There might
be much better (read: more performant, easier) ways to do what you want
to do without SOAP.
/philipp
Ross Allard schrieb:
Thanks Anne,
That seems rather harsh. I have in fact delivered Java objects via SOAP and Axis, albeit simple ones. And the Axis doc mentioned the ability to exchange "arbitrary" Java objects. However, I realize a Swing object is a bit of a stretch. I was just curious. Now on to Plan B.
Ross
-----Original Message-----
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 12, 2007 8:39 PM
To: [EMAIL PROTECTED]
Subject: Re: Delivering Swing component?
SOAP does not "deliver objects". It exchanges XML messages. Don't think of SOAP
as a distributed object system.
Anne
On 4/12/07, Ross Allard <[EMAIL PROTECTED]> wrote:
Has anyone created a service that delivers a Swing component (e.g. Jpanel)?
Thanks,
Ross
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
