[ http://issues.apache.org/jira/browse/MUSE-45?page=all ]
Dan Jemiolo closed MUSE-45.
---------------------------
Resolution: Fixed
Added on top of general muse-core persistence layer. Entries are persisted in a
way that is very similar to persistence of router entries - specifying a
location for the entry data to be saved:
<persistence>
<java-persistence-class>
org.apache.muse.ws.resource.sg.impl.ServiceGroupFilePersistence
</java-persistence-class>
<persistence-location>service-group-entries</persistence-location>
</persistence>
> Persistence for ServiceGroup and ServiceGroupEntry
> --------------------------------------------------
>
> Key: MUSE-45
> URL: http://issues.apache.org/jira/browse/MUSE-45
> Project: Muse
> Issue Type: New Feature
> Components: WSRF WSSG ServiceGroup
> Affects Versions: 2.0.0 M1
> Reporter: Dan Jemiolo
> Assigned To: Dan Jemiolo
> Fix For: 2.0.0 M2
>
>
> Muse's router persistence records all the EPRs/resource instances, but the
> WSSG impl still needs to save/reload all of the SG entry data for each entry
> resource. This should be the responsibility of each ServiceGroup impl - it
> should record its entry data (EPR and member EPR) and then find the entry (by
> EPR) upon reloading and assign all of its values back to pre-reboot state.
> This should require any change to the Entry component.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
