Andi Vajda wrote: >> I've attached an isolated testcase for you. You'll surely recognize the >> make file. It's based on your make file from PyLucene. I hope you don't >> mind ;) > > Thank you, that is very helpful in debugging this. > > But first, please do not contact me off list. Use the > pylucene-dev@lucene.apache.org mailing list. Your issue is of interest > to others.
Understood! I didn't want to spam a mailing list with an attachment. Most mailing lists I'm subscribed to have a no-attachment policy. > The reason for the error is that you're calling one of your native > extension methods, startDocument, from the PyPDFTextStripper constructor. > > While this is valid Java, it violates an unstated constraint of the code > generated by JCC: after the Java constructor returns, JCC generated code > to finish initializing the object, calling the > pythonExtension(pythonObject) method. > > The problem with this sequence of events is that if you call a native > extension method from the constructor, the python object to call a > method on from that native method is not yet set on the Java instance. > In other words, inside the constructor, the native extension methods > such as startDocument() depend on state on the instance that is not yet > set. > In order to set that state, the object has to be constructed first, so > we're in a bit of a catch-22 here. Unstated indeed ... :) Thanks again for your analysis and explanation of my issue. (Un)fortunately I'm very good in hitting obscure corner cases. The limitation isn't an issue for me. You've already shown me one way to work around it. I suggest that you add a note to the corresponding chapter of the README. I've permission from my employee to release the code once it's ready. I like to get your opinion regarding the packaging and setup of my code. Christian
