You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hivemind.apache.org by "Howard M. Lewis Ship (JIRA)" <hi...@jakarta.apache.org> on 2006/04/15 16:55:00 UTC

[jira] Created: (HIVEMIND-175) Extend the Messages interface to support querying to see if a particular key has a defined message

Extend the Messages interface to support querying to see if a particular key has a defined message
--------------------------------------------------------------------------------------------------

         Key: HIVEMIND-175
         URL: http://issues.apache.org/jira/browse/HIVEMIND-175
     Project: HiveMind
        Type: New Feature

  Components: framework  
    Reporter: Howard M. Lewis Ship
 Assigned to: Howard M. Lewis Ship 
     Fix For: 1.2


This is common in Tapestry, and I'd like to make it more so (in terms of smart defaults for components); currently code has to "sniff" the output message to see if it [LOOKS-LIKE-THIS].

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org


[jira] Closed: (HIVEMIND-175) Extend the Messages interface to support querying to see if a particular key has a defined message

Posted by "Howard M. Lewis Ship (JIRA)" <hi...@jakarta.apache.org>.
     [ http://issues.apache.org/jira/browse/HIVEMIND-175?page=all ]
     
Howard M. Lewis Ship closed HIVEMIND-175:
-----------------------------------------

    Resolution: Fixed

Marked a bunch of constructors on MessageFormatter as deprecated in the process. They weren't the ones anyone was using :-)

> Extend the Messages interface to support querying to see if a particular key has a defined message
> --------------------------------------------------------------------------------------------------
>
>          Key: HIVEMIND-175
>          URL: http://issues.apache.org/jira/browse/HIVEMIND-175
>      Project: HiveMind
>         Type: New Feature

>   Components: framework
>     Reporter: Howard M. Lewis Ship
>     Assignee: Howard M. Lewis Ship
>      Fix For: 1.2

>
> This is common in Tapestry, and I'd like to make it more so (in terms of smart defaults for components); currently code has to "sniff" the output message to see if it [LOOKS-LIKE-THIS].

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org


[jira] Commented: (HIVEMIND-175) Extend the Messages interface to support querying to see if a particular key has a defined message

Posted by "Howard M. Lewis Ship (JIRA)" <hi...@jakarta.apache.org>.
    [ http://issues.apache.org/jira/browse/HIVEMIND-175?page=comments#action_12374639 ] 

Howard M. Lewis Ship commented on HIVEMIND-175:
-----------------------------------------------

MessageFormatter used to log invalid keys as an error inside findMessage(), but that was stripped out, and was the only use of the Log instance, so that was removed, which is why the constructors that have a Log parameter are deprecated.

> Extend the Messages interface to support querying to see if a particular key has a defined message
> --------------------------------------------------------------------------------------------------
>
>          Key: HIVEMIND-175
>          URL: http://issues.apache.org/jira/browse/HIVEMIND-175
>      Project: HiveMind
>         Type: New Feature

>   Components: framework
>     Reporter: Howard M. Lewis Ship
>     Assignee: Howard M. Lewis Ship
>      Fix For: 1.2

>
> This is common in Tapestry, and I'd like to make it more so (in terms of smart defaults for components); currently code has to "sniff" the output message to see if it [LOOKS-LIKE-THIS].

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org