The WSDLS are bundled with the jar. We intended this to be the ONLY way
the wsdls were accessed, and made lots of changes to the wsdls accordingly,
so that they referenced other wsdls via the "file system". The wsdls are
the fixed up ones that are used to build the java stubs locally, plus a
Well i am not sure how they solved it - I will share a tested solution in Jira
and everyone can check. Maybe their wsdl is accessible through http?
What works is doing call through https, but thee fetching of WSDL did not - as
this is through another mechanism.
I don’t think that the open
I should say that we have (AFAICT) at least two independent installations
of the csws connector working in the field, at least one of them using
secure connections.
Karl
On Thu, Jan 16, 2020 at 6:54 AM Karl Wright wrote:
> We solved the WSDL fetching through HTTPS, or thought we had, by
>
We solved the WSDL fetching through HTTPS, or thought we had, by
restructuring the code according to a number of articles we found. This
was supposedly tested and worked in one installation. Nobody has ever
reported issues with the wsdls being fetched however; I worry that you may
have a
Ok i fixed the source to fetch WSDL from https (it is not perfect yet as it
does not use the truststore yet but this I can fix) - I will share later in a
Jira.
It is however now unable to locate the imported document /Authentication?xsd=2
relative to Authenticaton?wsdl#types1
I will look into
Coming back to the original topic. I believe SSL was never fully solved from
what i read in the corresponding issue. Apparently, the fetching of the WSDL
itself through https was not possible. Do you remember still some insights
beyond what is written in the issue ?
> Am 16.01.2020 um 00:37
