mercredi nov. 19, 2008

NetBeans 6.5 ou le grand écart entre Java EE et PHP

Les mois et les années passent et les versions de NetBeans apportent régulièrement leur lot de nouvelles fonctionnalités et d'amélioration de l'existant. Le tout avec un périmètre fonctionnel impressionnant. Les tchèques (l'essentiel de l'équipe NetBeans est à Prague) sont de redoutables ingénieurs.

NetBeans 6.5

Vu de ma fenêtre GlassFish j'apprécie beaucoup la compilation incrémentale et le déploiement instantané qui, completé par la préservation de sessions dans GlassFish v3 (lors de re-déploiements), donnent un paradigme de développement sauvegarde/rechargement très séduisant. Plus de compilation, de packaging, de déploiement explicites et autres redémarrages.

Le support Groovy et Grails est désormais intégré dans l'outils (là aussi le support Grails de GlassFish v3 est un bon complément), laissant ainsi Eclipse à la traine dans ce domaine en attendant les améliorations annoncées lors du rachat de G2One par SpringSource. La concurrence n'a (presque) que du bon.

Le support de Spring, Hibernate est amélioré, ainsi que la gestion de MySQL. Si on rajoute à ce dernier un support très abouti de PHP (refactoring, debug, ...), le bundle PHP de 24 Mb devrait en intéresser plus d'un. Le debug JavaScript coté client est une autre petite touche sympathique.

Enfin, vous avez aimé le support de JRuby, C/C++, JavaScript, Groovy, PHP, voici maintenant Python en Early access.

mercredi août 13, 2008

NetBeans 6.5 beta est disponible

On ne chôme pas au coeur de l'été chez NetBeans. Je suis sur un build intermédiaire de NetBeans 6.5 depuis fin juillet (après M1) et je compte passer à la 6.5 beta qui est maintenant disponible avec une collection de nouvelles fonctionnalités :
• Ouverture confirmée aux langages autres que Java (au delà de C/C++ et jRuby): Groovy et Grails (clin d'oeil à Guillaume ;), JavaScript (éditeur et débugger pour Firefox et IE), et PHP. C'est vrai dans l'IDE et son éditeur, mais aussi dans ses runtimes (GlassFish v3 par exemple)
• "Compile on Save" et "Deploy on change" (mais que reste-il à Eclipse ;-)
• intégration de GlassFish v3 "Prélude" prévu pour l'automne (kernel OSGi, démarrage ultra-rapide, support Web Conteneur Java, jRuby/Rails, Groovy/Grails, etc...)
• Complétion de code dans l'éditeur SQL et autres améliorations
• Complétion de code CSS/HTML
• Intégration native du support Hibernate (clin d'oeil à Emmanuel ;)
• Amélioration du JSF CRUD Generator (Ajax et plus flexible)
• Plus besoin de rajouter la bibliothèque Subversion (historiquement nécessaire pour des raisons de licence)
• autres fonctionnalités décrites sur le wiki...

Comme toujours les téléchargements sont proposés entre 18Mb tout mouillé pour C/C++ (Java SE est à 28Mb et PHP à 20Mb) au tout-en-un qui fait 203 Mb (3 runtimes Java EE, JavaME et tous les outils SOA inclus) et la possibilité d'installer petit et de rajouter tout le reste avec le centre de mise à jour.

mercredi juin 25, 2008

Groovy/Grails support in soon-to-come NetBeans 6.5

NetBeans 6.5 Milestone 1 is around the corner and the schedule promises a release date in a few months only. Demo extraordinaire Roman announces the integration of the Groovy/Grails plugins in the core of the IDE (not sure how it translates in terms of download bundles) and also tells you about his new job at Sun. Good luck Roman and folks!

jeudi janv. 03, 2008

SDPY - Happy Birthday Groovy

Groovy 1.0 is one year old. Version 1.5 has been released since and while Sun has been more focused on JRuby, Groovy and Grails are fairly well supported in both NetBeans and GlassFish.

jeudi juin 14, 2007

SDPY - Groovy

I'm starting a new category. Not that I don't like tags, I do (they let you do consume blogs in all sorts of interesting ways), but I though I'd comment some Same Day Previous Year (SDPY) posts.

A year ago exactly I was mentioning Groovy getting a new leader. Well, needless to say that Guillaume Laforge and the rest of the Groovy team have done a lot of progress pulling out a 1.0 for a technology some people considered was no longer relevant given how often 1.0 promises were made.

Oh and Guillaume is a really nice (almost always ;-) laid back guy too.

mercredi janv. 03, 2007

Groovy 1.0

Guillaume (Groovy leader) is proud to announce Groovy 1.0. Everyone (Romain "MVS" Guy, Charles "JRuby" Nutter, have already all congratulated the Groovy team. Given the time and dedication it took for Groovy to release a 1.0 version, I wonder if this could be considered straight as a 1.1...

It's only been 9 months or so since Guillaume took over the projet, so I think he deserves a lot of credit for turning around what some people considered a sinking ship.

I'm glad to see yet another promising language mature on the JVM. This one has been built from the ground up for the JVM which is both a strength (quite natural to learn for Java developers and already producing bytecode) and a weakness (a language out of nowhere needs to pick up steam). The 'Javaness' of Groovy is really important. I've heard here and there that while Ruby and certainly RoR is hot, people are not "willing to learn a totally new language to gain a little productivity on CRUD applications". While this is certainly exagerated, there's some truth to it and JRuby may well be much more relevant to Ruby developers than to the armies of Java developers. In a JSR 233 world, one size does not fit all and Groovy/Grails have their shot at getting a good chunk of the market.

It's kinda trendy to have key commiters join big companies (especially Sun lately). This hasn't happened yet for Groovy (although Jochen Theodorou was hired to work fulltime on Groovy). Now my personal Sun wish list to the Groovy world (or whoever feels concerned) :
- have Groovy run as an alternative to JavaScript in Phobos
- have Grails move to more standard Java EE 5 technologies such as JPA and JSF (on GlassFish of course)
- first class IDE support (NetBeans 6.0 in my case)
- read "Groovy in Action" (that's my AI of course)

To keep up with Groovy:

Oh and I'm looking forward to the Guillaume JavaPosse interview... Tor predicting Groovy/Grails a great future and Dick being a long-time Groovy fan and user should be make this all a nice but long overdue moment.

mercredi juil. 28, 2004

enum Topic {JavaOne, Rich Java, Tools, Creator}

So, I'm back home from JavaOne. I must say that I had a good time. This may sound very politically correct, but for starters, this year's conference was more technical and more united (IBM, JBoss, etc...) and the networking was great as always.

But hey, one big news is that I'm now blogging! This is really a Sun corporate thing as even Jonathan Schwartz has started his own blog and I believe all this blogging ecology is a very natural thing given Sun's culture. One of the best things about JavaOne is that you can meet people and be curious. I was lucky enough to meet Tim Bray at a Sun-internal conference a few days before JavaOne. His talk was concise and pretty fascinating. Tim seems to be very curious (see here) and has this wonderful ability to explain in simple words pretty much any concept or technology. This, together with Pat's repeated suggestions (thanks for the comment, I now have to live up to the reputation!), is really what got be started with this whole blogging thing. Hopefully I talked my French colleague Eric Mahé into starting his blog real soon.

But back to JavaOne, the things I'm taking back are mainly these :

Tiger: huge release (I'll probably spend the next few week reading O'Reilly's Developer's Notebook) and long release. Still need to wait until late September before it's final. So far, compatibility has been the good surprise of this release. I'm still tracking performance figures, but they already seem pretty good (broader OS/Processor support certainly is a plus there).

Creator / JSF: this was a big topic at the conference and since I've been meeting with many customers lately on the subject I'm glad the product is finally out. It still has a long way to go compared to its non-Java competition, but the basis are very good - JSF for Corporated Developers rather than the "Now my tool does JSF too" approach. One interesting experience I had was with a J2EE customer looking for a RAD tool. He gave Creator the advantage (even before it hit final release) over Microsoft's Visual Studio arguing standard J2EE applications and integration with his existing infrastructure were more important to this him than a mature full-featured product like Visual Studio. Now you can't comment Creator without mentionning JSF. While it is still pretty early in the game, I think that it can do most of what STRUTS does (STRUTS really needs to inovate to keep being up to speed technically) and that while it lacks some features from other frameworks, it is leveling the ground for a great UI component market, providing standard and scalable MVC2 infrastructure but most importantly it was built with tools in mind from day one.

JDNC / JDIC / JavaWebStart: this is really about rich clients and I must say that I like GUI development, that I share many ideas with Amy Fowler (once a JSF spec-lead!) but also that many customers are looking into a better alternative to web clients trying to behave like rich ones. These customers need to have better end-user experience, not require a server for simple things like sorting, but also notification, keyboard-driven application, off-line usage, etc. So, when talking about rich clients using Java on the desktop, there's really three issue: (1) JRE deployment, (2) Application deployment, (3) Java client technology. In the enterprise, (1) can be solved using Windows/Linux masters, Active Directory deployments, or silent installs. (2) is really Java Web Start's job and the technology really got better with version 5.0 - better desktop integration, single instance, lock-down feature, extensive enterprise configuration, smart card support, Pack200 compression, etc. (3) is about Swing vs. SWT and which protocol to choose to talk back to the server. I believe that Swing's increased performance and look-and-feel, JDNC's ease of development (although it's not final and tools are not yet available), JDIC and the Netbeans Platform (not the IDE) are many good reasons for making a strategic choice for Java and Swing as the base technology for competitive rich-based Java clients. The protocol is something I may address in another blog, but let's just say Web Services are not the cure for now as there's no portable stub API and JAX-RPC is not yet part of J2SE, sorry JDK 5.0.

Tools: even looking just at Sun, there's more to tools than just Java Studio Creator! A few things worth noting: Borland joined the JTC (Java Tools Community, Beehive (BEA's new open source project) gained support from Eclipse. Borland now provides some of their tools for Eclipse developers! Meanwhile, NetBeans is making huge progress with its upcoming 4.0 release:refactoring, performance tuning using JFuid technology, ANT-based build system, Tiger (JDK 5.0) support, and J2EE support including EJB and Web Services. I guess an eclipse just can't last forever! Also, Java Studio Enterprise (the commercial version of Sun's tools) previewed UML two-way-editing-with-no-annotation support (nice reverse-engineering demo), collaborative tools (instant messaging for the developer), integrated profiling tools (most of them demoed during James Gosling's general session). Also showed during a technical session was a very nice-looking real-world (i.e. document-centric, long-runing, asynchronous, and conversational) Web Services developement prototype based on Crupi's J2EE extented design patterns (this is all part of the Kitty Hawk project focusing on SOA). Most other tool vendors are coming out with support for things like "visual" Struts, EAI, BPEL, etc. As always, timing is everything and future will tell if UML or JSF are more relevant than BPEL and Struts in 2005. I don't have the answer.

Java & Open Source: no, Sun has not open sourced Java and I believe the debate with James Gosling and others did a good job of asking the main questions: what does Open Sourcing Java really mean and what's in for the developer? To have at least one Open Source implementation of Java? That's already true for J2EE and certainly possible with J2SE JDK. Sun could stick an open source license on Java and not solve the developers pains (this isn't necesseraly true for die-hard OSS bigots who are said to be looking at Mono as a java replacement). The belief is that Sun can fix many issues developers face (bug fixing is probably the top one) without open sourcing java, and weekly builds are a visible first step. It's sun's Glasnost experience.

Among other hot topics, AOP, scripting (Groovy, JSR 223) and EJB 3.0 (J2EE 5.0) were on my todo list and still are (at least before I can comment them here). All have in common great potential, but also the risk of fragmenting either the platform or the community.

Wow, this was a long blog, maybe too long. Next ones will be more bistro-style.

This blog has moved

Alexis Moussine-Pouchkine's Weblog

GlassFish - Stay Connected


« août 2016

No bookmarks in folder


No bookmarks in folder