struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Mitchell" <jmitch...@apache.org>
Subject Re: Compartmentalization of Modules (was Re: [18111] et al)
Date Thu, 22 Jan 2004 21:18:28 GMT
> <html:link module="exercise" action="welcome" />

I don't think that's the best idea.  Doing that means your pages know they
are in a particular module.  If I were to begin using them again, I like the
idea of being able to use (dare I say 'share') a single jsp in several
different Modules.  So you'll get a different looking (and acting) page but
you don't have to copy the jsp into that modules folder.  It simply renders
the images, css, scripts, etc, etc for the Module that it happens to be used
in.  Does that make sense?

If this needs more explanation, I can put something together that shows the
difference.


--
James Mitchell
Software Engineer / Struts Evangelist
http://www.struts-atlanta.org
678.910.8017 (cell)
AIM:jmitchtx
MSN: jmitchell@apache.org



----- Original Message -----
From: "Ted Husted" <husted@apache.org>
To: "Struts Developers List" <struts-dev@jakarta.apache.org>
Sent: Thursday, January 22, 2004 1:29 PM
Subject: RE: Compartmentalization of Modules (was Re: [18111] et al)


On Thu, 22 Jan 2004 01:00:55 -0600, Gary D Ashley Jr. wrote:
> .e.:  <html:link action="" module="" ...
>
>
> It seemed that if you have action="" attribute, then module="" was
> the next logical step with making struts modular.  For us, it
> certainly helped provide the glue in a very large data centric
> struts application. Large obviously relative to my situation, so
> more specifically: 20 modules, 10 state/local government agencies,
> 30 roles, 10,000 users (250 core 9am-5pm users), and 6 developers.
>
> It seems modular link and rewrite tags are a nice step in the right
> direction.  Well, just one perspective to consider.
>
> Thanks.

Well, that's an interesting idea:

<html:link module="exercise" action="welcome" />

versus

<html:link action="/exercise/welcome" moduleRelative="false" />

The former does seem cleaner to me.

The trick being that the default value for module is the current module :)

If you've implemented one like this, tell me, where there any issues about
using

<html:link module="" action="welcome" />

To indicate the "unnamed" default module?

-Ted.




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


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


Mime
View raw message