----- Original Message -----
Sent: Saturday, October 19, 2002 5:17
AM
Subject: Re: [Tapestry-developer] Re:
bugs
Sorry, I guess I never sent the reply to this
message, even though I wrote it.
I never intended services to support
namespaces; they are rarely used enough that using qualified names
(foo.bar.baz.myservice) is reasonable.
Hmm. I think it is quite likely for two unreleated people to write two
services with the same name (possibly doing the same thing, but having
different incompatible implementations). This can happen within the same
company, and it can certainly occur if components are exchanged within the
community (component A uses implementation X, component B uses implementation
Y; if you want to use both, you are in trouble). While services are certainly
rarer than pages, I do not think they are rare enough to ignore that
possibility. Just as an example, we would have had a similar situation at
least on one occasion in our company, but we found the duplication early
enough to standardize on one of the implementations.
BTW ... what is you app?
We have a number of intranet applications that we sell. Obviously, there is
a lot of common between them, so we have organized such functionality into
libraries (five or six at present count, I believe). We have three levels of
library nesting at places -- library A (content management) uses library B
(common components) uses Contrib. Hence the need we had for the fix :-). Btw,
please let me know whether I should check it in.
I will add a bug about the error messages shortly.
-mb
Do you Yahoo!?
Y! Web Hosting -
Let the expert host your web site
