On frames, that probably won't work if you already have frames in AppA, for obvious reasons, e.g. "target='_top'".
I am assuming that you want to port a non-struts application to struts. That should be not difficult, if that is is. Is it? Could you be more explicit about the situation you face? Is there any reasons why AppA and AppB cannot co-exist in the same application? That would be the natural solution, if possible, viz. if you want AppA in AppB, put it in there. However, your requirements may make that impossible.
Michael McGrady
Susan Bradeen wrote:
I have two web applications. App A is a finished, working web application. App B, a work in progress, is using Struts and Tiles, and has a requirement to essentially 'put App A in a content Tile' for use in App B. This will in affect produce a 'portal-like' function, with App A working as normal within the 'framework' produced by App B. (Hopefully that makes some sense.) Housing App A is not the sole purpose of App B, but just one functionality requirement.
From a search in the archives, it seems that Tiles is not (or can'tfunctionally be) the way to accomplish this. Opening a second browser and running App A in there is also not an option. I am not very familiar with Frames (and I didn't get a good reponse when I brought it up), but would this be my best choice? Other recommendations? Any pointers to information about doing something like this are also greatly appreciated. Googling for a set of options/pros&cons hasn't given me much so far.
Thanks, Susan Bradeen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]