Ted Husted wrote:
> 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?
I never actually tested attempting to link to the default module. The
implementation I use is based on the 1.1 release, and I changed the
computeUrl method in RequestUtils. Essentially:
moduleConfig = (ModuleConfig)
pageContext.getServletContext().
getAttribute(Globals.MODULE_KEY+modulePrefix);
If the default module was stored under Globals.MODULE_KEY, then it would
have been found.
I would agree that using module="" would point to the default module.
> Would we also want module links to check the default module before
going
> "unknown" (404)?
+1 to the idea of checking the default module (and maybe the current
module) if the supplied module / action pair could not be found before
giving 404.
A side note:
I did submit some code in late October based on the most recent nightly
build at the time, but I had combined the concept of checking roles with
it. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24235 As I am
freed up today, I'd be happy to convert this over to the latest CVS
branch if that'd help.
> -Ted.
Gary
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
