You need to log in before you can comment on or make changes to this bug.
In the same way as a JSR 296 application, with a connection to a db, can be created via a project template, there should be a template that does the same for the NetBeans Platform. It would be a NetBeans Platform application project template called "Database CRUD Application", the template would let the user select a db connection, and then a JPA-based application would be created, including best practices for such an application (i.e., maybe the application would be created with more than one module, maybe JSR 295 would be used for beans binding). The user should not have to reinvent the wheel (or use a tutorial or something) every time they want to implement this completely standard requirement. Plus, having this template would be a BIG "selling point" for the NetBeans Platform.
Here's an example of what would need to be generated by this module (not very much): http://netbeans.dzone.com/news/eclipselink-netbeans-platform Basically, we need to take the existing JSR-296 Swing Framework CRUD generator and let it generate NetBeans Platform code instead, similar to the code discussed in the blog entry above (that's a very simple case but at least gets the user somewhere beyond zero).
Thanks for the quick report. Now that we are into it, I would also like to suggest making the Collection, Set or List choices for the JPA entities creation wizard a little bit more flexible. For example, by allowing to specify any class implementing the required interface (Collection?) in the project's classpath. For example, something I sometimes do is generate from NB IDE and then edit the code to use the ObservableList from Beans Binding. I'll be nice to be able to accomplish that from within the wizard itself.
