A while back I installed Forte4J 2.0 on Win2000/Pro using JDK1.3...after 'updating' a Forte4J JAR file (or two), I went to launch the IDE and received a SEALING VIOLATION error. My bad. Now, when I go to re-install Forte (or install 3.0), no matter what I do, I receive the Sealing Violation error ad nauseum...Any way around this? I've uninstalled, re-installed, looked in the Win registry but to no avail...
> when I go to re-install Forte (or install 3.0)
Did you really uninstall the things prior to intalling again? Did you check the Forte directory after uninstalling? Make sure that your updated Fortje JARs are really gone... Maybe the uninstall does not delete your JAR file, and the installation program does not overwrite it, due to it's timestamp.
Also make sure to unset any classpath -- maybe your problem is not at all related to this Forte JAR, like maybe you've got some incompatible XML stuff in your classpath.
> I receive the Sealing Violation error
In case you don't know what the error means: see 3 threads down; http://forum.java.sun.com/thread.jsp?forum=60&thread=159824
a.
I greatly appreciate your response...I cleared the classpath (after uninstalling) but let the installer change the classpath. I did unistall the JAR files but also deleted the directory, re-booted, etc. I do understand the "sealing violation" exception and now am wondering if, in fact, the sharing of JARs (by Forte) is causing the problem and/or whether my other installations are conflicting - i.e., Tomcat, Cocoon, and/or other Java SDKs (i.e., messaging, JavaCard, J2MEWTK, etc.) ?
One possible solution that might help is upgrading my J2SE SDK. I had been running 1.3 and now have updated to 1.3.1 - in essence, a 'clean' install...unfortunately, this did not work either.
Still cannot use Forte4J, though I can use PointBase - which, by the way, is great. I guess tha gripe is simply that there is no 'graceful' error handle - the startup of the Forte IDE just 'locks' - I needed to (a) look at the log file or (b) edit the runide.bat file to even figure out that it was, in fact, a sealing violation that was the problem.
> edit the runide.bat file
Dos this file use a java command? If so, try to -verbose to see what class is causing the violation. Like
java -verbose -cp .. ..
I guess that Forte uses XML for user preferences -- the org.w3c classes are a well known cause for "Sealing Violation" or "No such method" errors. Any XML installation might give you the problems then, as the user preferences have to be read while starting Forte...
Arjan.
