• Post Reply Bookmark Topic Watch Topic
  • New Topic

EJB3.0 & usage of j2ee patterns

 
manish ahuja
Ranch Hand
Posts: 312
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All

I hope this question makes sense to all of you. From last week onwards I have been reading a lot of preliminary docs on EJB3.0 & enhnacements introduced in EJB with release3.

On the face of it seems , SUN really has managed to make EJB more approchable & intutive to the developer community. It has really sharpened the rough edges prevailing in EJB2 & also seems to be a good strategy to counter Dotnet.

My question is we had a lot of J2EE design patterns like (Value Objects, Service Locator etc) which were more a workaround to overcome the shortcomings of EJB2.
Do these patterns now become redundant with the advent of EJB3.

Rgrds
manish
 
Valentin Crettaz
Gold Digger
Sheriff
Posts: 7610
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Moving this thread over to the EJB and Other J2EE technologies. Please continue this discussion there. Thank you
 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Value objects - Yes it will become redundant. I am not sure about ServiceLocator since it it not clear to me how the client lookup code will look like.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!