Carsten Ziegeler wrote:
Daniel Fagerstrom wrote:
People, there seem to be some myths about that the trunk is unstable and
that it doesn't work anymore. And that I and other people have
unstabilized it beyond recognitions with the work on the blocks
architecture.
I cannot speak for
I just committed initial support in Felix for exploded bundle
directories as well as referenced bundle JAR files.
Regarding some of the other issues mentioned below by Daniel, I cannot
think of any major things that would prevent Felix from being used in a
servlet container. I know other
Carsten Ziegeler schrieb:
Daniel Fagerstrom wrote:
So the problems this far seem to be that default types not are handled
in a back compatible ways for component includes and that components are
not inherited properly to subsitemaps.
Hopefully Carsten have an idea about what is going on.
I'm trying to get the blocks fw working again after the switch to
Spring. It doesn't seem to be particularly easy as the tree processor
now is sprinkled with concrete references to
CocoonXmlWebApplicationContext which in turn extends the
Daniel Fagerstrom wrote:
I'm trying to get the blocks fw working again after the switch to
Spring. It doesn't seem to be particularly easy as the tree processor
now is sprinkled with concrete references to
CocoonXmlWebApplicationContext which in turn extends the
Carsten Ziegeler skrev:
Daniel Fagerstrom wrote:
...
I'm completely against having the treeprocessor hardwired to that freak
class. The treeprocessor should depend on a (small) interface that
describe what it actually need from its container.
Yeah, sure. The tree processor has a long history
Guys,
I want to get my hands on the new Dojo stuff, so I checked out the
latest version of the branch(! not trunk!). I ran into this:
- after a full build all flow-based cforms samples produce the same
error [1]
- my forms produce an error
(map:call continuation did not send a response).
On 25/02/06, Carsten Ziegeler [EMAIL PROTECTED] wrote:
Carsten Ziegeler schrieb:
Daniel Fagerstrom wrote:
So the problems this far seem to be that default types not are handled
in a back compatible ways for component includes and that components are
not inherited properly to subsitemaps.
You said you did a check-out. Did you do a clean check out or an update?
hepabolu wrote:
Guys,
I want to get my hands on the new Dojo stuff, so I checked out the
latest version of the branch(! not trunk!). I ran into this:
- after a full build all flow-based cforms samples produce the same
