[ALF-903] Deployment via AVM deployment should throw notification if web project is not created on receiver server Created: 16-Feb-10  Updated: 31-Aug-16  Resolved: 26-Apr-10

Status: Closed
Project: Alfresco
Component/s: ZZ_Archive
Affects Version/s: 3.2 R Enterprise
Fix Version/s: 3.3 Enterprise

Type: Bug Priority: Major
Reporter: Alfresco QA Team (Inactive) Assignee: Closed Bugs (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows Server 2003, Tomcat, MySQL, FF3


Attachments: JPEG File node browser view.jpg    
Issue Links:
Duplicate
Related
Testcase ID:

WCM-911

Date of First Response:

 Description   

Steps:
1.Install Alfresco on two servers (server1 and server2)
2. Create Web Project "Test" on server1 with configured DR:
Type: Live Server, Display Name: DR live, Host: server2, Port: 50500, admin/admin, Target Name: avm
3. Add any content item and submit it directly to Staging Sandbox;
4. When new snapshot is created Deploy an item --> Deployment is successfull

Expected result:
Friendly notification about absence of the avm store should be displayed, deployment shouldn't be successfull.
Current system behaviour is inconvenient and can confuse a user - web project is not created automatically, but user also can't create it after deployment, because avm store is created automatically (can be observed using NodeBrowser or AVM console - see attach) and user has a notification when creating a Web Project.

OlgaTa



 Comments   
Comment by Mark Rogers [X] (Inactive) [ 16-Feb-10 ]

The creation of an authoring environment for a live store is not a "normal" use-case and in fact will add authoring artifacts like ACLs that may not be relevant to a live store.

This proposed fix would break the primary use-case which would not have an authoring environment for a live store.

If there is a use-case to be able to view a live store then that is an enhancement that needs to be scoped rather than a bug.

Comment by Steve Rigby [X] (Inactive) [ 26-Apr-10 ]

Review for inclusion in 3.3E or for future

Comment by Steve Rigby [X] (Inactive) [ 12-May-10 ]

For retest in 3.3E build 27

Comment by Alfresco QA Team (Inactive) [ 14-May-10 ]

Closed according to resolution "Won't Fix"

Comment by Derek Hulley [X] (Inactive) [ 31-Aug-16 ]

The component originally used was not a supported, recognisable system component with an associated component owner. Either the component never existed (it was fictional) or it has reached end-of-life.
The issues will be closed. Reopen and assign to an existing system component if necessary. Use labels appropriately.

Generated at Sun Mar 07 17:13:12 GMT 2021 using Jira 7.13.15#713015-sha1:7c5ddd2c3e1709974ae9c48c17df8edd3919fe2c.