Daniel Fagerstrom wrote:
I think we make the servlet: protocol unnecessarily complicated if we
try to overload it with webapp global interpretations as well.
agreed
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?
no chance to distinguish between them, IMO.
<snip/>
But there are important use cases for run time discovery of servlet
services as well.
definitly. For the use cases that *I* have, a generator will be good enough - I
don't think that I need a source for them:
<map:generate type="servlets" src="data/myconfig.xml"/>
This could return something like this:
<servlets>
<service-A>
<config>...</config>
</service->
<service-B>
<config>...</config>
</service-B>
</servlets>
What are the usecases for implementing a servlets: protocol at all? (Maybe I'm
overlooking something important here ...)
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
