On 3/10/11 7:02 AM, bfischer wrote:
Hi all,
Unfortunately I'm only subscribed to this list - so I recognized the
announcement on the start page right now. That's my fault - but I like to
follow invitation for a comment at the end of the announcement.
First of all and to say it short - Camel is great and sure, developers
decide about the "future" of a project.
On the other side I don't understand that 26.88% of all customers running
their application on Sun JDK 1.5 (taken from survey) means "virtual no
interest in java 1.5".
We are on the way to choose ActiveMq and Camel as base for our
application(s) - but we are bound to Java 1.5 because of the commercial
environment we have to work with. Staying on Camel V2.6 "for ever" (or for a
longer time) isn't a convinient option for a new project.
Right now we are thinking about "compiling" our own "distribution" but we
aren't sure how big are the differences between Java 1.5 and 1.6 in reality
and finally how high the effort will be.
As there are some API changes between the Java 1.5 and 1.6, if you want
to build the code from trunk with Java 1.5, you may face some troubles,
like changing code and maintaining the changes yourself.
Do someone know about whether some of the commercial supporters (e.g. fuse
or others) are providing still support for Java 1.5?
FuseSource still maintains Camel 2.6 branch which is keeping merging the
bugs fixings and some important enhancements from the trunk.
You may consider to ask commercial support for that.
If all this options aren't successful than Camel isn't an option any longer
for us.
Would be a pity ...
-----
Bernd Fischer
GK Software AG
bfisc...@gk-software.com
--
View this message in context:
http://camel.465427.n5.nabble.com/Dropping-support-for-Java1-5-tp3419554p3419554.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
