Removing unnecessary jdbc jar files

[Jacopo Cappellato]

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
derbynet.jar
derbyclient.jar
derbytools.jar
derbyTesting.jar
derbyLocale*.jar

We should just leave the derby.jar file (and add to it the version suffix).

I'm running OFBiz without them with no problems.

What do you think?

Jacopo

[Jacopo Cappellato]

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 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
> derbynet.jar
> derbyclient.jar
> derbytools.jar
> derbyTesting.jar
> derbyLocale*.jar
>
> We should just leave the derby.jar file (and add to it the version suffix).
>
> I'm running OFBiz without them with no problems.
>
> What do you think?
>
> Jacopo

[David E Jones]

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 database that are important and are maintained  
there, but could be maintained in the dev space on docs.ofbiz.org  
just fine too.

-David


On Mar 28, 2007, at 1:25 AM, Jacopo Cappellato wrote:

> 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 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
>> derbynet.jar
>> derbyclient.jar
>> derbytools.jar
>> derbyTesting.jar
>> derbyLocale*.jar
>> We should just leave the derby.jar file (and add to it the version  
>> suffix).
>> I'm running OFBiz without them with no problems.
>> What do you think?
>> Jacopo
>

[cjhowe]

+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" <[hidden email]> wrote:

>
> 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 database that are important and are maintained  
> there, but could be maintained in the dev space on docs.ofbiz.org  
> just fine too.
>
> -David
>
>
> On Mar 28, 2007, at 1:25 AM, Jacopo Cappellato wrote:
>
> > 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 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
> >> derbynet.jar
> >> derbyclient.jar
> >> derbytools.jar
> >> derbyTesting.jar
> >> derbyLocale*.jar
> >> We should just leave the derby.jar file (and add to it the version
>  
> >> suffix).
> >> I'm running OFBiz without them with no problems.
> >> What do you think?
> >> Jacopo
> >
>
>

[Walter Vaughan]

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
something going on here" moment.

What would be worthwhile for someone (not me :) ) is to develop a sort of
installation application that basically follows the production setup guide to
build configurations [demo, demo with external db, production] with radio
buttons, check boxes, suggested values, etc... in order to get people up to
speed and if nothing but a checklist during a transition.

There probably is a Jira issue on this, but I'd rather use any karma points
towards that instead of removing one of the first point of contacts with the
"internals" of ofBiz.

--
Walter

[Jacopo Cappellato]

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 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 database that are important and are maintained there, but could be
> maintained in the dev space on docs.ofbiz.org just fine too.
>
> -David
>
>
> On Mar 28, 2007, at 1:25 AM, Jacopo Cappellato wrote:
>
>> 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 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
>>> derbynet.jar
>>> derbyclient.jar
>>> derbytools.jar
>>> derbyTesting.jar
>>> derbyLocale*.jar
>>> We should just leave the derby.jar file (and add to it the version
>>> suffix).
>>> I'm running OFBiz without them with no problems.
>>> What do you think?
>>> Jacopo
>>
>

[Ludovic Maître]

Walter Vaughan wrote:

> 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 something going on here" moment.
>
> What would be worthwhile for someone (not me :) ) is to develop a sort
> of installation application that basically follows the production
> setup guide to build configurations [demo, demo with external db,
> production] with radio buttons, check boxes, suggested values, etc...
> in order to get people up to speed and if nothing but a checklist
> during a transition.

Very good idea! We could do an IzPack (www.izforge.com/*izpack*/ )
installer for OfBiz, like this is done for Geronimo.
One good thing would be that we can use it in silent mode to install
OfBiz on several servers. Also and IMHO IzPack is really easy to use.
Let's find the human resources to do it :-)

> There probably is a Jira issue on this, but I'd rather use any karma
> points towards that instead of removing one of the first point of
> contacts with the "internals" of ofBiz.
>
> --
> Walter
>
>
>
>
>

--
Cordialement,
Ludo - http://www.ubik-products.com
---
"L'amour pour principe et l'ordre pour base; le progres pour but" (A.Comte)

[BJ Freeman]

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.
Trees are only expanded when the parent has been completed.
this resides in the webtools section and is run sort of like the install
is run.
Once someone says we have a freeze point, I would be glad to update my
code to that freeze point.

Walter Vaughan sent the following on 3/28/2007 3:06 PM:
> What would be worthwhile for someone (not me :) ) is to develop a sort
> of installation application that basically follows the production setup
> guide to build configurations [demo, demo with external db, production]
> with radio buttons, check boxes, suggested values, etc... in order to
> get people up to speed and if nothing but a checklist during a transition.

[Jacopo Cappellato]

Hi all,

apart from the changes to the enityengine.xml file, do you agree about
removing all the jdbc/*.jar files except derby.jar?

I've removed from my local copy:

p6spy.jar (and also the spy.properties file)
hsqldb.jar
derbyclient.jar
derbynet.jar
derbyclient.jar
derbytools.jar
derbyTesting.jar
derbyLocale*.jar

a few days ago without having any issues.
I'm not sure about the role of:
p6spy.jar (and also the spy.properties file)

If it's ok I will remove them from svn.

Jacopo


David E. Jones wrote:

>
> 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 database that are important and are maintained there, but could be
> maintained in the dev space on docs.ofbiz.org just fine too.
>
> -David
>
>
> On Mar 28, 2007, at 1:25 AM, Jacopo Cappellato wrote:
>
>> 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 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
>>> derbynet.jar
>>> derbyclient.jar
>>> derbytools.jar
>>> derbyTesting.jar
>>> derbyLocale*.jar
>>> We should just leave the derby.jar file (and add to it the version
>>> suffix).
>>> I'm running OFBiz without them with no problems.
>>> What do you think?
>>> Jacopo
>>
>

[Jacques Le Roux]

Jacopo,

We may keep hsqldb.jar. Often practical to have it on hand.

Jacques

----- Message d'origine -----
De : "Jacopo Cappellato" <[hidden email]>
À : <[hidden email]>
Envoyé : mercredi 4 avril 2007 10:45
Objet : Re: Removing unnecessary jdbc jar files

> Hi all,
>
> apart from the changes to the enityengine.xml file, do you agree about
> removing all the jdbc/*.jar files except derby.jar?
>
> I've removed from my local copy:
>
> p6spy.jar (and also the spy.properties file)
> hsqldb.jar
> derbyclient.jar
> derbynet.jar
> derbyclient.jar
> derbytools.jar
> derbyTesting.jar
> derbyLocale*.jar
>
> a few days ago without having any issues.
> I'm not sure about the role of:
> p6spy.jar (and also the spy.properties file)
>
> If it's ok I will remove them from svn.
>
> Jacopo
>
>
> David E. Jones wrote:
> >
> > 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 database that are important and are maintained there, but could
be
> > maintained in the dev space on docs.ofbiz.org just fine too.
> >
> > -David
> >
> >
> > On Mar 28, 2007, at 1:25 AM, Jacopo Cappellato wrote:
> >
> >> 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 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
> >>> derbynet.jar
> >>> derbyclient.jar
> >>> derbytools.jar
> >>> derbyTesting.jar
> >>> derbyLocale*.jar
> >>> We should just leave the derby.jar file (and add to it the version
> >>> suffix).
> >>> I'm running OFBiz without them with no problems.
> >>> What do you think?
> >>> Jacopo
> >>
> >
>

[David E Jones]

I've tested running without these for a bit too and don't see any  
problems with it, especially where we are running in embedded mode.  
It really is nice to have less stuff hanging around and trim out  
unused things, especially since it's so easy to download a full derby  
if someone needs/wants it.

How often do people actually use hsqldb? My vote would be to remove  
it and p6spy and it's just kind of clutter that hasn't been updated  
in a LONG time and I doubt it is used much, if ever, any more.

-David


On Apr 4, 2007, at 5:09 AM, Jacques Le Roux wrote:

> Jacopo,
>
> We may keep hsqldb.jar. Often practical to have it on hand.
>
> Jacques
>
> ----- Message d'origine -----
> De : "Jacopo Cappellato" <[hidden email]>
> À : <[hidden email]>
> Envoyé : mercredi 4 avril 2007 10:45
> Objet : Re: Removing unnecessary jdbc jar files
>
>
>> Hi all,
>>
>> apart from the changes to the enityengine.xml file, do you agree  
>> about
>> removing all the jdbc/*.jar files except derby.jar?
>>
>> I've removed from my local copy:
>>
>> p6spy.jar (and also the spy.properties file)
>> hsqldb.jar
>> derbyclient.jar
>> derbynet.jar
>> derbyclient.jar
>> derbytools.jar
>> derbyTesting.jar
>> derbyLocale*.jar
>>
>> a few days ago without having any issues.
>> I'm not sure about the role of:
>> p6spy.jar (and also the spy.properties file)
>>
>> If it's ok I will remove them from svn.
>>
>> Jacopo
>>
>>
>> David E. Jones wrote:
>>>
>>> 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 database that are important and are maintained there, but could
> be
>>> maintained in the dev space on docs.ofbiz.org just fine too.
>>>
>>> -David
>>>
>>>
>>> On Mar 28, 2007, at 1:25 AM, Jacopo Cappellato wrote:
>>>
>>>> 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 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
>>>>> derbynet.jar
>>>>> derbyclient.jar
>>>>> derbytools.jar
>>>>> derbyTesting.jar
>>>>> derbyLocale*.jar
>>>>> We should just leave the derby.jar file (and add to it the version
>>>>> suffix).
>>>>> I'm running OFBiz without them with no problems.
>>>>> What do you think?
>>>>> Jacopo
>>>>
>>>
>>
>