[
https://issues.apache.org/jira/browse/TUSCANY-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luciano Resende resolved TUSCANY-2837.
--------------------------------------
Resolution: Fixed
Fix Version/s: Java-SCA-Next
Java-SCA-1.5
Fixed. Added the following changes
- Added extension points to Implementation Widget (core-web)
- Updated ATOM (binding-atom-js) and JSON-RPC (binding-atom-js) bindings
using these extensions to provide Javascript Proxies
- Updated sample apps with new required dependencies
> Extension points for implementation.widget
> ------------------------------------------
>
> Key: TUSCANY-2837
> URL: https://issues.apache.org/jira/browse/TUSCANY-2837
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Widget
> Affects Versions: Java-SCA-1.4
> Reporter: Yang Lei
> Assignee: Luciano Resende
> Fix For: Java-SCA-1.5, Java-SCA-Next
>
>
> When looking at the current implementation of implemention.widget, I noticed
> that there is code like the following that hardcode the generate JS code for
> different protocol. I would like to see the code done through extension
> points, so it can be extended. e.g., here is the code in
> WidgetImplementatonInvoker.generateJavaScriptReferenceFunction:
> if(proxyClient.equals("JSONRpcClient")) {
> pw.println("referenceMap." + referenceName + " = new
> " + proxyClient + "(\"" + targetURI + "\").Service;");
> } else {
> pw.println("referenceMap." + referenceName + " = new
> " + proxyClient + "(\"" + targetURI + "\");");
> }
> If there are other places in implementation.widget doing this kind of switch,
> I would also like to see them done through extension points.
> Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
