[ http://issues.apache.org/jira/browse/AXIS-1780?page=comments#action_58010 ] Eugene Shershnev commented on AXIS-1780: ----------------------------------------
Was trying to clone another issue, but got the same description cloned into new issue. Here is the one for this bug: I'm deploying a wrapped style service using only an implementation and a WSDD file, but the generated WSDL document produced errors. WSDL defines a complex type (ArrayOf_xsd_anyType) based on the array convention defined in SOAP Encoding, which is not permitted by WS-I. Mailing list thread can be found here: http://marc.theaimsgroup.com/?l=axis-user&m=110631919625474&w=2 > Invalid Array type definition in generated WSDL according to WS-I > reccomendations > --------------------------------------------------------------------------------- > > Key: AXIS-1780 > URL: http://issues.apache.org/jira/browse/AXIS-1780 > Project: Axis > Type: Bug > Components: WSDL processing > Versions: 1.2RC2 > Environment: Windows 2000 Server, Tomcat 5.5 > Reporter: Eugene Shershnev > > I'm deploying a wrapped style service using only an implementation and a WSDD > file, but the generated WSDL document produced errors. There are a number of > elements defined in the schema > with invalid names. An element name must be of NCName type, but they have > been give QNames instead of NCNames. For example: > <element name="tns1:locale" type="xsd:string"/> > should be defined like this instead: > <element name="locale" type="xsd:string"/> > Mailing list thread can be found here: > http://marc.theaimsgroup.com/?l=axis-user&m=110631919625474&w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
