Pkg com.sap.aii.proxy.framework.core don't exist even added in the JRE path

Question

Hi All,
I am facing some error while activating the activity. I have checked-in the activity but getting the error while trying to activated the activity. there are two DC's in one of them i am gettign this error. i have not noticed this while check-in.
After checked in - i am not getting the  any such option --Revert activitty or delete activity.
This activity is alreday closed.. what i can do with this activity??  After this error i am not able to activate any activity. I am getting the below error in all the activity.
package com.sap.aii.proxy.framework.core does not exist even though i have added this into the  JRE path in NWDS. Do i need to import the same version file somewhere into J2ee server or somewhere else??
Regards,
Narpal

Answer 1

Hi,
javac ERROR: class file has wrong version 49.0, should be 48.0
This error means that the class file in question is being built with JDK1.5 (49), however it should be built with JDK1.4.2 (48).
In other words, as per the class the build expects a class file built with 1.4.2, but in your track JDK1.5 is configured for the build tool.
You need to therefore :
A.) review the CBS service settings, as most likely the parameters BUILDT_TOOL_JDK_HOME and JDK_HOME_PATHS are set up improperly.
B.) plus the build variant is incorrect in the track in question.
I'll refer below to the corresponding points with the letters A and B.
Some more explanation on the error:
If you check any class file with a hex editor, you'll see at the beginning of it this:
example: CA FE BA BE | 00 00 |00 31  ...
JDK 1.6 = 50 (0x32 hex)
JDK 1.5 = 49 (0x31 hex = (161)*3 + (160)*1 = 49)
JDK 1.4 = 48 (0x30 hex)
JDK 1.3 = 47 (0x2F hex)
JDK 1.2 = 46 (0x2E hex)
JDK 1.1 = 45 (0x2D hex)
On the first 4 bytes there's a magic number (CAFEBABE) which ensures this is a java class file, then on 2-2 bytes you'll see the minor and the major version (in this order). In the above example 00 00 | 00 31. This is what displayed as major.minor i.e. 49.0 what you can see in error messages. See also the attachment I've put to this thread minormajor.JPG.
More information on the class file structure:
http://java.sun.com/docs/books/jvms/second_edition/html/ClassFile.doc.html
For point A)
See the guide for doublechecking the CBS parameters
help.sap.com u2013 CBS Service Properties
http://help.sap.com/saphelp_nw70/helpdata/EN/53/75b3407e73c57fe10000000a1550b0/frameset.htm
Further explanation to the paramters
BUILD_TOOL_JDK_HOME and JDK_HOME_PATHS
BUILD_TOOL_JDK_HOME = <path to highest JDK>
JDK_HOME_PATHS = JDK1.3.1_HOME=<path of jdk131>;JDK1.4.2_HOME=<path of jdk142>;JDK1.5.0_HOME=<path of jdk150>JDK1.6.0_HOME=<path of jdk160>;default=<path of the JDK as default>
Some simple rules with examples:
- for BUILD_TOOL_JDK_HOME you simply enter the path to your JDK, e.g.: /opt/IBMJava2-amd64-142
- for JDK_HOME_PATHS you have to follow the scheme "key=value" e.g.: JDK_1.4.2_HOME=/opt/IBMJava2-amd64-142
- for BUILD_TOOL_JDK_HOME you always specify the highest JDK,
- for JDK_HOME_PATHS you list the available JDKs.
- JRE is not allowed, specify always JDK!
For point B)
Regarding the build variant in your track: check the page 13 for the paramter com.sap.jdk.home_path_key as per the guide :
How To... Setup an NWDI Track for Composition Environment Developments
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7014086d-3fd9-2910-80bd-be3417810c6f
Summary:
A. The first part of the solution is then to doublecheck the CBS service parameters. CBS service must be restarted after changes.
B. The second part is to doublecheck the build variant in the track (see the Build Variants tab on the Track Data tab on the CMS webui  - Landscape Configurator).
I recommend you to have
A) BUILD_TOOL_JDK_HOME = <highest available JDK, I recommend here to set the path to JDK1.5>
JDK_HOME_PATHS = JDK1.4.2_HOME=<path of jdk142>;JDK1.5.0_HOME=<path of jdk150>;default=<path of the JDK as default, set it to the same path as you did for 1.4.2_HOME>
B) set the com.sap.jdk.home_path_key in the build variant to 1.4.2_HOME, or leave it for the default. Do not forget to set this build variant explicitly for >= 7.1 tracks to JDK1.5.0_HOME
I hope this helps.
Best Regards,
Ervin