On Mon, 16 Jun 2003, Carsten Ziegeler wrote:
Hi,
I think I found a showstopper for 2.1 :( :
2.1 is not binary compatible to 2.0.x - if you compile a (sitemap)
component using 2.0.x and put this into 2.1 it will in most cases
fail to run. As a simple example, you can use the
Stefano Mazzocchi wrote, On 16/06/2003 21.12:
on 6/16/03 1:20 AM Carsten Ziegeler wrote:
Hi,
I think I found a showstopper for 2.1 :( :
2.1 is not binary compatible to 2.0.x -
...
Why is this so? Well, the reason is the change from Loggable
to LogEnabled.
...
I think, mostly this affects own
Nathaniel Alfred wrote:
Yes, it's only recompiling - nothing more (well, at least in
theory :) )
Carsten
For non-trivial Cocoon sites the 2.0.x to 2.1 migration will require
more than just recompiling component classes.
There are incompatibilities on different levels. The ones I am
For non-trivial Cocoon sites the 2.0.x to 2.1 migration will require
more than just recompiling component classes.
There are incompatibilities on different levels. The ones I am aware of
are:
1.) sitemap.xmap must add map:pipes in components definition.
2.) File upload class name changed from
...maybe would introduce an ant task to upgrade current webapps?
ups.. I meant could ;)
--
Torsten
: Tuesday, June 17, 2003 3:10 PM
To: [EMAIL PROTECTED]
Subject: Re: Cocoon 2.1 showstopper?
Nathaniel Alfred wrote:
Yes, it's only recompiling - nothing more (well, at least in
theory :) )
Carsten
For non-trivial Cocoon sites the 2.0.x to 2.1 migration will require
more than just
So, from the response I guess we go for recompiling.
If someone is against this, please stand up now :)
Carsten
Nicola Ken Barozzi wrote:
Well, there is a way out, but I don't know if we want to do it. It's
based on - ok, I'll say that word - an AOP interceptor mechanism(hehehe
a big wording for a simple concept).
Basically, we would have to use our own classloader in the
ComponentManager, and make it
Carsten Ziegeler wrote:
Nicola Ken Barozzi wrote:
Well, there is a way out, but I don't know if we want to do it. It's
based on - ok, I'll say that word - an AOP interceptor mechanism(hehehe
a big wording for a simple concept).
snip/
Interesting idea - but does it work? Both
Hi,
I think I found a showstopper for 2.1 :( :
2.1 is not binary compatible to 2.0.x - if you compile a (sitemap)
component using 2.0.x and put this into 2.1 it will in most cases
fail to run. As a simple example, you can use the FileGenerator.class
from 2.0.x.
Why is this so? Well, the reason
At 02:20 AM 6/16/2003, you wrote:
Hi,
I think I found a showstopper for 2.1 :( :
2.1 is not binary compatible to 2.0.x - if you compile a (sitemap)
component using 2.0.x and put this into 2.1 it will in most cases
fail to run. As a simple example, you can use the FileGenerator.class
from 2.0.x.
Geoff Howard wrote:
At 02:20 AM 6/16/2003, you wrote:
Hi,
I think I found a showstopper for 2.1 :( :
2.1 is not binary compatible to 2.0.x - if you compile a (sitemap)
component using 2.0.x and put this into 2.1 it will in most cases
fail to run. As a simple example, you can use the
Yes, it's only recompiling - nothing more (well, at least in
theory :) )
Carsten
For non-trivial Cocoon sites the 2.0.x to 2.1 migration will require
more than just recompiling component classes.
There are incompatibilities on different levels. The ones I am aware of
are:
1.)
not be affected.
Are there any projects out there that fall through the cracks?
- Original Message -
From: Carsten Ziegeler [EMAIL PROTECTED]
To: Cocoon-Dev [EMAIL PROTECTED]
Sent: Sunday, June 15, 2003 11:20 PM
Subject: Cocoon 2.1 showstopper?
Hi,
I think I found a showstopper for 2.1
14 matches
Mail list logo
