Tomcat Java Runtime Version java.lang.CharSequence

I have built some Java packages for use with ExternalTasks in TeamSite using j2sdk1.4.1_01. Now I would like to use the same classes in front-end stuff. When I try to instantiate these from within a JSP page using the Tomcat that gets installed with TeamSite, I get an error when the packages reference java.lang.Charsequence (used for parsing XML), which was apparently only introduced with 1.4.

What is the best way to get around this? Do I have to install another instance of Tomcat that uses a different Java runtime? Has anyone done this and if so, what are the issues? Or can I change the one that comes with TeamSite to use a different runtime?

Find more posts tagged with

Comments

Migrateduser

I went ahead and replaced IWHOME/tools/java1.3 with a current Java runtime and as far as I can tell everything seems to be working. Obviously I don't have time or even know how to test everything. And if it works, I don't understand why Interwoven would ship without the current Java runtime. Nor do I understand why the version of Perl shipped with TeamSite is so old.

Interwoven?

Adam Stoller

It's called QA and synchronization (or lack thereof) between various different products and their releases.

The matrix for testing all of our products with all of the 3rd party products we interact with on all of the different OS's that we are trying to support ... is quite a large matrix. Therefore, some things like newer versions of Java or Perl or **** (especially if they were released in the middle of our QA cycle) don't get officially tested and therefore don't get shipped with our products.

This doesn't mean it won't work - just that we cannot officially say it does work.

As time permits and new releases of such 3rd party products are considered to have stabilized, and/or are considered to fix major problems , we do try to get them incorporated into our products and our QA testing cycle.

The version of Perl is "old" because up until 5.8 there really wasn't anything significant to pick up and it was considered better to leave it alone and concentrate on other aspects of our products. I *believe* that we will be shipping with 5.8 in the relatively near future, but chances are that when we do it will not be the latestet/greatest/bleeding-edge version, but one or more revisions back - to a version that was considered stable at the time all the testing began.

So it's not that we intentially ship without the current versions of these utilities - it's that we intentially ship with versions that we've had the ability to test with.

--fish
(Interwoven Senior Technical Consultant)

dharrels

I have setup a similar scenario, though not to support External Tasks. We will be using Apache and Tomcat on our production environment and therefore need to develop and test JSP pages within TeamSite. The recommendation from IW support was to install a separate instance of Tomcat (make sure all of the ports it uses don't conflict with the instance that TS uses).

I didn't need to upgrade java as we'll be coding to the same spec, but I would imagine that you could install a copy of 1.4 in a separate dir and tell your 2nd installation of Tomcat to use SDK 1.4. We are also using mod_jk with Apache and it's working great on TeamSite.

-Dan