|mart...@tumbleweed.com||Oct 10, 2001 11:07 pm|
|James Holmes||Oct 11, 2001 3:46 am|
|Young, Wayne||Oct 11, 2001 5:32 am|
|Curt Hagenlocher||Oct 11, 2001 6:31 am|
|SCHACHTER,MICHAEL (HP-NewJersey,ex2)||Oct 11, 2001 9:11 am|
|Craig R. McClanahan||Oct 11, 2001 10:35 am|
|mart...@tumbleweed.com||Oct 11, 2001 11:09 am|
|mart...@tumbleweed.com||Oct 11, 2001 11:25 am|
|Craig R. McClanahan||Oct 11, 2001 1:37 pm|
|Ted Husted||Oct 13, 2001 2:58 am|
|James Holmes||Oct 13, 2001 4:29 pm|
|mart...@tumbleweed.com||Oct 13, 2001 9:33 pm|
|mart...@tumbleweed.com||Oct 13, 2001 9:57 pm|
|Ted Husted||Oct 14, 2001 2:26 am|
|James Holmes||Oct 15, 2001 6:17 am|
|Petr Jiricka||Oct 16, 2001 5:30 am|
|mart...@tumbleweed.com||Oct 16, 2001 3:14 pm|
|Subject:||Re: [PROPOSAL] XMLMessageResources|
|Date:||Oct 16, 2001 3:14:23 pm|
In my particular case, I need more fine-grained control than this would give me. For example, the application I am building includes a main menu which contains items from all of the installed products. In some cases, I have tabbed pages where the tabs come from different products.
Separate web apps are too separate to support this (unless there's something I'm missing). However, I should be able to use a single Struts application, as long as I can load multiple config files (as well as multiples of other things).
As for using an EAR file, well, that would require that I switch to a full J2EE container to get that support. :-)
If I *am* missing something, and there is a way to do this kind of thing with separate WAR files, I'd definitely be interested in knowing more.
-- Martin Cooper
At 05:30 AM 10/16/01, Petr Jiricka wrote:
What is the advantage of having multiple struts-config files over a model where you develop multiple Web Modules (.war files) and distribute them together in an .ear file (per the J2EE specification) ? I think the goal of the Web Module design was to support exactly this scenario. How do you think the J2EE specification would need to be enhanced to conveniently support this case ?
Personally, I am firmly in the second camp (reading multiple config files). My reasoning is as follows.
I am working on a large project that will result in a common framework, and product modules which plug in to that framework. The common framework, and all of the product modules, will use Struts. Product modules can be installed and uninstalled by our customers.
Using some kind of 'include' mechanism solves the problem of different product teams stepping on each others' toes when editing the Struts configuration. However, it makes installation and uninstallation somewhat harder, because those applications will have to understand the structure of the Struts configuration file.
Using multiple configuration files allows me to have one config file for the common framework, and then one more for each product. Each product team can concentrate on its own config file, and the installer and uninstaller only have to worry about which files to add or remove, and not about what they contain or how to modify them.
-- Martin Cooper
It seems there has been some discussion in the past about a new config file DTD that would support having "multiples" so that individuals could work on a particular section without affecting others. It seems there is also the camp that would rather just have the servlet read multiple config files. I am indifferent (at this point) to which solution i think should be adopted, but think that Struts could certainly be more "team development" friendly by choosing one and then offering it. I have some extra bandwith and would like to get involved in the "core" struts development. Craig/Ted/Others, I'd be happy to develop one or both. I guess I'd like to know what people want to see developed and what has the highest likelyhood of being incorporated into Struts and I will develop it.
What about the whole debate on multiple ActionServlets per WAR? If I were to "solve" this would this be something that could go into the core?
--- Ted Husted <hus...@apache.org> wrote:
Can we join this with the idea of having multiple Struts configuration files, or, on a related front, multiple workflow configuration files?
The Struts 1.1 TODO list contains the following item:
"XmlMessageResources. Implementation of MessageResources and MessageResourcesFactory that loads message keys and strings from one or more XML resources or files."
I have an implementation of this which I would like to contribute to Struts. The implementation is a drop-in replacement for the existing PropertyMessageResources. In fact, it is derived from it, and so shares the same file naming scheme for locale-specific
"SCHACHTER,MICHAEL (HP-NewJersey,ex2)" wrote:
In the jakarta-commons-sandbox, there's a folder called "resources" containing Struts MessageResources and some other classes that I was working on, but had to put off for a while.
__________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com