Ok, I see what a minOccurs means now. It does kind of make sense that no occurrence, no element in the message. Thanks, Anne.
On 4/9/08, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > If you specify minOccurs="1", then you can't return an empty array. > You must have at least one item in the array. > > > Anne > > > On Wed, Apr 9, 2008 at 2:05 AM, Tony Liu <[EMAIL PROTECTED]> wrote: > > The thing is that even I changed "minOccurs" to "minOccurs=1", which I > > suspect it means the corresponding element occuring at least once, but > it > > didn't seem to work. Or, have I missed something? > > > > > > > > On 4/9/08, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > If an element has been defined as minOccurs="0", and you have no > > > occurrences, then there should be no elements in the message. Is that > > > what you mean by "drops the array"? If you define an element to wrap > > > the array, then that element should still be there, but Axis2 > > > typically doesn't define an element to wrap an array. > > > > > > Anne > > > > > > > > > On Mon, Apr 7, 2008 at 4:24 PM, Tony Liu <[EMAIL PROTECTED]> wrote: > > > > Hi Axis users, > > > > > > > > Has anyone had a problem with returning an empty array but not null > > array? > > > > It seems Axis2 drops the array in the returning soap message if it > is > > empty > > > > (not null). > > > > There is an article about how to get around with it, but it doesn't > work > > for > > > > me. Can anyone help? > > > > http://www.ibm.com/developerworks/webservices/library/ws-array > > > > > > > > Regards, > > > > > > > > Tony > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
