ImageJ nifti_io.jar conflict with tudor dicom tools

[Barnes Anna (UNIVERSITY COLLEGE LONDON HOSPITALS NHS FOUNDATION TRUST - RRV)]

This is an inconvenience rather than a show stopper but if I use the File>open and open a NFTI format image and then try and open plugins>tudordicom>dicom manager it gives this error.

"java.lang.SecurityException: class "DICOM_Manager"'s signer information does not match signer information of other classes in the same package" plus other java messages.

If I then quit and open plugins>tudordicom>dicom manager it opens fine but then if I try and File>open nifti format image I get this error.

"java.lang.SecurityException: class "HandleExtraFileTypes"'s signer information does not match signer information of other classes in the same package" etc

So basically if I open anything in tudor dicom tools first it stops all the other plugins from working and vice versa.

So as I said quitting and restarting isn't terrible just a little annoying.

Anybody know how I can stop it happening?

thanks
Anna

********************************************************************************************************************

This message may contain confidential information. If you are not the intended recipient please inform the
sender that you have received the message in error before deleting it.
Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents:
to do so is strictly prohibited and may be unlawful.

Thank you for your co-operation.

NHSmail is the secure email and directory service available for all NHS staff in England and Scotland
NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients
NHSmail provides an email address for your career in the NHS and can be accessed anywhere

********************************************************************************************************************

[dscho]

Hi Anna,

On Wed, 23 May 2012, Barnes Anna (UNIVERSITY COLLEGE LONDON HOSPITALS NHS FOUNDATION              TRUST - RRV) wrote:

> "java.lang.SecurityException: class "DICOM_Manager"'s signer information
> does not match signer information of other classes in the same package"
> plus other java messages.

Two workarounds I can imagine:

1) re-sign the .jar files with your own key:

        http://docs.oracle.com/javase/tutorial/deployment/jar/signing.html

2) remove the signatures from the .jar files by opening them as .zip files
and removing the appropriate parts in META-INF/ (if I remember correctly,
lines were added to MANIFEST.MF but there might be more to it)

There is also another ugly workaround that should work: make a new text
file named, say, policy.txt containing these lines:

-- snip --
grant {
        permission java.security.AllPermission;
};
-- snap --

And then start the Java Virtual Machine with the option
-Djava.security.policy=policy.txt (this might be not practical, depending
how you usually start ImageJ).

Ciao,
Johannes