Related to modules: another feature is code sharing between modules: utility functions and even more functionality.
-- You received this bug notification because you are a member of Zorba Coders, which is the registrant for Zorba. https://bugs.launchpad.net/bugs/931816 Title: New way of classpath and JVM Singleton handling Status in Zorba - The XQuery Processor: New Bug description: This bug is to track work related to makeing Zorba modules implemented in Java be robust and working all together. It was decided that a few things need to happen: Critical: 1. (chris) add cmake macros to let build know a module is using java 2. (chris) cmake macros that define it's own jar implementation 3. (chris) cmake macros that define external dependencies (like xmlbeans.jar, xsl-fo.jar) 4. (cezar) add zorba classpath option, and CLASSPATH environment 5. (chris) add core module that can resolve a known (by URI) external module 6. (chris) add external java-helper module that provides concatenation of classpathes - the order on calsspath is: ModuleOwnPath, ModuleDependecy, zorba -cp, env CLASSPATH 7. (chris) make sure binary packages set up classpathes correctly 8. (cezar) add code to external java-helper module to create a singleton JVM 9. (cezar) refactor xmlbeans and xsl-fo modules to make use of external java-helper module Nice to have, not critical: 10. Have a generic way to implement modules directly in Java, Python etc, using swig extension. To manage notifications about this bug go to: https://bugs.launchpad.net/zorba/+bug/931816/+subscriptions -- Mailing list: https://launchpad.net/~zorba-coders Post to : email@example.com Unsubscribe : https://launchpad.net/~zorba-coders More help : https://help.launchpad.net/ListHelp