> Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
> list-help: <mailto:[EMAIL PROTECTED]>
> list-unsubscribe: <mailto:[EMAIL PROTECTED]>
> list-post: <mailto:[EMAIL PROTECTED]>
> Delivered-To: mailing list [EMAIL PROTECTED]
> From: "Arshad Mahmood" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Subject: Re: Proposal for implementation of lookup of localized
web-resources
> X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N
>
>
> ----- Original Message -----
> From: "Arieh Markel" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Friday, March 16, 2001 3:00 PM
> Subject: Re: Proposal for implementation of lookup of localized
> web-resources
>
>
> >
> > > To: [EMAIL PROTECTED]
> > > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
> > > Subject: Re: Proposal for implementation of lookup of localized
> > web-resources
> > > From: [EMAIL PROTECTED] (Kazuhiro Kazama)
> > > X-Dispatcher: imput version 20000228(IM140)
> > >
> > > Arieh,
> > >
> > > Basically lookup of localized resources is welcomed. As I have
> > > evaluated your localization codes to 3.2, I write comments:
> > >
> > > 1, Your file-based naming scheme isn't compatible with apache
> > > MultiView function that David Rees and Takashi Okamoto says.
> > >
> > > Now apache naming scheme becomes popular in Japan. But almost nobody
> > > uses your naming scheme. It is unhappy that we must change all
> > > filename that is written by apache naming scheme.
> > >
> > > At the least, compatible option is needed.
> >
> > I don't think that my intent was to be compatible with Apache.
> >
> > My first goal was to be compatible with Java localization.
> >
> > The context in which I am using Jakarta is as an 'embedded' servlet
> > container inside of a Java application.
>
> This is something which I am currently in need of for a project. The only
> reason I can see support for the Apache model is that the new mod_webapp
> connector I believe is structured so that static html is served by Apache
> and the dynamic side by tomcat, under these circumstances it would be better
> if they were both the same.
>
> Having said that, my own preference for my current project is for a DocBase
> approach.
Arshad,
thanks for your comments.
The implementation does not enforce any default.
Initially, there are three optional lookup schemes:
a. no localization (do not set the localization attribute on
StaticInterceptor) - this is the default
b. docbase localization (set to "docbase")
c. file localization (set to "file")
As mentioned in a previous post, the mechanisms are in place to add
other localization schemes.
Arieh
PS: as an aside, I believe Apache would benefit with a docbase-like
localization scheme. The advantage is to preserve separation of
localized content (which makes it easier to manage, especially
when developing the content).
--
Arieh Markel Sun Microsystems Inc.
Network Storage 500 Eldorado Blvd. MS UBRM11-194
e-mail: [EMAIL PROTECTED] Broomfield, CO 80021
Pray for snow !!!! Phone: (303) 272-8547 x78547
(e-mail me with subject SEND PUBLIC KEY to get public key)
