Zaq, I assume that your .net client will not only authenticate in the java web service. It looks like you are not able to perform the first operation i.e " logon". Therefore if you would like that your .net client also performs other operations, I will suggest you to follow the contract-first approach (also known as WSDL first) because you will have other troubles with the other function IMHO...
Hope this helps. Jose FERREIRO On 6/16/08, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > There no option for asking the tools to generate attributes rather > than elements. For the most part, it's considered a bad practice. Bear > in mind that attributes must be simple types. > > Anne > > On Mon, Jun 16, 2008 at 8:08 AM, Zaq Rizer <[EMAIL PROTECTED]> wrote: > > On Mon, Jun 16, 2008 at 6:54 AM, keith chapman <[EMAIL PROTECTED]> > > wrote: > >>> > >>> I'd suggest to switch to the contract-first approach: you'll have to > >>> learn WSDL, of course, but you have much more control over > interoperability > >>> and you'll get to use Axis2 (the latest version, at least) with > success. > >> > >> Thanks, > >> Keith > >> > >> Alternatively you can use a tool such a java2wsdl to generate the WSDL > for > >> you and then tune it accor ding to your needs (remove minoccurs and > >> nillable). > >> > >> Thanks, > >> Keith. > > > > Thanks for the input everyone. I will go with Keith's recommendation of > > modifying the produced WSDL. Does anyone know of a way to automatically > > change the format of the WSDL instead of modifying it by hand? (e.g. > > somehow modifying an underlying axis2 config file or perhaps even source > > file?). > > > > I'll see how this solution works for us. > > > > Regards, > > Zaq > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
