Jacopo,
We may keep hsqldb.jar. Often practical to have it on hand.
Jacques
- Message d'origine -
De : Jacopo Cappellato [EMAIL PROTECTED]
À : dev@ofbiz.apache.org
Envoyé : mercredi 4 avril 2007 10:45
Objet : Re: Removing unnecessary jdbc jar files
Hi all,
apart from the changes
The problem is there is no stability in the design to do a
implementation. At least the way I have done the install.
I something that works with the version I have, which is many versions
and structure behind where ofbiz is now.
It uses a tree type of outline to allow access to the setup data.
Hi all,
I think we could slim down (-6M) the size of the OFBiz trunk (and
upcoming distribution) by removing the following unneeded (?) jars, or
at least a part of them, from the framework/entity/lib/jdbc folder:
p6spy.jar (and also the spy.properties file)
hsqldb.jar
derbyclient.jar
Also, what do you think about cleaning up the entityengine.xml file from
all the examples of configurations for the different db (and just leave
the ones used by default)?
We could create a different file/readme in the same folder with all the
other ones.
Jacopo
Jacopo Cappellato wrote:
Hi
The examples in the entityengine.xml file are pretty important for
people setting up with different databases. If they aren't in that
file they need to be somewhere, like docs.ofbiz.org, and references
clearly in a comment in the entityengine.xml file. There are subtle
settings for each
+1 on the docs.ofbiz.org dev space for specific jdbc datasource
definitions. This will allow entityengine.xml to actually have meaning
to the deployment so the xml file can be used in applications (such as
providing a user with a listing of working datasources.
--- David E. Jones [EMAIL
David E. Jones wrote:
The examples in the entityengine.xml file are pretty important for
people setting up with different databases.
I have to agree strongly here. When I first looked at the project, the robust
number of connectors clearly documented there was a okay, these folks have
I agree that the example are very important; in fact I was thinking to
move them in a separate enitityengine-other-databases.xml file and
maintain it in the same folder in svn (framework/entity/conf).
Jacopo
David E. Jones wrote:
The examples in the entityengine.xml file are pretty