-
1. Re: Move configuration files to org.jbpm package
"vfritzsch" wrote:
Hello PVM Developers,
what do you think about moving the configuration files (hibernate.definition.hbm.xml etc.) from the default package into org.jbpm?
I am currently evaluating PVM (svn head) in an OSGi based project and - as far as I know - OSGi does not allow you to export the content of the default package. But to get PVM working, the hibernate bundle needs access to PVMs configuration files and, frankly, that's why I ask.
So, what do you think?
Best regards,
Volker
btw.: keep up the good work. PVM looks really promising. -
2. Re: Move configuration files to org.jbpm package
"vfritzsch" wrote:
as far as I know - OSGi does not allow you to export the content of the default package. But to get PVM working, the hibernate bundle needs access to PVMs configuration files and, frankly, that's why I ask.
makes sense.
guys, can someone confirm this ?"vfritzsch" wrote:
btw.: keep up the good work. PVM looks really promising.
it *is* really promising ! and we're going to deliver it (+jpdl) before the end of the year.
:-) -
3. Re: Move configuration files to org.jbpm package
Unfortunatly, I have not been able to find something in the specification that proves my assumption.
Just this (http://www.mail-archive.com/osgi-dev@bundles.osgi.org/msg00198.html) post on the osgi-dev list, that basically says that you cannot export the default package, because you will not be able to distinguish between different default packages during import, which makes sense to me.
Best regards,
Volker -
4. Re: Move configuration files to org.jbpm package
right. since you have to import packages explicitely, I will assume that your statement was right, unless someone proves the opposite.
so i'll move the config files to org.jbpm package.
thanks for letting me know
regards, tom. -
5. Re: Move configuration files to org.jbpm package
configuration files are moved to package org/jbpm in svn