Hi Ram snip....
> In case of JSON-RPC binding (our original scenario), when the interface is > not defined @Remotable the runtime just ignores the data transformation > between the binding without throwing any exception. In you test do you have binding.jsonrpc on reference and service sides? If so it's ignore it because I don't think reference side binding.jsonrpc has been implemented yet. > > But I have noticed that in case of Axis2 binding for the same scenario, we > get an exception as shown below. > *java.lang.IllegalArgumentException*: Can't handle *mixed* payloads between > OMElements and other types. > So the message is still going via the web service binding which still expects Axiom formatted input. But there must be a switch somewhere that says, if the interface is not marked as remotable then don't bother doing data transformations as messages will only be passed locally. I'll have to check in the code as I don't know how this fits in with cases where you might expect transformation to take place, e.g. talking locally to a non-java implementation such as BPEL. > I believe, just throwing a warning would not help for all kind of > bindings.... as such scenario could even throw runtime exceptions > sometimes. > Not sure how to handle such scenarios. Please suggest. > We really need to raise an error because it's not really a valid configuration. Where is the test going to happen? > > -- > Thanks & Regards, > Ramkumar Ramalingam >
