Grzegorz Kossakowski skrev:
Daniel Fagerstrom pisze:
Grzegorz Kossakowski skrev:
...
I think we make the servlet: protocol unnecessarily complicated if we
try to overload it with webapp global interpretations as well.
But we need to do that way. If Source returns globally unique URI it
means that is must handle it. That's why we must implement block id
handling in the servlet: source.
And as I asked before, how does the URI parser given e.g.
"servlet:foo/bar" know is "foo" is a servlet service local id or a
Spring bean id?
It should try both options or we could could introduce some syntax that
makes it easy to distinguish these two cases.
Trying both options is asking for hard to find bugs. Remember, we have
no control whatsoever of how users are going to chose bean ids and
servlet service connection names. The only thing we can be certain about
is that subtle clashes will happen and complicate life for our users.
A syntax that distinguishes the two cases is a must. Having a special
protocol (like the servlets: one) is one possibility, but maybe we could
find some sub syntax for the servlet: protocol.
/Daniel
