Incompatible class versions :linkage error- JAVADOM

HI,
   We have done Mapping using java DOm,created ZIp file & successfully imported in IR.  
My NWDS is using java 1.4.2_15
we are using PI70/Sp09/Java Version 1.5.0_14
During Execution in IE we  are getting this error.
error -
<SAP:Code area="MAPPING">LINKAGE_ERROR</SAP:Code>
<SAP:Stack>Incompatible class versions (linkage error)</SAP:Stack>
<Trace level="1" type="T">Interface Mapping http://XI/Mapping/JavaDom/DOMMapping4 IM_ORDER1_ORDER</Trace>
  <Trace level="1" type="T">LinkageError at JavaMapping.load(): Could not load class: CSJAVA/com/yash/xi/DOMMapping4</Trace>
  <Trace level="1" type="T">java.lang.NoClassDefFoundError: JAVA/com/xi/DOMMapping4 (wrong name: com//xi/DOMMapping4) at java.lang.ClassLoader.defineClass0
Regards
shekar chandra

Hi,
Check the links they may help u out.
Event or DOM parsing?
http://discuss.joelonsoftware.com/default.asp?design.4.156750.12
XML Parsers: DOM and SAX Put to the Test
http://www.devx.com/xml/Article/16922/1954?pf=true
Regards,
Phani

Similar Messages

  • Java mapping - Linkage Error

    Hello,
    We are on PI 7.0 SP10.
    Currently we are migrating the XI servers from Solaris to AIX IBM.
    When I try to run Java mapping, I get following error:
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">LINKAGE_ERROR</SAP:Code>
      <SAP:P1>sapmarkets/marketconnect/xcbl/r3/OrderMapping</SAP:P1>
      <SAP:P2>http://xi/SRM/ReceivePurchaseOrders</SAP:P2>
      <SAP:P3>22150771-0ee7-11dc-c87a-fe330a306909</SAP:P3>
      <SAP:P4>-1</SAP:P4>
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Incompatible class versions (linkage error)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Please help.
    Thanks in advance.
    Beena.
    Edited by: Beena Thekdi on Jan 22, 2008 8:05 PM

    Thanks Raj.
    But this note says
    >> The error is corrected with Support Package 5 for Support Package 03 for the XI TOOLS 3.0 software component.
    and I am already on PI 7.0.
    Please tell me still I need to apply this?
    Thanks,
    Beena.

  • Class Version Mismatch

    In respect to class loaders and JREs, what are some of the scenarios that could result in class version mismatch errors at runtime?
    I am assuming it will have to do with .class file's version stamp being different in different class loaders within the same JVM....can someone please shed some light on this. Thanks!

    Actually I think it would only happen if you're using a class that was compiled on a sufficiently newer compiler than the JVM you're running it on. As long as the JVM can handle all classes it's been given, I don't think the classes can mismatch among themselves.
    But check the language spec or the JVM spec to be sure.

  • Java Mapping - Class versions are incompatible (linkage error)

    Hi Friends,
        While testing java mapping in Integration Repository i am getting an error - "Class versions are incompatible (linkage error)". Can anyone plz tell what might be the reason.
    Regards,
    Gowtham Kuchipudi.

    hello
    I have this message but my trace look like this:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <Trace level="1" type="B" name="interface activity determination">
      <Trace level="1" type="T">Version 000</Trace>
      <Trace level="1" type="T">Message status 000</Trace>
      <Trace level="1" type="T">Interface action INIT</Trace>
      <Trace level="1" type="T">(must be INIT for a new determination)</Trace>
      <Trace level="1" type="T">Message type BEST EFFORT. -> No determination</Trace>
      <Trace level="1" type="T">Set interface action INIT into *MAST*</Trace>
      </Trace>
      <Trace level="1" type="E">CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV">
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Interface Mapping http://Migdal.co.il/CRM/SAP-CRM/ProposalDeatailsService ProposalDeatailsService_WS2RFC_IM</Trace>
      <Trace level="1" type="T">LinkageError at JavaMapping.load(): Could not load class: xmlpayload</Trace>
      <Trace level="1" type="T">java.lang.UnsupportedClassVersionError: xmlpayload (Unsupported major.minor version 49.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:539) at java.lang.ClassLoader.defineClass(ClassLoader.java:448) at com.sap.aii.ibrun.server.mapping.MappingLoader.findClass(MappingLoader.java:158) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at com.sap.aii.ibrun.server.mapping.JavaMapping.load(JavaMapping.java:95) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:45) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy158.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor428.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:107) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</Trace>
      <Trace level="1" type="T">Linkage error occurred when loading class xmlpayload (http://Migdal.co.il/CRM/SAP-CRM/ProposalDeatailsService, d7e31f30-53be-11dc-8fbd-ee09c0a8664d, -1)</Trace>
      <Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Linkage error occurred when loading class xmlpayload (http://Migdal.co.il/CRM/SAP-CRM/ProposalDeatailsService, d7e31f30-53be-11dc-8fbd-ee09c0a8664d, -1) at com.sap.aii.ibrun.server.mapping.JavaMapping.load(JavaMapping.java:115) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:45) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy158.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor428.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:107) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: java.lang.UnsupportedClassVersionError: xmlpayload (Unsupported major.minor version 49.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:539) at java.lang.ClassLoader.defineClass(ClassLoader.java:448) at com.sap.aii.ibrun.server.mapping.MappingLoader.findClass(MappingLoader.java:158) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at com.sap.aii.ibrun.server.mapping.JavaMapping.load(JavaMapping.java:95) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:45) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy158.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor428.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:107) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</Trace>
      <Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
    the error that I recieve in the SXMB is:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">LINKAGE_ERROR</SAP:Code>
      <SAP:P1>xmlpayload</SAP:P1>
      <SAP:P2>http://Migdal.co.il/CRM/SAP-CRM/ProposalDeatailsS~</SAP:P2>
      <SAP:P3>d7e31f30-53be-11dc-8fbd-ee09c0a8664d</SAP:P3>
      <SAP:P4>-1</SAP:P4>
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Class versions are incompatible (linkage error)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    this is my XI information
    Runtime Environment
    Java version:1.4.2_12
    Java vendor:Sun Microsystems Inc.
    Version
    Service pack:21
    Release:30_VAL_REL
    Latest change:409678
    Sync time:200709211024
    since I already have the SP required by the note, any other suggestions?
    Thanks
    Kfir

  • XI Mapping: Class versions are incompatible (linkage error)

    Hi,
    i have a simple File-to-File scenario, and I am getting the following error as observed in the XI Monitor:
    <SAP:Category>Application</SAP:Category>
    <SAP:Code area="MAPPING">LINKAGE_ERROR</SAP:Code>
    <SAP:Stack>Class versions are incompatible (linkage error)</SAP:Stack>
    To troubleshoot the mapping, I have removed all mappings, and put the target nodes to constant values. I am still getting the error in Mapping (linkage error).
    I am using XI3.0SP0 (J2EE SP07, ABAP SP3). Is this a known problem / OSS notes available ? thanks.
    Regards,
    Manish Agarwal.

    Hallo Agarwal,
    have a look in OSS Message #755302
    Regards Franz Forsthofer

  • Class versions are incompatible (linkage error)

    Hi All,
    I New to SAP XI and i've been working on java mapping, i Used RAD 6.0 for generation of class files, i imported the generated files into Integration builder.
    but when i execute the scenario i'm getting this error
    "Class versions are incompatible (linkage error)"
    in message monitoring with a red flag..
    can anyone explain me why i'm getting this error....
    Thanks & Regards,
    Sai Kumar Madduri

    Hi,
    Our PI Details:
    Runtime Environment
    Java version: 1.5.0_14
    Java vendor:Sun Microsystems Inc.
    Version
    Service  pack:09
    Release: 645_VAL_REL
    NWDS IDE: 1.5.0_14
    XI
    Software component details
    XI TOOLS 3.0
       Support Package 11 of SAP_XITOOL, 3.0 SP011 011
    XI TOOLS 7.0
       No Entry for Support Packages.
    Request to advise what is the best option for my JAVA Dom program to run
    regards
    shekar Chandra

  • JAVAMAP-Sax Parser ...............Linkage error when loading the class.

    Dear all,
    Do we have any extra things to execute the Java mapping using the Sax Parser?
    When I am executing the interface mapping ,I am getting the" Linkage error when loading the class" error.
    Kindly let me know your personnel maildId so that I can mail you the screen shots.
    Thanks,
    Srinivasa

    Dear sunil,
    Find the File.
    Source:
    <MTO_FTP_MAT_DETAILS>
    <MATDETAILS>
    <MAKTX>
    <MATNR>
    <WERKS>
    <LABST>
    <MEINS>
    <PERCNT>
    TARGET
    MTI_FTP_MAT_DETAILS
    <MATDETAILS>
    <MAKTX>
    <MATNR>
    <WERKS>
    <LABST>
    <MEINS>
    <PERCNT>
    Source:
    <MTO_FTP_MAT_DETAILS>
    <MATDETAILS>
    <MAKTX>
    <MATNR>
    <WERKS>
    <LABST>
    <MEINS>
    <PERCNT>
    TARGET
    MTI_FTP_MAT_DETAILS
    <MATDETAILS>
    <MAKTX>
    <MATNR>
    <WERKS>
    <LABST>
    <MEINS>
    <PERCNT>
    import java.io.IOException;
    import java.io.InputStream;
    import java.io.OutputStream;
    import java.util.Map;
    import javax.xml.parsers.SAXParser;
    import javax.xml.parsers.SAXParserFactory;
    import org.xml.sax.Attributes;
    import org.xml.sax.SAXException;
    import org.xml.sax.helpers.DefaultHandler;
    import com.sap.aii.mapping.api.StreamTransformation;
    class Echo {
    public static OutputStream out;
    public class myEcho extends DefaultHandler implements StreamTransformation {
    private Map map;
    public void setParameter(Map param) {
    map = param;
    public void execute(InputStream in, OutputStream out) {
    DefaultHandler handler = this;
    SAXParserFactory factory = SAXParserFactory.newInstance();
    try {
    SAXParser saxParser = factory.newSAXParser();
    Echo.out = out;
    saxParser.parse(in, handler);
    } catch (Throwable t) {
    t.printStackTrace();
    public void startDocument() throws SAXException {
    try {
    Echo.out.write("<?xml version='1.0' encoding='UTF-8'?>".getBytes());
    } catch (IOException e) {
    e.notify();
    public void endDocument() throws SAXException {
    try {
    Echo.out.flush();
    } catch (IOException e) {
    throw new SAXException("I/O error", e);
    public void startElement(String namespaceURI, String sName, // simple name
    String qName, // qualified name
    Attributes attrs) throws SAXException {
    String eName = sName; // element name
    if ("".equals(eName))
    eName = qName; // not namespace-aware
    if ("ns0:MTO_SAP_MAT_DETAILS".equals(qName)) {
    try {
    Echo.out.write(("<MTI_FTP_MAT_DETAILS>").getBytes());
    } catch (Exception e) {
    e.printStackTrace();
    } else {
    try {
    Echo.out.write(("<" + qName + ">").getBytes());
    } catch (Exception e) {
    e.printStackTrace();
    public void endElement(String namespaceURI, String sName, // simple name
    String qName // qualified name
    ) throws SAXException {
    String eName = sName; // element name
    if ("".equals(eName))
    eName = qName; // not namespace-aware
    if ("ns0:MTO_SAP_MAT_DETAILS".equals(qName)) {
    try {
    Echo.out.write(("</MTI_FTP_MAT_DETAILS>").getBytes());
    } catch (Exception e) {
    e.printStackTrace();
    } else {
    try {
    Echo.out.write(("</" + qName + ">").getBytes());
    } catch (Exception e) {
    e.printStackTrace();
    public void characters(char buf[], int offset, int len)
    throws SAXException {
    String s = new String(buf, offset, len);
    try {
    Echo.out.write(s.getBytes());
    } catch (Exception e) {
    e.printStackTrace();

  • Linkage error occurred when loading class MyClass

    Hi
    I have written one simple class name MyClass and i have created jar file and i imported into import archive... but in interface mapping while i am testing i am getting the <b>"<b>Linkage error occurred when loading class MyClass"</b></b> error.... why i am getting this error
    Thanks & Regards
    Ravi Shankar B

    Here it goes:
    Symptom
    The LINKAGE_ERROR error occurs during the mapping.
    The trace contains "java.lang.NoClassDefFoundError: Illegal name":
    Other terms
    XI 30, Mapping, Linkage Error
    Reason and Prerequisites
    As of the jdk 1.4.2_05 from Sun, this program error occurs during the mapping in the runtime or during testing in the Repository. This error may also occur in conjunction with jdks of other vendors or other versions.
    Solution
    The error is corrected with Support Package 5 for Support Package 03 for the XI TOOLS 3.0 software component.
    Import the corresponding archive SAPXITOOL03P_5.SCA for SAP Exchange Infrastructure XI 3.0 as described in the Netweaver 04 Support Package Stac Guide.
    You will find the archive and the guide in the SAP Service Marketplace under the alias "SP stacks -> SAP NetWeaver -> SAP NetWeaver 04".
    Regards
    Vijaya

  • Incompatible Xalan version in IDE class path?  (Max OS X Leopard)

    Hi all,
    I have been using NetBeans 6.1 for a while and all was well. I then installed a few plug-ins (including iReport, which I believe may be the problem). When I start the IDE I get the error "Incompatible Xalan version found in IDE class phat" and gives some link that didn't help. I have uninstalled NetBeans and reinstalled, which obviously didn't fix the problem. If anybody can help me at all, I would appreciate it very much. I really need this to run, I would hate to completely reinstall the OS to get it back going. Thanks in advance for any support.
    Edited by: JavaChip on Jul 7, 2008 4:32 PM

    Hi,
    I encountered this problem today and I'm also using Netbeans 6.1 on Mac OS X (10.5.4). It was definitely the iReports plugin. I found a solution here:
    [http://blogs.sun.com/geertjan/entry/analyzing_the_jasperreports_visual_designer]
    However, I only had to remove the file xalan.jar (and keep xalan-2.7.0.jar) from the ~/.netbeans/6.1/modules/ext directory. No changes to the config were required and the iReport plugin worked.
    Edited by: d_herb on Aug 5, 2008 7:45 AM

  • LINKAGE ERROR in Java Mapping

    Hi Friends,
    I am getting LINKAGE ERROR when executing JAVA mapping as its not able to reference AbstractTransform class provided by SAP PI API.
    This problem occurs in particular environment for this particular mapping. For other environments this is working fine.
    I assume it has something to do with Java Library reference which is mis-configured during transport. Can anyone let me know how and where the library path is configured for Imported Achieves in SAP PI 7.1.
    We are using java 1.5 for building and creating java achieves.
    Many thanks,
    SK

    Hi Sumant,
      This error occurs when the jdk version of XI server and the library version you used to develop the mapping are incompatible. Make sure you use the same version as of the server
    have a look in SAP Note 755302
    Regds,
    Pinangshuk.

  • How to avoid Linkage Error in JAVA Mapping

    Dear Experts,
    I am trying to test the JAVA mapping compiled in NWDS but receiving the error
    "LinkageError at JavaMapping.load(): Could not load class".
    java.lang.NoClassDefFoundError: JSONXMLProject/bin/com/sap/json/ConvJson2Xml (wrong name: com/sap/json/ConvJson2Xml)
    at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:735)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:716) at java.lang.ClassLoader.defineClass(ClassLoader.java:537)
    at com.sap.aii.ib.server.mapping.execution.MappingLoader.findClass(MappingLoader.java:195)
    Following are the details:
    SAP PO 7.4
    SP Stack Number 05
    JDK Version jdk16
    NWDS
    SAP Enhancement Package 1 for SAP NetWeaver Developer Studio 7.3 SP10 PAT0000
    1.Created the Project , Package and then class (Included the logic)
    2. Included 1 JSON Jar file into my project and the Added to build path.
    3.Exported the project as Archive File and saved in desktop
    4.Imported into SAP PO system as Imported Archive
    5.Could not observe the JSON jar file which i used as referenced JAR in NWDS
    6.Tested in OM after referencing the JAVA class and found the above error.
    I have JDK 5, 6 and 7 present in my local desktop and I am trying to export the compiled code using both JAVA SE 1.6 and 1.5 in NWDS seperatly after going several discussions.
    Can any one hep me with the screenshots and tell me how to include all the reference jar files in exported project..
    Regards..

    Dear Anand,
    I did exactly as you shared. As the JSON jar has number of classes, then in OM all the Classes had to be assigned. Then the linkage error went.
    But in execution , it shows a new error that all the classes of the JSON jar has to be implemented with interface StremTransformation or AbstractTransformation.
    I assume in the Operation Mapping I will use only 1 class as JAVA Class. Anyway I am attaching the document with navigation.
    Do we have any other alternative??
    Please rename the extension of the document by remove .txt
    Regards

  • Linkage Error while setting up webApp

              Hi,
              In my webApp I bumped into following Exception while running JSPs which queries
              database.
              Platform : Windows NT 4, webLogic 5.1 with SP 8.
              Action : WLSServer crashes with Dr. Watson application error.
              I am using a custom Connect.java class ( through javax.sql.DataSource, as recommended
              by WLS 5.1 docs ) to connect to Oracle database using JDBC thin client. If I do
              not use webApp architecture then the same class works good to connect to DB.
              Also, if I maintain identical class hierachy into my weblogic.class.path classpath
              settings I do not get this exception and everything works fine.
              I read into this search group messages about Linkage problems caused because of
              having duplicate classes available to the server at runtime and so I ensured that
              I do not keep classpaths which can cause duplicate classes into runtime environment
              of wlsserver but still the same problem persists.
              any help is appreciated,
              thanks,
              - Rajesh.
              Mon Apr 02 16:19:11 PDT 2001:<I> <WebAppServletContext-eTools> Generated java
              file: c:\project\etools\WEB-INF\_tmp_war_eTools\jsp_servlet\_jsp\_xyz.java
              Mon Apr 02 16:19:13 PDT 2001:<E> <WebAppServletContext-eTools> Servlet failed
              with Exception
              java.lang.LinkageError: Class java/sql/Connection violates loader constraints
              at weblogic.jdbc20.common.internal.RmiDataSource.getConnection(RmiDataSource.java:53)
              at weblogic.jdbc20.common.internal.RmiDataSource_ServiceStub.getConnection(RmiDataSource_ServiceStub.java,
              Compiled Code)
              at com.bea.etools.common.Connect.getConnection(Connect.java:51)
              at jsp_servlet._jsp._xyz._jspService(_xyz.java, Compiled Code)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
              at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
              at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
              at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
              

    Hi again
              Plase check you JAVA_CLASSPATH and WEBLOGIC_CLASSPATH variables
              make sure the paths. May be, the script that you use, define the class in
              the incorrect path
              Rajesh <[email protected]> escribió en el mensaje de noticias
              [email protected]...
              >
              > Hi,
              > The problem is solved.
              > I have 4.5.2 and 5.1 versions of webLogic installed on my machine
              > and in my system classpath I had
              > c:\weblogic452\classes\boot;c:\weblogic510\boot which caused this problem
              > I removed c:\weblogic452\classes\boot from the above classpath and it
              works.
              >
              > I tried to tweak through the above weblogic classes dirs and I did not
              find anything
              > similar to below classes for which the I got Linkage error.
              >
              > question is why would weblogic look for
              weblogic.jdbc20.common.internal.RmiDataSource.getConnection
              > ( (this class resides in c:\weblogic452\classes dir and not in
              c:\weblogic452\classes\boot
              > which is there in system classpath)of /weblogic452 directory when I am not
              even
              > booting up 4.5.2 instance of the server.
              >
              > >java.lang.LinkageError: Class java/sql/Connection violates loader
              constraints
              > > at
              >weblogic.jdbc20.common.internal.RmiDataSource.getConnection(RmiDataSource.j
              ava:53)
              >
              >
              > "Rajesh" <[email protected]> wrote:
              > >
              > >Hi,
              > >
              > >In my webApp I bumped into following Exception while running JSPs which
              > >queries
              > >database.
              > >
              > >Platform : Windows NT 4, webLogic 5.1 with SP 8.
              > >Action : WLSServer crashes with Dr. Watson application error.
              > >
              > >I am using a custom Connect.java class ( through javax.sql.DataSource,
              > >as recommended
              > >by WLS 5.1 docs ) to connect to Oracle database using JDBC thin client.
              > >If I do
              > >not use webApp architecture then the same class works good to connect
              > >to DB.
              > >
              > >Also, if I maintain identical class hierachy into my weblogic.class.path
              > >classpath
              > >settings I do not get this exception and everything works fine.
              > >
              > >I read into this search group messages about Linkage problems caused
              > >because of
              > >having duplicate classes available to the server at runtime and so I
              > >ensured that
              > >I do not keep classpaths which can cause duplicate classes into runtime
              > >environment
              > >of wlsserver but still the same problem persists.
              > >
              > >any help is appreciated,
              > >
              > >thanks,
              > >
              > >- Rajesh.
              > >
              > >------------------
              > >
              > >Mon Apr 02 16:19:11 PDT 2001:<I> <WebAppServletContext-eTools> Generated
              > >java
              > >file:
              c:\project\etools\WEB-INF\_tmp_war_eTools\jsp_servlet\_jsp\_xyz.java
              > >Mon Apr 02 16:19:13 PDT 2001:<E> <WebAppServletContext-eTools> Servlet
              > >failed
              > >with Exception
              > >java.lang.LinkageError: Class java/sql/Connection violates loader
              constraints
              > > at
              weblogic.jdbc20.common.internal.RmiDataSource.getConnection(RmiDataSource.ja
              va:53)
              > > at
              weblogic.jdbc20.common.internal.RmiDataSource_ServiceStub.getConnection(RmiD
              ataSource_ServiceStub.java,
              > >Compiled Code)
              > > at com.bea.etools.common.Connect.getConnection(Connect.java:51)
              > > at jsp_servlet._jsp._xyz._jspService(_xyz.java, Compiled Code)
              > > at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              > > at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :106)
              > > at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              l.java:907)
              > > at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              l.java:851)
              > > at
              weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
              Manager.java:252)
              > > at
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
              > > at
              weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
              > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
              > >Code)
              >
              

  • Class Not Registered error upon using MS Office Report

    Hello,
    Using LabVIEW 2010, I've just installed the Microsoft RGT trial from NI, along with the Office 2010 trial from Microsoft. Upon trying to drag the MS Office Report VI to my block diagram, the configuration dialog appears but immediately an error dialog shows up over top, with a Class Not Registered error. Attached is the screenshot. If I close the error and try to configure the VI for a basic Excel report, I get a file-not-found error in reference to the Excel template, which I have verified is indeed at the target path and opens with my version of Excel just fine. Any ideas how to get past this error?
    Attachments:
    error.JPG ‏42 KB

    Hello,
    It sounds like you have to reinstall the RGT. Have a look at this documentation.
    http://digital.ni.com/public.nsf/allkb/B7F980D169474D568625760E0055D55E
    Eric
    Eric Liauw
    AE Specialist - Automated Test | CLD | CTD
    National Instruments

  • Linkage error while doing java mapping

    Hi,
    I Have written a java mapping but when i use it in xi.It is showing an error as linkage error
    LinkageError at JavaMapping.load(): Could not load class: com/satyam/nestle/JavaMap
    Can anyone explain what does this mean and how to overcome it.
    Thanks in advance,
    Bhargav

    Did you try testing the java mapping seperately....that it does not have any errors??? Also check the cahce update. Sometimes it happens that XI is not able to load the class file from the cache. Perform a CPA cache refresh (delta). This should solve the problem
    Reward if helpful.

  • Class not found error afer loading classes to oracle

    hi i have loaded quite a few jars into oralce 11g databse
    created a java stored function
    and executed it
    some times it works... and hits the java front end environment... we are hitting a servlet.. and recording some output statements .. in the function
    but sometimes it throws class not found error
    any idea why its working sometimes and not some othr times?
    Also when i load the jars.. the classes are loaded but when i see the name of the classes using
    select * from user_objects where object_type like 'J%'
    then i see some additional characters prefixxed the class names ... is that causing the problem?
    something like this
    /1a248e6f_GetMethod
    Edited by: learning_man on Mar 11, 2010 1:27 PM

    Learning_man,
    Obviously you need to learn how to ask a question.
    There is nothing in your post other than 'It doesn't work. Why? Help"
    without any specific example. Also you still fail to include a 4 digit version!!!
    It is also the third or the fourth time you asked this very same question.
    Can you learn how to ask a question please? And stop repeating the question when you don't get a response?
    And no, the extra characters are not the problem.
    An incorrect CLASSPATH probably is.
    Sybrand Bakker
    Senior Oracle DBA

Maybe you are looking for