You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Weaver, Scott" <Sw...@rippe.com> on 2003/10/13 21:50:55 UTC
RE: [JETSPEED 2] using commons Digetser/Betwixt as an eventual re
plac ement for Castor
Hi Robert,
Well, I was having trouble with betwixt mapping correctly. Unfortunately, I could not find any good examples of a semi-complicated object model/xml mapping for betwixt. Digester seemed quite a bit more straight forward in its "pure" form as opposed to using betwixt on top of it. Plus I was able to find a couple of articles on Digester on the web that were very helpful.
However, if you have any experience with betwixt I would me more than happy to convert the digester version I'm working on to betwixt with your help.
Regards,
O-------------------O
| Scott T Weaver o---------------O
o-------------------o |
| Apache Jetspeed Portal Project |
| Apache Pluto Portlet Container |
o-------------------o |
| weaver@apache.org o---------------O
O-------------------O
> -----Original Message-----
> From: robert burrell donkin [mailto:rdonkin@apache.org]
> Sent: Monday, October 13, 2003 2:51 PM
> To: Jetspeed Developers List
> Subject: Re: [JETSPEED 2] using commons Digetser/Betwixt as an eventual
> replac ement for Castor
>
> hi scott
>
> were you thinking about using plain old digester or betwixt (which uses
> digester)?
>
> - robert
>
> On Monday, October 13, 2003, at 07:23 PM, Weaver, Scott wrote:
>
> > I would like to see what everyone's opinion on starting to replace
> Castor
> > with a combination of Digester/Betwixt. I have already been able to
> > replicate and surpass what we already have in Castor with regards to
> > marshaling the portlet.xml for deployment. Digester offers much more
> > flexibility when mapping xml into an existing object model than Castor
> > does. For example, we had to extend the existing object model to make
> it
> > work with Castor, with digester, this was not necessary. I am using our
> > standard Pluto implementation classes with little or no modifications.
> > IMOHO, the learning curve for digester is MUCH smaller than Castor's.
> > Within a matter of an hour, I was able to surpass the current level of
> > compatibility we have with the Castor implementation, and that was with
> > no previous experience with Digester. Another advantage is the size,
> > digester and betwixt are tiny compared to Castor.
> >
> > So, I would like to get everyone's blessing before I replace that Castor
> > piece with Digester for deploying the portlet.xml descriptor.
> >
> >
> > Regards,
> > O-------------------O
> > | Scott T Weaver o---------------O
> > o-------------------o |
> > | Apache Jetspeed Portal Project |
> > | Apache Pluto Portlet Container |
> > o-------------------o |
> > | weaver@apache.org o---------------O
> > O-------------------O
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [JETSPEED 2] using commons Digetser/Betwixt as an eventual re plac ement for Castor
Posted by robert burrell donkin <rd...@apache.org>.
On Monday, October 13, 2003, at 08:50 PM, Weaver, Scott wrote:
> Hi Robert,
hi scott
> Well, I was having trouble with betwixt mapping correctly. Unfortunately,
> I could not find any good examples of a semi-complicated object
> model/xml mapping for betwixt. Digester seemed quite a bit more straight
> forward in its "pure" form as opposed to using betwixt on top of it.
> Plus I was able to find a couple of articles on Digester on the web that
> were very helpful.
>
> However, if you have any experience with betwixt I would me more than
> happy to convert the digester version I'm working on to betwixt with your
> help.
i work on both betwixt and digester. betwixt does some pretty cool and
complex stuff but is still very much an alpha. i'd recommend sticking with
digester.
if you need a generative mapper (start-from-schema rather than
start-from-java) then you might like to look at xml-beans (but it's
probably more complex than digester).
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org