That makes sense. Currently, JavaStubWriter does not have access to the variable "Emitter.bGenerateAll" and hence I was unable to detect whether "--all" was used or not. That is the reason why I did not do what you have described.
Should all pertinent information from the Emitter be passed to the Writer class? Charles -----Original Message----- From: Russell Butek [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 01, 2002 4:32 PM To: [EMAIL PROTECTED] Subject: Re: [PATCH] WSDL2Java - BindingStub not registering all types. Your solution would work. And thanks for offering it! But this brings up an issue. What do we do when a WSDL file has two (or more) portTypes/bindings in it? Your solution would register ALL referenced types in ALL stubs. When the --all flag is turned on, that's probably what we MUST do. But when it's not turned on, then we should only register those types used by that stub. So the old code should be used when --all is not used, and your new code should be used when --all is turned on. Sound reasonable to folks? Comments? Russell Butek [EMAIL PROTECTED] "Ng, Charles" <[EMAIL PROTECTED]> on 05/01/2002 03:16:30 PM Please respond to [EMAIL PROTECTED] To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: Subject: [PATCH] WSDL2Java - BindingStub not registering all types. I've attached a patch for this problem. The type mappings were generated from types that are used in operations. Having the "-a" option does not change that fact. I've modified the code to get the types from the symbol table and only generate the type mappings where the types are referenced. (The "-a" flag makes all symbol table entries referenced) Charles > -----Original Message----- > From: Russell Butek [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 22, 2002 12:07 PM > To: [EMAIL PROTECTED] > Subject: Re: WSDL2Java - BindingStub not registering all types. > > > Sylvain, I thought the -a option ws supposed to register all > types. We > discussed this a while ago and I believe we agreed. Either > we never did > the work or it was inadvertently removed. > > All types should be registered in both the Stub AND in the > deploy.wsdd file > if -a is turned on. > > I'll fix this after beta 2. > > Russell Butek > [EMAIL PROTECTED] > > > "St-Germain, Sylvain" <[EMAIL PROTECTED]> on > 04/22/2002 10:19:58 > AM > > Please respond to [EMAIL PROTECTED] > > To: "Axis Dev (E-mail)" <[EMAIL PROTECTED]> > cc: > Subject: WSDL2Java - BindingStub not registering all types. > > > > Hi all, > > When the -a option was added to WSDL2Java it was mainly to serve the > purpose > of being able to use (thus serialize) the objects defined in > the WSDL even > though they appeared unused from a WSDL perspective. > > I realize now that WSDL2Java does some smarts about it and > will not define > the QName for a type for which it does not find a > reference... or something > like that. > > All types I define (this is true for all my SOAP Header types) are not > being > mapped in my BindingStub. Is it possible to add mapping in the > BindingStub > for all types defined in the WSDL regardless of them being > referred to or > not? > > This is using -the somewhat old- March 25th build. I will > check with a > more > recent build. > -- > Sylvain > > This message may contain privileged and/or confidential > information. If > you > have received this e-mail in error or are not the intended > recipient, you > may not use, copy, disseminate or distribute it; do not open any > attachments, delete it immediately from your system and > notify the sender > promptly by e-mail that you have done so. Thank you. > > This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you.
