InviteService creates a random extra person on rejection of an invite and requires a write transaction for some unknown reason

Description

This problem was discovered when Kevin changed all read-only web scripts to use read transactions in revision 14672.

This line was added to invites.get.desc.xml

<transaction allow="readonly">required</transaction>

The unit test then fails on testRejectInvite trying to create a Person and we're not sure why it's doing this.

Environment

None

Testcase ID

None

Activity

Show:
All Replies
October 31, 2020, 1:14 AM

[This issue has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The reporter of this issue was dward]

All Replies
January 22, 2016, 2:36 AM

[This comment has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The author of this comment was resplin] This issue was reported against an unsupported version of Alfresco Community Edition.

Alfresco 5.1will is nearing release, and contains many improvements that address old problems. We are closing old issues so that we can better prioritize our efforts.

If you verify that the issue still exists in at Early Access release of Alfresco 5.1, please reopen the issue. If you have any trouble reopening the issue, then leave a comment or email us at community@alfresco.com so that we can assist.

Thank you for collaborating with us on improving Alfresco.

All Replies
November 6, 2009, 1:12 PM

[This comment has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The author of this comment was mrogers] Assigning to services team.

I suspect this issue may have already been resolved.

All Replies
June 25, 2009, 5:41 PM

[This comment has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The author of this comment was mrogers] Reducing the severity of this issue from "Blocker" to "Major".

This script is deprecated and should not be called.

All Replies
June 25, 2009, 3:45 PM

[This comment has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The author of this comment was mrogers] The problem was due to the "auto" creation of users who were being listed by this method. It's an unwanted side-effect.

However this script is no longer called from Share so I don't want to spend too much time fixing it.

I can't remove this method since there are Unit tests depending on it so I have marked it as "deprecated".

As and when MOB-128 is resolved then this script can be removed.

Won't Fix

Assignee

All Replies

Reporter

All Replies