without regard to the topic of this thread, could you elaborate on what
you mean here, and maye be give a usecase as example?
Kevin Menard wrote:
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
