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.

Sign up for GitHub

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

Jump to bottom

targetNamespace could not be extracted from WSDL file continue #12

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

targetNamespace could not be extracted from WSDL file continue #12

marcinsienko opened this issue Jul 5, 2017 · 3 comments
Milestone
1.1.2.RELEASE

Comments

@marcinsienko
Copy link

marcinsienko commented Jul 5, 2017 •
edited
Loading

Hi,

Is any chance to support also namespaces with "-" signs like:

<xsd:schema elementFormDefault="qualified" targetNamespace="urn:microsoft-dynamics-schemas/page/customers" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

?

Thanks a lot.
Regards,
Marcin
@jonashackt
Copy link
Member

Sure. We´ll have a look onto it and come back to you here.

jonashackt added a commit that referenced this issue Jul 14, 2017
@jonashackt
#12: Now also supporting dashes ('-') inside the target namespace. No…
0a739ed 
…te: the dash is converted into a dot by the XJC-algorithm
@jonashackt
Copy link
Member

jonashackt commented Jul 14, 2017 •
edited
Loading

@marcinsienko the code now also supports dashes - I´ll release the new 1.1.2 now, this will take some while, till it´s available through Maven Central (think, tomorrow it will be accessible :) ). Just watch out for the 1.1.2.RELEASE

@marcinsienko
Copy link
Author

Thanks a lot :).

Regards,
Marcin

@jonashackt jonashackt mentioned this issue Jul 14, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
1.1.2.RELEASE
Development

No branches or pull requests
2 participants
@jonashackt @marcinsienko