Hello, I've found a solution but I have not figured out the cause of the problem. I believe its something to do with threading as when I put the method inside a swing worker it works out fine. Without the swing worker, my variable seems to reference the wrong object. It seems the when the runnable runs, the object inside the runnable is referencing the new object and not the one that called it. Like somehow the runnable replace the reference to the first object with the second object.
thomas.deweese wrote: > One thing that looked a little fishy was the id generation. The id generation is just grabs a available # from the database. vyang -- View this message in context: http://www.nabble.com/invokelater-thread-issue--tf4319567.html#a12395333 Sent from the Batik - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
