I too am new to Wicket, and wanted to start using it without having to learn a persistance tool. I have never used a framework before, just JSP and Servlets. I tried dabbling a little with JPA, but found it confusing - especially when working with tables whose primary keys have more than one field. I use MyEclipse within Eclipse, and that helped me some.
My app was mostly inquiry only into a legacy database created in SQL Server. I come from an AS400/ISeries background. We took the database from that system and converted to SQL Server. This app had a search panel, and several repeaters that took you to more detail. What I did from the JPA experience was create a java class for most of my tables and also a detachable model class for those that made sense. I have one DAO - Data Access Object - a class that would connect to DB via JDBC and using SQL populate (map from DB to) the objects. This DAO had several methods that either populated the table object with one row, or another method that would create a LIST object containing several rows. I would use these LIST objects to populate whatever Wicket repeater you wanted to use. I found it much better/faster to create a java class for just the fields that the LIST needed, and then through the selected LIST row, I would get the larger chunk of data to populate a panel. The LIST would always contain the "keys" I needed to get the larger chunk from the DAO. The table to object java classes (I guess you could call them beans) contained all the fields in the SQL result set that I was going to use, getters and setters, and a build method. I found placing the build method within the bean was much easier than doing it in the DAO. The DAO instantiated the object and called the build method - passing the resultset as a parameter. I hope this makes sense. It took my quite a while to get to this point, and was the most difficult part of learning Wicket. You have to play with it a bit to see exactly where you want to call your DAO and build your data objects. I do want to learn a persistance tool and integrate that since most Wicket users tend to use this practice. I am by no means "good" at using Wicket yet, but have a thurst to dig deeper. I just bought the Wicket In Action book and hope that this will do the trick. -- View this message in context: http://www.nabble.com/Wicket-database-access-tp15613515p15634454.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
