Thanks Tom, That is what I though, the process is currently pretty straight forward so for now there is no need to play in the SymbolTable.
Sylvain. -----Original Message----- From: Tom Jordahl [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 5:23 PM To: '[EMAIL PROTECTED]' Subject: RE: Symbol tables If you have all you need from the SymbolTable already, I heartily recommend not touching that class if you don't have too. The whole idea is to put the WSDL info in a form that is simpler to deal with in (generally) the writer methods. If you are scrounging around in the WSDL in the stub writer however, I think this kind of work should be done 'up front' in the Symbol Table. -- Tom Jordahl Macromedia -----Original Message----- From: St-Germain, Sylvain [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 3:06 PM To: Axis Dev (E-mail) Subject: Symbol tables Hi all, I am currently implementing the header stuff, I got most of the client side magic done, now I need the JavaStubWriter modified in order to get my BindingStub class created properly. I noticed that most (?) of the processing during a WSDL2Java session caches stuff in SymbolTable.java, I am now wondering if this is a MUST DO IT THAT WAY rule or not? It seems that I have all I need within JavaStubWriter.writeFileBody() to do the kunfu I need. I started imitating the processing done for Parameters but after a little while I realized that parameters were much more complex to deal with than headers which may be the reason for caching the info. I do not think I need to go that route... But the question is: should I? -- Sylvain St-Germain (613) 738.1338 x5250 Macadamian Technologies @ Cognos [EMAIL PROTECTED] "Software experts to the world's leading technology companies" 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.
