AW: AW: [Betwixt] XMLBeanInfo customization

2002-11-19 Thread h . dietrich
> -Ursprüngliche Nachricht- > Von: robert burrell donkin > [mailto:[EMAIL PROTECTED]] > Gesendet: Montag, 18. November 2002 22:53 > An: Jakarta Commons Developers List > Betreff: Re: AW: [Betwixt] XMLBeanInfo customization > > > On Monday, November 18, 2

Re: AW: [Betwixt] XMLBeanInfo customization

2002-11-18 Thread robert burrell donkin
On Monday, November 18, 2002, at 08:41 PM, [EMAIL PROTECTED] wrote: <%--- snip ---%> For handling XMLBeanInfos i guess a pluggable mechanism could be the right way, since there are different opinions about how and where to store XMLBeanInfos. IMHO these are solutions to different problems.

AW: [Betwixt] XMLBeanInfo customization

2002-11-18 Thread h . dietrich
<%--- snip ---%> > > Is there a reason for keeping the XMLBeanInfos inside the > Introspector. I > > would prefer something like an XMLBeanInfoRegistry class, > which keeps the > > instances. This would make it easier to provide > XMLBeanInfo, which might > > me > > generated on the fly withou

AW: [Betwixt] XMLBeanInfo customization

2002-11-18 Thread h . dietrich
Is there a reason for keeping the XMLBeanInfos inside the Introspector. I would prefer something like an XMLBeanInfoRegistry class, which keeps the instances. This would make it easier to provide XMLBeanInfo, which might me generated on the fly without using an Introspector. For handling XMLBeanIn

AW: [Betwixt] XMLBeanInfo customization [WAS Re: AW: [Betwixt] Support of user defined XMLBeanInfo?]

2002-11-14 Thread h . dietrich
... the solution you are suggesting would be very nice. I guess this could solve all my problems. I would provide a proxy object, which can be put in place of a object (reference). This object has getter and setter methods for a link and an object. The BeanReader and Writer then would just care ab