Adding external jars to content center webapp

Hello All,

We are trying to add some custom JARS to content-center.

When we rebuild cc using make_toolkit.ipl our jars are copied to

iw-home/httpd/webapps/content_center/WEB-INF/lib

but we get class not found exceptions.

Deploying the same application on a local Tomcat instance works fine.

has anyone had any similar experiences or found a resolution to this?

Many Thanks.

Find more posts tagged with

Comments

Valentine

- Is it new classes, is it possible that they conflict with the existing ones?

- Have you tried cleaning up tomcast's "work" directory? (iw-home/servletd/work)

chicka

Hello All,

We are trying to add some custom JARS to content-center.

When we rebuild cc using make_toolkit.ipl our jars are copied to

iw-home/httpd/webapps/content_center/WEB-INF/lib

but we get class not found exceptions.

Deploying the same application on a local Tomcat instance works fine.

has anyone had any similar experiences or found a resolution to this?

Many Thanks.

I beleive you need to place the JARs in customer_src/lib folder and rebuild the UI.
Please have a check on the same.

dazzlad

I beleive you need to place the JARs in customer_src/lib folder and rebuild the UI.
Please have a check on the same.

Errr.... from my original post

When we rebuild cc using make_toolkit.ipl our jars are copied to

iw-home/httpd/webapps/content_center/WEB-INF/lib

dazzlad

The issue seems to be specific to cssdksoap.jar

I have added our own jars and they work fine.

cssdksoap.jar deploys correctly when make_toolkit.ipl is called, but I am still getting these class not found exceptions for the CSSoapFactory.....

Any ideas?

Migrateduser

The issue seems to be specific to cssdksoap.jar

I have added our own jars and they work fine.

cssdksoap.jar deploys correctly when make_toolkit.ipl is called, but I am still getting these class not found exceptions for the CSSoapFactory.....

Any ideas?

The cssdk*.jars should already be present within teamsite web app. So you should not copy this in customer_src\lib folder. The way we got around this was to include a new classpath element in the TeamSite\local\config\lib\content_center\reference\build.xml file
E.g.
< pathelement path="${iw-home}/cssdk/cssdkiface.jar" / >