changes pageContext's module

[Leonardo Quijano Vincenzi <lq...@hotpop.com>]

Hi Everybody  (i'm resending this because I think it didn't get to the 
mailing list the first time)

I recently put a bug report in BugZilla 
(http://issues.apache.org/bugzilla/show_bug.cgi?id=18887) about Tiles 
changing the active module when it inserts a definition with a 
controller URL. I'm continuing the discussion here to see what everybody 
thinks.

To put you on track:
1) <tiles:insert> is "destructive" with the application state. It 
changes the active module for the pageContext. I don't know it this is 
such a good thing even if we want to keep independent modules in our code.
2) David Graham wrote

"IMHO, the independent nature of modules is a good thing.  I can plugin 
a forums
module to my app without changing any other modules, files, code, etc.  
If you
want to continue this discussion, please post to the struts-dev mailing 
list.  Bugzilla is an awkward tool for discussion :-)."

So, you are saying is good that modules are independent because we can 
"turn them on" and start using them. So is a WAR. Aren't we reinventing 
the wheel? After all, if I wanted to plugin a forums module into my app 
without changing existing code, I just copy the WAR file to Tomcat's 
webapp dir and I'm all set.

3) Modules interoperation *is* a good thing. I might have a "clients" 
module, which in turn could be used from the "sales" module to show 
common forms, or show data. That promotes code reuse, I think. If I 
wanted the same functionality with isolated modules, I'd had to copy the 
clients JSPs to all the other modules.

Leonardo





---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org