zope3 and zope.conf without the zodb

--===============0902132992==
Content-Type: multipart/alternative; 
	boundary="----=_Part_6942_12760994.1193855524508"

------=_Part_6942_12760994.1193855524508
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I've been using zope3 as a wsgi app, without a zodb. it bypasses the zodb
publishing traversal via replacement of the published application, all of
which can be managed in zcml.

One issue I've run into is configuring an app through zope.conf forces you
to have an open zodb, because of the required attribute in zope.app.appsetup
schema.xml

Allowing zope3 usage without a zodb attached, is basically a one line fix
here. Would there be any objections to removing it?

cheers,

kapil

------=_Part_6942_12760994.1193855524508
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I&#39;ve been using zope3 as a wsgi app, without a zodb. it bypasses the zodb publishing traversal via replacement of the published application, all of which can be managed in zcml. <br><br>One issue I&#39;ve run into is configuring an app through 
zope.conf forces you to have an open zodb, because of the required attribute in zope.app.appsetup schema.xml<br><br>Allowing zope3 usage without a zodb attached, is basically a one line fix here. Would there be any objections to removing it?
<br><br>cheers,<br><br>kapil<br><br><br><br>

------=_Part_6942_12760994.1193855524508--

--===============0902132992==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline