On Tue, Sep 27, 2011 at 2:10 PM, Vaclav Barta <v...@comp.cz> wrote: > On Tuesday 27 September 2011 09:50:51 Sagara Gunathunga wrote: >> Both Axis2 server side and client side have enough capabilities to >> process and generate xsi:type attributes, basically it supports for >> following cases. >> >> 1.) For any standard XSD data type. ( XSD int ,string . date etc.) >> 2.) Any POJO referenced by the web service method signature. > I'm not starting from POJOs, but from WSDL (using ADB - I could use other > bindings if they're more suitable, but the result has to agree with the WSDL). > As a first step, I'd like to return login success, i.e. > > <errorCode xsi:type="ns1:LoginErrorEnum">OK</errorCode>
Once you define all your types in WSDL then you can generate server/client side codes that can process those types through the xsi:type attribute. > > (with the rest of SOAP around it, of course) where > xmlns:ns1="http://www.betfair.com/publicapi/types/global/v3/"; and > ns1:LoginErrorEnum is defined in > https://api.betfair.com/global/v3/BFGlobalService.wsdl . > >> Also you could extend above POJO support by using extraClass parameter >> , this [1] post explain real example of this extraClass concept. > What is the reference? http://ssagara.blogspot.com/2011/07/how-to-get-best-use-of-axis2-object.html but this post related to code first approach. Thanks ! > > Bye > Vasek > -- > http://www.mangrove.cz/ > Open Source integration > -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/ LinkedIn - http://www.linkedin.com/in/ssagara --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org
