Martijn Faassen wrote:
>> JSR-170 would be great. Can we be JSR-170 compliant even if we do not
>> use Java stuff?
>
>
> No, JSR-170 is explicitly a Java API, so:
>
> * if we want our repository to be JSR-170 compliant, we'd need to
> support a Java API to it somehow. This would not be easy and the
> question is whether that'd be worth it now.
>
> * if we want to *use* a JSR-170 compliant repository (as an option),
> we'd need to interface our code with Java. This is somewhat easier, and
> might be worth exploring. Apache Jackrabbit for instance aims at being a
> JSR-170 repository.
for interating with java:
http://jpype.sourceforge.net/
"""
JPype is an effort to allow python programs full access to java class
libraries. This is achieved not through re-implementing Python, as
Jython/JPython has done, but rather through interfacing at the native
level in both Virtual Machines.
"""
"""
Using JPype
Here is a sample program to demonstrate how to use JPype :
from jpype import *
startJVM("d:/tools/j2sdk/jre/bin/client/jvm.dll", "-ea")
java.lang.System.out.println("hello world")
shutdownJVM()
"""
I am planning to use JPype to interface with foring Java stuff in the
near future. Perhaps it will ne easier than rewriting in python or using
xml-rpc. At least I hope so ;-)
> * Lowest hanging fruit would be to be inspired by the JSR-170 API.
> Instead of designing our repository API from scratch, we could base it
> on JSR-170's, even though we'd probably change some APIs to make them
> more Pythonic. This gives us the advantage of benefiting from the
> thinking who wrote that spec, and also allows us to point people who
> want to learn about our repository API to a written spec that is
> *mostly* correct, even though some interpretation by the reader will
> need to be done. I think this can still be very valuable.
>
<snip>
>> Yep, that's really an important thing. But also much effort is needed
>> here. Missing SAP R/3 connectivity was one major reason why my boss
>> would not let me even present a Zope-based approach to our Management
>> Board...
>
> Right, SAP tends to get this kind of 'holy temple' status within
> organisations, and everything needs to adapt to SAP. :) We need to
> figure out what such an integration could look like at all, as right now
> I have no clue. :) Perhaps you or your boss can tell us more.
we also need to have good database bindings. one major obstacle for us
is the lack of good Zope2 Oracle DA adapters.
For the project I am finishing now, we have used cx_oracle, but with
minimal Zope integration. Works quite well but it is not tied to the
transaction mechanism of zope.
But lack of Oracle Support in Zope2 is worrying.
/dario
--
-- -------------------------------------------------------------------
Dario Lopez-Kästen, IT Systems & Services Chalmers University of Tech.
"...and click? damn, I need to kill -9 Word again..." - b using macosx
Hosting: Nuxeo: Zope service provider