I have used the java.beans.XMLEncoder and java.beans.XMLDecoder and it has worked great for both transitions as long as all the bean properties and sub properties implement Serializable. I will look into Betwixt to see if there are some advantages.
Thanks, Greg -----Original Message----- From: Craig R. McClanahan [mailto:craigmcc@;apache.org] Sent: Wednesday, October 23, 2002 1:20 PM To: Struts Users Mailing List Subject: Re: Managing User defined Web Content design advice? On Wed, 23 Oct 2002, Eddie Bush wrote: > > commons-digester does a *nice* job of turning XML into instantiated > objects. You have to setup some rules, but that's not hard at all. > Refer to the javadoc for commons-digester. I'm not sure if it can > "serialize objects to XML" or not. I don't think that is the job it was > designed for. Craig could say better than I. It really makes > reading/instantiating objects represented in XML very easy though. > Digester is focused on the XML-->JavaBean transition, not the other way. You might investigate using another Commons package called Betwixt for doing the JavaBean-->XML thing. One of the examples is round tripping using both Digester and Betwixt together. Craig -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
