Hi Kjell , There is no such a limitation , and we have set of test cases to test all those scenarios , are you using Axis2 1.2 or the SNAPSHOT. Please try Axis2 SNAPSHOT and see whether you have the issues , if so please create a JIRA and attach your java classes.
Thanks Deepal > Hi > > This is a newbee question. I just started with Axis2 and have gone > through the samples. As I thought the POJO solution looked simple and > yet powerful I tried to extend the sample to use complex datatypes, > aka objects as argument and returnvalue. > > I first changed the operation findEntry to return an object (class > MyResponse) that contained another object (Entry) and that worked > without problem. So I could get a structure of objects back using the > ADB client which was nice. > > After that success I tried to change the argument to an object (class > MyRequest) that contained the String name. But that did not work. The > ADB client reported that he found an unexpected Text. > > So know I wonder befor I put too much effort inte this: Is there some > architectual constrains with the POJO solution that doesn't allow > complex datatypes in the argument? > If there is what solution do you suggest. Im going to implement a > webservice with a not to complicated structure of objects as argument > and returnvalue to the operation. > > Maybee the problem lies in that I am using an ADB client and that the > server is not the problem. > > Please enlighten me :) --kjell > Kjell Nilsson > Oops Ab > www.oops.se > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Thanks, Deepal ................................................................ "The highest tower is built one brick at a time" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
