Re: [Keelgroup] Service Dependancies

All,

In a continuation of Mike's efforts to split out Persistence, we have 
moved a few other things, mostly config, JDBC JARs, tests, etc. out of 
the keel-* modules into svc-persistent-base.  Most importantly, 
sample-config for JDBC drivers was moved out of keel-server and into 
svc-persistent-base. There is now a small-deploy.properties file which 
will let you build an app with just keel-*, svc-model-defaultmodel, 
svc-event-default, app-navigate and Struts.

This is all just moving files around, none of the API or functionality 
has changed.  Please let us know if you have trouble building/running 
from CVS.

Shash

Michael Nash JGlobal.com wrote:

>I'm just about to check this in. It hasn't broken anything as far as the unit & functional tests are concerned, but please let me know if anyone sees
>a problem as a result. It does make the keel-container a bit thinner - further weight reduction is possible, though :-)
>
>Don't forget to check out svc-persist-base as a new module.
>
>(Shash - Should I add this to the "all" or "default" alias in CVS modules?)
>
>Mike
>
>On Thu, 25 Mar 2004 13:54:50 -0600
>"Shash Chatterjee" <[email protected]> wrote:
>
>  
>
>>Mike,
>>
>>svc-persist-base sounds logical.  +1.
>>
>>I think this will get us closer to being able to do a really pared down Keel
>>if we ever get around to doing that,
>>
>>Shash
>>
>>    
>>
>>>I've run into an interesting situation: If you configure a *-
>>>deploy.properties to include neither of the current implementations 
>>>of persistence service, the resulting Keel server will not start. 
>>>This is because there are classes in keel-container that depend on 
>>>persistence (the List Header stuff, the Database type classes, etc). 
>>>It seems inappropriate that we can't configure an app without 
>>>persistence (especially if that app uses JDO service, for example!)
>>>
>>>These classes are only used for the persistence service, and are not 
>>>required for keel-container otherwise, but I'm not sure where they 
>>>should go. They're used by both svc-persist-default and svc-persiste-
>>>hibernate, so it makes no sense to duplicate them in both. svc-
>>>persist-base perhaps? Module proliferation can get to be too much 
>>>eventually, but maybe this is a case for it?
>>>
>>>Suggestions/opinions appreciated!
>>>
>>>-- 
>>>Michael Nash
>>>
>>>JGlobal Ltd 
>>>Next-Generation Web Application Development and Open Source Support
>>>http://www.jglobal.com
>>>
>>>Bahamas Commerce and Trade
>>>Offshore eCommerce Hosting and Business Services
>>>http://www.bahamascommerce.com
>>>
>>>http://keelframework.org/documentation
>>>Keelgroup mailing list
>>>[email protected]
>>>http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
>>>      
>>>
>>
>>http://keelframework.org/documentation
>>Keelgroup mailing list
>>[email protected]
>>http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
>>    
>>
>
>
>  
>