Re: Configuring 2nd and on DBs

Michael Nash wrote:
> Gene:
> 
> I think you hit the nail on the head: the Xpath expressions will, by
> default, change *everything* they match (which is quite handy when
> that's what you want, and quite a pain when it's not). I was thinking we
> can set up one (for example) to change *all* logging levels to WARN or
> DEBUG, for example.

A perfect example of override use.  I've gone *many* times to stop the 
container, update logging levels, then restart.  Then, just have to 
reset the levels after put into production!

I've also created a map to remove the ${method} parameter from the 
logkit config.  Found out I was taking a HUGE performance hit by leaving 
it in.

Thanks
gene

> 
> Mike
> 
> On Mon, 2005-02-07 at 00:34, Gene wrote:
> 
>>i THINK i fixed my same situation by editing the keel-map.properties.
>>
>>i altered the xpath to only change the dbtype for keel-dbtype, 
>>otherwise, it seemed to change each instance of the dbtype
>>
>>svc.persist.dbtype.INNODBmysql=//INNODBmysql[@id='keel-dbtype-INNODBmysql']|id
>>(I've added an INNODBmysql type, which simply supports transactions)
>>
>>I think if that attribute check on each dbtype, it would clear this 
>>problem up.  With the addition of the check on the id value, i think my 
>>db access started working again.  Let me know if that doesn't do it, 
>>because i have the same problem, but have it working.
>>
>>gene
>>
>>Shash Chatterjee wrote:
>>
>>>Mike,
>>>
>>>The app's been running fine for a while, but I dusted off the dev. copy 
>>>this weekend for the first time since Nov. and ran into this problem:
>>>
>>>org.keel.services.persist.PersistenceException: Role 
>>>'org.keel.services.persist.DatabaseType' does not have an implementation 
>>>with id/hint 'ba-dbtype'. It's available implementations are 
>>>keel-dbtype-informix, keel-dbtype-oracle, keel-dbtype, 
>>>keel-dbtype-mysql, keel-dbtype-postgresql, keel-dbtype-sqlserver. 
>>>(Key='org.keel.services.persist.DatabaseType/ba-dbtype').
>>>
>>>Here's my config in system.xconf, after the merge:
>>>
>>>    <default-persistent security="default" logger="ba-persist" 
>>>activation="request" name="ba" id="ba">
>>>      <dbpool>ba-dbpool</dbpool>
>>>      <dbtype>ba-dbtype</dbtype>
>>>      <snip...../>
>>>
>>>    </default-persistent>
>>>    <jdbc id="ba-dbpool">
>>>      <pool-controller timeout="-1" min="1" blocking="true" 
>>>connection-class="org.apache.avalon.excalibur.datasource.JdbcConnection" 
>>>trim-interval="60000" maxStrict="true" max="10" auto-commit="true">
>>>        <keep-alive disable="true"/>
>>>      </pool-controller>
>>>      <driver>org.hsqldb.jdbcDriver</driver>
>>>      <dburl>jdbc:hsqldb:./db/ba-hsqldb</dburl>
>>>      <user>sa</user>
>>>      <password/>
>>>    </jdbc>
>>>    <hsqldb id="ba-dbtype">
>>>      <type to="bit" suffix="" prefix="" from="boolean"/>
>>>    </hsqldb>
>>>
>>>What do I need to change?
>>>
>>>In this deployment, I have two hsqldb DBs.  In other apps, I have hsqldb 
>>>for the keel-specific tables, and Oracle for the custom apps/services. I 
>>>am sure I'll have to make similar adjustments there too.
>>>
>>>Thanks,
>>>Shash
>>>http://keelframework.org/documentation.shtml
>>>Keelgroup mailing list
>>>[email protected]
>>>http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
>>>
>>
>>http://keelframework.org/documentation.shtml
>>Keelgroup mailing list
>>[email protected]
>>http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
> 
> 
> http://keelframework.org/documentation.shtml
> Keelgroup mailing list
> [email protected]
> http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
> 
http://keelframework.org/documentation.shtml
Keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com