You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-dev@ws.apache.org by "Joel Hawkins (JIRA)" <ji...@apache.org> on 2006/08/16 21:06:15 UTC
[jira] Created: (MUSE-60) Add opt-in or opt-out persistence
handling at the resource definition level
Add opt-in or opt-out persistence handling at the resource definition level
---------------------------------------------------------------------------
Key: MUSE-60
URL: http://issues.apache.org/jira/browse/MUSE-60
Project: Muse
Issue Type: Improvement
Components: Core Engine - Routing and Serialization
Reporter: Joel Hawkins
Assigned To: Dan Jemiolo
The current implementation of persistence doesn't retain some of the semantics of the original "startup-count". One use case that isn't well served is the case where a ServiceGroup is desired at startup, but the contents of the service group are always added dynamically. At present, persistence is a function of the router definition, and there's no opt-out (or opt-in, we can debate which is more appropriate) ability at the resource definition level.
--
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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Updated: (MUSE-60) Add opt-in or opt-out persistence
handling at the resource definition level
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-60?page=all ]
Dan Jemiolo updated MUSE-60:
----------------------------
Fix Version/s: 2.0.0
Affects Version/s: 2.0.0 M2
Due Date: 31/Aug/06
Accepted for 2.0.0 final release
> Add opt-in or opt-out persistence handling at the resource definition level
> ---------------------------------------------------------------------------
>
> Key: MUSE-60
> URL: http://issues.apache.org/jira/browse/MUSE-60
> Project: Muse
> Issue Type: Improvement
> Components: Core Engine - Routing and Serialization
> Affects Versions: 2.0.0 M2
> Reporter: Joel Hawkins
> Assigned To: Dan Jemiolo
> Fix For: 2.0.0
>
>
> The current implementation of persistence doesn't retain some of the semantics of the original "startup-count". One use case that isn't well served is the case where a ServiceGroup is desired at startup, but the contents of the service group are always added dynamically. At present, persistence is a function of the router definition, and there's no opt-out (or opt-in, we can debate which is more appropriate) ability at the resource definition level.
--
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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Closed: (MUSE-60) Add opt-in or opt-out persistence handling
at the resource definition level
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-60?page=all ]
Dan Jemiolo closed MUSE-60.
---------------------------
Resolution: Fixed
Fixed: http://svn.apache.org/viewvc?view=rev&revision=433004
> Add opt-in or opt-out persistence handling at the resource definition level
> ---------------------------------------------------------------------------
>
> Key: MUSE-60
> URL: http://issues.apache.org/jira/browse/MUSE-60
> Project: Muse
> Issue Type: Improvement
> Components: Core Engine - Routing and Serialization
> Affects Versions: 2.0.0 M2
> Reporter: Joel Hawkins
> Assigned To: Dan Jemiolo
> Fix For: 2.0.0
>
>
> The current implementation of persistence doesn't retain some of the semantics of the original "startup-count". One use case that isn't well served is the case where a ServiceGroup is desired at startup, but the contents of the service group are always added dynamically. At present, persistence is a function of the router definition, and there's no opt-out (or opt-in, we can debate which is more appropriate) ability at the resource definition level.
--
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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org