Jason McKerr wrote:
I have finished the third installment of connecting up Spring and OJB. This covers using non-local configurers (it eliminates the need for ojbConfigurer) so that you can use JNDI data sources and caching strategies other than Per Broker.

Armin,  included is the text file that you asked for.


Thanks again! I added your "Howto" to 1.0.x CVS branch. Will be included in 1.0.4.
http://cvs.apache.org/viewcvs.cgi/db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/howtos/howto-use-spring.xml?rev=1.1.2.1&only_with_tag=OJB_1_0_RELEASE&view=markup

Ops, in OJB 1.1 trunk I found a Spring Howto by Robert S. Sfeir
http://cvs.apache.org/viewcvs.cgi/db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/howtos/howto-use-ojb-with-springframework.xml?rev=1.3&view=markup

This stuff was checked in 7 month ago. Is it up to date? What's the difference compared with your articles?

regards,
Armin


Thanks,

Jason

Jason McKerr wrote:

Armin,

I am just finishing up the third article today. As soon as I get that done, I will write this and send along.

Jason

Armin Waibel wrote:

Hi Jason,

Jason McKerr wrote:

Hi Thomas,

If you guys want, feel free to take the two articles that I put up and move them into the How-to page. I will have the third entry done in the next few days.


Thanks a lot!
I will add your articles to OJB's Link page.

Jason, if you send me a summing-up of your three articles as normal .txt-file I will transform it to a forrest-compatible Howto and add it to OJB-docs.

regards,
Armin


Jason

Thomas Dudziak wrote:

On 6/24/05, Jason McKerr <[EMAIL PROTECTED]> wrote:
I've finished the second (more simple) installment of Spring with OJB if
anyone is interested.

http://staff.osuosl.org/~mckerrj/?p=4





First off, thanks for sharing this with us ! I use OJB with Spring for
several months now, but never got around writing a tutorial for it ;-)
Just a quick comment: the separation that Matt made concerning DAOs
and services is actually a really good idea because it separates
concerns - your actions want to execute business logic not database
accesses, and you can often want to combine several database accesses
into one business method. Also it greatly simplifies testing because
you can replace the DAOs easily (by using a different
applicationContext file) and thus test your services without having to
have a database at hand but instead against mock DAOs.

Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



------------------------------------------------------------------------

Included are three articles that are in-depth How-to's for using Spring 
Framework's declarative transaction engine with OJB's Persistence Broker 
implementation.  For each article, I have included a complete sample 
application with an embedded database that you can run.  They are simple to 
setup and require minimal configuration.

The first article covers a basic configuration and setup for integrating Spring 
with OJB.  It covers:
-Connecting to the database using Spring's local datasources 
(LocalOjbConfigurer)
-Register the appropriate transactionManager for use with OJB 
(PersistenceBrokerTransactionManager)
-Creating beans and interfaces for use with the database
-Having Spring handle transactions for the beans in declarative fashion

The article link is: http://staff.osuosl.org/~mckerrj/?p=3

The second article covers more advanced Spring usage, separating out the 
database implementation code from your Data Access Objects.  This is an 
important abstraction layer for controlling data access ubiquitously.

The article is http://staff.osuosl.org/~mckerrj/?p=4

The Third article covers using OJB's datasourcing and caching strategies.  The 
first two articles require local datasources and Per Broker caching because of 
the way that the OjbConfigurer works.  Now that we've completed basics of 
integrating OJB in Spring, this last entry shows how to use JNDI datasourcing 
with OJB and Spring, which in turn allows users to get back to other OJB 
caching strategies.

The article is: http://staff.osuosl.org/~mckerrj/?p=8

Jason


------------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to