Matt RaibleMatt Raible is a Web Developer and Java Champion. Connect with him on LinkedIn.

The Angular Mini-Book The Angular Mini-Book is a guide to getting started with Angular. You'll learn how to develop a bare-bones application, test it, and deploy it. Then you'll move on to adding Bootstrap, Angular Material, continuous integration, and authentication.

Spring Boot is a popular framework for building REST APIs. You'll learn how to integrate Angular with Spring Boot and use security best practices like HTTPS and a content security policy.

For book updates, follow @angular_book on Twitter.

The JHipster Mini-Book The JHipster Mini-Book is a guide to getting started with hip technologies today: Angular, Bootstrap, and Spring Boot. All of these frameworks are wrapped up in an easy-to-use project called JHipster.

This book shows you how to build an app with JHipster, and guides you through the plethora of tools, techniques and options you can use. Furthermore, it explains the UI and API building blocks so you understand the underpinnings of your great application.

For book updates, follow @jhipster-book on Twitter.

10+ YEARS


Over 10 years ago, I wrote my first blog post. Since then, I've authored books, had kids, traveled the world, found Trish and blogged about it all.
« Damn | Main | Indian Summer »

An ORM Standard: EJB and JDO cooperating?!

Dion mentioned this might happen: Happy Harmony for EJB3 & JDO. This is very cool IMO - and I hope it works out. I'd love to see a standard way to map POJOs to databases. The best part is both camps hope to move quickly on this.

The technical objective for this new POJO persistence model is to provide a single object/relational mapping facility for all Java application developers that works in both J2SE and J2EE. The work will be done within the J2EE 5.0 time frame.

Posted in Java at Sep 24 2004, 04:29:28 PM MDT 2 Comments
Comments:

Matt, that would be good to see. From a pure OO position, EJB is kind of a hack, IMHO. I hate that the context object contains operations that only apply to certain types of EJB's. All the interfaces that don't have to be implemented but are required. It just is not the kind of OO art java heads like.

Posted by 67.176.118.130 on September 25, 2004 at 11:01 AM MDT #

A lot of smart people think this is good. I am not in the group that think this is good.;-)
JDOQL and EQL are not as good as ANSI SQL on a DB engine. People will get better use out of JDBC as DAO then EJB as DAO. I a Celko Book, SQL for Smarties... not one of those tekniques works with EQL.
98% of time you do not need transaction more than DB commit/rollback
Petstore is a vampire, keeps coming back. There are better DAO's. iBatis PetStore is now Apache, that is a good example
.NET is better than EJB. DAO is better than .NET.
JCP has enough vendors showing of technology. They need users so that they solve problems we have - not technology looking for a problem. Like ... why would I EJB for muti row CRUD when I have alternatives.
Users show file a lawsuit against vendors that lie if the vendor promises that EJB is fast an simple, and if then EJB's ad to project complexity.
"goal of programing is to control complexity" - K&R!
Enough w/ the elephats.

.V

Posted by Vic on September 25, 2004 at 01:30 PM MDT #

Post a Comment:
  • HTML Syntax: Allowed