I thin it needs some separation "model" can be used in tools like compiler,
doclet,
source code generator, debuger, editor ... . Default implementation can be
based on reflection (packages,classes, methods, costructors, fields ... ) .
Framework can be in separate paskage ( properties, events, delegates ... ).
I think it will be more simple to understand and reuse, it is like java's
reflect/beans.
> This adds to the complexity of the API. What advantages do we get in
return?
> (Certainly naming would be easier ;-)
>
> Stephen
>
> ----- Original Message -----
> From: "Juozas Baliuka" <[EMAIL PROTECTED]>
> To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]>
> Sent: Monday, October 28, 2002 7:27 PM
> Subject: Re: [clazz] Some code to consider
>
>
> > Hi,
> > I want to add all "features" to Meta* interfaces, I think this model
must
> > not to "reduce" jdk reflection.
> > I propose two packages :
> > 1) "xreflect" package (we can use naming like java.lang.reflect.* +
> > "attributes").
> > 2) "xbeans" package for "beans" like framework. ("delegate" can live
> here)
> >
> > "tools" like "xdoclets" is subject for next component, but we need some
> API
> > in [clazz] to plug implementations.
> >
> >
> >
> >
> >
> >
> >
> > --
> > 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>
>
--
To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
