wael aoudi
|
| Posted: 04/18/2004, 4:13 AM |
|
I had a problem setting the classpath for the JDK at first. I had it pointing to a jdk1.4.2 and that wouldnt find the javac but it allowed for the servlet api and ant to work.. I had to download jdk1.3 and tried that and it worked , but it wouldnt build the servlet api nor the ant . For the ant i have it pointing to the ant.bat file. (ant bin folder-which worked before jdk1.3) and servlet api I have it classpathed in the properites page pointing to servlet.jar file. Allof these files and paths refer to different location on my development machine.. does that effect it plus i am using Tomcat 5.0. Please advise,. I have spent many hours on this and I am very frustrated. FYI I have a Mysql database connected and i like the concept or theory behind this software (runnning trial version)and asoon as i have it working i will definately consider buying the license.
|
|
|
 |
peterr
Posts: 5971
|
| Posted: 04/18/2004, 2:06 PM |
|
AFAIK we are working on the support for Tomcat 5 while current CCS supports Tomcat 4. You can request temporary patch for Tomcat 5 via our support at http://support.codecharge.com.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
 |
|
dekacode
Posts: 53
|
| Posted: 05/21/2004, 6:02 PM |
|
Peter,
Env: WinXP Tomcat 5, JVM 1.4.2
Does this temporary patch for Tomcat fix the following error?
"bad class file: C:\Program Files\Java\j2re1.4.2_04\lib\rt.jar(java/lang/Object.class)
class file has wrong version 48.0, should be 47.0"
|
|
|
|
peterr
Posts: 5971
|
| Posted: 05/23/2004, 4:03 PM |
|
No, the patch only changes the format for TLD descriptors from format 1.1 to 1.2.
We're not aware of any other problems with Tomcat 5.
The above message doesn't look like it's related to TLD format although I'm not sure.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
ignat
Posts: 55
|
| Posted: 05/24/2004, 12:47 AM |
|
This error occurs when you have an old or conflicting jar in your CLASSPATH. The solution is to clean up your classpath.
Regards,
Ignat.
|
|
|
|
