- Zope-Dev - Zope lists

Zope 2.9 and Soap
by Michael Johnson 18 Dec '06

18 Dec '06

I've seen work with ZSI and Zope3 which provides soap views for objects. I was wondering what the preferred way for handling Soap with Zope 2.9.x is? I've seen a Soap product on the Zope.org site which uses SoapPy as well as some work done for Cignex by Benjamin Saller. Both of these require patches to core code. Any chances of adding minimal Soap support at the publisher level (or suggesting an approach)? Thanks, Michael Johnson

1 0

Merging buildout/egg from ZODB 3.7 into trunk?
by Sidnei da Silva 18 Dec '06

18 Dec '06

Jim recently added buildout/egg support into ZODB 3.7 branch. Should that be merged into trunk? -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

2 1

Zope Tests: 7 OK
by Zope Tests Summarizer 18 Dec '06

18 Dec '06

Summary of messages to the zope-tests list. Period Sun Dec 17 12:00:00 2006 UTC to Mon Dec 18 12:00:00 2006 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.6 Python-2.1.3 : Linux From: Zope Unit Tests Date: Sun Dec 17 21:05:26 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006845.html Subject: OK : Zope-2.6 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Dec 17 21:06:56 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006846.html Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Dec 17 21:08:26 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006847.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Dec 17 21:09:56 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006848.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Dec 17 21:11:26 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006849.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Dec 17 21:12:57 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006850.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Dec 17 21:14:27 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006851.html

1 0

[Zope 2.10/ZPT] Fixes for encoding and webdav issues
by Andreas Jung 18 Dec '06

18 Dec '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've created a branch svn+ssh://svn.zope.org/repos/main/Zope/branches/ajung-zpt-encoding-fixes that should fix several encoding and webdav issues that unfortunately were discovered before the final 2.10 release. What has changed? Until Zope 2.10 the ZopePageTemplate class had no notion of an encoding. You could upload ascii, iso-8859-15, utf8...or whatever...everything has been stored as a Python byte string. For backward compatibility we did not convert the data into Python unicode strings with the introduction of the Zope 3 ZPT implementation. Although the ZopePageTemplate implementation already had a 'strict' flag (to enforce the conversion to Python unicode) the Zope 2 implementation did not enforce unicode as storage for a ZPT. This caused several encoding problems when editing a ZPT through the ZMI and in addition the WebDAV support was broken in Zope 2.10.0 and Zope 2.10.1. A ZPT has now something as an output_encoding. When you create a ZPT through the ZMI you'll be asked about the encoding (which is utf8 by default). The pt_render() method now converts the internal unicode representation back to the output encoding. This is basically the behavior of the old ZPT implementation. In addition the __call__() method sets the 'charset' property of the content-type header according to the configured output encoding. WebDAV: the PUT factory was using the write() method to store uploaded content. This method wasn't aware of the output encoding. PUT() now uses pt_edit(). This implies that the uploaded content must have the same encoding as the output encoding. Means: when you create a ZPT with encoding UTF-8 you can't upload new content with a different encoding. This is a slightly different behavior from older Zope versions and might break backward compatibility. Anyone having such a usecase? One might check in addition for the 'encoding' attribute inside the XML preamble or for the 'charset' property inside a <meta http-equiv="content-type" ..> tag for HTML documents. Any objections merging the changes on the head after further polishing and writing some more test? Andreas - -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info(a)zopyx.com - Phone +49 - 7071 - 793376 E-Publishing, Python, Zope & Plone development, Consulting -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (Darwin) iD8DBQFFhWvECJIWIbr9KYwRAg5xAJ9LEYbyy2TCrKj1b4VUcqE90qqqkwCeLr6B F3YYBC8V2oPEaOq1xH1FeFg= =68R/ -----END PGP SIGNATURE-----

2 3

Zope Tests: 7 OK
by Zope Tests Summarizer 17 Dec '06

17 Dec '06

Summary of messages to the zope-tests list. Period Sat Dec 16 12:00:00 2006 UTC to Sun Dec 17 12:00:00 2006 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.6 Python-2.1.3 : Linux From: Zope Unit Tests Date: Sat Dec 16 21:07:21 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006838.html Subject: OK : Zope-2.6 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Dec 16 21:08:51 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006839.html Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Dec 16 21:10:22 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006840.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Dec 16 21:11:52 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006841.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Dec 16 21:13:22 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006842.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Dec 16 21:14:52 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006843.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Dec 16 21:16:22 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006844.html

1 0

Zope Tests: 7 OK
by Zope Tests Summarizer 16 Dec '06

16 Dec '06

Summary of messages to the zope-tests list. Period Fri Dec 15 12:00:00 2006 UTC to Sat Dec 16 12:00:00 2006 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.6 Python-2.1.3 : Linux From: Zope Unit Tests Date: Fri Dec 15 21:08:16 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006831.html Subject: OK : Zope-2.6 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Dec 15 21:09:46 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006832.html Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Dec 15 21:11:16 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006833.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Dec 15 21:12:46 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006834.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Dec 15 21:14:16 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006835.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Dec 15 21:15:46 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006836.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Dec 15 21:17:16 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006837.html

1 0

Zope Tests: 7 OK
by Zope Tests Summarizer 15 Dec '06

15 Dec '06

Summary of messages to the zope-tests list. Period Thu Dec 14 12:00:00 2006 UTC to Fri Dec 15 12:00:00 2006 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.6 Python-2.1.3 : Linux From: Zope Unit Tests Date: Thu Dec 14 21:06:23 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006824.html Subject: OK : Zope-2.6 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Dec 14 21:07:54 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006825.html Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Dec 14 21:09:24 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006826.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Dec 14 21:10:54 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006827.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Dec 14 21:12:24 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006828.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Dec 14 21:13:54 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006829.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Dec 14 21:15:24 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006830.html

1 0

Zope Tests: 7 OK
by Zope Tests Summarizer 14 Dec '06

14 Dec '06

Summary of messages to the zope-tests list. Period Wed Dec 13 12:00:00 2006 UTC to Thu Dec 14 12:00:00 2006 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.6 Python-2.1.3 : Linux From: Zope Unit Tests Date: Wed Dec 13 21:07:39 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006817.html Subject: OK : Zope-2.6 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed Dec 13 21:09:09 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006818.html Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed Dec 13 21:10:40 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006819.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed Dec 13 21:12:10 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006820.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Dec 13 21:13:40 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006821.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Dec 13 21:15:10 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006822.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Dec 13 21:16:40 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-December/006823.html

1 0

ZopeVersionControl bug
by Rob Miller 14 Dec '06

14 Dec '06

is there a current maintainer or development process for ZopeVersionControl? there's been a little bit of activity lately, but it's still in CVS. in any event, CMFEditions (a versioning system for Plone) depends on ZVC, and it seems that some recent changes to Zope's DateTime implementation have caused a ZVC bug to come to the surface. dorneles has recently improved the ISO8601 support in the DateTime module (http://tinyurl.com/y9weck) one of the results is that DateTime('1') now is interpreted similarly to DateTime(1), whereas before it would raise an error. in ZVC's Repository.getVersionOfResource() method (http://tinyurl.com/yab2xw) a selector is passed in, which the method will try to use in a number of ways before deciding that there's no matching version to return. the final test looks like this: try: date = DateTime(selector) except: raise VersionControlError( 'Invalid version selector: %s' % selector ) else: ... RETRIEVE BY TIMESTAMP HERE thus the change in DateTime behaviour means if the selector is a string representation of an integer, it formerly would have been rejected as invalid, but now will be considered a timestamp lookup. since version ids are commonly string representations of integers, this can be a bit of a problem. i'm not sure whether the DateTime behaviour should be reverted, or if there should be a change in ZVC. and i'm also not sure what's going on w/ ZVC's maintenance... are there any plans to bring it over to subversion? i'm happy to commit a fix, if someone can point me in the right direction. thx, -r

3 2

Moving ZopeVersionControl to subversion?
by Wichert Akkerman 13 Dec '06

13 Dec '06

I noticed that ZopeVersionControl is still actively maintained in CVS. Would its maintainers mind moving it to subversion? That would make it a lot easier for us to include it in the Plone 3.0 bundle. Wichert. -- Wichert Akkerman <wichert(a)wiggy.net> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple.

6 8