> -----Original Message-----
> From: Ted Husted [mailto:[EMAIL PROTECTED]]
> 11/22/2002 1:26:45 PM, "Nelson, Laird" <[EMAIL PROTECTED]>
> wrote:
> >Is my company unique in trying to do
> >things this way?
>
> Probably not, but Struts hasn't been trying to be all things to
> all people. =:0)
>
> It does what the people working on it need it to do, and if it
> doesn't do what we need, then we work to change it. But we're not
> sitting around a whiteboard trying to figure out the best way to
> capture market share.
(Sorry; my previous message wasn't intended to be whiny. I just wondered
whether what we were doing warranted my digging further or if I should just
let Struts be and keep our patches in house. It sounds like the
multiple-servlet-mapping thing that we're doing to keep our reporting folks
happy is fairly unique and nasty.)
> Struts does restrict what URIs you can map to an Action. The
> underlying issue, as Craig pointed out, is that the Action path is
> not a truly logical identifier. It's a hash based on the URI that
> Struts munged and demunges.
Isn't it just pathinfo (in the case of prefix mapping, not extension
mapping)? Or is there a section of the code besides processPath() I should
be looking at?
> There are of course other ways we could link up actions and URIs,
> but that would be something we'd explore in the Struts 2.0 frame.
One thing I was looking at on an earlier project was setting up the action
mappings section of the struts-config.xml file to be able to switch not only
off of URL fragments like pathinfo but also the presence or absence of
certain attributes in various scopes. Interestingly, of course, Struts
offers XML tags that test for the presence or absence of such
attributes--wouldn't it be twisted and awful and cool to use those tags in
the action-mappings section?
So you could say (warning; unchecked syntax but you get the idea):
<action-mappings>
<logic:present name="loggedIn" scope="session">
<action ... />
</logic>
</action-mappings>
Anyway, just brainstorming. Thanks as always for your (and Craig's) time
and input.
Cheers,
Laird (at work on a Saturday :-( )
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
