This one time, at band camp, [EMAIL PROTECTED] said:
>> <quote>
>> At any rate, in applications I've built in the past where I
>> wasn't using
>> Castor, I implemented both toString() and toXml() methods.
>> </quote>
>
>You lost me at a single blow. Do you mean to distinguish from toXmlCharArray()? Let's
>make the option Keith mentioned earlier a function-name
>in org/exolab/castor/builder/castorbuilder.properties:
>org.exolab.castor.builder.stringName = toBla
My apologies. What I was talking about was just a general-use method for
printing out an XML string representation of an object, not necessarily
for use with Castor XML.
>Anyway, I can get my hands on a string representation of the object, I'm just asking
>for less code in my program.
>
>Here it is:
>
>String xmlString(){
> StringWriter w = new StringWriter();
> this.marshal(w);// maybe the more generic way instatiate a marshaller:-{
> return w.toString;
>}
Definitely possible. I've always just encapsulated the marshal() method
inside my own method called marshal() and the same with unMarshal().
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
