I have a question (possibly a bug) for the UnclaimedFieldWorker class. Suppose i have a worker class implementing ComponentClassTransformWorker2, this class adds extra fields to the class using plastic: plasticClass.introduceField
Now it looks like this field is gonna be missed in the UnclaimedFieldWorker making this new field not thread-safe ?! Because, as I understand, the sequence is the following: 1. Construct a PlasticClassImpl (existing fields are added) 2. Pass this to the ClassTransformWorker2 chain 3. <Myclass> adds field (added to fieldNames and classNode.fields, but not to fields) 4. UnclaimedFieldWorker transforms all fields returned by PlasticClassImpl.getFields(), which misses the introduced field Or am i missing something here ? -- View this message in context: http://tapestry.1045711.n5.nabble.com/BUG-UnclaimedFieldWorker-tp5718537.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
