This week's book giveaway is in the General Computing forum. We're giving away four copies of Arduino in Action and have Martin Evans, Joshua Noble, and Jordan Hochenbaum on-line! See this thread for details.
I'm facing a weird problem for which I don't have a clue...
I'm trying to develop a NetBeans 6.1 rich client application and I want to use JAXB for Java-XML-Binding in one module of this project.
What I've already done so far is the basic structure of the rich client application and an ordinary Java project with JAXB. Both projects work fine!
The problem now is, that I created the simple Java application with JAXB just for testing purposes, and I want to integrate this functionality in a separate NetBeans module in order to use it in the rich client application. I've already created a module for this purpose and added the necessary dependencies for the JAXB libraries (which are included in the current NetBeans platform). I have access to all the classes from the JAXB libraries in this module now.
What I am missing is the context menu entry if I right-click the module project and choose "New -> ...". For "normal" Java projects I've got an option here to add a "JAXB Binding", but for my NetBeans module project I don't have this option. Of course I could try to add and edit the necessary build files etc. which I've got in my ordinary Java project, but I think this isn't a real solution. It would be very helpful to have the full IDE support to auto-generate the JAXB Java classes and so on. And as I said the NetBeans IDE has this support for plain Java projects, so it'd be a waste of time to do this by hand.
Anyone similar experiences? Unfortunately the usage of JAXB isn't probably too widespread, so I guess I'm out of luck in this case. But perhaps someone has made such experiences with other IDE features that are missing when developing a NetBeans module in contrast to a normal Java application.
In the meantime I found out, that my problem is simply due to restrictions of the JAXB wizard in NetBeans 6.x! The wizard only works for Java SE, Web or EJB projects. So it has nothing to do with unsatisfied dependencies or missing libraries.
I guess then the only workaround will be to create a Java SE project and use a library wrapper module to integrate it into the rich client application. Any comments?