On Thu, Mar 10, 2011 at 12:44 AM, Hadrian Zbarcea <hzbar...@gmail.com> wrote: > Hi Bernd, > > First of thanks for using camel and for taking the time to express your > thoughts. Much appreciated. > > Comments inline. > > Hadrian > > On Mar 10, 2011, at 12: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. > Perfect. > >> >> First of all and to say it short - Camel is great and sure, developers >> decide about the "future" of a project. > Actually the community decides and users are part of the community too. We > strongly encourage you to express your thoughts and your needs. > >> >> 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". > What I meant was no interest in java 1.5 for new development. We know of > users who have camel in production running on java 1.5, but for applications > that have no interest of migrating to a newer version of the jre, there is no > interest in migration to a new version of camel either at this point. It just > works, and that's it. > > As far as I know you are actually the first to express interest in continued > development on java 1.5 since the announcement was made a month ago. > >> >> 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. > Well, staying on Java 1.5 "for ever" may not be convenient either. >
Other Apache projects is dropping JDK 1.5 support for their next major release such as AMQ 5.5, SMX 4.4 etc. >> >> 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. > Personally I would encourage you to try that. It is not that hard and the > best thing would be to continue maintaing the code from the camel-2.6.0 tag. > If you need help, you will probably get many of your questions answered on > this list. I wouldn't expect a lot of fixes/maintenance to be necessary as > you'll probably focus not on enhancing the camel framework, but just keep it > running in your very controlled application (unless I misinterpret your > needs). > >> >> Do someone know about whether some of the commercial supporters (e.g. fuse >> or others) are providing still support for Java 1.5? > You can ask that on the fusesource forums for an authoritative answer or > maybe one of the fuse engineers will answer here. > Talend is another company supporting Camel, but I know it does not support it > on jdk 1.5. > Yes FuseSource continue to support Camel 2.6 on JDK 1.5. In fact we have cherry picked commits from trunk and applied on our 2.6 branch. That means you will get the latest bug fixes and important improvements, and depending on customer needs, even new features as well. Here is a snippet from some of the latest merges we have done on the 2.6 branch: * fb88adb 2011-03-09 | CAMEL-3769: Fixed issue when using starttls with camel-mail. Thanks to Alfred for the patch. (HEA * ac7614d 2011-03-06 | CAMEL-3760: Fixed thrad pools naming not being quoted when registered in JMX. [Claus Ibsen] * f0b235b 2011-03-04 | Fixed potential NPE on startup due IoC wiring invoking static method with null CamelContext. [Cla * 0cdfb84 2011-03-04 | CAMEL-3749: Fixed issue with SFTP producer using temp file name and writing with no leading path * 8858959 2011-03-02 | CAMEL-3740 excluded the servlet spec dependency in the camel-servlet [Willem Ning Jiang] * 5f38098 2011-03-01 | CAMEL-3733 Added comments on isUseRouteBuilder method of CamelContextTestSupport [Willem Ning Jia * a7f89df 2011-03-01 | CAMEL-3733 Added comments on isUseRouteBuilder method of CamelContextTestSupport [Willem Ning Jia * 138f4af 2011-03-01 | CAMEL-3731: Logging ignored exception at DEBUG level instead of INFO. [Claus Ibsen] * 9e67ce4 2011-02-28 | CAMEL-3650: SMSC initiated unbind spawns exponential amounts of reconnect threads [Christian Muel * 9fea6b4 2011-02-28 | CAMEL-3727: Fixed recipient list in parallel mode creating a new thread pool for aggregator backg * 7fab7fa 2011-02-28 | CAMEL-3727: Fixed recipient list in parallel mode creating a new thread pool for aggregator backg * fa99630 2011-02-28 | CAMEL-3570: only output address info in toString for snmp endpoint to avoid showing credentails o * 894bea5 2011-02-27 | CAMEL-3650: SMSC initiated unbind spawns exponential amounts of reconnect threads [Christian Muel * e7305a6 2011-02-26 | CAMEL-3720: Disable optimize concurrent gets. Thanks to Dan for the patch. [Claus Ibsen] * 63679e1 2011-02-25 | CAMEL-3718: Fixed OracleAQ not supporting JMSReplyTo and thrown exception on accessing. [Claus Ib * a3e48d6 2011-02-25 | Fixed CS. [Claus Ibsen] * a02acaf 2011-02-25 | [CAMEL-3620] Blueprint container goes 'GracePeriod' if component is defined in the same XML file * 5d93f0a 2011-02-24 | CAMEL-3711: Fixed onException with same type is preserved in same order when route is built [Clau * 80cf6a7 2011-02-24 | Fixed CS error of OsgiServletRegisterer [Willem Ning Jiang] * 682b012 2011-02-24 | CAMEL-3713. Checkstyle fix. [Hadrian Zbarcea] * d73eccf 2011-02-24 | CAMEL-3713. Fix for duplicate mail attachments. Thanks to Paul for providing the patch. [Hadrian * 15d5f62 2011-02-23 | Avoid using tcp port for testing to avoid issues with port number in use at CI servers. [Claus Ib * 0d0c3d2 2011-02-23 | CAMEL-3692: Fixed Boolean getter/setter being java bean spec compliant. Make it easier to use int * 9411e01 2011-02-21 | CAMEL-3694: Do not use CXF continuation if option is disabled [Claus Ibsen] * 4838e5d 2011-02-21 | CAMEL-3694: camel-cxf will lazy initialize CXF Continuation, so its only used if enabled. Thanks * 10ccdc6 2011-02-21 | Fixed camel-jms working with Spring 2.x [davsclaus] * 468c707 2011-02-21 | CAMEL-3687: camel-javaspace now works with latest gigaspaes. Thanks to David Greco for patch. [Cl * af35fde 2011-02-21 | CAMEL-3690: Fixed endpoints not being registers in services to close as endpoints is enlisted in * 9892409 2011-02-19 | CAMEL-3685: Fixed splitter in parallel mode blocking if nothing to iterate during splitting. [Cla * c608e42 2011-02-18 | CAMEL-3683 Updated the content message header of multi-part request in camel-cxf component [Wille * 131520f 2011-02-18 | CAMEL-3681: Added byte[] to DOMSource converter. [Claus Ibsen] * 571794e 2011-02-17 | CAMEL-3678: Added endChoice in the DSL so you can use any EIPs inside the Content Based Router an * 194ee89 2011-02-19 | Update parent pom version [Hiram Chirino] * 36d090f 2011-02-17 | CAMEL-3675: Fixed <jmxAgent> supporting property placeholders in the disabled option. [Claus Ibse * 2a2dd2a 2011-02-16 | fix for https://issues.apache.org/jira/browse/CAMEL-3672 [Robert Davies] * a044c4c 2011-02-16 | Avoid poential NPE when stopping jms consumer. [Claus Ibsen] * 85c82e4 2011-02-16 | CAMEL-3670: Fixed concurrency issue with bean component when choosing method to invoke. BeanInfo * bfab9af 2011-02-16 | Polished. [Claus Ibsen] * 04d1d48 2011-02-15 | CAMEL-3650: SMSC initiated unbind spawns exponential amounts of reconnect threads [Christian Muel * cd99baf 2011-02-15 | CAMEL-3666: Content-Type can be optional. Thanks to Fernando for the patch. [Claus Ibsen] * a5425b3 2011-02-14 | CAMEL-3665: AdviceWith will now fail if using error handler, as its not supported. Fixed potentia * 5fec62d 2011-02-14 | Mark ref as @Required for throwException EIP for tooling purpose [Claus Ibsen] * c954dde 2011-02-14 | CAMEL-3664: Fixed NPE in toString [Claus Ibsen] * fd5fdb1 2011-02-13 | CAMEL-3650: SMSC initiated unbind spawns exponential amounts of reconnect threads [Christian Muel * 59c65dc 2011-02-13 | added missing license and notice file [Christian Mueller] * b93e7a4 2011-02-13 | added missing license and notice file [Christian Mueller] * 07b3e27 2011-02-13 | added missing license and notice file [Christian Mueller] * d4b5dc6 2011-02-13 | added missing license and notice file [Christian Mueller] * bcd6709 2011-02-11 | CAMEL-3650: SMSC initiated unbind spawns exponential amounts of reconnect threads [Christian Muel * 2430004 2011-02-11 | CAMEL-3654: BinaryPredicate is now thread safe. [Claus Ibsen] * ae68234 2011-02-11 | Fixed test. [Claus Ibsen] * 58a60a2 2011-02-11 | CAMEL-3640: Lucene should type convert to String for headers and not type cast. [Claus Ibsen] * 48435fa 2011-02-11 | CAMEL-3644: Added getter for endpoints in the abstract XML CamelContext FactoryBean so its avail * 4f00ed8 2011-02-11 | CAMEL-3653: Fixed sonartype issues. Thanks to Tracy for patch. [Claus Ibsen] * 001d5e3 2011-02-11 | CAMEL-3639: Fixed sonortype reported issue. Thanks to Tracy Snell for the patch. [Claus Ibsen] * 332994a 2011-02-10 | CAMEL-3652: Fix the Sonar Critical issue: Performance - Inefficient use of keySet iterator instea * 26ba9bb 2011-02-18 | Fixed pom.xml invalid tags [davsclaus] * 5b7bf12 2011-02-10 | CAMEL-3650: SMSC initiated unbind spawns exponential amounts of reconnect threads [Christian Muel * 4cb895d 2011-02-09 | CAMEL-3647: Fix the Sonar Blocker: Performance - Maps and sets of URLs can be performance hogs [C * 5c1e2db 2011-02-09 | removed a bunch more default JAXB default values so that by default we only marshal attributes wh * ea5e9c1 2011-02-09 | CAMEL-3268: Fix features-maven-plugin validate goal, remove tabs and fix a few minor issues in th * 726df02 2011-02-09 | avoid outputting a deprecated attribute when marshalling the XML [James Strachan] * cba35c5 2011-02-09 | ensured that the deprecated attribute is optional, not mandatory for the endpoint element [James * 7e19954 2011-02-09 | CAMEL-2853 - camel-stream - tailing logfile does not seem to work when logfile is rolled over upd * 7f42038 2011-02-17 | Make sure we use an apache version for maven test dependencies [Guillaume Nodet] * da79585 2011-02-17 | Merge branch '2.6.x-fuse' of ssh://forge.fusesource.com/camel into 2.6.x-fuse [Guillaume Nodet] |\ >> If all this options aren't successful than Camel isn't an option any longer >> for us. >> >> Would be a pity ... > Just out of curiosity, what would the alternative be? > > >> >> ----- >> 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. > > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
