I meant the RPCMessageReceiver. I assume you're already using it. Anne
On 10/31/07, Simon Steinacker <[EMAIL PROTECTED]> wrote: > Thank you for you help! I now use the unwrap option and I obtain the simple > rpc method calls. > > But what did you mean with '..., and use the RPC provider? Where can I find > documentation about that or where can I configure any provider axis2 uses? > What is the provider concept? > > Thanks a lot, > Simon > > > On Tuesday 30 October 2007 22:43:06 Anne Thomas Manes wrote: > > Use doc/literal wrapped style (specify that you want the "unwrap" > > option), and use the RPC provider. > > > > Anne > > > > On 10/30/07, Simon Steinacker <[EMAIL PROTECTED]> wrote: > > > Hello, > > > > > > I am participating in a project that was until now based on Axis 1.3. Now > > > we want to migrate to the new Axis2 1.3 version. > > > > > > So fare we heavily made use of Web Service calls based on RPC mechanism, > > > resulting in Axis providing (transparant) rpc method calls. For example > > > at the server side we hade a method > > > > > > public void someMethod(SomeType t1, SomeOtherType t2) > > > > > > After generating the client with Axis we obtained simple client stubs, > > > that provided the above described method as a simple java method call. Is > > > there a way how to achieve this comfortability with Axis2? > > > > > > Furthermore we were up to now able to use the same classes on the service > > > side and the client side. That means we could exchange the generated data > > > types with the original ones (e.g. SomeType, SomeOtherType). This is > > > important for us, since we have a service oriented architecture, where > > > one service calls another one and data types are handed on from one > > > service to another. So we basically excluded the data classes from client > > > generation and generated the client stubs only. Therefore we used the > > > same (original) data classes on the client and server side. Is there a > > > way to do this with Axis2? > > > > > > Thanks, > > > Simon > > > > > > --------------------------------------------------------------------- > > > 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]
