This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When I try visually to create a Swing Form (Wizards and Visual Editor) with NetBeans it support only JDBC Connection (DataSource, EntityManager) as available source of data. This is not usable for Enterprise Client/Server applications like GlassFish, JPA and JNLP Swing because in that type of application all data manipulation (retrieving, persist, delete) is served through EJB3 Session Beans which are in Server side. For that reason to use NetBeans for Enterprise Client/Server applications is not possible or we have to work in older way without BeansBinding and Java Application Framework. This can be fixed when the page of Database Connection/Table Selection is replaced with EJB Session Selection. Then instead table selection we can choose between method (properties) selection. It is good immediately after that page (form) to add another form where to create BindingGroups (one form can have more than one Binding Group) and to associate the properties selected from the previous page to each BindingGroup. Also in that page we can set which of the properties are for read/write or just read access. The EJB support for visually creation of forms with AWT, Swing, and JavaBeans is extremely important for one Rich Enterprise Client/Server application.
I would like to share another features related with that matter. For example depending on the method return parameter type different JComponent can be added to the form. If the returned parameter is some kind of Collection then JXTable, JXComboBox, JXList or/and another single data component can be used. If the returned parameter is Date JXDatePicker or another Date related JComponent can be used.
This defect mixes many things together. * support for binding in EJB applications This is already possible. Beans binding is not restricted to JDBC applications. The same holds for NetBeans. You can binding whatever properties you want. The only requirement is to let the GUI builder know about these beans and properties e.g. you must add the beans into the form or make them available via some properties. For example, you can add List<Clients> getClients() and setClients(List<Clients>) methods into the form file and bind your table to Form (binding component) and ${clients} (binding expression). The getClients() method can (obviously) obtain the data from any source (including application server that supports EJB). * master/detail sample using EJB We don't plan to add master/detail sample for EJB similar to JPA one. The purpose of master/detail sample is to provide an example how JPA can be used together with beans binding. This example is far from real-world application, but it provides a good starting point for beginners. Once you understand the principles covered by this example then you should be able to modify it to use EJB instead of JPA. * usage of other components in master/detail sample We plan to improve the master/detail sample to show how to use JFormattedTextField to bind Date objects, but we don't plan to use 3rd party components (like SwingX ones). It would be an overkill to bundle SwingX components just for this purpose.