You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I went/played through the code and read other issue or request messages.
I think what I'm going to ask will not make a lot of practical sense ; I'm more asking where do you think I should start to implement such a thing with wash_out.
I need to implement quite a large WSDL with a lot of custom simpleType definitions like these :
Where do you I should start to hack wash_out to define these new simpleType ?
I need my WSDL to output these and to be able to use them in my complexType without Wash_out throwing an exception.
I started hacking here and there but I'm really not sure I'm taking the simplest or quickest road to achieve my goal.
I would greatly welcome any feedback from you :)
The text was updated successfully, but these errors were encountered:
I was trying to get my WSDL to output the custom reusable types created but I think I can manage without it.
And if it appears I have to, I can still hack your gem to include in the WSDL a custom tailored external file that will show these definitions.
I haven't used SOAP a lot but I think you must have reasons for not outputting these ?
I went/played through the code and read other issue or request messages.
I think what I'm going to ask will not make a lot of practical sense ; I'm more asking where do you think I should start to implement such a thing with wash_out.
I need to implement quite a large WSDL with a lot of custom simpleType definitions like these :
Those are then used in complexType definitions.
Where do you I should start to hack wash_out to define these new simpleType ?
I need my WSDL to output these and to be able to use them in my complexType without Wash_out throwing an exception.
I started hacking here and there but I'm really not sure I'm taking the simplest or quickest road to achieve my goal.
I would greatly welcome any feedback from you :)
The text was updated successfully, but these errors were encountered: