commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From h.dietr...@webfair.com
Subject AW: [Betwixt] XMLBeanInfo customization
Date Mon, 18 Nov 2002 10:59:17 GMT
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 XMLBeanInfos i guess a pluggable mechanism could be the right
way, since there are different opinions about how and where to store
XMLBeanInfos.

BTW: I got my code running and it works well, but I still use the
Introspector to get an XMLBeanInfo and modify it the way I want to use it.

- Harald

> -----Urspr√ľngliche Nachricht-----
> Von: Stephen Colebourne [mailto:scolebourne@btopenworld.com]
> Gesendet: Sonntag, 17. November 2002 22:37
> An: Jakarta Commons Developers List
> Betreff: Re: [Betwixt] XMLBeanInfo customization
> 
> 
> From: "robert burrell donkin" <robertburrelldonkin@blueyonder.co.uk>
> > On Saturday, November 16, 2002, at 02:08 PM, Martin van den 
> Bemt wrote:
> > >> since XMLBeanInfo's were supposed to correspond to 
> java.beans.BeanInfo.
> > >> BeanInfo supports programmatic implementations. so if 
> you had something
> > >> like xxx.yyy.zzz.FooBean then betwixt might look for a
> > >> xxx.yyy.zzz.FooBeanXMLBeanInfo class which would be a 
> programmatic
> > >> XMLBeanInfo.
> > >>
> > >> i don't know if adding this feature would help you or not.
> > >
> > > This is already "kind of" supported, from a 
> java.beans.Introspector
> > > perspective. Don't think it is an ellegant solution 
> though that sun
> > > chose (with registring searchpaths)
> >
> > agreed :)
> >
> > i was thinking along the lines of allowing a custom programmatic
> > XMLBeanInfo implementation but insisting that the package 
> and name match
> > exactly. so, for example, if you have a bean with full name
> > xxx.yyy.FooBean, betwixt would try to discover a class called
> > xxx.yyy.FooBarXMLBeanInfo.
> >
> > anyone have any improvements on this plan?
> 
> I've lost track of the original request, but...
> [clazz] is intended to provide a pluggable replacement to 
> Introspector,
> capable of pulling in data from XML files or specially coded classes.
> Ideally I would like to see [betwixt] use [clazz] once 
> complete, thus maybe
> the effort should go into [clazz] as a broader solution?
> 
> Stephen
> 
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: 
> <mailto:commons-dev-help@jakarta.apache.org>
> 

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message