One newbie to another... We found camel-ibatis component with ServiceMix 4.2 to be quite powerful and a very thin lightweight layer on top of JDBC, feels much closer to the SQL layer than JPA for example. Since you typically pre-build the queries in the ibatis SqlMapConfig.xml file, it has more control than just pumping out raw SQL as you might do with JDBC. We saw this as a big plus since the queries could be well defined ahead of time, and less likely to fail at runtime than on-the-fly SQL query strings. Might be too restrictive for some applications though.
You can have camel-ibatis bundle up all query results in a List<> response, or stream the records to a JMS queue... very nice options to have. ibatis also appears to support connection pooling capabilities... which is nice since the ServiceMix container didn't seem to provide container-style connection pooling for you automatically as you might expect if you were using an EJB container. It might, I've just not noticed yet. I'm kinda new at this myself. See my recent message about a couple of camel-ibatis work arounds we found to work in the latest ServiceMix. You could also look at JPA. The examples-jpa-osgi in ServiceMix 4.2.0 has a working example of a WSDL service with a custom JPA backend. Use "features:install examples-jpa-osgi" to see it in action and also see the readme.txt in the examples source directory. Installing this feature also has the added bonus of deploying all your hibernate 3.4.0.GA EntityManager & dependencies, which was painful to do manually last time we tried it. Wish I'd known about this sooner. In fact, the difficulty of setting up hibernate was the reason we moved away from camel-jpa and started using EclipseLink 2.0.0 bundle from the Spring Enterprise Bundle Repository and our own backend JPA classes that were reverse engineered using the dali Eclipse plugin (part of MyEclipse). This seemed to give us more control to handle our more advanced use-cases better than straight camel-jpa component. But now that ServiceMix 4.2.0 is released, I'm anxious to try the hibernate JPA support again, and see if it is working better than last time we tried it. Perhaps we can migrate from EclipseLink back to Hibernate. 3 weeks into ServiceMix and that's about all I know at this point about database connectivity. Thushara Seneviratne wrote: > > Hi all , > > AFAIK there is no JDBC BC component available with SMX . we can think > JDBC > also as a another connectivity such as HTTP or JMS. > > 1.) what is the recommended way to connect to a database in SMX through > JDBC > ? > > > > Thanks, > > Thushara > > -- View this message in context: http://old.nabble.com/Best-way-to-handle-JDBC-connectivity-in-SMX-tp27635179p27682909.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
