|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] 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
As an Amazon Associate we earn from qualifying purchases.
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.