I can see what you mean about the validation of the keys and the index issue. I am mostly thinkin on this from a Seam perspective, where I need to make sense of the path. I begs an interesting question of how to handle complex keys and how to represent what element in invalid in the collection.
I know the set iterator and map values iterator will not always produce the correct index. For set, there really is no other choice except maybe the object's id. For Map, the map key would be fine as well in the path. The problem for key and set item ID is that if the objects are complex, then they will not translate into a string path. As I mentioned, I thought this would be a good "initial" release. Hopefully there is enough in the patch to make it easier for you or another hibernate developer to get a good head start to completing the functionality. I am about to finish the patch for seam assuming that this code is not changed drastically. -Andrew View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3924832#3924832 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3924832 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
