Thanks, Thierry.
I think the real problem with ZCA and ZCML is "bad press". We did not face
any ZCML problem when we worked on the Zope3 projects. It was later,
thankfully, that we came across the negative opinion. ZCA did require a
mindset change for some, but more often than not it has helped them in
their future work on other platforms too.
But that was 10 years ago... Don't know about now.


On Sun, Sep 7, 2014 at 11:43 AM, Thierry Florac <> wrote:

> Hi,
> Le Sun, 7 Sep 2014 09:26:43 +0530,
>   Milind Khadilkar <> a écrit:
> > Seems there will be no Zope4. Puts a fond hope to rest.
> >
> > I have one large Zope2 (Zope 2.6) project, one large Zope3 (Zope 3.4)
> > project, two medium sized Grok projects, one GAE project, allof them
> > need to be maintained beyond two years.
> > I would like, if possible, to redevelop them using ONE single
> > framework. While some of the original developers are available, most
> > work would need to be done through people who need to be trained from
> > the ground up.
> >
> > My first choice (mainly because I have a complex Zope3 project to
> > redevelop) would be Bluebream, even if it means using ZCML and
> > programming in ZCA-shackles. But I am speaking without any real
> > experience of it. (Negative press ensured that I did not go for it...)
> >
> > Any suggestions?
> If you are considering a complete re-development, maybe you should have
> a look at Pyramid.
> It allows you to reuse a lot of Zope related technologies, including
> ZODB, traversing and even ZCA ! ;-)
> I use and develop ZTFY which is based on Bluebream (with updated
> packages based on ZTK) and which is used in many of my own projects
> with great success, but which is probably condamned to death in a
> relatively near future...
> Regards,
> Thierry
> P.S.: by the way, I don't really understand where is the real problem
> with ZCA (which is so powerful, and not so complicated!) and with ZCML
> (which is nothing in XML files terms compared to any "serious" Java
> server development environment...)
Zope3-users mailing list

Reply via email to