Daniel Fagerstrom pisze:
Grzegorz Kossakowski skrev:
Daniel Fagerstrom pisze:
So would it be possible to access resources via servlets: source (by
using internally a servlet: source) or not?
I think that should be possible. URIs could look like:
servlets:/<bean id>/<internal path>
I wonder why we really need new source in this case at all. Possibility to reference bean by bean id instead of connection name was already
discussed: https://issues.apache.org/jira/browse/COCOON-2044
Why do we need to invent new source?
After having a list of servlets we would have to find out which one
contain samples. I guess that it's good idea to ask every servlet for
certain resource (e.g. samples.xsamples file).
Yes.
But how we do this not being connected to all these servlets?
As Giacomo suggested it could be done by making the list from
o.a.c.servletservice.DispatcherServlet#createMountableServletsMap
available in a Spring bean. Another possibility would be to let the
blocks source depend on a bean map
http://svn.apache.org/repos/asf/cocoon/trunk/core/cocoon-configuration/cocoon-spring-configurator/src/main/java/org/apache/cocoon/spring/configurator/impl/BeanMap.java
that collects all beans that implement Servlet.
Do you mean that servlet will be able to construct it's connection at runtime or it will be able to reference resources from servlets that
it is not connected to?
Does second option fits to our design of servlet-service-fw?
--
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/
