SymbolTable is populated by reading in a WSDL file. Users of the symbol table are allowed to add info to the existing symbol table entries but they're not allowed to change the symbol table. Before the symbol table is given to the back end there is some verification and conflict resolution done on it. You could end up with an inconsistent symbol table if you added symbols after this stage.
What exactly are you trying to accomplish here? Why do you have to add things to the symbol table? Russell Butek [EMAIL PROTECTED] Neil Smyth <[EMAIL PROTECTED]> on 04/19/2002 05:04:50 AM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: changing permissions on SymbolTable.add() I am looking to leverage the code in wsdl.toJava.SymbolTable and the wsdl.toJava package in general, to generate sample XML for a given message part. Currently I am using a slightly modified version of beta1 where I have upgraded the permission on SymbolTable.add() to public as it is currently protected, and with beta2 coming down the pipeline I was hoping this change could make it into it. The only information I am interested in from the wsdl file is the parts description, so going through the whole writerFactory/writer mechanism is overkill. I think the symbol table is useful in its own right but keeping the add method protected makes it difficult to get a populated symbol table, though not impossible, from the current API. I am happy to update my code as the toJava package changes as I am aware that it is not a stable API. Regards, Neil
