Hi there, there is no client side DD or such. We haven't really thought of a way of doing that either but the bias is to do it without such a configuration file. When we use the code generation tool, all the necessary details can be generated into the stubs! So no worries about client side DD's that complicate things (this also means that we plan to have a more sophisticated code generator this time :)). All the test clients are purely hand written! So you can just write a client code that uses your HTTPsender. For a sample have a look at the userguide.sample1.SynchronousClient.
On Wed, 23 Mar 2005 16:38:15 +0530, jayachandra <[EMAIL PROTECTED]> wrote: > Extremely sorry guys! > Resending with proper subject line > > ---------- Forwarded message ---------- > From: jayachandra <[EMAIL PROTECTED]> > Date: Wed, 23 Mar 2005 16:14:00 +0530 > Subject: Doubts regarding client side DD and test case for > HTTPTransportSender. > To: [email protected] > > With the idea of each transport being a new module, the way any > TransportSender handler gets picked up got totally changed. > Everything seems to be through DD. On the client side how should the > deployment info be mentioned to use a specific transport handler for > communication, is it through some client.xml present in the classpath. > Can someone point to some example/resource relevant to this. > > I've with me a CommonsHTTPTransportSender file written to fit into the > Axis2 codebase. It will provide synchronous invocation functionality. > And I want to provide a test case to prove that it's working. Are > there any test cases written to test the functionality of > HTTPTransportSender (synchronous invocation only) currently, I'll go > in those lines. > > JC > > -- > -- Jaya > -- Ajith Ranabahu
