You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Francis Amanfo <fa...@tydex.com> on 2005/03/22 16:48:18 UTC
Tapestry 3.1
I think the changes made in 3.1 are so radical that 3.1 needs to be a 4.0
release to avoid confusions.
However, I do have one question. Why the tight integration of Hivemind IOC
in Tapestry 3.1? I've been doing my middle tier with Spring and have no
short term plans to switch. Why must I be bothered with Hivemind
configurations if I only need Tapestry soley for the presentation layer?
Or
am I missing something?
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Tapestry 3.1
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
You'll have to "deal" with it, sure. But you shouldn't be "bothered"
by it :)
Please trust that Howard has done an incredible job with the HiveMind
integration and Tapestry is far more extensible than ever before. And
you should not have to extend the engine (I don't think) to configure
services in 3.1/4.0. You'll use HiveMind configuration files to do
that instead of literally subclassing BaseEngine like is often done
now.
Erik
On Mar 22, 2005, at 12:21 PM, Henri Dupre wrote:
> On Tue, 22 Mar 2005 10:56:57 -0500, Erik Hatcher
> <er...@ehatchersolutions.com> wrote:
>> You won't be "bothered" by HiveMind configuration in Tapestry in
>> normal
>> usage - you'll still use .application/.page/.jwc specification files
>> like you do in 3.0. Only when you need to extend Tapestry would you
>> configure those extensions with HiveMind.
>>
>> Erik
>
> It seems to me that making a real world website always requires
> extending the engine in 3.0... My bet is that you will have to deal
> with HiveMind in 3.1. I also vote for 4.0 +1
>>
>>
>> On Mar 22, 2005, at 10:48 AM, Francis Amanfo wrote:
>>
>>> I think the changes made in 3.1 are so radical that 3.1 needs to be a
>>> 4.0
>>> release to avoid confusions.
>>>
>>> However, I do have one question. Why the tight integration of
>>> Hivemind
>>> IOC
>>> in Tapestry 3.1? I've been doing my middle tier with Spring and have
>>> no
>>> short term plans to switch. Why must I be bothered with Hivemind
>>> configurations if I only need Tapestry soley for the presentation
>>> layer? Or
>>> am I missing something?
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail:
>>> tapestry-user-help@jakarta.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Tapestry 3.1
Posted by Henri Dupre <he...@gmail.com>.
On Tue, 22 Mar 2005 10:56:57 -0500, Erik Hatcher
<er...@ehatchersolutions.com> wrote:
> You won't be "bothered" by HiveMind configuration in Tapestry in normal
> usage - you'll still use .application/.page/.jwc specification files
> like you do in 3.0. Only when you need to extend Tapestry would you
> configure those extensions with HiveMind.
>
> Erik
It seems to me that making a real world website always requires
extending the engine in 3.0... My bet is that you will have to deal
with HiveMind in 3.1. I also vote for 4.0 +1
>
>
> On Mar 22, 2005, at 10:48 AM, Francis Amanfo wrote:
>
> > I think the changes made in 3.1 are so radical that 3.1 needs to be a
> > 4.0
> > release to avoid confusions.
> >
> > However, I do have one question. Why the tight integration of Hivemind
> > IOC
> > in Tapestry 3.1? I've been doing my middle tier with Spring and have no
> > short term plans to switch. Why must I be bothered with Hivemind
> > configurations if I only need Tapestry soley for the presentation
> > layer? Or
> > am I missing something?
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Tapestry 3.1
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
You won't be "bothered" by HiveMind configuration in Tapestry in normal
usage - you'll still use .application/.page/.jwc specification files
like you do in 3.0. Only when you need to extend Tapestry would you
configure those extensions with HiveMind.
Erik
On Mar 22, 2005, at 10:48 AM, Francis Amanfo wrote:
> I think the changes made in 3.1 are so radical that 3.1 needs to be a
> 4.0
> release to avoid confusions.
>
> However, I do have one question. Why the tight integration of Hivemind
> IOC
> in Tapestry 3.1? I've been doing my middle tier with Spring and have no
> short term plans to switch. Why must I be bothered with Hivemind
> configurations if I only need Tapestry soley for the presentation
> layer? Or
> am I missing something?
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org