ore.co.in/directory.html
> --
>
>
> -- Forwarded message --
> From: Pavan Kumar Choukhada <[EMAIL PROTECTED]>
> To: jayachandra <[EMAIL PROTECTED]>
> Date: Wed, 02 Mar 2005 11:57:39 +0530
> Subject: Re: stub
--
Netcore Solutions Pvt. Ltd.
Website: http://www.netcore.co.in
Spamtraps: http://cleanmail.netcore.co.in/directory.html
- Begin Message ---
On Wed, 2005-03-02 at 11:43,
Not that easy buddy.
Even for RPCProvider how is it to know from the plain SOAP message to
which Java classes the XML need to be deserialized before invoking the
java class.
There comes the need for skeleton code.
Jayachandra
On Wed, 02 Mar 2005 11:23:44 +0530, Pavan Kumar Choukhada
<[EMAIL
that's true i am not using static invocation.
but i think we do not require skelton on server.
because as i mentioned earlier using RPCProvider axis invoke java class
via reflection.
On Wed, 2005-03-02 at 11:04, Shahi, Ashutosh wrote:
> Pavan,
> The skeleton code is used at the server for
Pavan,
The skeleton code is used at the server for delegating the work
to the actual java class. The stubs are used at the client end if u r
using static invocation, which I think you r not using, so u can do
without them at client.
Ashutosh
-Original Message-
From: Pavan Kumar
