[
https://wso2.org/jira/browse/MASHUP-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16378#action_16378
]
Jonathan Marsh commented on MASHUP-725:
---------------------------------------
Hmm, too bad - would be nice to keep it with localHostName (there is no way
that could ever change between services? Even if added some proxying
capability in the future?) And it's nice not to pollute the space with too
many new objects and methods (working on some bugs related to that now). Is it
worth considering proxying the system object on a per-service basis so we can
add service-specific properties and methods to it? Introducing another object
like "environment" with such similarity to the system object will likely be
very confusing.
Actually, I just did a test:
system.endpointURL = "http://whatever";
function foo() {
return system.endpointURL;
}
Actually works fine, and doesn't seem to bleed between services - so maybe
instead of injecting a variable, can we just inject a property value at the
Javascript level instead of at the host object level?
> 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