by Anonymous Coward writes:
on Wednesday November 05, 2003 @12:46PM (#7397279)
I'm a C++ coder whoose boss needs him to go on a course to learn J2EE/JBoss for an upcoming project. The thing is, I'd much rather stick to C++ if I can - is there any feasible way of implementing typical J2EE projects in C++ instead of Java?
The first thing you state is 'don't be an idiot.' Then you go into a tyrade about how idiots need Java because they can't handle C++. So if you want the guy to not be an idiot, shouldn't he be using C++???
From my limited experience, it appears that servlets simply wrap cgi functionality into a nice little package. Why not consider using cgicc (http://www.gnu.org/software/cgicc/cgicc.html) for C++ applications.
Like another poster said, it depends on what part of J2EE you're talking about here. In general, J2EE components rely on containers (specific to the component) which do a lot of lifting for you.
I'm unaware of any C/C++ implementation of an EJB container for instance. However with the Axis C/C++ implementation (notice I've segue'd back into the topic here), it opens up the possibility of a C/C++ client talking to a SOAP-wrapped J2EE server tier.
I used to be a pretty heavy C++ guy back in the day. I've been doing almost exclusively Java for the last (gawd!) 7 or so years. I really don't miss C++ at all. Especially the maintenance headaches induced by implementations of large domain models. The larger the model the more it seemed to spin out of control with C++. It still has a tendency to spin out of control with Java, but not to the same degree.
Well, I came from your perspective a couple of years ago and had to go down J2EE route. I wish I hadn't but then again, I may well have had greater regrets if I had stuck with C++. EJB overhead is pretty horrendous but does provide locking, persistence, transactions, concurrency, caching, DB pooling, security, clustering.
I dont think clustering would be necessary without huge overhead introduced by J2EE, but its no picnic either way.
If a thing's worth doing, it is worth doing badly.
-- G.K. Chesterton
Hmm... (Score:0)
Re:Hmm... (Score:1)
Re:Hmm... (Score:2, Insightful)
If you just need to create a webservice, then this (Axis c++) is all you need.
If you need your thing to run in an EJB or Servlet container, ie: your backend has to be J2EE, then you may be out of luck.
You might want to consider the course (if it's free!).
Re:Hmm... (Score:1)
Re:Hmm... (Score:4, Interesting)
I'm unaware of any C/C++ implementation of an EJB container for instance. However with the Axis C/C++ implementation (notice I've segue'd back into the topic here), it opens up the possibility of a C/C++ client talking to a SOAP-wrapped J2EE server tier.
I used to be a pretty heavy C++ guy back in the day. I've been doing almost exclusively Java for the last (gawd!) 7 or so years. I really don't miss C++ at all. Especially the maintenance headaches induced by implementations of large domain models. The larger the model the more it seemed to spin out of control with C++. It still has a tendency to spin out of control with Java, but not to the same degree.
I could go on here, but I think I've said enough.
Re:Hmm... (Score:2)
Java Servlets are simple and easy to work with; you can get started with them and JSP pages (or Velocity) pretty simply.
bite the bullet, go on, learn a bit of Java. It is easier than learning C++.
Re:Hmm... (Score:2)
I dont think clustering would be necessary without huge overhead introduced by J2EE, but its no picnic either way.