The situation I am in is already having the WSDL definition and wish to
generate some sample XML for each part in the wsdl definition. Once I have
the symbol table populated, I then query it for the various type/element
definitions and loop through the structure to generate XML. I am not adding
extra information to the symbol table once it is populated via the add()
method. For example, the WSDL segment
....
<s:element name="StockGetter">
<s:complexType>
<s:sequence>
<s:element maxOccurs="1" minOccurs="1"
name="StockPrice" type="s:double"/>
<s:element maxOccurs="1" minOccurs="1"
name="ExercisePrice" type="s:double"/>
</s:sequence>
</s:complexType>
</s:element>
...
<message name="SomeMessage">
<part name="StockPrice" element="s:StockGetter"/>
</message>
...
should generate sample XML (ignoring namespaces for simplicity) along the
lines of
<StockGetter>
<StockPrice>10</StockPrice>
<ExercisePrice>1</ExercisePrice>
</StockGetter>
I would like to use Axis's support in this area in order to leverage the
JAX-RPC schema subset support.
The current code setup requires that you create an emitter, which you then
call emit() on with the definiton to generate all the output. I'd like to
avoid creating the emitter and providing it with a Noop writer factory etc
just to get access to a populated symbol table.
Regards,
Neil
-----Original Message-----
From: Russell Butek [mailto:[EMAIL PROTECTED]]
Sent: 19 April 2002 14:07
To: [EMAIL PROTECTED]
Subject: Re: changing permissions on SymbolTable.add()
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
