The easiest framework for Java Database applications developmentreleased for production use

[Tom Anderson]

It is .NET and not directly applicable.

But it seems to me that your approach and DAAB (especially in early
versions) share some philosophy.

I'm too lazy too look myself, but i'll ask: does this framework do
anything iBatis or Spring JDBC templates don't?

tom

 

[Arved Sandstrom]

On 11-02-08 09:44 AM, yaormaAdmin wrote:
[ SNIP ]

Thanks for the comments Wojtek. In the example code the connection is
instantiated using the DriverManager just to make the example simpler
(and so it stands on its own, without needing additional
dependencies). The Yaorma framework has been used in several
applications using pooled connections. Most of this work has used
Tomcat and would only run inside some sort of container. I'll look
into Proxool more, thanks for the tip. What would you consider the
gold standard for a connection pool for a desktop/rich client (Swing,
RCP, etc.) application?

Thanks again,
John

I dunno about "gold standards", but C3PO is a much-used connection
pooling library.

AHS

 

[Arved Sandstrom]

On 11-02-08 09:44 AM, yaormaAdmin wrote:
[ SNIP ]

Thanks for the comments Wojtek. In the example code the connection is
instantiated using the DriverManager just to make the example simpler
(and so it stands on its own, without needing additional
dependencies). The Yaorma framework has been used in several
applications using pooled connections. Most of this work has used
Tomcat and would only run inside some sort of container. I'll look
into Proxool more, thanks for the tip. What would you consider the
gold standard for a connection pool for a desktop/rich client (Swing,
RCP, etc.) application?

Thanks again,
John

I dunno about "gold standards", but C3PO is a much-used connection
pooling library.

AHS

And that should be c3p0. ('0' not 'O')

I've been working with J2EE apps that operate in production under
moderately heavy load, and they have used c3p0 for years 24/7.

AHS

 

[Arne Vajhøj]

yaormaAdmin wrote :

Or you could just use a connection pool manager such as proxool. Use
proxool to log into the database and then it manages all of that. DB
connections which are idle for a given number of milliseconds are
automatically closed. So all of the extra coding to fit yet another
framework is not needed

Plus you get far better DB performance under load as you do not need the
expensive connection establishment for every DB operation.

It is good advice to use a connection pool.

But if you don't close the connections then they
are not returned to the pool and the pool will run
out of connections very quickly.

Arne

 

[Arne Vajhøj]

Thanks for the comments Wojtek. In the example code the connection is
instantiated using the DriverManager just to make the example simpler
(and so it stands on its own, without needing additional
dependencies). The Yaorma framework has been used in several
applications using pooled connections. Most of this work has used
Tomcat and would only run inside some sort of container. I'll look
into Proxool more, thanks for the tip. What would you consider the
gold standard for a connection pool for a desktop/rich client (Swing,
RCP, etc.) application?

Desktop apps does not always need connection pools - I may even say
that they rarely need it.

http://commons.apache.org/dbcp/ is good database connection pool.

Arne

 

[Lew]

And that should be c3p0. ('0' not 'O')

I've been working with J2EE apps that operate in production under moderately
heavy load, and they have used c3p0 for years 24/7.

Do they pay George Lucas for that name, the way the cellphone world does for
"Droid"?

--
Lew
Ceci n'est pas une fenêtre.
..___________.
|###] | [###|
|##/ | *\##|
|#/ * | \#|
|#----|----#|
|| | * ||
|o * | o|
|_____|_____|
|===========|

 

[Arne Vajhøj]

I'm too lazy too look myself, but i'll ask: does this framework do
anything iBatis or Spring JDBC templates don't?

I don't know them that well.

But based on my limited knowledge then:
* iBatis is an ORM (a database centric ORM)
* Spring JDBC template provide some of the same features
as DAAB and Yaorma, but has has a strong focus on the
data processing part and is not quote as simple

Arne

 

[Wojtek]

Arne Vajhøj wrote :

It is good advice to use a connection pool.

But if you don't close the connections then they
are not returned to the pool and the pool will run
out of connections very quickly.

proxool auto-closes idle connections

 

[Lew]

Arne Vajhøj wrote :

proxool auto-closes idle connections

After how long? This is no refutation of Arne's point.

Pretty much every pooling library supports the auto-close of idle connections,
e.g., DBCP does. Since all the major ones do, there's no reason to use a
pooler that lacks the feature.

The default for DBCP is to allow five minutes before calling a connection
"abandoned".

Under heavy load, abandoned connections can be a problem, During that five
minutes (or whatever), a lot of connections can be rejected if all the pool's
connections are in use or abandoned but not yet auto-closed. So Arne's advice
is correct, even in the face of auto-close being enabled.

--
Lew
Ceci n'est pas une fenêtre.
..___________.
|###] | [###|
|##/ | *\##|
|#/ * | \#|
|#----|----#|
|| | * ||
|o * | o|
|_____|_____|
|===========|

 

[Tom Anderson]

I don't know them that well.

But based on my limited knowledge then:
* iBatis is an ORM (a database centric ORM)
* Spring JDBC template provide some of the same features
as DAAB and Yaorma, but has has a strong focus on the
data processing part and is not quote as simple

Cheers.

tom