Bug 793577 (JBEPP-656)

Summary: Docs: Site Publisher Release Notes
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: Scott Mumford <smumford>
Component: DocumentationAssignee: Scott Mumford <smumford>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.2.0.GACC: epp-bugs
Target Milestone: ---   
Target Release: 5.2.x   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-656
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-17 05:12:31 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 793372    

Description Scott Mumford 2010-11-22 01:18:06 UTC 
Affects: Documentation (Ref Guide, User Guide, etc.)
project_key: JBEPP

Issues relating to the Site Publisher Release Notes.
Comment 1 Scott Mumford 2010-11-22 01:19:31 UTC 
Add content re the following SP Clustering scenario:

scenario : UserA is served on Server1. Server1 is killed, UserA lose his session and currently edited content but not all the changes already persisted in the JCR.

There's no guaranty you will keep your content (the one in your session) but the persisted data (JCR) should not be corrupted.

Until then, my opinion is : if we lose a server node, you will lose the current content you edit. But you can switch to another node and go back to work. That's the failover we support.

For this reason, we added a "Save as draft" that doesn't close the edit dialog so contributors can save when they want. When they work on critical data they can save and continue to work.
Comment 2 Scott Mumford 2011-02-15 07:36:07 UTC 
Release Notes Docs Status: Added: Not Required