[
https://wso2.org/jira/browse/MASHUP-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585#action_16585
]
Jonathan Marsh commented on MASHUP-794:
---------------------------------------
I don't really care which way the URLs work, or whether there are aliases. My
comment is that the WSDL itself "looks" inconsistent - which isn't a large
problem but if somebody took the WSDL and then coded a service off of it they
might have trouble - most likely just momentary confusion. In our case it
highlighted a bug in our absolutization algorithm, so the appearance of the
inconsistency was a good thing, and caused the bug to found and fixed. But it
did complicate even our life as a result. I can also imagine at some point if
we did decide to disallow SOAP requests from being served at
digit2image.HTTPEndpoint (sounds like a source of security vulnerability) then
all our WSDLs would truly be broken.
> whttp:location doesn't match endpoints.
> ---------------------------------------
>
> Key: MASHUP-794
> URL: https://wso2.org/jira/browse/MASHUP-794
> Project: WSO2 Mashup Server
> Issue Type: Bug
> Reporter: Jonathan Marsh
> Assignee: Keith Godwin Chapman
> Fix For: 1.1
>
>
> Getting a ?wsdl2 for a service presents an oddity.
> The endpoint addresses recently changed to include an indication of the
> endpoint being used to invoke the service, e.g.
> http://10.1.1.3:7762/services/system/digit2image.HTTPEndpoint. Yet the
> whttp:location misses this extra information, e.g. digit2image/digit2image.
> Should it not be digit2image.HTTPEndpoint/digit2image?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
