File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Struts and the fly likes J2ee complaints .. when we will say Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Frameworks » Struts
Bookmark "J2ee complaints .. when we will say" Watch "J2ee complaints .. when we will say" New topic
Author

J2ee complaints .. when we will say

kolkata halder
Greenhorn

Joined: Jun 06, 2006
Posts: 8
I have two fundamental questions.


1.when we will call an application J2ee complaint

2.If we can do all activities using jsp and servlet then why we will think for j2ee.IF we can make mvc pattern using jsp/servlet is there any need for j2ee.
Merrill Higginson
Ranch Hand

Joined: Feb 15, 2005
Posts: 4864
when we will call an application J2ee complaint

It is the creators of Java Application Servers that have to worry about whether their products are "J2EE compliant", not application developers. When the JCP (Java Community Process) publishes a specification of J2EE (Now called Java EE, by the way, not J2EE) If the creator of an Application Server makes a product that conforms to all the specifications, submits it for review, and pays a fee to Sun Microsystems, that manufacturer can claim that their product is J2EE or Java EE version x.x compliant.

As far as application developers are concerned, if they create an application and it runs on a J2EE Application server, it's automatically J2EE compliant.

If we can do all activities using jsp and servlet then why we will think for j2ee.IF we can make mvc pattern using jsp/servlet is there any need for j2ee.


The above question indicates a misunderstanding of what J2EE is. J2EE encompasses a number of other specifications, including the servlet spec, and the JSP spec. So, when you write servlets and JSPs, you are using J2EE.

I suspect that the question you may be meaning to ask is "If we can do everything with Servlets and JSPs, why do we need Enterprise Java Beans (EJBs)?". My answer is, it's true, you can get by without using them. However, they do offer some powerful features that you may want or need in your application, such as security, transactions, remote calls, etc. The EJB spec has been much criticised because of it's bulkiness and complexity. The latest EJB spec (Java EE 5) is much better than previous ones, and much simpler to implement.

My advice is to find out what functions are available in EJBs, and then decide if you need or want those functions. If you don't, then just continue happily developing your applications without them.


Merrill
Consultant, Sima Solutions
kolkata halder
Greenhorn

Joined: Jun 06, 2006
Posts: 8
thx a lot.
really i had big confusion over those two questions.
now it's clear.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: J2ee complaints .. when we will say
 
Similar Threads
passing parameters from servlet to jsp
JSTL with struts?
slow initial jsp - - - suggestions needed to fast it up.
Front Controller doubt
New to J2EE: Is browser only option as the front end tool in J2EE