We have just released our first Maintenance Release of JDBC RowSet Implementations. Check out the JDBC Technology Homepage to grab your latest copy.
JDBC 4.0 contains new features that will make it easier for developer
Applications written in different languages often manipulate the same records, and this shared access leads to a fundamental problem: How do you know that your data is in sync with the RDBMS?
A small case example of how inadequate access permissions can cause problems in unexpected ways over RMI. (or "The coding gods don't hate you, they just want you to work smarter")
This week I've been playing with some neat features in Struts 1.2, and also discovered the joys of Hypersonic
The TSSS happened a few days ago and many bloggers have posted comments about talks that covered the upcoming EJB 3.0 spec. I must say I'm really impressed by some of the major changes that (apparently) are going to be made, but some critical points still need to be addressed. This entry shows how EJB 3.0 could be simplified even more and be even more flexible than now.
The JSR 170 (Content Repository API) public review period is open until July 19, 2004.
In the quest for an object persistence solution that doesn't require duplication of information, writing XML mapping files, extending gross framework classes or implementing complicated interfaces, I stumbled across pBeans. If you use it with Groovy Beans, you can build a database-backed persistent object system in literally minutes.
JSR 243 for JDO 2.0 has just been approved. However, the approval has been vetoed by three vendors - IBM, BEA, and Oracle. What does this mean for the future of JDO 2.0?
I am a huge fan of O/R mappers like Hibernate and JDO. They insulate developers from the database mechanics, speeding up development and boosting productivity. They also add a layer of insulation above the database itself, which aids portability. However, insulating developers from the database layer completely is not always a good thing. Developers still need to be aware of the performance impact of the code they are writing at that moment
Bruce Tate's article "For JDO, the Time Is Now" brings up many good points, but it misses a key concern of mine: JDO and CMP should be complementary rather then competing solutions
In the old client-server days, we used only two layers: data (based on SQL) and the user interface, which was proprietary. Is that approach now dead? Or are there times when this old fashioned approach to application development is applicable?
Joshua discusses why the networked applications are coming and what UI technology we will need to build them.
The Hibernate project has released version 2.1 of their open-source (LGPL) object/relational persistence system.
When someone asks me, "What is the JSP EL good for, who is using it?", and they throw in some other questions relating to it, this is how I answer.
Ever find that you need a database, but don't want to hassle with installing one? Me too. Then I stumbled on SQLite.
A look at some of the announcements (Hibernate, Rave), a look at some of the technologies people have been talking about (AspectJ), and a question regarding embeddable Java technologies (JSP servers and Java databases).