token-profile | Blockchain coin and token profile collection | Cryptocurrency library

I am posting this here so anyone else looking for an answer will have it. I found the answer with some Googling, a link from a colleague, and trial and error. I was able to replicate the example using two JavaScript code files. I combined them into one below for ease.

In the end the reply provided here by Dhaval Kateliya was the way to go. I add here my version of the method.

We can't change the Java version in runtime. Hence, we have to build a new image with the required Java version. You can either use the existing Dockerfile and modify it to build an image from the scratch or you can build a new image on top of the wso2/wso2mi and change the Java version in it.

For reference, here is the Dockerfile used to build the wso2/wso2mi images.

Given below is a sample Dockerfile and the steps used to build the image with Java 8 locally

• Update the existing CentOS Dockerfile with Java 8 base image

Perhaps the $xmlRequest variable is not being set properly because it's a multiline string.

Instead of

Core does not support Wshttpbinding, wcf only supports BasicHttpBinding, CustomBinding, NetHttpBinding, NetTcpBinding：

I suggest you continue to use the .net framework or modify the server-side binding.

For more information about WCF Features in core, you can refer to this link.

Based on the error message I assume the web service you have there isn't fully WSI compliant. See http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html, rule R2209:

A wsdl:binding in a DESCRIPTION SHOULD bind every wsdl:part of a wsdl:message in the wsdl:portType to which it refers to one of soapbind:body, soapbind:header, soapbind:fault or soapbind:headerfault.

The web service runs and you can call it with any client that can send it the expected SOAP message, it's just that the service doesn't respect interoperability specifications.

It's been a while since I troubleshooted WSDLs for interoperability, but I think you need to add a to and in your s.

If you don't control the web service then that's not something you can do. You might try to run WSDLToJava without the -validate flag to see if it generates the code.

I changed a few things and it started working. Firstly the AsymmetricSecurityBindingElement;

• Set EnableUnsecuredResponse to false.
• Added SecurityHeaderLayout that defaults to "Strict" and set it to "SecurityHeaderLayout.LaxTimestampLast".

Then, I added a custom MessageEncodingBindingElement that implements a custom MessageEncoder. This encoder adds the To and MessageID headers although I do not think this was the problem.

It‘s a SOAP version mismatch, server expects version 1.2 but client is sending 1.1 (I am confused about SOAP namespaces). You need to implement (here: construct request based on) wsdl from server and make sure to use version 1.2

If you follow the XSD schema for the wsu namespace, you will see it points to http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd

No luck though in getting a description of the value. However, if you look for the specification document you find https://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf

This documents describes the wsu namespace and also mentions:

This specification defines and illustrates time references in terms of the xsd:dateTime type defined in XML Schema. It is RECOMMENDED that all time references use this type.

So it's the standard dateTime type from the XML Schema. The fractional seconds by the way are optional, so I'm not sure why you get an error because of it. Are you sure it's not a red herring?