You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Tyrell Perera <ty...@wso2.com> on 2008/06/05 08:37:48 UTC
Title not being read from the gadget xml
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm writing a dashboard page using the Shindig samples as a guideline
and noticed that the 'Title' attribute defined in a gadget xml is not
read (at least in the sample container pages).
Is there a way to get the value given in the title attribute to be
displayed in the UI widgets title?
thanks,
Tyrell
- --
Tyrell Perera
Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/
email: tyrell@wso2.com; cell: +94 77 302 2505
"Oxygenating the Web Service Platform."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIR4m8ehFdPcgGx7oRArhDAKDPcOQwpnGtZkCj9NLEIQoiYye6CACguKuI
Q3/kwbUj9sq/PzjSttVQzhw=
=Dq8a
-----END PGP SIGNATURE-----
Re: Title not being read from the gadget xml
Posted by Tim Thelin <tt...@google.com>.
At this point if I were in your position, I'd start putting in print
statements to trace through the code to find out the point of failure.
Since it's an embedded device, hopefully you have a writable file system /
ram drive / tmp area that you can log to...
I'm not that familiar with Tomcat, so I wouldn't know about any explicit
issues it might have in this regard.
-Tim
On Thu, Jun 5, 2008 at 7:37 PM, Tyrell Perera <ty...@wso2.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Unfortunately I'm not getting a stack trace on this occasion. My
> environment is linux/jdk 1.5.0_15/tomcat 5 (embedded)
>
> I tried in a standalone tomcat 6 instance and the example worked. Can it
> be tomcat 5 that's failing JSON? It seems like it is. My integration
> project requires the first setup. Any workarounds appreciated.
>
> Tyrell
>
>
> Tim Thelin wrote:
> | Normally when the gadget server gives you an error as the http
> response, it
> | dumps a stack trace in the terminal where it's running. That stack trace
> | would be useful for figuring this out.
> |
> | -Tim
> |
> | On Thu, Jun 5, 2008 at 12:28 PM, Tyrell Perera <ty...@wso2.com> wrote:
> |
> |
> | Thanks Tim.
> |
> | I tried the approach you mentioned since both my container and the
> | gadget server are from the same origin, however the post fails with a
> | 500 error. The message I get is "Unable to write JSON".
> |
> | I can't run the example either. It fails with the same error.
> |
> | Am I missing something?
> |
> | Tyrell
> |
> |
> | Tim Thelin wrote:
> | | The gadget server is what has the direct access to fields like title
> (the
> | | metadata), but the gadget server does not make your gadget's chrome
> (the
> | | outer parts like the title bar, settings button, etc). So when your
> | | container starts making the chrome around a gadget, it needs to
> | contact the
> | | gadget server to get the metadata from it. This can either be done
> | | directly (XMLHttpRequest) or indirectly (your webserver does the http
> | | request, passing back the results to your page).
> | |
> | | javascript/container/sample-metadata.html is an example of doing it
> | directly
> | | using XMLHttpRequest, but it only works if the gadget server is on the
> | same
> | | origin as the container.
> | |
> | | More likely (like in my case) you'll have to do this request indirectly
> | by
> | | having your webserver make the http request to the gadget server.
> | Once your
> | | webserver receives the json metadata response, it passes it to the
> | container
> | | javascript for use.
> | |
> | | -Tim
> | |
> | |
> | | On Wed, Jun 4, 2008 at 11:37 PM, Tyrell Perera <ty...@wso2.com>
> wrote:
> | |
> | | Hi,
> | |
> | | I'm writing a dashboard page using the Shindig samples as a guideline
> | | and noticed that the 'Title' attribute defined in a gadget xml is not
> | | read (at least in the sample container pages).
> | |
> | | Is there a way to get the value given in the title attribute to be
> | | displayed in the UI widgets title?
> | |
> | | thanks,
> | | Tyrell
> | |
> | |
> | |>
> |
> |>
>
> - --
> Tyrell Perera
> Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/
> email: tyrell@wso2.com; cell: +94 77 302 2505
>
> "Oxygenating the Web Service Platform."
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFISKL+ehFdPcgGx7oRAsqLAJ9s6ivDAHosq2laTFLuKF/q9wbYwgCfQPuI
> sfVwNhPj2IJtj+KDDewmdJ4=
> =xexy
> -----END PGP SIGNATURE-----
>
Re: Title not being read from the gadget xml
Posted by Tyrell Perera <ty...@wso2.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Unfortunately I'm not getting a stack trace on this occasion. My
environment is linux/jdk 1.5.0_15/tomcat 5 (embedded)
I tried in a standalone tomcat 6 instance and the example worked. Can it
be tomcat 5 that's failing JSON? It seems like it is. My integration
project requires the first setup. Any workarounds appreciated.
Tyrell
Tim Thelin wrote:
| Normally when the gadget server gives you an error as the http
response, it
| dumps a stack trace in the terminal where it's running. That stack trace
| would be useful for figuring this out.
|
| -Tim
|
| On Thu, Jun 5, 2008 at 12:28 PM, Tyrell Perera <ty...@wso2.com> wrote:
|
|
| Thanks Tim.
|
| I tried the approach you mentioned since both my container and the
| gadget server are from the same origin, however the post fails with a
| 500 error. The message I get is "Unable to write JSON".
|
| I can't run the example either. It fails with the same error.
|
| Am I missing something?
|
| Tyrell
|
|
| Tim Thelin wrote:
| | The gadget server is what has the direct access to fields like title
(the
| | metadata), but the gadget server does not make your gadget's chrome (the
| | outer parts like the title bar, settings button, etc). So when your
| | container starts making the chrome around a gadget, it needs to
| contact the
| | gadget server to get the metadata from it. This can either be done
| | directly (XMLHttpRequest) or indirectly (your webserver does the http
| | request, passing back the results to your page).
| |
| | javascript/container/sample-metadata.html is an example of doing it
| directly
| | using XMLHttpRequest, but it only works if the gadget server is on the
| same
| | origin as the container.
| |
| | More likely (like in my case) you'll have to do this request indirectly
| by
| | having your webserver make the http request to the gadget server.
| Once your
| | webserver receives the json metadata response, it passes it to the
| container
| | javascript for use.
| |
| | -Tim
| |
| |
| | On Wed, Jun 4, 2008 at 11:37 PM, Tyrell Perera <ty...@wso2.com> wrote:
| |
| | Hi,
| |
| | I'm writing a dashboard page using the Shindig samples as a guideline
| | and noticed that the 'Title' attribute defined in a gadget xml is not
| | read (at least in the sample container pages).
| |
| | Is there a way to get the value given in the title attribute to be
| | displayed in the UI widgets title?
| |
| | thanks,
| | Tyrell
| |
| |
| |>
|
|>
- --
Tyrell Perera
Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/
email: tyrell@wso2.com; cell: +94 77 302 2505
"Oxygenating the Web Service Platform."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFISKL+ehFdPcgGx7oRAsqLAJ9s6ivDAHosq2laTFLuKF/q9wbYwgCfQPuI
sfVwNhPj2IJtj+KDDewmdJ4=
=xexy
-----END PGP SIGNATURE-----
Re: Title not being read from the gadget xml
Posted by Tyrell Perera <ty...@wso2.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Unfortunately I'm not getting a stack trace on this occasion. My
environment is linux/jdk 1.5.0_15/tomcat 5 (embedded)
I tried in a standalone tomcat 6 instance and the example worked. Can it
be tomcat 5 that's failing JSON? It seems like it is. My integration
project requires the first setup. Any workarounds appreciated.
Tyrell
Tim Thelin wrote:
| Normally when the gadget server gives you an error as the http
response, it
| dumps a stack trace in the terminal where it's running. That stack trace
| would be useful for figuring this out.
|
| -Tim
|
| On Thu, Jun 5, 2008 at 12:28 PM, Tyrell Perera <ty...@wso2.com> wrote:
|
|
| Thanks Tim.
|
| I tried the approach you mentioned since both my container and the
| gadget server are from the same origin, however the post fails with a
| 500 error. The message I get is "Unable to write JSON".
|
| I can't run the example either. It fails with the same error.
|
| Am I missing something?
|
| Tyrell
|
|
| Tim Thelin wrote:
| | The gadget server is what has the direct access to fields like title
(the
| | metadata), but the gadget server does not make your gadget's chrome (the
| | outer parts like the title bar, settings button, etc). So when your
| | container starts making the chrome around a gadget, it needs to
| contact the
| | gadget server to get the metadata from it. This can either be done
| | directly (XMLHttpRequest) or indirectly (your webserver does the http
| | request, passing back the results to your page).
| |
| | javascript/container/sample-metadata.html is an example of doing it
| directly
| | using XMLHttpRequest, but it only works if the gadget server is on the
| same
| | origin as the container.
| |
| | More likely (like in my case) you'll have to do this request indirectly
| by
| | having your webserver make the http request to the gadget server.
| Once your
| | webserver receives the json metadata response, it passes it to the
| container
| | javascript for use.
| |
| | -Tim
| |
| |
| | On Wed, Jun 4, 2008 at 11:37 PM, Tyrell Perera <ty...@wso2.com> wrote:
| |
| | Hi,
| |
| | I'm writing a dashboard page using the Shindig samples as a guideline
| | and noticed that the 'Title' attribute defined in a gadget xml is not
| | read (at least in the sample container pages).
| |
| | Is there a way to get the value given in the title attribute to be
| | displayed in the UI widgets title?
| |
| | thanks,
| | Tyrell
| |
| |
| |>
|
|>
- --
Tyrell Perera
Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/
email: tyrell@wso2.com; cell: +94 77 302 2505
"Oxygenating the Web Service Platform."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFISJ7pehFdPcgGx7oRAuqiAKDqOizmMmUj+BHRztXfNd6ESh0FjACfaFvQ
bRH6GEUARgltrlDAys4E00c=
=cC4y
-----END PGP SIGNATURE-----
Re: Title not being read from the gadget xml
Posted by Tim Thelin <tt...@google.com>.
Normally when the gadget server gives you an error as the http response, it
dumps a stack trace in the terminal where it's running. That stack trace
would be useful for figuring this out.
-Tim
On Thu, Jun 5, 2008 at 12:28 PM, Tyrell Perera <ty...@wso2.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Thanks Tim.
>
> I tried the approach you mentioned since both my container and the
> gadget server are from the same origin, however the post fails with a
> 500 error. The message I get is "Unable to write JSON".
>
> I can't run the example either. It fails with the same error.
>
> Am I missing something?
>
> Tyrell
>
>
> Tim Thelin wrote:
> | The gadget server is what has the direct access to fields like title (the
> | metadata), but the gadget server does not make your gadget's chrome (the
> | outer parts like the title bar, settings button, etc). So when your
> | container starts making the chrome around a gadget, it needs to
> contact the
> | gadget server to get the metadata from it. This can either be done
> | directly (XMLHttpRequest) or indirectly (your webserver does the http
> | request, passing back the results to your page).
> |
> | javascript/container/sample-metadata.html is an example of doing it
> directly
> | using XMLHttpRequest, but it only works if the gadget server is on the
> same
> | origin as the container.
> |
> | More likely (like in my case) you'll have to do this request indirectly
> by
> | having your webserver make the http request to the gadget server.
> Once your
> | webserver receives the json metadata response, it passes it to the
> container
> | javascript for use.
> |
> | -Tim
> |
> |
> | On Wed, Jun 4, 2008 at 11:37 PM, Tyrell Perera <ty...@wso2.com> wrote:
> |
> | Hi,
> |
> | I'm writing a dashboard page using the Shindig samples as a guideline
> | and noticed that the 'Title' attribute defined in a gadget xml is not
> | read (at least in the sample container pages).
> |
> | Is there a way to get the value given in the title attribute to be
> | displayed in the UI widgets title?
> |
> | thanks,
> | Tyrell
> |
> |
> |>
>
> - --
> Tyrell Perera
> Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/
> email: tyrell@wso2.com; cell: +94 77 302 2505
>
> "Oxygenating the Web Service Platform."
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFISD5iehFdPcgGx7oRAj9DAJ90OWzLObqnWYaNyK6lDlt/7Hu/MgCfX3Xb
> zqnV4tYS4B5i0uzfUc2g+0E=
> =FPZg
> -----END PGP SIGNATURE-----
>
Re: Title not being read from the gadget xml
Posted by Tyrell Perera <ty...@wso2.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thanks Tim.
I tried the approach you mentioned since both my container and the
gadget server are from the same origin, however the post fails with a
500 error. The message I get is "Unable to write JSON".
I can't run the example either. It fails with the same error.
Am I missing something?
Tyrell
Tim Thelin wrote:
| The gadget server is what has the direct access to fields like title (the
| metadata), but the gadget server does not make your gadget's chrome (the
| outer parts like the title bar, settings button, etc). So when your
| container starts making the chrome around a gadget, it needs to
contact the
| gadget server to get the metadata from it. This can either be done
| directly (XMLHttpRequest) or indirectly (your webserver does the http
| request, passing back the results to your page).
|
| javascript/container/sample-metadata.html is an example of doing it
directly
| using XMLHttpRequest, but it only works if the gadget server is on the
same
| origin as the container.
|
| More likely (like in my case) you'll have to do this request indirectly by
| having your webserver make the http request to the gadget server.
Once your
| webserver receives the json metadata response, it passes it to the
container
| javascript for use.
|
| -Tim
|
|
| On Wed, Jun 4, 2008 at 11:37 PM, Tyrell Perera <ty...@wso2.com> wrote:
|
| Hi,
|
| I'm writing a dashboard page using the Shindig samples as a guideline
| and noticed that the 'Title' attribute defined in a gadget xml is not
| read (at least in the sample container pages).
|
| Is there a way to get the value given in the title attribute to be
| displayed in the UI widgets title?
|
| thanks,
| Tyrell
|
|
|>
- --
Tyrell Perera
Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/
email: tyrell@wso2.com; cell: +94 77 302 2505
"Oxygenating the Web Service Platform."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFISD5iehFdPcgGx7oRAj9DAJ90OWzLObqnWYaNyK6lDlt/7Hu/MgCfX3Xb
zqnV4tYS4B5i0uzfUc2g+0E=
=FPZg
-----END PGP SIGNATURE-----
Re: Title not being read from the gadget xml
Posted by Tim Thelin <tt...@google.com>.
The gadget server is what has the direct access to fields like title (the
metadata), but the gadget server does not make your gadget's chrome (the
outer parts like the title bar, settings button, etc). So when your
container starts making the chrome around a gadget, it needs to contact the
gadget server to get the metadata from it. This can either be done
directly (XMLHttpRequest) or indirectly (your webserver does the http
request, passing back the results to your page).
javascript/container/sample-metadata.html is an example of doing it directly
using XMLHttpRequest, but it only works if the gadget server is on the same
origin as the container.
More likely (like in my case) you'll have to do this request indirectly by
having your webserver make the http request to the gadget server. Once your
webserver receives the json metadata response, it passes it to the container
javascript for use.
-Tim
On Wed, Jun 4, 2008 at 11:37 PM, Tyrell Perera <ty...@wso2.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> I'm writing a dashboard page using the Shindig samples as a guideline
> and noticed that the 'Title' attribute defined in a gadget xml is not
> read (at least in the sample container pages).
>
> Is there a way to get the value given in the title attribute to be
> displayed in the UI widgets title?
>
> thanks,
> Tyrell
>
>
> - --
> Tyrell Perera
> Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/
> email: tyrell@wso2.com; cell: +94 77 302 2505
>
> "Oxygenating the Web Service Platform."
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFIR4m8ehFdPcgGx7oRArhDAKDPcOQwpnGtZkCj9NLEIQoiYye6CACguKuI
> Q3/kwbUj9sq/PzjSttVQzhw=
> =Dq8a
> -----END PGP SIGNATURE-----
>