Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

targetNamespace could not be extracted from WSDL file more complicated issue #14

Closed
marcinsienko opened this issue Jul 20, 2017 · 3 comments

Comments

@marcinsienko
Copy link

marcinsienko commented Jul 20, 2017

Hi again,

This issue is a little complicated. I have a project and try to generate classes from wsdl. i have targetNamespace: http://webservice_v26.tag.crm.comarch.com/ and it not works beacuse of

targetNamespace could not be extracted from WSDL file

It is regexp issue i think but there is also more complicate issue. When I add second WSDL that has supported namespace urn:microsoft-dynamics-schemas/page/customers build process passed but assign the same wsdl location to both generated services:

  • CustomersService
  • TAGExternalAPIImplService

@WebServiceClient(name = "TAGExternalAPIImplService", targetNamespace = "http://webservice_v26.tag.crm.comarch.com/", wsdlLocation = "/wsdl/Customers.wsdl")

@WebServiceClient(name = "Customers_Service", targetNamespace = "urn:microsoft-dynamics-schemas/page/customers", wsdlLocation = "/wsdl/Customers.wsdl")

In TAGExternalAPIImplService it should be /wsdl/tagExternalAPIv26.wsdl

More support targetNamespace like http://webservice_v26.tag.crm.comarch.com/ also will be helpful. :)

Could you take a look at it in meantime please?
I use version 1.1.2.RELEASE.

Thanks a lot and regards,
Marcin

@jonashackt
Copy link
Member

jonashackt commented Sep 13, 2017

Sorry for the late reply. The implementation now also supports underscores like in your example http://webservice_v26.tag.crm.comarch.com/. I will release it soon, so I would appreciate if you could test it.

Then we´ll have a look at the second problem you mentioned. Ah I see now, the project´s design goal is to only support one WSDL per Spring Boot microservice at a time, not more than 1! So if you want to use 2 WSDLs, simply create 2 Spring Boot projects. It should be no problem :) So I close this issue now and release the plugin on Maven Central. I´ll drop a note here, if it´s done.

@jonashackt
Copy link
Member

jonashackt commented Sep 13, 2017

@marcinsienko the Plugin with 1.1.3.RELEASE is now released, but it will take a few hours till you could get it over Maven Central. Have fun :)

@marcinsienko
Copy link
Author

marcinsienko commented Sep 25, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants