I think we can all make strong cases for situations in which detaching the ID makes sense, and depending on the needs of the app, also situations where just serializing the POJO makes sense. Shades will work with either case.
What I would like, is the freedom to offer the deployer of the Phonebook, the opportunity to choose the strategy. Could we have some sort of configuration parameter that controlled the detachment strategy of DetachableContactModel? Some property like serializeOnDetach=false This would give the deployer the freedom to make the "space vs. time" decision. -geoff ____________________________________________________________________________________ Low, Low, Low Rates! Check out Yahoo! Messenger's cheap PC-to-Phone call rates (http://voice.yahoo.com) ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
