right. I fixed this last week for the upcoming final release. Thanks for
reporting anyway!
Pierre-Yves Saumont wrote:
If you follow the tutorial, you will end with two blocks containing the
same classes and the same beans (same id). In that case, no one can tell
which class and which bean is used. In my case, bean from one block is
injected with the property of the other block. Of course, as the two
classes and the two property values are the same, no one can notice
anything. But if you customise the two classes and the two property
values, you will get very strange results!
Reinhard Poetz a écrit :
Pierre-Yves Saumont wrote:
Yes, this is correct. Cocoon 2.1 was based on Avallon. Spring is
definitely a much better option. There is a tutorial for version 2.2
with a Spring example. But be carefull, if you follow the tutorial,
you will have a very buggy example. (But a working one!)
What do you mean by buggy?
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair [EMAIL PROTECTED]
_________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
