Solved: Modules and Frames

[Derek Richardson]

For the archives, my problem had nothing to do with frames per se. The frames were, 
however, directly referencing JSPs, which it turns out is a no-no when using modules. 
Everything has to go through the ActionServlet. Or, at least, everything that will be 
rewriting URLs to add the module path.

> -Original Message-
> From: Derek Richardson 
> Sent: Friday, February 14, 2003 3:49 PM
> To: Struts Users Mailing List
> Subject: Modules and Frames
> 
> 
> I have an application module running in frames. In some 
> cases, the frames are nested to a depth of 4. All the src 
> attributes for the frame tags use h:rewrite with the page 
> attribute, so that the app prefix and module prefix should 
> both be prepended.
> 
> The frame src attributes in the top-level frameset are being 
> correctly rewritten with the module path and are loading 
> correctly. The problem is that the frame src attributes in 
> the second level of framesets are not being rewritten correctly.
> 
> The application runs correctly when it is in the default 
> module. The three changes I made to move it from an explicit 
> module to the default module were (1) change web.xml so that 
> the init-param for the explicit module is commented out, (2) 
> change web.xml to add a comma and the struts-config file path 
> to the default module's param-value, and (3) move the jsp's 
> physical location up one level in the directory tree, out 
> from under the directory named for the explicit module.
> 
> Searching the archives with marc turned up nothing about 
> modules and frames. I'm hoping someone has some experience or 
> theory to share.
> 
> I am running struts 1.1b3 on Tomcat 4.1.18 in eclipse 2.1. 
> Here is the post-move-back-to-default-app relevant section 
> from my web.xml:
> 
> 
>   config
>   
> /WEB-INF/struts-config.xml,/WEB-INF/struts-config
> -dt.xml
> 
> 
> 
> Let me know if there is any additional information I can 
> provide to help you diagnose my problem.
> 
> Thanks,
> 
> Derek Richardson
> 
> -
> 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]

Modules and Frames

[Derek Richardson]

I have an application module running in frames. In some cases, the frames are nested 
to a depth of 4. All the src attributes for the frame tags use h:rewrite with the page 
attribute, so that the app prefix and module prefix should both be prepended.

The frame src attributes in the top-level frameset are being correctly rewritten with 
the module path and are loading correctly. The problem is that the frame src 
attributes in the second level of framesets are not being rewritten correctly.

The application runs correctly when it is in the default module. The three changes I 
made to move it from an explicit module to the default module were (1) change web.xml 
so that the init-param for the explicit module is commented out, (2) change web.xml to 
add a comma and the struts-config file path to the default module's param-value, and 
(3) move the jsp's physical location up one level in the directory tree, out from 
under the directory named for the explicit module.

Searching the archives with marc turned up nothing about modules and frames. I'm 
hoping someone has some experience or theory to share.

I am running struts 1.1b3 on Tomcat 4.1.18 in eclipse 2.1. Here is the 
post-move-back-to-default-app relevant section from my web.xml:


  config
  
/WEB-INF/struts-config.xml,/WEB-INF/struts-config-dt.xml



Let me know if there is any additional information I can provide to help you diagnose 
my problem.

Thanks,

Derek Richardson

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]