Issue Details (XML | Word | Printable)

Key: XALANJ-2283
Type: Improvement Improvement
Status: Closed Closed
Resolution: Duplicate
Priority: Minor Minor
Assignee: Unassigned
Reporter: Dave Brosius
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
XalanJ2

[PATCH] remove needless synchronization

Created: 20/Mar/06 08:21 AM   Updated: 09/Jan/08 03:49 AM
Return to search
Component/s: None
Affects Version/s: 2.7
Fix Version/s: 2.7.1
Security Level: No security risk; visible to anyone (Ordinary problems in Xalan projects. Anybody can view the issue.)

Time Tracking:
Not Specified

Issue Links:
Duplicate
 

Xalan info: PatchAvailable
Fix priority: fp4
Resolution Date: 15/Oct/06 02:45 PM


 Description  « Hide
Several places in the code uses synchronized collections for local variables that are not exposed outside of the method in which they are declared. this is just a waste. This code, changes these instances to use non-synchronized collections.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Brian Minchau added a comment - 05/Apr/06 02:20 AM
Dave, you've marked this one as 'PatchAvailable'. Where is the attached patch for us to look at? Or is this one superseded by XALANJ-2284?

Brian Minchau added a comment - 05/Apr/06 03:30 AM
Comments from Triage on April 4, 2006:
> No patch, probably a duplicate of 2284

Brian Minchau added a comment - 15/Oct/06 02:45 PM
Duplicate of xalanj-2284 (which has the same description but has the patch).

Brian Minchau added a comment - 11/Dec/07 03:16 PM
This issue is no longer relevant for 2.7.1, it is fixed in 2.7.1.
Changing the affected version to 2.7.

Brian Minchau added a comment - 11/Dec/07 04:57 PM
Would the originator of this issue please verify that this issue is fixed in the 2.7.1 release, by adding a comment to this issue, so that we can close this issue.

A lack of response by February 1, 2008 will be taken as consent that we can close this resolved issue.

Regards,
Brian Minchau