× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
We are running WSAD v4 with WebSphere v4

I have an EA (EA1) which contains 2 webapps (WA1, WA2).

EA1
I added 2 jarfiles to EA1
- jt400.jar
- owntools.jar

WA1
I added both jar's to the 'Java Build Path' using 'add jars'
I can see both files in it's 'Libraries' tag.

WA2
I added both jar's to the 'Java Build Path' using 'add jars'
I can see both files in it's 'Libraries' tag.
(Did same as WA1)

QUESTION 1
I can't run webapp's in 'buildt-in test server' because it can't find
jt400.jar
When I add jt400.jar to the classpath of the 'buildt-in test server', both
applications work.
why is this needed?  owntools.jar seems to be found....

QUESTION 2
After exporting EA1 to local Win2000 WebSphere, both applications didn't
work.
I added jt400.jar to the WebSphere's classpath
WA1 worked, WA2 not!
I loaded EA1 into AAT to check both WA-configurations
WA1 has 'owntools.jar' in it's classpath, WA2 hasn't!
I added owntools.jar to the classpath of WA2 and saved EA1
WA2 worked
==> Why isn't owntools.jar in WA2's classpath ???
==> Why isn't jt400.jar in both classpath's ???


"   I don't have problems, only challenges...  "

Patrick Goovaerts
WebMaster
Clipper Support nv
TEL : 0032 (0)3 5453991
GSM: 0498 610 325
WEB: www.conti7.be


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.