nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Our worksite only works with JVM version 1.4.2_03

trond

Hi all,

we have been using Worksite MP for about 6 months now, and are still having major issues with the JVM compatibility.

It seems that all our users MUST have version 1.4.2_03 of the JVM installed - and NOT multiple version in addition. The problem is that we have a lot of developers in our company that create products using the newest version of JVM. They are currently not able to use worksite because they require updated versions of JVM installed on their computers.

If they have another verison installed, they will experience java script errors when they try to log in, when they try to check in/check out documents, or when they try to open the 'add workgroup' menu. Some will not even be able to log in due to this. Also, if they have multiple versions of the JVM installed, the same errors occurs. It does not matter what OS the clients are using.

Has anyone else experienced this problem? Are there any hotfixes/service packs available that allows worksite to be used with any version of JVM? Is JVM 1.4.2_03 the ONLY version of JVM that works? If so, would that update erase our current settings/data?

Is it possible to migrate to the .NET version of Worksite without losing our settings/data? Would that mean we need to re-purchase Worksite?

Any help would be greatly appreciated.

Find more posts tagged with

Comments

peter_choe

i have been able to get worksite mp 4.1. sp 1 to work with sun java jre 1.5. but i needed to change some javascript to let worksite mp accept the version 1.5. the worksite mp will look specifically for version 1.4, but it can be modified to accept other versions. you usually can tell the browser what version of java to use in the options.

JTNeville

**warning, none of this is supported by Interwoven! ** back up all files before modifying anything!! Try out all changes on a test server!!

I've experimented too and found that MP is stable up to 1.4.2_08 without major issue, and like Peter have edited these files in the bc directory:

bcheck.js
bcheck.jsp

to get MP to run with newer versions of java and alternate browsers. I think that is all I edited (but it's been a while), though I did customize some of the other files (recommended_jvm.jsp and wrongbrowser.jsp) to make the messages more friendly when a users system wasn't up to snuff and give them links to fixes, workarounds, feedback.

The .java files are in their two for msJVM and msJVMBeanInfo in case you like to tinker and write your own classes to handle stuff.

I also add a javascript popup for whenever someone wasn't using an Interwoven approved version of the java to warn them that they might and if they had any issues to email me please.

You can also comment out the browser/jsp check in the index.jsp page but then you are opening the door for errors without warning/explanantion and this often makes users/clients more annoyed than happy.

hth

Migrateduser

you might want to think about moving up to 4.1 SP1. This version allows you to not have to use a JVM. I haven't tried it; but I was told there a few small user limitations with this option.

Regards,

lissa