Rumors are that the next generation of Java CAPS will be based on a new Netbeans version. No more fights with the eDesigner, eventually. ICAN 5.0 and JCAPS 5.1 IDEs were based on a very old Netbeans (v 3.5) heavily customized by SeeBeyond, called the eDesigner. Additionally jcaps 6 JEE runtime is going to be Glassfish, the Sun open-source application server (at present jcaps runs over old SJAS 8.0).
For seasoned jcaps developers, used to workaround some eDesigner's weird behaviors, it will be a huge improvement, as Netbeans 6 represents probably the most advanced Java IDE in the market (and yes, I mean even better than Eclipse). Glassfish then is one of the best JEE 5 and EJB 3 implementation available, this means Java CAPS 6 is evolving to a complete and powerful Java enterprise application development environment, not limited to EAI only. That shows a strong Sun's commitment in favor of jcaps, good for both partners and customers.
According to a demo we saw, if you develop/edit 5.1.3 components in JCAPS 6, it will load the old eDesigner inside of JCAPS 6 (which is NetBeans 6.1) . No word on how easy the migration tool will be, to actually use the cool JCAPS 6 interface.
ReplyDeleteWhat I can see is different (see my next post with screenshot): Java CAPS components are really loaded into Netbeans 6.1, no more old, crappy eDesigner!
ReplyDeleteWhat happens is that you have kind of two version of the product, one called jcaps "classic" which is retro-compatible with 5.1, and the new mode which make use of OpenESB. That is necessary if you want to allow people to load older jcaps projects, but the IDE is really the brand new Netbeans.
Regards
Ciao,
ReplyDeleteI have created a small demo of Java CAPS 6 to connect to SAP in "repository based mode".
For the moment you can see a draft here:
http://lerognon.club.fr/jcaps6bapi/index.html
I will find the time to publish that on blogs.sun.com and explain better the interaction with JBI, OpenESB and so on.
Regards
Eric Lerognon.