[WEB400] WAS4 + WSAD4: helperclasses not found in WebApp = WSAD problem (SOLVED)

[P.Goovaerts@xxxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
STUPID ME!

meta-inf and/or manifest.mf is handled by 'edit module dependencies...' of
webapplication.  While testing app in wsad-was, I probably used this
option to configure classpath for an application which didn't find some
classes.  I actually managed to get the pieces together using following
guidance:
http://www7b.boulder.ibm.com/wsdd/library/techarticles/0206_robinson/robinson.html


"   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
----- Forwarded by Patrick Goovaerts/Clipper Support on 23-10-02 02:50 PM
-----


Patrick Goovaerts
23-10-02 02:11 PM


        To:     web400@midrange.com
        cc:
        bcc:
        Subject:        WAS4 + WSAD4: helperclasses not found in WebApp = WSAD 
problem


After checking out WAS4 (with upgrade to v4.0.3) I decided to go back to
WSAD to find out why 'owntools.jar' was only published in classpath of WA1
and 'jt400.jar' wasn't published in either of 2 WA's.

I found out that
1) WA1 has a META-INF folder with a MANIFEST.MF file.  This file has a
classpath statement with 'owntools.jar' only.
2) WA2 hasn't the folder, nor the file.

I manually edited the MANIFEST.MF file of WA1 (add jt400.jar to classpath)
and copied folder+file to WA2.  Then I republished EA1.  Now both
applications work in WAS4.0.3

Question:
Shouldn't both manifest.mf file be generated/updated by WSAD itself?  I
think that this file should be changed when one changes the 'java build
path' in 'properties' of webapplication.  What could be the reason that
they aren't?


"   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