You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jeff Lubetkin (JIRA)" <ta...@jakarta.apache.org> on 2005/07/27 20:05:18 UTC

[jira] Created: (TAPESTRY-447) Messages in org.apache.tapestry.engine.EngineMessages should be public

Messages in org.apache.tapestry.engine.EngineMessages should be public
----------------------------------------------------------------------

         Key: TAPESTRY-447
         URL: http://issues.apache.org/jira/browse/TAPESTRY-447
     Project: Tapestry
        Type: Bug
  Components: Framework  
    Versions: 4.0    
    Reporter: Jeff Lubetkin
    Priority: Minor


When creating a custom service, it'd be nice to use the existing messages in org.apache.tapestry.engine.EngineMessages.  As only one of them is public (serviceNoParameter), the others can't be used.

This issue is mentioned in TAPESTRY-157, but I thought it deserved its own bug, since this issue is mostly unrelated to the main issue in 157.

-- 
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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


[jira] Closed: (TAPESTRY-447) Messages in org.apache.tapestry.engine.EngineMessages should be public

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

    Fix Version: 4.0
     Resolution: Fixed

> Messages in org.apache.tapestry.engine.EngineMessages should be public
> ----------------------------------------------------------------------
>
>          Key: TAPESTRY-447
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-447
>      Project: Tapestry
>         Type: Bug
>   Components: Framework
>     Versions: 4.0
>     Reporter: Jeff Lubetkin
>     Assignee: Howard M. Lewis Ship
>     Priority: Minor
>      Fix For: 4.0

>
> When creating a custom service, it'd be nice to use the existing messages in org.apache.tapestry.engine.EngineMessages.  As only one of them is public (serviceNoParameter), the others can't be used.
> This issue is mentioned in TAPESTRY-157, but I thought it deserved its own bug, since this issue is mostly unrelated to the main issue in 157.

-- 
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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


[jira] Assigned: (TAPESTRY-447) Messages in org.apache.tapestry.engine.EngineMessages should be public

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

Howard M. Lewis Ship reassigned TAPESTRY-447:
---------------------------------------------

    Assign To: Howard M. Lewis Ship

> Messages in org.apache.tapestry.engine.EngineMessages should be public
> ----------------------------------------------------------------------
>
>          Key: TAPESTRY-447
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-447
>      Project: Tapestry
>         Type: Bug
>   Components: Framework
>     Versions: 4.0
>     Reporter: Jeff Lubetkin
>     Assignee: Howard M. Lewis Ship
>     Priority: Minor

>
> When creating a custom service, it'd be nice to use the existing messages in org.apache.tapestry.engine.EngineMessages.  As only one of them is public (serviceNoParameter), the others can't be used.
> This issue is mentioned in TAPESTRY-157, but I thought it deserved its own bug, since this issue is mostly unrelated to the main issue in 157.

-- 
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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org