This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Our application purpose is to keep upto date info to users .We dont have to use EJB or any other technolgy of j2ee except JSP,jdbc,servlet. Would JMS will be good idea if we use Application server for just messaging,because i have read in different article dont use EJBS until u need atleast 4-5 service of Application server. Please justify.
Originally posted by jawwad ahmed: ....dont use EJBS until u need atleast 4-5 service of Application server. Please justify.
didn't get that one.... could you please explain?
I'm not going to be a Rock Star. I'm going to be a LEGEND! --Freddie Mercury
Joined: Dec 01, 2001
From services i mean persistence secutirt,naming,distributed objects etc.
Joined: Nov 27, 2001
If you like to take advantage of the JMS api (asynchronous communication, message filtering, different types of messages, queues or topics, etc..), go ahead and use JMS. It all depends on your requirements, I'd say. But this doesn't mean you have to use an application server. There are many implementations of the JMS specification out there that you can use. OpenJMS, for example is one implementation. I've used it once and I didn't need EJB's at all, I just wanted to incorporate to my application asynchronous messaging. I wouldn't say:
dont use EJBS until u need atleast 4-5 service of Application server