Instance Variables in JavaScript

Hey guys,

From an Xforms page I wanted to create a popup to another page. I wanted to do this using Javascript: “window.open('http://localhost:8080/DwrTest1/index.html?id=blah’)”.

 The other preferred option was doing this with an iframe like:

<xhtml:iframe name="iframe" src="http://localhost:8080/DwrTest1/index.html?id=blah"/>

Either way, I wanted to replace “blah” with a variable stored in the Xforms instance. I tried something like window.open('http://localhost:8080/DwrTest1/index.html?id=<xforms:output ref=instance(‘req_instance’)/id/>”) but that returned some errors. Does anyone know the syntax I have to use?

Thanks,

Naman

Alex,

I did use xforms:input and there isn't really any stack trace. Firebug just shows that there was an error on that line. (Print Screen attached)

Joseph also advised me of another option:

<xforms:action>

<xforms:load resource="http://www.google.com" xxforms:target="iframe"/>

</xforms:action>

This was placed in a trigger action and this actually works in Liferay. But I really wanted the iframe to load as soon as the page loads rather than pressing a button. So I added:

<xforms:model>

...

      <xforms:action ev:event="xforms-ready">

            <xxforms:script>ORBEON.xforms.Document.dispatchEvent("main-model", "get-content-data");</xxforms:script>

      </xforms:action>

<xforms:action ev:event="get-content-data">

                  <xforms:load resource="http://www.google.com" xxforms:target="iframe"/>

      </xforms:action>

..

Now this works if you run it under Orbeon but unfortunately it doesn’t work in Liferay. I have a good feeling that Liferay doesn’t like this ORBEON.xforms.Document function. Furthermore nothing showed up in Firebug in this example????

I have attached the app, so if you extract it into the oxf:/apps directory you can see for yourself.

Thanks for everything

Naman

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro Vernet
Sent: Thursday, 3 May 2007 7:04 AM
To: [hidden email]
Subject: Re: [ops-users] Instance Variables in JavaScript

Naman,

On 5/1/07, Naman Joshi <[hidden email]> wrote:

> I hope you don't mind me replying to you directly...i just didn't want

> to flood the mailing list.

Don't worry about flooding the mailing list. In fact it is better to

respond on the mailing list, rather than in private, so everyone can

contribute to the discussion and benefit from the information which is

exchanged.

> I saw that in the documentation before but I thought there might've been

> a way without setting up a control. Anyways I tried it and unfortunately

> it doesn't work when I'm using it in a portlet in Liferay. I used

> Firebug and found that I got this error:

> 

> element has no properties

> http://localhost:8080/ops/ops/javascript/xforms.js

> Line 197

Is the control an xforms:input? If it is not, can you try with an

xforms:input and let me know if it works? If it doesn't work with an

XForms input, can you take a screenshot of the stack trace for this

error in Firebug?

Alex

--

Orbeon Forms - Web 2.0 Forms for the Enterprise

http://www.orbeon.com/

Did anyone get a chance to look at this? L

Alex,

I did use xforms:input and there isn't really any stack trace. Firebug just shows that there was an error on that line. (Print Screen attached)

Joseph also advised me of another option:

<xforms:action>

<xforms:load resource="http://www.google.com" xxforms:target="iframe"/>

</xforms:action>

This was placed in a trigger action and this actually works in Liferay. But I really wanted the iframe to load as soon as the page loads rather than pressing a button. So I added:

<xforms:model>

...

      <xforms:action ev:event="xforms-ready">

            <xxforms:script>ORBEON.xforms.Document.dispatchEvent("main-model", "get-content-data");</xxforms:script>

      </xforms:action>

<xforms:action ev:event="get-content-data">

                  <xforms:load resource="http://www.google.com" xxforms:target="iframe"/>

      </xforms:action>

..

Now this works if you run it under Orbeon but unfortunately it doesn’t work in Liferay. I have a good feeling that Liferay doesn’t like this ORBEON.xforms.Document function. Furthermore nothing showed up in Firebug in this example????

I have attached the app, so if you extract it into the oxf:/apps directory you can see for yourself.

Thanks for everything

Naman

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro Vernet
Sent: Thursday, 3 May 2007 7:04 AM
To: [hidden email]
Subject: Re: [ops-users] Instance Variables in JavaScript

Naman,

On 5/1/07, Naman Joshi <[hidden email]> wrote:

> I hope you don't mind me replying to you directly...i just didn't want

> to flood the mailing list.

Don't worry about flooding the mailing list. In fact it is better to

respond on the mailing list, rather than in private, so everyone can

contribute to the discussion and benefit from the information which is

exchanged.

> I saw that in the documentation before but I thought there might've been

> a way without setting up a control. Anyways I tried it and unfortunately

> it doesn't work when I'm using it in a portlet in Liferay. I used

> Firebug and found that I got this error:

> 

> element has no properties

> http://localhost:8080/ops/ops/javascript/xforms.js

> Line 197

Is the control an xforms:input? If it is not, can you try with an

xforms:input and let me know if it works? If it doesn't work with an

XForms input, can you take a screenshot of the stack trace for this

error in Firebug?

Alex

--

Orbeon Forms - Web 2.0 Forms for the Enterprise

http://www.orbeon.com/

NOTICE

This e-mail and any attachments are confidential and may contain copyright material of Macquarie Bank or third parties. If you are not the intended recipient of this email you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. Macquarie Bank does not guarantee the integrity of any emails or any attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Macquarie Bank.