Leszek Gawron skrev:
Daniel Fagerstrom wrote:
Leszek Gawron skrev:
Joerg Heinicke wrote:
On 03.11.2006 23:17, Carsten Ziegeler wrote:
With the help from Leszek we now have a Cocoon version in trunk which
does not need any deployment plugin. This means you can just drop the
jar files into WEB-INF/lib and are done! So it doesn't matter if
you're
using Maven, Ant or some other strange tool :)
All you need is the main Spring applicationContext.xml with our two
elements for setting up Cocoon and the Avalon bridge.
Thanks very much for your efforts. I highly appreciate everything
easing the usage of Cocoon.
Once we have solved these three issues we should release a RC-1 asap.
+1
I still would like 2 things resolved (maybe not directly fixed but at
least addressed somehow):
- running cocoon without servlet context
The far easiest way to achieve this is to create a mock servlet
context. Only a handful of methods needs implementation that require a
non null answer.
Looks it's not that easy after all. My current implementation:
Might be that it will not that easy to create a mock servlet context
that contain exactly what is needed for creating beans in a
XmlWebApplicationContext. In my experience getting the different context
used within Cocoon is never easy. But I can assure you that creating a
mock servlet context is a much simpler solution to the problem that you
want to solve than refactoring Cocoon so that it doesn't depend on
having a servlet context available.
We should of course provide a mock servlet context so that users doesn't
need to implement one themselves.
For the particular problem you get, I would need to see what the
malformed URL looks like to have any clue about what goes wrong.
/Daniel
