May 2000 - Zope-Dev - Zope lists

ZSQL Methods
by David Cooper 25 May '00

25 May '00

Using ZSQLMethods against an ORACLE 8.0.6 Database. I have two tables, each with a NUMBER(6) key field. If I create a method which selects against each of the tables then method returns an integer (e.g. 5040), as expected. select index_number from names where name = 'name' or select index_number from aliases where alias = 'name' If I attempt to get the combined list select index_number from names where name = 'name' union select index_number from aliases where alias = 'name' I get a float back (e.g. 5040.0). Is this expected/correct? If so how do I force it to return the integer. David Cooper dcooper(a)nosc.mil

1 0

Ending up with a wrapped object through the web?
by Kevin Dangoor 25 May '00

25 May '00

I'm trying to import KM|Net News into the latest Zope CVS. I am unable to import the .zexp or XML files into the latest (tracebacks at the end). When importing the .zexp, I get an "Attempt to store a wrapped persistent object" error. This is really puzzling, because I'm not sure how a completely through-the-web Product would have a wrapped object stored in it. I tried removing the PythonMethods to see if they were stored in an unusual way, and this did not change the behavior... Does anyone have any ideas about this? It's very odd and could be a major nuisance for people who are trying to move things between 2.1.x and 2.2... Kevin The .zexp gives this error: Error Type: InvalidObjectReference Error Value: Attempt to store a wrapped persistent object Traceback (innermost last): File /home/kid/Zope2/lib/python/ZPublisher/Publish.py, line 224, in publish_module File /home/kid/Zope2/lib/python/ZPublisher/Publish.py, line 189, in publish File /home/kid/Zope2/lib/python/Zope/__init__.py, line 221, in zpublisher_exception_hook (Object: ElementWithAttributes) File /home/kid/Zope2/lib/python/ZPublisher/Publish.py, line 179, in publish File /home/kid/Zope2/lib/python/ZODB/Transaction.py, line 237, in commit File /home/kid/Zope2/lib/python/ZODB/Connection.py, line 347, in commit (Info: (('OFS.Application', 'Application'), '\000\000\000\000\000\000\000\002', '')) InvalidObjectReference: (see above) The XML generated by 2.1.6 gives this error: Error Type: TypeError Error Value: ('not enough arguments; expected 2, got 1', <extension class ZClasses.Method.MW at 834bc68>, ()) Traceback (innermost last): File /home/kid/Zope2/lib/python/ZPublisher/Publish.py, line 224, in publish_module File /home/kid/Zope2/lib/python/ZPublisher/Publish.py, line 189, in publish File /home/kid/Zope2/lib/python/Zope/__init__.py, line 221, in zpublisher_exception_hook (Object: ElementWithAttributes) File /home/kid/Zope2/lib/python/ZPublisher/Publish.py, line 175, in publish File /home/kid/Zope2/lib/python/ZPublisher/mapply.py, line 160, in mapply (Object: manage_importObject) File /home/kid/Zope2/lib/python/ZPublisher/Publish.py, line 112, in call_object (Object: manage_importObject) File /home/kid/Zope2/lib/python/OFS/ObjectManager.py, line 506, in manage_importObject (Object: ElementWithAttributes) File /home/kid/Zope2/lib/python/ZODB/ExportImport.py, line 216, in importFile File /home/kid/Zope2/lib/python/ZODB/ExportImport.py, line 318, in importXML File /home/kid/Zope2/lib/python/ZODB/ExportImport.py, line 283, in importFile TypeError: (see above) http://www.byproducts.com - Humor and Novelties

1 0

ZCatalog and Unique IDs
by Chris Withers 25 May '00

25 May '00

Hi, I hope this is a stupid question but why does ZCatalog use the URL of an object to uniquely identify it? Why not just use a reference to the object? Persistent object identifiers must exist for the ZODB so why not use them instead? cheers, Chris PS: This would solve all the problems with ZCatalogs and virtually hosted sites... I think the traversal interface is needed for other reasons but it should remove ZCatalog from the list of things that need it... not that I've just been bitten by this or anything ;-)

4 11

another validation problem
by Robin Becker 25 May '00

25 May '00

The latest CVS version is giving autorization demands (and failures) with this DTMLmethod. This kind of construct used to work fine. <dtml-var standard_html_header> <h2><dtml-var title_or_id> <dtml-var document_title></h2> <dtml-with "_.namespace(SUB=[1,2])"> <dtml-if "_.len(SUB)>0">non-empty<dtml-else>empty</dtml-if> </dtml-with> <dtml-var standard_html_footer> Zope Error Zope has encountered an error while publishing this resource. Unauthorized Sorry, a Zope error occurred. Traceback (innermost last): File C:\Python\devel\Zope\lib\python\ZPublisher\Publish.py, line 224, in publish_module File C:\Python\devel\Zope\lib\python\ZPublisher\Publish.py, line 189, in publish File C:\Python\devel\Zope\lib\python\ZPublisher\Publish.py, line 175, in publish File C:\Python\devel\Zope\lib\python\ZPublisher\mapply.py, line 160, in mapply (Object: xxx) File C:\Python\devel\Zope\lib\python\ZPublisher\Publish.py, line 112, in call_object (Object: xxx) File C:\Python\devel\Zope\lib\python\OFS\DTMLMethod.py, line 164, in __call__ (Object: xxx) File C:\Python\devel\Zope\lib\python\DocumentTemplate\DT_String.py, line 500, in __call__ (Object: xxx) File C:\Python\devel\Zope\lib\python\DocumentTemplate\DT_With.py, line 146, in render (Object: _.namespace(SUB=[1,2])) File C:\Python\devel\Zope\lib\python\DocumentTemplate\DT_Util.py, line 327, in eval (Object: _.len(SUB)>0) (Info: SUB) File C:\Python\devel\Zope\lib\python\OFS\DTMLMethod.py, line 184, in validate (Object: xxx) File C:\Python\devel\Zope\lib\python\AccessControl\SecurityManager.py, line 139, in validate File C:\Python\devel\Zope\lib\python\AccessControl\ZopeSecurityPolicy.py, line 160, in validate Unauthorized: SUB -- Robin Becker

2 2

Re: [Zope-dev] XML to SQL or XML into tables
by Dieter Maurer 25 May '00

25 May '00

Kent Polk writes: > On 24 May 2000 07:20:00 -0500, Thomas Weholt wrote: > >Hello, > > > >Has anybody tried to somehow get xml-data into SQL-statements or in some > >other way use xml-data as datasource for insertion into tables? > >It shouldn`t be impossible, if we could just agree on some format or DTD to > >use. > > I'm headed that way - I'm planning on using XML-RPC to insert table > records into an SQL database. You may find RAX (Record API for XML) useful: http://www.digitome.com/rax.html Introduction: http://www.xml.com/pub/2000/04/26/rax RAX is > A simple, record-oriented API for XML. Provides a simple, efficient > interface for processing the sort of XML often generated from > databases. Dieter

1 0

Re: [Zope-dev] Product Loading
by Heine Gregor 25 May '00

25 May '00

Hi! Just to be sure: did you restart zope after you changed/added the products? If no: do it! If yes: take a look at the Boring Product HOWTO ( http://www.zope.org/Members/gtk/Boring/HowTo-Boring/ ), maybe it enlights you. If you have your Zope installed locally and running Windows try the PythonWin-Debugger. Install Python 1.5 and then add import sys sys.path.append('c:/path/to/python') sys.path.append('c:/path/to/python/PythonWin') sys.path.append('c:/path/to/python/win32') sys.path.append('c:/path/to/python/win32/lib') in your product's python-modules. To start the debugger insert import pywin.debugger; pywin.debugger.set_trace() at the point, where the debugger should start. Good luck! MacGregor! > I've already posted this problem to the Zope list, which is the correct > place to post I believe, but to no avail. So I'm trying here - apologies, > but just as I'm getting really excited about Zope I hit a brick wall > (...familiar lament?) and I'm at a complete loss. > So apologies for my newbieness; here's my problem: > > my zope won't load products into its products folder. I had some success > initially. Then I found some bugs in my initialize code that were breaking > the product. From then on, whenever I changed the initialize code, the > changes were only getting reflected sporadically in the traceback. > > I found I could even delete my product from the Products folder and it would > stay in Zope. Now even when I create a really simple product, it doesn't > appear. > > I presume I am doing something stupid. Especially considering I can install > 3rd party products without a problem. My assumption was that to create a > product: > > I create a Test folder in the Products directory, with an __init__.py which > contains an import Test and an initialize(context) function. Then I do a > context.registerClass(stuff). Then I do the logic stuff in Test.py. > > Even if I don't put any logic in Test.py, *something* should appear in the > products list, right? How can I start debugging this problem? > > Thanks so much for any help... > > Seb. >

1 0

zpatterns: win32 dll for DynPersist?
by Jephte CLAIN 25 May '00

25 May '00

Hello, Has someone compiled the DynPersist dll for win32? if someone has done so, it would be glad to send me a copy by tomorrow. it will help me greatly. TIA, jephte clain minf7(a)educ.univ-reunion.fr

1 0

Product Loading
by Seb Bacon 25 May '00

25 May '00

folks, I've already posted this problem to the Zope list, which is the correct place to post I believe, but to no avail. So I'm trying here - apologies, but just as I'm getting really excited about Zope I hit a brick wall (...familiar lament?) and I'm at a complete loss. So apologies for my newbieness; here's my problem: my zope won't load products into its products folder. I had some success initially. Then I found some bugs in my initialize code that were breaking the product. From then on, whenever I changed the initialize code, the changes were only getting reflected sporadically in the traceback. I found I could even delete my product from the Products folder and it would stay in Zope. Now even when I create a really simple product, it doesn't appear. I presume I am doing something stupid. Especially considering I can install 3rd party products without a problem. My assumption was that to create a product: I create a Test folder in the Products directory, with an __init__.py which contains an import Test and an initialize(context) function. Then I do a context.registerClass(stuff). Then I do the logic stuff in Test.py. Even if I don't put any logic in Test.py, *something* should appear in the products list, right? How can I start debugging this problem? Thanks so much for any help... Seb.

1 0

Re: [Zope-dev] Observer / Notification Interface Proposal
by Tres Seaver 25 May '00

25 May '00

"Phillip J. Eby" wrote: > > At 09:15 PM 5/24/00 -0400, Tres Seaver wrote: > > > >Note that the scaling requirement (no blocking/long-running actions > >inside the notification call) is intended to support intra-request > >notification. A ConcreteObserver implementation which needs to > >perform such work (e.g., send an e-mail message, etc.) will have to > >extract whatever data it needs from the subject and enqueue it for > >processing in some other thread, by the asyncore machinery, etc. > > > >Note as well that it would be possible to install an Observer which > >could "veto" the change by raising an exception (a clever > >ConcreteSubject might ignore such a veto, of course). > > As you've probably noticed, I've been working on something similar for > ZPatterns, but it's specifically oriented to the needs of > Attribute/SheetProviders and Index/RuleAgents. The list of observers > is effectively predefined, and the DataManager acts as a "tee" fanning > out the events to the interested parties. However, subscription scope > is per-transaction; the subscription takes place the first time an > object hooks up with its DataManager in that transaction. I added motivating examples to the two interfaces pages: e-mail notification and workflow state-machine transitions. Both of these involve persistent subscriptions. > >I'm don't have any use case in mind for a cross-transaction "event". > > Perhaps I was unclear. I was referring to maintaining the link between > subject and observer for longer than a single transaction. That is, a > persistent subscription. Ah, ok -- I was planning simply to leverage the ZODB's facilities for maintaining persistent references in the DefaultObservable mix-in; more elaborate schemes would be possible (for instance to support rack-mounted observers?) > >I also have hopes for a set of federated, filterable > >NotificationChannels (like CORBA's NotificationService) which would > >allow Observer-in-Zope to scale up enormously. > > Hm. It seems to me that something like that would require persistent > subscriptions to be of any real use, since re-subscribing on every > transaction would likely be inefficient. I apologize for the confusion -- I certainly didn't intend to convey that subscriptions were transient. As you note, that would be a less than useful "feature." -- ========================================================= Tres Seaver tseaver(a)digicool.com Digital Creations "Zope Dealers" http://www.zope.org

2 1

Re: [Zope-dev] zpatterns: rackmountables must be of-wrapped
by Jephte CLAIN 25 May '00

25 May '00

"Phillip J. Eby" a écrit : > >So: retrieveItem, createItem use vanilla objects > retrieveItem and createItem are not intended to be public methods; the only > reason they don't begin with an "_" is that I wanted to make it possible > for them to be implemented as DTMLMethods or PythonMethods. you missed the point. I wasn't that clear neither ;-) I know that retrieveItem and createItem are not public API, and are meant to be overidable. I believe that telling the rackmountable what rack it belongs to in getItem and newItem it not sufficient. It has to be wrapped in the context of the rack with something like: # this works for me item = self.retrieveItem(key) if item is not None: item._setRack(self.aq_inner) return item.__of__(self) # keep other acquisition wrappers, # no need to get aq_inner or: # untested item = self.retrieveItem(key) if item is not None: rack = self.aq_inner item._setRack(rack) return item.__of__(rack) When I don't wrap items like this, I get strange unauthorized errors. Only the super user can use the items. All the other users (Managers or not) can't. Remember that I use python classes as rack-mountables, and they don't get the fancy acquisition wrapping that zclasses get. regards, jephte clain minf7(a)educ.univ-reunion.fr

2 1