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 <[email protected]> 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: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
