cancel
Showing results for 
Search instead for 
Did you mean: 

Resource not found: META-INF/services/javax.xml.parsers.DocumentBuilderFactory

Former Member
0 Kudos

Hi All,

We are creating SAP to SFDC Scenario using SOAP channel.

As part of getting the session id, we have used the java mapping as specified in the below blog

https://wiki.scn.sap.com/wiki/display/XI/SFDC+Integration+using+PI+7.1+-+How+to+add+SOAP+Envelope+in...

We have made changes to the credentials and updated our respective channel in our environment. We have referenced the channel in a dummy ICO. We are on PI 7.5 single stack system.

When we use the exported Jar which contains the Java mapping in our PI system, we are getting the below error

However, we are getting below error in operation mapping testing:

  • Resource not found: META-INF/services/javax.xml.transform.TransformerFactory
  • Resource not found: META-INF/services/javax.xml.parsers.DocumentBuilderFactory

We have used NWDS which runs on Java1.8.

Please suggest possible reasons and solution for resolving this issue.

Thanks in advance

Regards,

Ragulan Ravikesavan

Accepted Solutions (0)

Answers (10)

Answers (10)

You could implement SAP-Note 2669221 or direct use the implementation class:

DocumentBuilderFactory factory = new com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl();

Hi All,

Is there any solution to this problem ?

I am also facing the same issue for DocumentBuilderFactory Class not loaded in PO 7.5. After explicitly adding parsers jar also same issue is coming. Please help.

Thanks in advance ..

former_member273615
Discoverer

Hi all,

I'm facing same issue as well.
Can you plese share resolution if you have it?

Thanks,
Paulo

surender_durgam
Explorer

Hi Matthias Fricke,

Did you resolved the error, if yes please let us know how you done. We are also facing same error.

We are in critical position please let us know if anybody find the solution.

Regards

Surender D

former_member277492
Participant
0 Kudos

Hi All,

I am working on a upgrade project from SAP PI7.0 to SAP PO 7.5 single stack system.

I have created File to AS2 Interface, When I use the Java mapping in our PO system getting the below exception as exactly stated above..

However, I am getting below exception in Messge monitoring logs;

Couldn't parse message. Status Code: 500 Message: <?xml version='1.0' encoding='UTF-8'?><error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><code>Internal Server Error</code><message xml:lang="en">while trying to invoke the method java.io.InputStream.read(byte[]) of a null object loaded from local variable 'is'</message></error>parsing issuein operation mapping testing:

Opertional Mapping run exception;

  • Resource not found: META-INF/services/javax.xml.transform.TransformerFactory
  • Resource not found: META-INF/services/javax.xml.parsers.DocumentBuilderFactory
  • com.sap.aii.ib.server.mapping.execution.MappingClassNotFoundException: META-INF/services/javax.xml.parsers.documentbuilderfactory at com.sap.aii.ib.server.mapping.execution.InternalMappingFinder.getInputStream(InternalMappingFinder.java:119)
    at com.sap.aii.ib.server.mapping.execution.InternalMappingFinder.readFile(InternalMappingFinder.java:62)
    at com.sap.aii.ib.server.mapping.execution.MappingLoader.findResources(MappingLoader.java:354)
    at java.lang.ClassLoader.getResources(ClassLoader.java:1246)
    at java.lang.ClassLoader.getResources(ClassLoader.java:1242)
    at java.util.ServiceLoader$LazyIterator.hasNextService(ServiceLoader.java:348)
  • Would really appreciate If anybody could through some light on the same as we are working under tight schedule for making the same Live.

Thanks in advance,

Best Regards,

Sree!!

sapstern
Participant
0 Kudos

Seems to be a dam bug in SAP PO 7.50.

I fiddled around on this problem for ages.

Offical statement from SAP is that with PO 7.3x onwards you can use the standard XML processing tools. (disable xmltoolkit)

I tried to do so in using a plain SAX parser, but it is throwing an exception:

SAXParserFactory theFactory = SAXParserFactory.newInstance();

So, I tried to overcome it in bundling it it with the xerces implmenttion of sax, but still I get an exeption:

Resource not found: META-INF/services/org.apache.xerces.xni.parser.XMLParserConfiguration

Well, I will open an OSS with them beeing fed up...lets see how long that takes to be solved.

Best

Matthias

randrews
Discoverer
0 Kudos

Matthias, did they solve this problem ? Is OSS closed?

0 Kudos

Hi Matthias,

Did you get any solution ?

Thanks.

sapstern
Participant
0 Kudos

Hello,

sorry for late reply, I moved on to another Project, so lost out on this issue.

Best

Matthias

matheusog
Participant
0 Kudos

Hi Ragulan!

Can you please let me know if you have solved this issue.

We are facing same issue, Can you please help?

Former Member
0 Kudos

Hi Ragulan,

Can you please let me know if you have solved this issue.

We are facing same issue, Can you please help

0 Kudos

Hi Ragulan,

I'am facing exactly the same error after upgrading SAP PO to NW7.50 SP5.

Did you already find a solution for this problem?

Best regards,
Joost Weghorst

manoj_khavatkopp
Active Contributor
0 Kudos

Joost,

It's just a warnings and not an error, you will get the exact same output as it was in the older version of PI.

I have tried this while migrating from 7.1 to 7.5.

Br,
Manoj

surender_durgam
Explorer
0 Kudos

Hi Manoj,

Did you resolved the error, if yes please let us know how you done. We are also facing same error.

We are in critical position please let us know if anybody find the solution.

Regards

Surender D

former_member186851
Active Contributor
0 Kudos

Hello,

I think you missed importing the JAR files,Check the below link

https://archive.sap.com/discussions/thread/3942550

Former Member
0 Kudos

Hi Raghuraman,

We also tried to do the same thing as said in the blog mentioned by you. Extract the zip files first and then import the jar files in NWDS. But we are still facing the same error.

We also tried to import the extracted jar files into PI by creating an imported archive, but even this didn't help.

Regards,

Ragulan Ravikesavan

surender_durgam
Explorer
0 Kudos

Hi Ragulan,

We are also facing same error.

We are in critical position please let us know if you find the solution.

Regards

Surender D