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. Also you could extend above POJO support by using extraClass parameter , this [1] post explain real example of this extraClass concept. Thanks ! On Tue, Sep 27, 2011 at 12:22 PM, Vaclav Barta <v...@comp.cz> wrote: > Hi, > > I'm trying to implement a webservice proxy (for Betfair - it would be nice if > one could test new clients without actually betting real money) using Axis2, > but it doesn't work very well. Specifically, it doesn't work with bfplusplus, > the most popular Open Source Betfair client, apparently because bfplusplus > (which is written in Python) doesn't use the webservice schema, but relies on > xsi:type declarations (provided by Betfair but not by my proxy) to transform > XML responses into Python structures. So, I'd like to set up my Axis2 > webservice to provide xsi:type declarations - how do I do that? I've read > http://axis.apache.org/axis2/java/core/docs/adb/adb-advanced.html#typeSupport > , but can't say I understand it - and it seems to be concerned with clients, > while my problem is on the server... Can Axis2 webservices generate xsi:type > declarations at all? > > Bye > Vasek > -- > http://www.mangrove.cz/ > Open Source integration > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org > For additional commands, e-mail: java-user-h...@axis.apache.org > > -- 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
