Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Very important fot me!!!!  RSS feed

Ahamed Sharif
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi to everyone,
It was a argument in my company,
why Java beans cannot use on serverside components??
but java beans also using on serverside but why??
why EJB only can use on serverside components??
What is the difference between these two?? ofcourse i got
some links to difference between these 2 technologies but i read
some materials Java beans has been extended for serverside programming
also then i did not understand why again has been extended??
and I did not give proper explaination of these two technlogies
in my meeting.
So i need some real examples to explain between these 2 technologies
and how can I explain to clear picture of these 2 technologies??
Because upto now I used java beans on Tomcat and Axis for web services,
but my plan is to use EJB instead of java beans using some application
server but if I plan to change from java beans to EJB these arguments were
coming in my meeting..
As for I know java beans is for client side components and
EJB is for server side componenets, but why java bens again using
on serverside also this one i am not understanding please any one
give some real examples to understand clearly..
Lasse Koskela
Posts: 11962
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You can use JavaBeans on both client-side and server-side. They're just plain old J2SE. Enterprise JavaBeans, on the other hand, are J2EE and thus not available for a standalone Swing application, for example. EJBs need a J2EE application server. Now, the reason why EJBs need a J2EE server is that EJB provides certain services such as transaction management, declarative security, caching, remoting, etc., which are not provided by the JVM alone.
In general, if you don't see a need for distributing your application logic, or using the transactional features of EJB, you'll probably be better off using the plain old JavaBeans.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!