[morph-developer] [ morph-Bugs-1148597 ] Concurrency issues with Delegating____

[SourceForge.net <no...@so...>]

Bugs item #1148597, was opened at 2005-02-22 14:35
Message generated for change (Comment added) made by sgarlatm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=700930&aid=1148597&group_id=124910

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 6
Submitted By: Matt Sgarlata (sgarlatm)
Assigned to: Nobody/Anonymous (nobody)
Summary: Concurrency issues with Delegating____

Initial Comment:
If the setComponents method is called by two separate
threads on the same DelegatingConverter, the behavior
of the invoked converter is arbitrary, since derived
information about the components may be in an
inconsistent state in the object.  Should document this
or disallow setting the components property after it
has initially been set (kind of like how Chains are
"frozen" in the Commons Chain package).

----------------------------------------------------------------------

>Comment By: Matt Sgarlata (sgarlatm)
Date: 2005-12-06 11:34

Message:
Logged In: YES 
user_id=1161666

Fixed by adding the synchronized keyword to the signature of
the setComponents method.  Fix will appear in build after 0.9.2

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=700930&aid=1148597&group_id=124910