You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Randy Watler (JIRA)" <ji...@apache.org> on 2010/07/11 17:41:49 UTC
[jira] Created: (SHINDIG-1380) Sample Container RPC Javascript
Errors
Sample Container RPC Javascript Errors
--------------------------------------
Key: SHINDIG-1380
URL: https://issues.apache.org/jira/browse/SHINDIG-1380
Project: Shindig
Issue Type: Bug
Components: Javascript
Environment: Linux Server
Firefox 3.0 browser with Firebug installed
Shindig SVN revision 962749
Reporter: Randy Watler
Fix For: 2.0.0-RC1, 2.0.0
Attachments: container-osapi-handle-gadget-rpc-method.patch, gadget-rpc-transport-container-init.patch
Several Javascript errors are present in the browser while starting the Sample Container and custom containers derived from it.
- No relay set (used as window.postMessage targetOrigin), cannot send cross-domain message
- Unknown RPC service: osapi._handleGadgetRpcMethod http://localhost:8080/gadgets/js/core:rpc:pubsub:shindig-container.js?c=1&debug=1 (line 779)
Both of these errors are related to the initialization and configuration of the RPC libraries. I have attached two patch files that correct these issues.
The first patch, (gadget-rpc-transport-container-init.patch), disables initialization of jsonrpctransport.js and gadgetsrpctransport.js in the container context. The code in these scripts used to assume that gadgets.config variable would only appear in gadgets and not the container. This changed late in 2009 and is no longer the case. This patch adds some gadgets.config flags via feature scripts that can be used reliably to determine whether in a gadget or container context. These flags are then used to enable/disable RPC initialization.
The second patch, (container-osapi-handle-gadget-rpc-method.patch), again includes the osapi.js portion of the shindig.container that implements the missing osapi._handleGadgetRpcMethod handler in feature.xml. It also cleans up some other related issues with the use of container.listMethods dynamic configuration, (i.e. it no longer attempts to rebind osapi.newBatch or isapi.container.listMethods).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-1380) Sample Container RPC Javascript
Errors
Posted by "Randy Watler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randy Watler updated SHINDIG-1380:
----------------------------------
Description:
Several Javascript errors are present in the browser while starting the Sample Container and custom containers derived from it.
- No relay set (used as window.postMessage targetOrigin), cannot send cross-domain message
- Unknown RPC service: osapi._handleGadgetRpcMethod http://localhost:8080/gadgets/js/core:rpc:pubsub:shindig-container.js?c=1&debug=1 (line 779)
Both of these errors are related to the initialization and configuration of the RPC libraries. I have attached two patch files that correct these issues.
The first patch, (gadget-rpc-transport-container-init.patch), disables initialization of jsonrpctransport.js and gadgetsrpctransport.js in the container context. The code in these scripts used to assume that gadgets.config variable would only appear in gadgets and not the container. This changed late in 2009 and is no longer the case. This patch adds some gadgets.config flags via feature scripts that can be used reliably to determine whether in a gadget or container context. These flags are then used to enable/disable RPC initialization.
The second patch, (container-osapi-handle-gadget-rpc-method.patch), again includes the osapi.js portion of the shindig.container that implements the missing osapi._handleGadgetRpcMethod handler in feature.xml. It also cleans up some other related issues with the use of container.listMethods dynamic configuration, (i.e. it no longer attempts to rebind osapi.newBatch or osapi.container.listMethods).
was:
Several Javascript errors are present in the browser while starting the Sample Container and custom containers derived from it.
- No relay set (used as window.postMessage targetOrigin), cannot send cross-domain message
- Unknown RPC service: osapi._handleGadgetRpcMethod http://localhost:8080/gadgets/js/core:rpc:pubsub:shindig-container.js?c=1&debug=1 (line 779)
Both of these errors are related to the initialization and configuration of the RPC libraries. I have attached two patch files that correct these issues.
The first patch, (gadget-rpc-transport-container-init.patch), disables initialization of jsonrpctransport.js and gadgetsrpctransport.js in the container context. The code in these scripts used to assume that gadgets.config variable would only appear in gadgets and not the container. This changed late in 2009 and is no longer the case. This patch adds some gadgets.config flags via feature scripts that can be used reliably to determine whether in a gadget or container context. These flags are then used to enable/disable RPC initialization.
The second patch, (container-osapi-handle-gadget-rpc-method.patch), again includes the osapi.js portion of the shindig.container that implements the missing osapi._handleGadgetRpcMethod handler in feature.xml. It also cleans up some other related issues with the use of container.listMethods dynamic configuration, (i.e. it no longer attempts to rebind osapi.newBatch or isapi.container.listMethods).
> Sample Container RPC Javascript Errors
> --------------------------------------
>
> Key: SHINDIG-1380
> URL: https://issues.apache.org/jira/browse/SHINDIG-1380
> Project: Shindig
> Issue Type: Bug
> Components: Javascript
> Environment: Linux Server
> Firefox 3.0 browser with Firebug installed
> Shindig SVN revision 962749
> Reporter: Randy Watler
> Fix For: 2.0.0-RC1, 2.0.0
>
> Attachments: container-osapi-handle-gadget-rpc-method.patch, gadget-rpc-transport-container-init.patch
>
>
> Several Javascript errors are present in the browser while starting the Sample Container and custom containers derived from it.
> - No relay set (used as window.postMessage targetOrigin), cannot send cross-domain message
> - Unknown RPC service: osapi._handleGadgetRpcMethod http://localhost:8080/gadgets/js/core:rpc:pubsub:shindig-container.js?c=1&debug=1 (line 779)
> Both of these errors are related to the initialization and configuration of the RPC libraries. I have attached two patch files that correct these issues.
> The first patch, (gadget-rpc-transport-container-init.patch), disables initialization of jsonrpctransport.js and gadgetsrpctransport.js in the container context. The code in these scripts used to assume that gadgets.config variable would only appear in gadgets and not the container. This changed late in 2009 and is no longer the case. This patch adds some gadgets.config flags via feature scripts that can be used reliably to determine whether in a gadget or container context. These flags are then used to enable/disable RPC initialization.
> The second patch, (container-osapi-handle-gadget-rpc-method.patch), again includes the osapi.js portion of the shindig.container that implements the missing osapi._handleGadgetRpcMethod handler in feature.xml. It also cleans up some other related issues with the use of container.listMethods dynamic configuration, (i.e. it no longer attempts to rebind osapi.newBatch or osapi.container.listMethods).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-1380) Sample Container RPC Javascript
Errors
Posted by "Randy Watler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randy Watler updated SHINDIG-1380:
----------------------------------
Attachment: gadget-rpc-transport-container-init.patch
container-osapi-handle-gadget-rpc-method.patch
> Sample Container RPC Javascript Errors
> --------------------------------------
>
> Key: SHINDIG-1380
> URL: https://issues.apache.org/jira/browse/SHINDIG-1380
> Project: Shindig
> Issue Type: Bug
> Components: Javascript
> Environment: Linux Server
> Firefox 3.0 browser with Firebug installed
> Shindig SVN revision 962749
> Reporter: Randy Watler
> Fix For: 2.0.0-RC1, 2.0.0
>
> Attachments: container-osapi-handle-gadget-rpc-method.patch, gadget-rpc-transport-container-init.patch
>
>
> Several Javascript errors are present in the browser while starting the Sample Container and custom containers derived from it.
> - No relay set (used as window.postMessage targetOrigin), cannot send cross-domain message
> - Unknown RPC service: osapi._handleGadgetRpcMethod http://localhost:8080/gadgets/js/core:rpc:pubsub:shindig-container.js?c=1&debug=1 (line 779)
> Both of these errors are related to the initialization and configuration of the RPC libraries. I have attached two patch files that correct these issues.
> The first patch, (gadget-rpc-transport-container-init.patch), disables initialization of jsonrpctransport.js and gadgetsrpctransport.js in the container context. The code in these scripts used to assume that gadgets.config variable would only appear in gadgets and not the container. This changed late in 2009 and is no longer the case. This patch adds some gadgets.config flags via feature scripts that can be used reliably to determine whether in a gadget or container context. These flags are then used to enable/disable RPC initialization.
> The second patch, (container-osapi-handle-gadget-rpc-method.patch), again includes the osapi.js portion of the shindig.container that implements the missing osapi._handleGadgetRpcMethod handler in feature.xml. It also cleans up some other related issues with the use of container.listMethods dynamic configuration, (i.e. it no longer attempts to rebind osapi.newBatch or isapi.container.listMethods).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SHINDIG-1380) Sample Container RPC Javascript
Errors
Posted by "Paul Lindner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Lindner resolved SHINDIG-1380.
-----------------------------------
Fix Version/s: (was: 2.0.0)
Resolution: Fixed
patches applied. Thanks!
> Sample Container RPC Javascript Errors
> --------------------------------------
>
> Key: SHINDIG-1380
> URL: https://issues.apache.org/jira/browse/SHINDIG-1380
> Project: Shindig
> Issue Type: Bug
> Components: Javascript
> Environment: Linux Server
> Firefox 3.0 browser with Firebug installed
> Shindig SVN revision 962749
> Reporter: Randy Watler
> Fix For: 2.0.0-RC1
>
> Attachments: container-osapi-handle-gadget-rpc-method.patch, gadget-rpc-transport-container-init.patch
>
>
> Several Javascript errors are present in the browser while starting the Sample Container and custom containers derived from it.
> - No relay set (used as window.postMessage targetOrigin), cannot send cross-domain message
> - Unknown RPC service: osapi._handleGadgetRpcMethod http://localhost:8080/gadgets/js/core:rpc:pubsub:shindig-container.js?c=1&debug=1 (line 779)
> Both of these errors are related to the initialization and configuration of the RPC libraries. I have attached two patch files that correct these issues.
> The first patch, (gadget-rpc-transport-container-init.patch), disables initialization of jsonrpctransport.js and gadgetsrpctransport.js in the container context. The code in these scripts used to assume that gadgets.config variable would only appear in gadgets and not the container. This changed late in 2009 and is no longer the case. This patch adds some gadgets.config flags via feature scripts that can be used reliably to determine whether in a gadget or container context. These flags are then used to enable/disable RPC initialization.
> The second patch, (container-osapi-handle-gadget-rpc-method.patch), again includes the osapi.js portion of the shindig.container that implements the missing osapi._handleGadgetRpcMethod handler in feature.xml. It also cleans up some other related issues with the use of container.listMethods dynamic configuration, (i.e. it no longer attempts to rebind osapi.newBatch or osapi.container.listMethods).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.