You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Luciano Resende (JIRA)" <de...@tuscany.apache.org> on 2009/02/11 05:01:00 UTC

[jira] Assigned: (TUSCANY-2837) Extension points for implementation.widget

     [ https://issues.apache.org/jira/browse/TUSCANY-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luciano Resende reassigned TUSCANY-2837:
----------------------------------------

    Assignee: Luciano Resende

> 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 Web App Integration
>    Affects Versions: Java-SCA-1.4
>            Reporter: Yang Lei
>            Assignee: Luciano Resende
>
> 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.