dims, Remy, and Anne, thanks for your answer & comments. To: dims
I logged this issue to JIRA as AXIS2-756. I also mentioned about 'attributeFormDefault' in JIRA. To: Remy >I tried with Axis 1.2 and 1.4 and .Net framework 1.0 and 2.0 I tried with Axis2 1.0 and VisualStudio .NET 2003 and Office XP Web Services Toolkit 2.0 (from Excel). >I suppose it is mandatory for .Net. I think so, too. I was checking auto-generated client proxy code of .NET. There was a different between 'unqualified' and 'qualified'. And 'unqualified' one never succeed, always gets 'Nothing'. To: Anne >I just scanned through the WS-I Basic Profile, >and I found no rules or recommendations to specify "unqualified" I'm sorry. This is my mistake. I misunderstood some articles. >(e.g ., if you specify elementFormDefault="unqualified", .NET will handle it properly) I had specified elementFormDefault="unqualified" when I tested with .NET. But .NET could not handle returned message, and got 'Nothing' object. Axis2 seems always generates the elementFormDefault attribute. Regards, kinichiro __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
