Hi all,
catching up - somewhat over a week ago Scott sent me two patches to make
ServletConfiguration work again:
Scott Finnerty wrote:
> I was wondering if you've had a chance to look at the patches I sent you
> addressing the BasicServletConfiguration issue? Any comments? I've been
> using my cooked version of cayenne with the changes for a bit now and have
> not run into any issues.
Unfortunately, apart from a brief look I've had _zero_time to work on this
(and the Configuration doc updates - yeah blame me) but being away, flaky
email for several days and much, much more pressing things were simply not
helpful. I have all the time in the world starting the weekend after the
25th (next week Friday). Andrus, can we delay beta1 until then? I don't
think it would be a good idea to release beta1 with outdated config
instructions. Here's two things to discuss in the meantime:
- while looking over Scott's patches it occurred to me that I do not
really understand the separation between BasicServletConfiguration and
ServletConfiguration. Shouldn't we merge the two into one working, instead
of two that both don't work anymore and somehow seem to be linked together
for no (?) good reason?
- Scott, you introduced a new parameter cayenne.configuration.path - why?
It seems to add a search path to the RL and comes from the ServletContext.
Is this a common way to configure Servlet apps? (I really don't know). The
previous ServletConfig works without external parameters (always a good
cause for setup difficulties) and I'd like to keep it that way, simply
because it's IMHO yet another thing that people will most likely get
wrong. This was one of the ideas behind the ResourceLocator, as I
understood it. It seems to work without, if I read the code correctly.
I can apply & commit the patches so that everybody else can look at and
comment on them in the meantime. Would that help?
Holger
This archive was generated by hypermail 2.0.0 : Fri Apr 18 2003 - 06:57:25 EDT