I am doing the same with ant/build process, is there any aother way? Is
there a way to keep these files in a acommon place?
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Τρίτη, 1 Ιουλίου 2003 6:15 πμ
To: 'Struts Users Mailing List'
Subject: RE: Modules
> Thanks Wendy, but the situation is a little different. They are common
> resources, not necessarily static resources.
Hmmm... in that case, I'd maintain them in one place in the source tree and
use the build process to put copies everywhere they're needed. Disk space
is cheaper than maintaining
quot; <[EMAIL PROTECTED]>
To
'Struts Users Mailing List' <[EMAIL PROTECTED]>
cc
Subject
RE: Modules and common files
Geoff wrote:
> We have just started using modules and have run into a problem when it
> comes to common files between the modules (eg: javascript
Geoff wrote:
> We have just started using modules and have run into a problem when it
> comes to common files between the modules (eg: javascript, stylesheets,
images).
> Has anyone else had this problem? If so, what did you do?
I have Apache serve these static resources. For example, off the m
in the img tags or use page
URL patterns without $M for common files.
Jing
Netspread Carrier
http://www.netspread.com
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 30, 2003 2:32 AM
Subject: Modules and common files
> Hi,
>
I have not done it, but there are definitions in each
request processor that can tell whether or not paths
are relative. So the struts-config for the module has
a request processor element that has global
configuration info for the module.
sandeep
--- [EMAIL PROTECTED] wrote:
> Hi,
>
> We have j
Hi,
We have just started using modules and have run into a problem when it
comes
to common files between the modules (eg: javascript, stylesheets, images).
It
appears that all files required for a module must be in that module's
directory.
Which means that if all modules used the same styleshee
7 matches
Mail list logo
