Whoa - just ran into something in my quest to port Spindle over. The Messages strategy used by Hivemind and thus now by Tapestry makes it hard for Spindle to produce messages identical to those one would see at runtime.
Would it be a real pain to change this private static final MessageFormatter _formatter (found in all the Messages subclasses I've looked at so far) into this.. protected static final MessageFormatter _formatter That way I can subclass the Messages and add Spindle specific stuff. This impacts quite a few classes in Tapestry *and* Hivemind BTW. Geoff P.S. I know that these classes are package protected and that's fine I can deal with that. On 5/12/05, Geoff Longman <[EMAIL PROTECTED]> wrote: > Geoff Longman: +1 > > On 5/12/05, David Solis <[EMAIL PROTECTED] > wrote: > > David Solis: +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]
