• Post Reply Bookmark Topic Watch Topic
  • New Topic

To Bruce Tate and Justin  RSS feed

 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Bruce and Justin,

Welcome to Javaranch!

I have some questions for you.

1. What motivated you to write this book?

2. Where can I get Table of Contents of the book.

3. What is your opinion regarding Spring and Hibernate ? Do you recommend us to use them in enterprise applications -Do they scale well ? Is it better to write applications using open source products or stick to standards like J2EE i.e. Open source vs standrds debate.

4.Please talk about the future of EJB particularly since 3.0 is on its way? Are you happy with the draft.

5. Your opinion on using annotations in EJB 3.0. I am not sure whether there will be vendor specific annoations. If yes will it not cause portability problem as I will have to change the source code. How do we handle this case.

6. Your thoughts on the new persistence API by Sun.
http://java.sun.com/j2ee/letter/persistence.html

Thanks a lot!
 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Bruce and Justin,

How do you compare PicoContainer with Spring?
 
B Tate
Author
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Good questions. I decided to write this book because I was not having much success as an EJB developer. You can read an article called "Don't Make me Eat the Elephant Again" at java.net, and that sums up the experience well for me.

- You can get the toc at the O'Reilly site. We actually have the preface on line there, and there are a few sample chapters at the server side as well. The core principles are simplicity, focus, transparency, foundations, and extensibility. We address each of these, and then measure Hibernate and Spring against those criteria, and then show an application.

- Definitely recommend Spring and Hibernate for enterprise applications. If your relational model is different from your data model and is highly normalized, you may get better milage out of Kodo JDO instead, but Hibernate is ideal for many applications.

- Read "Don't Make me Eat the Elephant Again" on java.net for answer to EJB 3. It's better, but a lightweight container plus, say, Hibernate, is better still for most simpler applications.

- Annotations in EJB 3 are overused. Combines too much metadata into the code that should be broken out, and also couples container with annotations.

- New API is very good move. See elephant article at java.net.
 
B Tate
Author
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Good question on pico vs Spring.

- Pico is a lightweight container. Uses dependency injection design pattern. Is very simple, uses primarily constructor based injection (though not exclusively).

- Spring is a lightweight container (with DI also). Uses setter based injection mostly (though supports constructor injection also.) The biggest difference is that Spring has helper classes to let you do things like remoting, declarative transactions, and persistence. You can add these services to POJO (plain old Java objects).

I hope this helps.

-bt
 
Karthik Guru
Ranch Hand
Posts: 1209
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by B Tate:

- Annotations in EJB 3 are overused. Combines too much metadata into the code that should be broken out, and also couples container with annotations.



Bruce I have some idea of annotations. It probably does what XDoclet already does except that you can query the class at runtime and figure what kind of services are needed for the object at runtime and container can apply them accordingly?.

When do we say that annotations are overused. Would it be possible for you to give me any examples?

Say am using XDoclet for an EJB, and am adding an XDoclet tag that specifies the role that the caller needs to subscribe to , would you call it overuse? since that can be changed during deployment and hence s'd go in a descriptor and not into source file?.

Adding XDoclet container specific tags(weblogic, jboss etc) ...would this qualify as an overuse?

Say I beleive that a method s'd always execute in a new transaction, this I would think belongs in the source file.
 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Definitely recommend Spring and Hibernate for enterprise applications


Thanks Bruce. Could you please name some enterprises which have successfully adopted Spring and Hibernate. Thanks again.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!