since I'll have to deal with a lot of SQL operations in my Java code, I'm searching a suitable way to get my life easier.... I thought about SQLJ but I'm not sure if this technology really took off or if I should considerate it obsolete....
There are a few mentions of SQLJ over the net, most of them seem to suggest the days of SQLJ have already passed. There is certainly not widespread support for SQLJ these days and you could have difficulties find someone in a forum to help you if you run into problems.
I personally like the SQLJ idea. I didn't explore it yet, since I didn't want yet another tool to learn when I switched to Java a few years ago. If I started a new project nowadays, I'd probably try to see if it integrates to my IDE (or any IDE) and build process and might give it a try. Having SQL statically checked against a schema seems a big boon to me.
Some people suggest using an ORM framework (such as Hibernate), therefore avoiding the need for SQL (and by extension SQLJ) in the code.
Martin Vajsar wrote:I personally like the SQLJ idea. I didn't explore it yet, since I didn't want yet another tool to learn when I switched to Java a few years ago. If I started a new project nowadays, I'd probably try to see if it integrates to my IDE (or any IDE) and build process and might give it a try. Having SQL statically checked against a schema seems a big boon to me.
To be fair, the idea of embedding SQL in code is not that bad. C# has LINQ that can more or less do the same.
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.