DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17439>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17439 WSDD causes deserialisation error ... not able to distribute the service! ------- Additional Comments From [EMAIL PROTECTED] 2003-03-09 09:54 ------- Today it is the 3rd time I try to answer you. Obviously 2 answers has been lost. I do not unserstand what you mean by saying "Please provide a complete test case that recreates the problem. Please include the code, wsdl's and schemas that lead to the problem.". You got as attachement the WSDL and the necessary XSD files. With those files in your hand you have all what is needed to re-create the case, just by using the WSDL2Java (I know you know that, if one knows it, then you!). What I saw is that in the new release you generate some classes where the constructor is declared as "PROTECTED" , why?. To me they are useless and causes a problem for the serialisation/de-serialisation. An other problem is that you do not add set- and get-method as well as a value-slot for the element which are declared without attribute or element. You'll see types that have only a group-element. I think for those generated classes we shall add a "default" VAR (String _value_) and the respective setter- and getter-Methods. Because the classes are referenced and again we get a serialisation problem.
