All the IDataProvider implementations I have seen use a single POJO. What about an example with multiple POJOs?
For a single POJO I normally have a DataProvider object that gets data from my DAO object. For multiple POJOs would it be best to have a DataProvider object that gets data from a DAO which is based on a query of multiple POJOs (tables in my case) ? I am not immediately sure of the ramifications of doing this. Is there a better way that I just don't realize? -- View this message in context: http://www.nabble.com/IDataProvider-Best-Practice-for-multiple-POJOs-tf4879377.html#a13963492 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
