Just like in the server side, there is an axis2.xml to configure the client side. It is in the axis2-kernel.jar. For example the following line uses that axis2.xml to configure itself by default. ServiceClient serviceClient = new ServiceClient (); Either you can remove that file and put a changed axis2.xml in the classpath.
Instead you can give an axis2.xml and repository as follows, ConfigurationContext configContext = ConfigurationContextFactory.createConfigurationContextFromFileSystem( axis2RepoLocation, axis2XmlLocation); ServiceClient serviceClient = new ServiceClient(configContext , null) When using the stub there will be constructor which takes a given configuration object. Stub stub = new Stub(configContext, epr); Good luck Upul On 10/17/07, mathieu fabre <[EMAIL PROTECTED]> wrote: > > > Hi, > > i use axis2 with tomcat and i don't know axis2 very well. > i have made a simple service, and i wrote a client which use the client > stub. > i want to use my own transport, so i made a simple jar that contain the > minimum > files like http protocol.(i begin to copy the http protocol and i will > write changes after). > I change the axis2.xml file and my server is using my jar for the > transport. > But i don't know how to do the same thing for the client because the > client use the axis2-kernel.jar > which contain normal version of the http transport. > > How could i force the client to use my jar for the transport..? > > thank in advance. > > mathieu Fabre > > (sorry for my english, i'm french) >
