Skip to main content



      Home
Home » Newcomers » Newcomers » SE vs EE(Corporate project - camel, activemq, jms, spring, web)
SE vs EE [message #847190] Tue, 17 April 2012 00:39 Go to next message
Eclipse UserFriend
Currently our team has SE JDK 1.7 installed in our boxes with:
- Eclipse Indigo SR2
- Tomcat 7.0.22
- Camel 2.9
- ActiveMQ 5.5.1
- Spring 3.1.0
- JMS
In the near future, we are going to develop web project creating servlets, JavaBeans, JSP, JAX-WS, JAXB plus middle-tier components like EJB..etc.
1. We were told that we don't need Java EE but this seems to be contrary from what we have read on internet? Can someone shed the light on this?
2. Can we keep Java SE and install Java EE on top of it? or do we have to un-install Java SE?
3. Which Java EE version do we need? Does it always come with glassfish? Is there one suitable for web development but without glassfish?
4. There is one called "Java EE 6 Web Profile SDK Upd 4 w/ Java 7 Upd 3". Is that one okay?
5. Does it matter that some of the developers are using Eclipse Helios instead of Indigo? Thanks!
Re: SE vs EE [message #847640 is a reply to message #847190] Tue, 17 April 2012 09:57 Go to previous messageGo to next message
Eclipse UserFriend
On 4/16/2012 10:39 PM, roy lou wrote:
> Currently our team has SE JDK 1.7 installed in our boxes with:
> - Eclipse Indigo SR2
> - Tomcat 7.0.22
> - Camel 2.9
> - ActiveMQ 5.5.1
> - Spring 3.1.0
> - JMS
> In the near future, we are going to develop web project creating
> servlets, JavaBeans, JSP, JAX-WS, JAXB plus middle-tier components like
> EJB..etc.
> 1. We were told that we don't need Java EE but this seems to be contrary
> from what we have read on internet? Can someone shed the light on this?
> 2. Can we keep Java SE and install Java EE on top of it? or do we have
> to un-install Java SE?
> 3. Which Java EE version do we need? Does it always come with glassfish?
> Is there one suitable for web development but without glassfish?
> 4. There is one called "Java EE 6 Web Profile SDK Upd 4 w/ Java 7 Upd
> 3". Is that one okay?
> 5. Does it matter that some of the developers are using Eclipse Helios
> instead of Indigo? Thanks!

This is really more a Java question...

1. Java EE includes web-relevant support. Of course, Maven will fix
everything in terms of where and what you're getting JAR-wise.
Increasingly, you have to acquire a lot of experience in Java, Eclipse
and development to be able to avoid using Maven as it's everywhere
preached and used, like beer or religion. (I remain steadfastly pagan,
however.)

2. I ignore whatever Java my host is relying on, I use Ubuntu, but also
Windows in my life. On both platforms, I routinely download and explode
one or more separate, private JDKs locally to my user to which I wire up
Eclipse via the -vm option in eclipse.ini, and then again in Window ->
Preferences -> Java -> Installed JREs. That way, I'm never bugged by
updates to my host and I don't bug my host with what I wish to run on.
(There's no reason you must do it this way; I think most do not. It was
a lot bigger deal back in the days when I had to straddle Java 4/Java 5.)

3. For some time, JavaEE has come with Glassfish. It only takes up a bit
more room, however, there are lots of advanced (Java 6- and Java
7-relevant) classes down inside there, some of which you might wish to
use whether or not, like me, you choose not to use Glassfish the server
container.

4. Whatever you use, unless your hardware/OS requires special treatment,
use nothing else than what you can get at http://java.sun.com. Wave your
mouse over the Downloads link at top in the middle, then choose Java for
Developers under the Popular Downloads cartouche in the resulting pop-up.

5. Helios was a dynamite release of Eclipse, the best ever (I started on
the eve of the Europa release). Likely Indigo will follow suit. I rarely
if ever hear of insurmountable trouble with Indigo any more, though I'm
still using Helios (I've downloaded and used Indigo, but just not gone
to the trouble to remake my launchers and install all my software
fancies in it yet). If you're just starting out, why not use the latest?

Hope this helps.
Re: SE vs EE [message #847985 is a reply to message #847640] Tue, 17 April 2012 17:10 Go to previous messageGo to next message
Eclipse UserFriend
Indigo came out last June. Unless you have explicit reasons to stay on Helios, I can't imagine why you wouldn't already be on Indigo SR2. And the parts of the Java EE APIs your application would rely on are provided as part of the server software you intend to target. Unless there's something specifically in the Java EE SDK that you need, you probably won't need it at all.
Re: SE vs EE [message #851652 is a reply to message #847985] Sat, 21 April 2012 02:31 Go to previous message
Eclipse UserFriend
Thank you for all the valuable information. Currently we have decided to stay with Java SE and see how far Maven can provide the support without Java EE. We are new to Java and learning everything bit by bit here and there. We appreciate that some of the things we stumbled upon can actually be resolved from here. Again, thank you all very much!
Previous Topic:Content Assist - Scrapbook
Next Topic:problem with websphere application server
Goto Forum:
  


Current Time: Fri Sep 12 10:59:36 EDT 2025

Powered by FUDForum. Page generated in 0.05506 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top