You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by robert burrell donkin <ro...@blueyonder.co.uk> on 2002/11/14 19:38:04 UTC
[Betwixt] XMLBeanInfo customization [WAS Re: AW: [Betwixt] Support of user defined XMLBeanInfo?]
On Tuesday, November 12, 2002, at 06:45 PM, h.dietrich@webfair.com wrote:
> Hi Robert,
hi Harald
<snip>
> But anyway I would like to use Betwixt in a more flexible way (e.g. having
> own XMLBeanInfos for some Beans).
<snip>
> But on the other hand, if you are interested in making the way beans are
> written and read more flexible I would like to support you. For example
> what
> is it about the .betwixt files? I could not further information about
> them.
.betwixt files are the way that betwixt allows XMLBeanInfo's to be
customized. you can do things such as deciding which properties are going
to be mapped to xml etc. there is (some) documentation on them on the web
site (http://jakarta.apache.org/commons/betwixt).
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.
- robert
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Betwixt] XMLBeanInfo customization
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On Sunday, November 17, 2002, at 09:36 PM, Stephen Colebourne wrote:
> From: "robert burrell donkin" <ro...@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?
probably so. unfortunately the amount of effort that i had intended to
devote to the above solution is probably too little to make a difference
to [clazz] ;)
a pluggable introspection solution would be cool.
what i was talking about (above) is a little different since really it'd
be an alternative to .betwixt files for custom mappings. when you're using
a custom mapping then betwixt only makes limited use of the introspector
(if at all).
- robert
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Betwixt] XMLBeanInfo customization
Posted by Stephen Colebourne <sc...@btopenworld.com>.
From: "robert burrell donkin" <ro...@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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Betwixt] XMLBeanInfo customization
Posted by robert burrell donkin <ro...@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?
- robert
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Betwixt] XMLBeanInfo customization [WAS Re: AW: [Betwixt]
Support of user defined XMLBeanInfo?]
Posted by Martin van den Bemt <ml...@mvdb.net>.
> 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)
Mvgr,
Martin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>