Advanced search

LIFO | Best Practice collection page

Coming soon

Namespace declaration. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" is missing in received invoices from Access Point

We found strange issue of missing namespace declaration in couple of invoices that we recieved through our access point. Customer is sending invoice to us invoice with namespace(xmlns:xsi) in root tag…

Exception in startap client when connecting to external parties

We have both startap client and startap server. We can send messages successfully from our client to our server. But when we try to send messages from our client to external parties (other startap…

Source code of XKMSResponder

The source code of the XKMS Responder package (https://joinup.ec.europa.eu/software/peppol/release/110) do not compile. The missing classes (in the importexport) seems to be generated by JAXB, but…

Error resolving SMl/SMP DNS resolution : no mapping for dns-translation

Hi, While using SML/SMP, to find correct destination accesspoint, we are getting error: 2012-01-18 16:30:54,489 [main ] INFO Peppol_Src_Ap - Creating MetadataPublisherClient object with following…

Negative testing of message acknowledgement in peppol destination accesspoint

How to produce negative test scenario for Metro reliable messaging's acknowledgement ? Component Miscellaneous Category Support

Class collision between LIME and START on the same JVM

The new START wsdl 2.0 has introduced an issue that is causing a collision with a LIME server on the same JVM (but possibly on .NET implementation too). The class org.w3._2009._02.ws_tra.Resource…

AP not configured to send its own x509 cert back to message exchange initiator.

Current SVN head wsdl for ap seems to specify: <sp:RecipientToken> <wsp:Policy> <sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/…"> <wsp…