openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fernando Padilla <f...@alum.mit.edu>
Subject Re: dual node URLs (of SolidDB)
Date Wed, 03 Dec 2008 15:40:46 GMT
I think supporting commas in the url should be supported for any 
database server (mysql also has support for loadbalanced replicants, etc 
etc).  Have you filed a bug for this yet?


Jaeger, Michael wrote:
> Hi all,
> 
> we know that soliddb is not among the supported databases of OpenJPA.
> Thus we would like place our experience with soliddb + openjpa to
> discussion (if support for SolidDB is anticipated).
> 
> The main reason why we use soliddb is its hot-standby-feature. For
> setting up hot standby, just pass the JDBC driver a dual node URL.
> Solidtech has decided to separate the adresses of two nodes by a comma
> where normally a single host is named. looks like this:
> 
> 	Url=jdbc:solid://comp1:1315,comp2:1315/myusr/mypw 
> 
> so the point with OpenJPA here is that properties are separated by ","
> as well, so the rest of the URL is cut away then:
> 
> 	Url=jdbc:solid://comp1:1315
> 	comp2:1315/usr/pw
> 	DriverClassName=solid.jdbc.SolidDriver
> 
> We have patched this (Configurations.parseProperties()), simply inject
> the complete URL at some later point again. 
> 
> Clearly, the support for malformed URLs can be put into question. thus,
> on first hand, take our e-mail as feedback where one major point would
> come up when using SolidDB. We have had also some other issue which we
> fixed with a custom dictionary. In summary our experience with using
> openjpa + soliddb is very positive apart from the fundamental issue with
> the dual node URL.
> 
> - Michael
> 
> PS. the warning message when using a dictionary not belonging to the
> right package is also not very nice and here on our site has disturbed
> the developers. anyone experience with this one?

Mime
View raw message