B2B Connection via ebXML

[Former Member]

I'm hoping someone here could shed a bit of light on my situation.

We are currently attempting a new B2B connection with a partner who is using the Seeburger adapter.

When they receive our message, their parser is returning an error.

It appears it is having problems finding the payload attachment...

What I'm curious about - does the Seeburger adapter require the eb:id attribute? As this is optional in the ebXML 2.0 spec.

The required xlink attribute is there and it is valid.

We are connected with other partners with no issues, so this has me at a loss...

Error while parsing ebXML message: java.lang.NullPointerException: while trying to invoke the method java.lang.String.equals(java.lang.Object)

of an object returned from com.seeburger.ebxml.message.descriptions.PayloadDetails.getId() Caused by: java.lang.NullPointerException: while trying to invoke the

method java.lang.String.equals(java.lang.Object) of an object returned from com.seeburger.ebxml.message.descriptions.PayloadDetails.getId()

            at com.seeburger.ebxml.message.result.EbXMLDecomposerResult.getPayloadsAsHashtable(EbXMLDecomposerResult.java:1256)

            at com.seeburger.ebxml.message.tasks.EbXMLMessageDecomposer.extractAttachments(EbXMLMessageDecomposer.java:1104)

            at com.seeburger.ebxml.message.tasks.EbXMLMessageDecomposer.parse(EbXMLMessageDecomposer.java:525)

            at com.seeburger.ebxml.message.tasks.EbXMLMessageDecomposer.parse(EbXMLMessageDecomposer.java:187)

            at com.seeburger.ebxml.message.tasks.EbXMLMessageDecomposer.parse(EbXMLMessageDecomposer.java:157)

            at com.seeburger.ebxml.http.impl.EbXMLSHCInitiatorImpl.parseEbXMLMessage(EbXMLSHCInitiatorImpl.java:1592)

            at com.seeburger.ebxml.http.impl.EbXMLSHCInitiatorImpl.asyncParsing(EbXMLSHCInitiatorImpl.java:476)

            at com.seeburger.ebxml.http.impl.EbXMLSHCInitiatorImpl.receivedMessage(EbXMLSHCInitiatorImpl.java:381)

            at com.seeburger.ebxml.http.impl.EbXMLSHCInitiatorImpl.doWork(EbXMLSHCInitiatorImpl.java:277)

            at com.seeburger.ebxml.http.impl.EbXMLSHCInitiatorImpl.preInitiation(EbXMLSHCInitiatorImpl.java:181)

            at com.seeburger.http.core.SHCTaskInitiator.doInitiation(SHCTaskInitiator.java:151)

            at com.seeburger.http.core.SHCTaskInitiator.run(SHCTaskInitiator.java:122)

            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:182)

            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:280)

[benjamin_bichler · Accepted solution]

Hi Richard.

Yes, there are old versions of the SEEBURGER EbXML adapter (versions created before 2011-08-15) out there in which this phenomenon occurs if the optional eb:id is missing.

I suppose your partner has a support contract with SEEBURGER?

If so, he should contact SEEBURGER support and check with them whether he is in fact using such an old version and whether there is a newer release version or hotfix available for him which improves this behaviour.

Regards

Benjamin

[Former Member · Accepted solution]

I'm sure they have support, but there has been a lot of push back on me to 'fix' the messages on my side.

I will ask for more information from the partner.

I sincerely appreciate that information Benjamin.

Thanks a ton!