I wonder what timeframe I should aim for with my IoC modifications and
the multiple databases patch that depends on these IoC modifications. It
would be nice to get at least some parts tested by other people.
On 07/26/2011 11:40 PM, Howard Lewis Ship wrote:
On Tue, Jul 26, 2011 at 1:41 PM, Igor Drobiazko
<[email protected]> wrote:
I need to fix some issues with the JPA integration and some minor issues
with Kaptcha component.
Again, great ... that's what's beta is for (solidifying). What I'm
looking for is buy-in that it's time to shift from rapid, far-reaching
changes to stabilization. It would be awesome if we could be at RC
status by JavaOne.
On Tue, Jul 26, 2011 at 6:20 PM, Howard Lewis Ship<[email protected]> wrote:
I'm running down my list of things I want for the beta. I only have
two main things that I really want to get in this release:
1) A standard, adaptable system for global alerts. I've prototyped a
system for this in my client app, and want to move that code into the
main code base. It would be an SSO, with services for adding alerts
and clearing them both on the server side (integrated with Ajax
updates) and on the client side.
2) A replacement for MultiZoneUpdate with more features and an easier API.
What's on everyone else's list?
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Best regards,
Igor Drobiazko
http://tapestry5.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
