I'd really like to see something on passing meta data to HiveMind before
4.0, even if it's just a documented workaround. I know this was brought
up as an issue with HiveMind, but given that it wasn't fixed before the
1.1 release, Tapestry users need to pay for it.
Am I just a really vocal minority? If so, I'll sit back a bit and quiet
down a bit. Everyone has pet issues they'd like to see taken care of. It
just seems to me like it'd be the best way to pass off configuration data
to services and it doesn't really work.
--
Kevin
On Wed, 30 Nov 2005 22:27:27 -0500, Howard Lewis Ship <[EMAIL PROTECTED]>
wrote:
By the time this vote ends, we'll have some kind of fix for
TAPESTRY-724. I think, with that, Tapestry 4.0 is ready for prime
time. We've already had the discussion of outstanding bugs needing
fixing. I think we should get 4.0 out the door.
Howard M. Lewis Ship: +1 (binding)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
