[Registry-dev] Persistence registry - Implementation options

[Paul Fremantle]

The problem with SQL+JDBC is that it doesn't necessarily flex to support 
different SQL syntaxes. Unfortunately there are minor variations that 
can affect portability from say Oracle to JDBC. For an example of these 
you can see the configurability list in
http://openjpa.apache.org/docs/latest/manual/ref_guide_dbsetup_dbsupport.html#ref_guide_dbsetup_dbdictprops

To be fair I'm not sure how big a problem this is in real-life. I know 
it was a problem with complex J2EE apps, but maybe we can use very 
simple SQL :)

The alternative is to use OpenJPA from Apache. Thoughts?

Paul



Sanjiva Weerawarana wrote:
> I'm -1 on Hibernate. Let's just do SQL + JDBC .. that'll make it easier 
> to do a good search API too.
> 
> We should be storing fairly simple structured info in the database 
> tables- I really don't see a need to use an ORM tool.
> 
> Sanjiva.
> 
> Chathura C. Ekanayake wrote:
>>
>> Hi,
>>
>> I have implemented the persistence registry for the previous requirements
>> (i.e. with version control, links, etc.) using hibernate. But as we 
>> are going to
>> cut down most of those features in 0.1 release, I have to rewrite some 
>> of the
>> code. So it is easier if we finalize on the database implementation at 
>> this
>> stage.
>>
>> We are having following options:
>>
>> Hibernate
>> Plain SQL + JDBC
>> Apache iBATIS
>>
>> As I have already implemented it using hibernate, it is easier to modify
>> it to the new requirements, if we continue to use hibernate.
>>
>> Comments...
>>
>> Thanks,
>> Chathura
>>
>> _______________________________________________
>> Registry-dev mailing list
>> Registry-dev at wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
>>
> 

-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

Office: +1 646 290 8050
Cell: +44 798 447 4618

blog: http://pzf.fremantle.org
paul at wso2.com

"Oxygenating the Web Service Platform", www.wso2.com