Well, you could take a single row from the ResultSet equivalent, or even the entire ResultSet, 'lock it' (by overriding with all .updateDB() methods cleared out, or, better yet, no need to do so as the object you need to update the DB is separate from the ResultSet which is side-effect free immutable), and then pass it around with abandon. Right now you have to either trust the code you hand resultsets to, or, more usually, extract what you need, wrap it in some other object (usually POJOs, sometimes automated via JPA), and then hand those around.
... but read-and-rewrap is something that has other advantages, so I'm not sure how much this is worth. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/i0DQG3mAC0IJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
