OpenDDS Java Binding Developer Guide Example error

Following the OpenDDS Developer’s Guide – Chapter 11 I ran into an error like this:

Using …/ACE_wrappers/bin/MakeProjectCreator/config/MPC.cfg
CIAO_ROOT was used in the configuration file, but was not defined.
Generating ‘gnuace’ output using default input
Skipping Foo (Foo.mpc), it requires java.
Generation Time: 1s

I have solved following the suggestion from a post on sourceforge tracker that I report here just for an easy access on that info. (Personally I have user -features java=1 as parameter of the script)

Welcome to OpenDDS!

In $DDS_ROOT/java/INSTALL, in Step 4 (Configure TAO), there are
instructions for enabling Java support by setting java=1 in the appropriate
file(s) (depending upon your platform) or passing -features java=1 on the command line when you build ACE+TAO. The recommended approach is to
set java=1 in $ACE_ROOT/bin/MakeProjectCreator/config/default.features so
it is always set whenever you run

You can also enable Java support for OpenDDS when you install ACE+TAO with
the $DDS_ROOT/configure script with ./configure –java from $DDS_ROOT. See
$DDS_ROOT/INSTALL for more information on using the configure script and
run ./configure –help to see all the options.

(Note: If you are on Windows using Visual Studio, the command to run the
configure script is just configure from a Visual Studio command prompt.)


Eclipse Access Restriction Error

Clickide 3

Image via Wikipedia

When in Eclipse you have an error like: “Access restriction: The constructor AppletAudioClip(URL) is not accessible due to restriction on required library C:\Programmi\Java\jdk1.6.0_24\jre\lib\rt.jar” You simply need to follow these steps to avoid compilation error:

Click on the Properties of your project Go to Java Compiler–>Errors/Warnings search for “Deprecated and Restricted API” and set to warning “Forbidden reference (access rules)” item.

That’s it.

Java – Single Application Instance

Duke, the Java Mascot, in the waving pose. Duk...

Image via Wikipedia

If you want to prevent the user from running multiple copies of your Java application here are two approaches I could suggest you:
1) You can verify if a busy file exist. If one exists, abort. If not create one.  The process to test and create the file can be developed in the script file that triggers the application or in the application itself.  When the app exists it deletes the busy marker file. The main problem with this simple approach is if your app crashes, it won’t delete the busy file. You have to manually delete it before you can run the app again.

2) Another approach is to have your application open a ServerSocket on a particular port number. The OS will prevent other processes from opening a ServerSocket that uses the same port. If you start the application and are unable to open your ServerSocket (i.e. if you get an “address already in use” exception) assume that the application is already running. In that case, you can use a Socket to connect to the running application and pass it whatever commands you like, or just abort.


Installing Java on CentOS 5.5

Trying to use the standard java distribution from Oracle (….Sun was acquired from Oracle…) could be a little confusing so I just link another blog were you find described the adopted solution for CentOS 5.2 but that is applyable also to CentOS 5.5.