You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Fernando Padilla <fe...@alum.mit.edu> on 2009/02/16 23:05:41 UTC
Re: tapestry-spring
you're saying that I should be able to use it with the snapshot builds now?
how do I turn it off?
Howard Lewis Ship wrote:
> That has been implemented (Tapestry 5.0.18 spring bean behavior); the
> question is whether it should be enabled or disabled by default.
> Currently, it is disabled; an upgrade to 5.1 will use the new
> functionality and it'll be your responsibility to switch it off.
>
> On Mon, Feb 16, 2009 at 1:27 PM, Fernando Padilla <fe...@alum.mit.edu> wrote:
>> As everyone is listing out specific bugs that we think are blockers:
>>
>> https://issues.apache.org/jira/browse/TAP5-428
>> https://issues.apache.org/jira/browse/TAP5-431
>>
>> These are the two bugs dealing with how tapestry-spring was totally broken,
>> and the only "work around" was to simply not use the latest tapestry-spring.
>> I think that solution is not a good long term solution, and thus a hack..
>> :)
>>
>> A clean solution should be reached where the old tapestry-spring behavior
>> still works ( Tapestry will bring in Spring Beans from a Spring Context
>> constructed outside of Tapestry ).
>>
>>
>> Howard Lewis Ship wrote:
>>> I'd to put together a plan to get an alpha release of Tapestry 5.1 out the
>>> door.
>>>
>>> I've put in place all the major enhancements that I want for the release.
>>>
>>> There's a few bugs, mostly Ajax related, to tackle. Those should be
>>> handled before the 5.1 final release, but an alpha release does not
>>> need to wait for them.
>>>
>>> I'm very interested in getting a 5.1 final release out. As I've
>>> pointed out in prior threads, it would be good for the community to
>>> demonstrate a significantly enhanced Tapestry that's compatible with
>>> 5.0.18.
>>>
>>> What's on everyone's "must have" list?
>>>
>>> For example, I'd like to finish the Spring Web Flow integration, but
>>> I'm willing to defer that out to 5.2 in the interest of fast
>>> turnaround 5.1.
>>>
>> ---------------------------------------------------------------------
>> 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: tapestry-spring
Posted by Alex Kotchnev <ak...@gmail.com>.
Howard,
thanks for the clarification, I didn't realize that there was such a
distinction (e.g. I understand that non-services can be injected). What are
the consequences of Spring services not being T5 services : e.g. what are
the kind of facilities that are available to T5 services that Spring
services wouldn't have ? I was poking around the documentation to try to
understand the difference that you outlined, and here's what I found:
( ---- from the environmental services page ---- )
Environmental services represent yet another, distinct form of injection.
Unlike service injection (injection via a service implementation's
constructor) or normal component injection (directly into component fields,
via the @Inject annotation) where the injected value is always the same,
with environmental services, the injected value is very late bound and
dynamic.
-----------------
So, one aspect that is evidently different is that services can have their
arguments injected into the constructor (which wouldn't be an issue w/
Spring services, as they're constructed and instantiated by Spring). What
are other aspects that were available to Spring services "before", and will
not be available after 5.1 ?
Cheers,
Alex Kotchnev
On Wed, Feb 18, 2009 at 6:12 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
> The spring beans are still fully injectable, they just aren't
> represented as Tapestry IoC services.
>
> On Tue, Feb 17, 2009 at 1:50 PM, Alex Kotchnev <ak...@gmail.com> wrote:
> > My personal opinion is that the "compatibility" mode should be the
> default
> > mode : e.g. up to this point, there is no code that depends on the "new"
> > mode. I find the "Spring beans are no longer exposed as services"
> > particularly bothersome : for some reason, I think that there is a much
> > better chance (at least in my apps) that I might have a "generally
> > available" spring services that I'd need to inject into Tapestry than the
> > other way around.
> >
> > Can somebody clue me in : what is the most important feature that
> requires
> > the "incompatible" mode to be the default ? I remember reading on the
> list
> > about Spring Web Flow integration, but is that the only thing that makes
> the
> > new and incompatible mode the default ? What if the 'compatible' mode was
> > the default, and if someone wanted SWF, they could enable the
> incompatible
> > one ?
> >
> > Cheers,
> >
> > Alex Kotchnev
> >
> > On Tue, Feb 17, 2009 at 3:31 AM, Massimo Lusetti <ml...@gmail.com>
> wrote:
> >
> >> On Mon, Feb 16, 2009 at 11:05 PM, Fernando Padilla <fe...@alum.mit.edu>
> >> wrote:
> >>
> >> > you're saying that I should be able to use it with the snapshot builds
> >> now?
> >> >
> >> > how do I turn it off?
> >>
> >> Does this sounds good to you?
> >>
> >> From http://tapestry.formos.com/nightly/tapestry5/tapestry-spring/
> >>
> >> =============================================================
> >> 5.0 Compatibility Mode
> >>
> >> In some circumstances, it is desirable to configure the Spring
> >> ApplicationContext externally. The context <config-param>
> >> "tapestry.use-external-spring-context" can be configured to "true".
> >> Tapestry will then use an existing ApplicationContext, provided by a
> >> Spring ContextLoaderListener. You will still be able to inject Spring
> >> beans into Tapestry components and services, and the
> >> ApplicationContext service will be visible ... but you will not be
> >> able to inject Tapestry IoC services into Spring beans.
> >>
> >> This option provides compatibility with the tapestry-spring 5.0,
> >> including exposing Spring beans as Tapestry IoC services (something
> >> that no longer occurs unless compatibility mode is enabled).
> >> =============================================================
> >>
> >>
> >> Regards
> >> --
> >> Massimo
> >> http://meridio.blogspot.com
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: dev-help@tapestry.apache.org
> >>
> >>
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: tapestry-spring
Posted by Howard Lewis Ship <hl...@gmail.com>.
The spring beans are still fully injectable, they just aren't
represented as Tapestry IoC services.
On Tue, Feb 17, 2009 at 1:50 PM, Alex Kotchnev <ak...@gmail.com> wrote:
> My personal opinion is that the "compatibility" mode should be the default
> mode : e.g. up to this point, there is no code that depends on the "new"
> mode. I find the "Spring beans are no longer exposed as services"
> particularly bothersome : for some reason, I think that there is a much
> better chance (at least in my apps) that I might have a "generally
> available" spring services that I'd need to inject into Tapestry than the
> other way around.
>
> Can somebody clue me in : what is the most important feature that requires
> the "incompatible" mode to be the default ? I remember reading on the list
> about Spring Web Flow integration, but is that the only thing that makes the
> new and incompatible mode the default ? What if the 'compatible' mode was
> the default, and if someone wanted SWF, they could enable the incompatible
> one ?
>
> Cheers,
>
> Alex Kotchnev
>
> On Tue, Feb 17, 2009 at 3:31 AM, Massimo Lusetti <ml...@gmail.com> wrote:
>
>> On Mon, Feb 16, 2009 at 11:05 PM, Fernando Padilla <fe...@alum.mit.edu>
>> wrote:
>>
>> > you're saying that I should be able to use it with the snapshot builds
>> now?
>> >
>> > how do I turn it off?
>>
>> Does this sounds good to you?
>>
>> From http://tapestry.formos.com/nightly/tapestry5/tapestry-spring/
>>
>> =============================================================
>> 5.0 Compatibility Mode
>>
>> In some circumstances, it is desirable to configure the Spring
>> ApplicationContext externally. The context <config-param>
>> "tapestry.use-external-spring-context" can be configured to "true".
>> Tapestry will then use an existing ApplicationContext, provided by a
>> Spring ContextLoaderListener. You will still be able to inject Spring
>> beans into Tapestry components and services, and the
>> ApplicationContext service will be visible ... but you will not be
>> able to inject Tapestry IoC services into Spring beans.
>>
>> This option provides compatibility with the tapestry-spring 5.0,
>> including exposing Spring beans as Tapestry IoC services (something
>> that no longer occurs unless compatibility mode is enabled).
>> =============================================================
>>
>>
>> Regards
>> --
>> Massimo
>> http://meridio.blogspot.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: tapestry-spring
Posted by Alex Kotchnev <ak...@gmail.com>.
My personal opinion is that the "compatibility" mode should be the default
mode : e.g. up to this point, there is no code that depends on the "new"
mode. I find the "Spring beans are no longer exposed as services"
particularly bothersome : for some reason, I think that there is a much
better chance (at least in my apps) that I might have a "generally
available" spring services that I'd need to inject into Tapestry than the
other way around.
Can somebody clue me in : what is the most important feature that requires
the "incompatible" mode to be the default ? I remember reading on the list
about Spring Web Flow integration, but is that the only thing that makes the
new and incompatible mode the default ? What if the 'compatible' mode was
the default, and if someone wanted SWF, they could enable the incompatible
one ?
Cheers,
Alex Kotchnev
On Tue, Feb 17, 2009 at 3:31 AM, Massimo Lusetti <ml...@gmail.com> wrote:
> On Mon, Feb 16, 2009 at 11:05 PM, Fernando Padilla <fe...@alum.mit.edu>
> wrote:
>
> > you're saying that I should be able to use it with the snapshot builds
> now?
> >
> > how do I turn it off?
>
> Does this sounds good to you?
>
> From http://tapestry.formos.com/nightly/tapestry5/tapestry-spring/
>
> =============================================================
> 5.0 Compatibility Mode
>
> In some circumstances, it is desirable to configure the Spring
> ApplicationContext externally. The context <config-param>
> "tapestry.use-external-spring-context" can be configured to "true".
> Tapestry will then use an existing ApplicationContext, provided by a
> Spring ContextLoaderListener. You will still be able to inject Spring
> beans into Tapestry components and services, and the
> ApplicationContext service will be visible ... but you will not be
> able to inject Tapestry IoC services into Spring beans.
>
> This option provides compatibility with the tapestry-spring 5.0,
> including exposing Spring beans as Tapestry IoC services (something
> that no longer occurs unless compatibility mode is enabled).
> =============================================================
>
>
> Regards
> --
> Massimo
> http://meridio.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: tapestry-spring
Posted by Massimo Lusetti <ml...@gmail.com>.
On Mon, Feb 16, 2009 at 11:05 PM, Fernando Padilla <fe...@alum.mit.edu> wrote:
> you're saying that I should be able to use it with the snapshot builds now?
>
> how do I turn it off?
Does this sounds good to you?
>From http://tapestry.formos.com/nightly/tapestry5/tapestry-spring/
=============================================================
5.0 Compatibility Mode
In some circumstances, it is desirable to configure the Spring
ApplicationContext externally. The context <config-param>
"tapestry.use-external-spring-context" can be configured to "true".
Tapestry will then use an existing ApplicationContext, provided by a
Spring ContextLoaderListener. You will still be able to inject Spring
beans into Tapestry components and services, and the
ApplicationContext service will be visible ... but you will not be
able to inject Tapestry IoC services into Spring beans.
This option provides compatibility with the tapestry-spring 5.0,
including exposing Spring beans as Tapestry IoC services (something
that no longer occurs unless compatibility mode is enabled).
=============================================================
Regards
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org