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

WSDL with dependencies are not supported #85

Open
milkotodorov opened this issue Oct 11, 2018 · 7 comments
Open

WSDL with dependencies are not supported #85

milkotodorov opened this issue Oct 11, 2018 · 7 comments
Assignees
Labels

Comments

@milkotodorov
Copy link

Hello @karldahlgren.

the solution proposed in #68 doesn't solve the issue.

By the way it would be nice to leave the issue opened and close them after user's confirmation that this problem is fixed.

Thanks,
Milko

@karldahlgren
Copy link
Collaborator

Hi @milkotodorov.
Would it be possible for you to send me these WSDL files so I can give it a try?
Btw, you should not upload the XSD files since no information will be extracted from them. Only the WSDL files contains information about the actual service.

Thanks!
Best regards,
Karl Dahlgren

@karldahlgren karldahlgren self-assigned this Oct 14, 2018
@karldahlgren karldahlgren modified the milestones: 1.30, 1.31 Oct 14, 2018
@milkotodorov
Copy link
Author

milkotodorov commented Oct 14, 2018

Hi @karldahlgren,

I think I already attached them to the initial issue, but sure - I'm sending it to you once more.
By the way don't you think it is better to leave the issue opened until it is fixed and confirmed to be fixed from the reporter and then close it - then we will avoid creating many issues linked to each other.

Regards,
Milko
CreditSafe_WSDL_Local.zip

@karldahlgren
Copy link
Collaborator

Hi @milkotodorov.
I see now why these doesn't work. Hmmm will be a little bit tricky to solve. I have to dig deeper into this before I can give any estimation. I will keep you posted.

Thanks!
Best regards,
Karl Dahlgren

@milkotodorov
Copy link
Author

Hi @karldahlgren,

did you have the change to check this?

@karldahlgren karldahlgren modified the milestones: 1.31, 1.35 Dec 12, 2018
@karldahlgren karldahlgren modified the milestones: 1.35, 1.36 Jan 3, 2019
@castlemock castlemock removed this from the 1.36 milestone Feb 17, 2019
@milkotodorov
Copy link
Author

Hi @karldahlgren,

any updates?

@karldahlgren
Copy link
Collaborator

Hi @milkotodorov.
Sorry for the late answer. I haven't been able to resolve this issue yet. It is quite complexed and way harder to solve and I originally thought it would be. I hope that I will be able to look into this as soon as possible.

Best regards,
Karl Dahlgren

@cceelen
Copy link

cceelen commented Jun 21, 2023

Hi
I just ran into this problem and means that i cannot use castlemock for the WSDLs and XSDs i have. These follow OTA implementation standards, which means you have the definitions split into several XSDs for type definitions, several XSDs for message definitions, one WSDL for operation mapping, and one WSDL for implementation mapping/binding. All this is rather quickly 30-80 files.
Would it be possible to perhaps import such a structure as a zip archive instead of one WSDL at a time and then just select the WSDLs to import into a project?

Best Regards,
Christian

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

No branches or pull requests

4 participants