Edited by author 04-24-2001 13:45
Please add your comments the jRelational Framework (http://jrf.sourceforge.net).

For example, you could include some or all of these types of things:

• How you see this framework comparing to other relational mapping tools.
• Strengths you see in this framework.
• Weaknesses you see in this framwork.
• The kinds of tasks it does well for.
• The kinds of tasks it does not do well at.
• Why you chose this framework.
• What other technologies are you using this with? (EJB, Struts, JSP, etc.)
• What kind of application are you building with jRF (B-to-B, web store, client-server, etc.)
  

Thank you! Other users will appreciate the feedback, both positive and negative.

I haven't tried other relational mapping tools, but I did look at brief blurbs about several and explored the docs of some. I'd found a page in a webzine that listed about 30 related tools. These are the things that drew me and my colleagues to it over other solutions:

• open source
• straightforward and understandable
• well documented
• offered under the respected SourceForge auspices
• seemed to have a reasonably sized user community
• Explicity doesn't try to hide SQL knowledge (we really liked that)
• once I got going and had questions, your response was quick and knowledgable

Current weakness is that it doesn't go very far beyond single table mapping (though you're working on that) -- but it shouldn't go very far if it wants to keep the same appeal of simplicity.
We're using it with JSP, though not directly -- layers between.
The app is a financial marketplace.

Excellent work! Please keep it up!

Ditto to all of the positive comments already posted. I had written an O/R mapper last year, but quickly adopted JRF as soon as I encountered it. I have made very good use of the schema-based source generator. I like the ease of extending and modifying the classes. I have used JRF with Jakarta Struts in two non-profit organization web sites to great advantage. Jonathan and the people on the user list have been very helpful when I have had questions. I look forward to a little more "out of the box" relational mapping, but it is not that much trouble to do anyway. A great tool!

We evaluated JRF to be used between Oracle and EJBs but decided against it after some performance tests. I found it a good easy to use mapping tool but due to out required throughput we need PreparedStatements for all SQL

Our company has used JRF successfully on several projects. Great job!!

Recently I evaluated JRF and Cocobase for a new project. JRF was by far easier to use and had a much lower ramp-up time. There is a little more coding work up front with JRF, but usage is far simpler. Plus the source generation class provided me with 80% - 90% of what I needed anyway. We are currently using JRF for the project and are very pleased with it. Also, the documentation for JRF was outstanding.