You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by devel - Fashion Content <de...@fashioncontent.com> on 2006/07/31 12:47:33 UTC
IoC handling in T5
What if T5 implemented a strictly annotation based IoC container, and
HiveMind supported the same annotations but also supported the current xml
based configuration.
What if T5 could work together with HiveMind or on it's own depending on
wether you need backwards compatibility.
Yes I see that it would potentially require a parallel set of annotation
classes and parsing methods and some odd glue to merge the two, but wouldn't
it be a neat way to achive both objects from the user perspective.
Henrik
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: IoC handling in T5
Posted by adasal <ad...@gmail.com>.
This is what I have been thinking, and it seems to me that James is moving
in this direction with his thoughts on interceptors as he is suggesting that
HM will look like AspectJ, but externalised into XML.
I think that sometimes it is advantageous to use annotations, but sometimes
to use XML. At least in this regard that with annotations they are
immiediate and the thought process of the developer is uninterupted whereas
with XML there is a central repository to the "annotations" that can be
inspected, thought about and modified on their own, without having to look
at many different classes.
Adam
On 31/07/06, devel - Fashion Content <de...@fashioncontent.com> wrote:
>
> What if T5 implemented a strictly annotation based IoC container, and
> HiveMind supported the same annotations but also supported the current xml
> based configuration.
>
> What if T5 could work together with HiveMind or on it's own depending on
> wether you need backwards compatibility.
>
> Yes I see that it would potentially require a parallel set of annotation
> classes and parsing methods and some odd glue to merge the two, but
> wouldn't
> it be a neat way to achive both objects from the user perspective.
>
> Henrik
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: IoC handling in T5
Posted by devel - Fashion Content <de...@fashioncontent.com>.
What I imagine is that T5 might have an annotation package that mirrored the
HM annotations, and an implementation that essentially did the same, but
would detected HM if already loaded and merge the T5 annotation & HM
annotation based configuration runtime into a HM configuration.
Given my limited understanding of how annotations work I might be wrong, but
the only overhead I can identify is duplicate code and a minor one merging
the configuration.
A commons project would be another way to do it, but would of course add
dependencies.
Henrik
----- Original Message -----
From: "James Carman" <ja...@carmanconsulting.com>
To: "'Tapestry development'" <de...@tapestry.apache.org>
Sent: Monday, July 31, 2006 11:55 AM
Subject: RE: IoC handling in T5
> Well, if you wanted us to share annotations, you'd have to have T5 use
> HM's
> annotations, because there's no way that HM is going to introduce T5 (or a
> small part of it) as a dependency. I don't think HM is going to do away
> with the XML configuration completely. I would definitely vote against
> that. There are times when you don't have the luxury of source code in
> which to add the annotations.
>
> The idea I have had in the past would be to create a project that allowed
> you to use XML files or Annotations or anything else to supply the
> metadata
> to your applications, but access the metadata using the same API
> regardless
> of the source. I would call it Jakarta Commons Metadata or something.
>
> -----Original Message-----
> From: devel - Fashion Content [mailto:devel@fashioncontent.com]
> Sent: Monday, July 31, 2006 6:48 AM
> To: Tapestry development
> Subject: IoC handling in T5
>
> What if T5 implemented a strictly annotation based IoC container, and
> HiveMind supported the same annotations but also supported the current xml
> based configuration.
>
> What if T5 could work together with HiveMind or on it's own depending on
> wether you need backwards compatibility.
>
> Yes I see that it would potentially require a parallel set of annotation
> classes and parsing methods and some odd glue to merge the two, but
> wouldn't
>
> it be a neat way to achive both objects from the user perspective.
>
> Henrik
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
RE: IoC handling in T5
Posted by James Carman <ja...@carmanconsulting.com>.
Well, if you wanted us to share annotations, you'd have to have T5 use HM's
annotations, because there's no way that HM is going to introduce T5 (or a
small part of it) as a dependency. I don't think HM is going to do away
with the XML configuration completely. I would definitely vote against
that. There are times when you don't have the luxury of source code in
which to add the annotations.
The idea I have had in the past would be to create a project that allowed
you to use XML files or Annotations or anything else to supply the metadata
to your applications, but access the metadata using the same API regardless
of the source. I would call it Jakarta Commons Metadata or something.
-----Original Message-----
From: devel - Fashion Content [mailto:devel@fashioncontent.com]
Sent: Monday, July 31, 2006 6:48 AM
To: Tapestry development
Subject: IoC handling in T5
What if T5 implemented a strictly annotation based IoC container, and
HiveMind supported the same annotations but also supported the current xml
based configuration.
What if T5 could work together with HiveMind or on it's own depending on
wether you need backwards compatibility.
Yes I see that it would potentially require a parallel set of annotation
classes and parsing methods and some odd glue to merge the two, but wouldn't
it be a neat way to achive both objects from the user perspective.
Henrik
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org