Yeap, I played myself with this maxOccurs thing, and experienced the same. It doesn't really matters what you type in. I also tried to play with a string type, which had some restriction on it (regular expression). That restriction didn't appear anywhere in the code. Okay, I said, Axis cannot handle everything in a WSDL, it just has to ignore some things. It cannot generate Java code for everything. My problem was that not even a string attribute appeared in this case in the generated object (the restricted String). Although this maxOccurs thing seems an easy job to me. Are we missing something [like always :)] ? Br, Geza
BTW: congrats for Axis, we just love it ! :) Really. >I'm wondering if the minOccurs / maxOccurs-Attribute are analyzed by the >wsdl2java-Tool. >I noticed that there's always the same generated Class no matter what the maxOccurs >says. >The tool seems to assume that it's always 1. For example I tested the following: ...
