By Martin Grebac on Mar 23, 2011
Just a short migration note ... this blog will be migrated to blogs.oracle.com in a month or two.
While working on some parts of JAXB, and using NetBeans myself for development, I came across the two projects parse-ipr and parse-dot-classpath, which are useful when you need to invoke your project files from command line without an IDE. I developed a NetBeans equivalent of those: parse-nb. What it does?
Basically, it allows you to parse your NetBeans Java project files (nbproject/project.xml, project.properties) and give you a java classpath-way formatted string as an output.
So if you run it on JAXB2.1 project (which I just updated from freeform to regular NB J2SE project), you get a scary output like this:
I believe you would never want to write or maintain this by hand, and it is still useful to have it to be able to run e.g. an individual tests manually from command line, so this way you can write your own scripts to set whatever classpath you wish to set. Read more at parse-nb website, and download from the project's download area.
I do run it as a part of bash setup, so that I can then always start debugging tests like this:
java $DBG $JB21 TestCaseRunner .
And here's a usage info:
It of course lacks in many areas, so improvements are always welcome! I'd also appreciate if the NetBeans library system gets much simpler, as it's very hard to work with currently.
Couple of people asked about availability of the new features I described earlier. The bits there point to NetBeans 6.5 builds. Question is whether you can use the same bits for NetBeans 6.1?
Unfortunately the answer so far is no, it is not possible. However, come here for updates.
I've tried to keep the bits the same, but there has been a change in classpath apis which didn't allow me to produce the same artefacts for both 6.5 and 6.1 builds. There's also a WS server api redesign planned for 6.5. So, I'll try to provide the build, but we'll see.
Ashutosh reminded me of a feature which was not supported yet by NetBeans. It's the ability to sign and encrypt message attachments. This is connected to the message level specific settings.
For each operation, or better say for each message of your web service, you have an option to select whether the whole message body shall be encrypted, or signed, or both. If you don't want to process the whole body, and want to sign & encrypt only specific credit card information field to improve performance significantly, you may specify such configuration as well.
The new feature now enables you to configure the same for message attachments. You may choose to sign and/or encrypt message attachments. Just click "Add Attachments" button and then check checkboxes in respective columns:
The security policy generated from such configuration looks like this:
The views expressed on this [blog; Web site] are my own and do not necessarily reflect the views of Oracle.