[
https://wso2.org/jira/browse/MASHUP-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382#action_16382
]
Keith Godwin Chapman commented on MASHUP-725:
---------------------------------------------
OK seems like I can put in a workaround to get this working. But a few
questions.
What do u really expect when u call system.endpointURL? Are you expecting the
Mashup server to calculate its endpoint URL for you or are you expecting the
server to get it off the request URL.
Implementation wise both are possible but each has uits problems. In the first
case this will case problems in a deployment such as mooshup.com where the
server is behind a proxy. In the second case the URLs will change depending on
the transport been used to call the service. e.g http, https, JMS and so on.
> Could use a way to find the endpoint of a service from within the Javascript.
> -----------------------------------------------------------------------------
>
> Key: MASHUP-725
> URL: https://wso2.org/jira/browse/MASHUP-725
> Project: WSO2 Mashup Server
> Issue Type: Improvement
> Reporter: Jonathan Marsh
> Assignee: Keith Godwin Chapman
> Fix For: 1.1
>
>
> A function (system object?) that would provide the endpoint URI at which the
> service was invoked would be very valuable. How else, for instance, can I
> construct a feed link that won't break as my service is invoked through
> different bindings, and won't break when the mashup is migrated?
> I'm thinking something like a read-only property:
> var myURL = system.endpointURL;
--
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
