Stephen,
As to the first part of your question, I can not say for certain if WebLogic
will have the same problem with IFrames, I do not encounter any with JBoss,
and since they are inline as part of the main HTML document I don't believe
that you will have an issue. As for updating the surrounding stuff, yes it
is possible. However, if the content received by the iframe is to update
surrounding elements in the DOM, then the content must be received from the
same DOMAIN otherwise you will receive a security exception by default. The
other issue is if you must support Netscape versions prior to 6.x (I think
it is 6.b1, not sure).
I have used this for RPC invocation of validation and population of certain
components in web-apps, generally takes around .5 seconds for the round trip
to the server to have the action generate the results. The results are
returned to the iframe which then use some standard javascript to populate
the appropriate fields with values. Works good for selection list and drop
downs rather then having the entire screen re-paint every time an option
changes. Also works well for field validation which must take place on the
server. What I have done is to simply create a iframe 0px by 0px and then
use it for the RPC.
Let me know if you have any questions.
Regards,
Todd G. Nist
-Original Message-
From: Molitor, Stephen [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 19, 2002 7:08 PM
To: 'Struts Users Mailing List'
Subject: IFrame Newbie Looking for IFrame Advice
We're starting a new Struts app, and it might be nice to use IFrames in it.
Are there any gotchas with iframes in a J2EE / Struts app that I should be
aware of? For example, the WebLogic documentation states that normal frames
can cause problems with the session id getting lost if improperly used.
Could this be a problem with iframes too? Also, what if, as a result of the
user submitting something in the body page contained within the iframe, we
need to reach out and update the surrounding stuff. Is that possible?
Thanks!
Steve Molitor
[EMAIL PROTECTED]
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
