• déploiements beaucoup plus rapides
• généralisation de Java 7 (par défaut pour toute nouvelle application)
• amélioration du plugin Maven, développé par l’équipe AppEngine, propose la génération de code Cloud Endpoints et se trouve (avec ses archetypes) dans Maven Central
• nouveau scheduling pour un auto-scaling encore plus efficace (perf et donc $/€)
• amélioration des performance de la console et de ses rapports de charge

Deux autres modifications concernent:

• la facturation (un nouveau système est maintenant en place) avec la suppression des $2.10 de “ticket d’entrée”
• l’introduction du Cloud SDK, une consolidation des outils en ligne de commande des différentes offres de Cloud Google: Storage, Compute Engine, CloudSQL, BigQuery et AppEngine

A partir de cette version les logs contiennent maintenant la version AppEngine.

Rendez-vous maintenant à Google I/O (15-17 mai 2013) pour une version avec son lot de nouveautés.
Ship early ship often!

• A (somewhat naive) lead and creator of the project caught in the middle of politics
• Red Hat’s experience with Netty influencing its current behavior
• VMWare claiming they have lots of open source experience too
• The idea that foundations would solve all the IP and governance issues
• My foundation is better than yours arguments
• The realization that neither Eclipse nor Apache are ideal
• Jenkins’ Kohsuke suggesting nonprofits for shared assets
• The Eclipse Foundation being called once again a trade association
• etc…

Clearly, as Simon Phipps writes in his column, “In an age of open source, it’s hard to acquire a technology” and this brings up what I think is a paradox for any open source believer :

This recent episode will make it even harder for startups to bet on open source to find funding and for companies to be acquired for their open source assets, thus in turn leading to less usage of open source.

In the end, isn’t this underlying a weakness of the greater open source cause or should open source technologies never be a reason to acquire (or sell) a company?

• What’s new with the Android SDK by Tor and Xav, mostly demo-driven.
• Securing the Client Side by Mike West. Get your security straight!
• Putting the App back into Web Apps by Seth Ladd. Dart and more.
• What’s new with Android by Romain & Chet. Covers 4.1 and 4.2.
• The complete 3-hour “Faster Web Sites – Crash course on web performance” part 1, part 2 by Ilya Grigorik. Take your time to go through the 3 hours but you’ll be glad you did!

If you like shorter formats, you might enjoy these 3 to 10-minute interviews with some of the Google speakers.

Améliorer son niveau d’anglais peut être parfois difficile si l’on n’est pas immergé dans un environnement de collègues parlant tous l’anglais. Il est aussi quasi-impossible de rester informé sur les dernières nouveautés technologiques sans maîtriser cette langue. L’apprentissage de la technologie et de l’anglais sont des efforts perpétuels.

Les ingénieurs ont de nombreuses opportunités de lire de la documentation, de communiquer avec des communautés open source, de visionner des vidéos sur YouTube, le tout en anglais et désormais il existe une méthode gratuite pour améliorer ses connaissances techniques et son anglais en même temps.

Apprendre l’anglais sur la chaîne Google Developers sur YouTube
Le principe ici est de rajouter des sous-titres de qualité aux vidéos techniques.

Ces sous-titres permettent :

• d’entraîner vos oreilles à un anglais parlé
• de consulter sur le champ la définition de mots que vous ignorez
• d’apprendre des constructions et des expressions propres à l’anglais parlé

Tout ceci est certainement plus efficace qu’une simple lecture ou écoute de contenu en anglais.

Tout le contenu produit dans le cadre de Google Developers Live (GDL) est proposé avec des sous-titres. Il s’agit d’une initiative de l’équipe Developer Relations de Google dont l’objectif est de promouvoir auprès des développeurs des technologies comme Chrome/HTML5, Android, ou le Cloud. Ces vidéos sont publiées immédiatement après leur passage en direct et les transcriptions manuelles (et donc à priori de qualité) sont habituellement disponibles dans les deux semaines suivantes.

Pour accéder aux sous-titres traduits manuellement, il vous suffit de choisir “Anglais” comme indiqué dans l’image ci-dessus. Si le bouton est rouge, le choix “Anglais” fait référence à une transcription de qualité effectuée par un humain.

Si vous êtes intéressés, il ne vous reste plus qu’à vous abonner à la chaîne Google Developers sur YouTube pour commencer à apprendre votre technologies favorite en même temps que d’améliorez votre anglais. Ces vidéos sont également accessibles depuis l’application YouTube sous Android et iOS.

Quelques vidéos recommandées

• Chrome: The Breakpoint
• HTML5: Chrome Special Event: Movi Kanti Revo—Behind the Divs
• Android: Android Design in Action: Responsive Design
• Cloud: Google BigQuery – New features (JSON, nested/repeated, improved data loading) + Office Hours

Of course, you’ll hear about Android, HTML5/Chrome and Cloud/AppEngine, but let me start with the less obvious Google content at Devoxx :

• Damon, the lead for ROSjava, will talk about “Cloud Robotics” (a good reason to stay until Friday), he has some amazing demos
• Tom will present j2objc, the recently announced Java to iOS Objective-C translation tool and runtime (also on Friday)
• Nicolas will be busy presenting on OAuth 2 (a very widely-used technology for Google) together with Tim Bray (the Google keynote speaker) as well as on the Google Drive SDK. Both talks are on Thursday.
• Probably the most hard-core Java talk by Google this year will be given by Jérôme and Nicholas on “Effective Dependency Injection“, a session based on experience refactoring massive projects such as GMail (and GlassFish). Also on Thursday.
• Ian should give a fun talk (a Wednesday BOF) on how to build a Google+ client in Clojure.

As you know Android 4.2 is around the corner, so you should expect a thing or two about this new version and likely even Nexus devices to check out at the Google booth. Scheduled Android content include (mostly duets as you can see) :

• Starting on Monday, Nick and Rich will offer a 3-hour-long Android Hands-on lab.
• On Tuesday, Romain and Chet will cover “Important Android Stuff” in a 3-hour University session. Expect important Android stuff.
• Another duet, Xav and Tor the tools guys, will offer an “Android Tools in Action” and a session on “What’s new in Android Developers’ Tools“.
• On Wednesday, Nick and Rich are back for a live Google Developer Live EMEA Office Hours session from the interview lounge.
• Romain and Chet have two regular 1-hour conference sessions on “What’s new with Android” and a more advanced graphics session titled “For butter or worse“.
• Xav will also cover the new Android build system in a BOF on Tuesday.
• There are many more Android talks from the community!

On the Web / HTML 5 / Chrome front, there’s also plenty of exciting sessions :

• Ilya is holding a 3-hour “Faster Websites: Crash Course on Frontend Performance” University talk on Tuesday and a Chrome DevTools talk on Wednesday.
• Seth will provide an update on the Dart side (Milestone 1 and beyond) in his “Putting the App back into Web Apps” session on Wednesday
• Mike will offer a “Building safe web applications with HTML5″ session, surely followed by many (security matters and sells)
• Paul will take a slightly different take on Chrome and HTML 5 with the newly announced Chrome Packaged Apps in a Wednesday evening BOF.
• Sam will cover exciting and bleeding-edge “disruptive media” technologies in HTML 5 such as WebRTC/getUserMedia() as well as “Fast UIs for the mobile web”, with both sessions are scheduled on Thursday.
• Last but not least, the AngularJS team (Igor, Vojta and Misko) are offering no less than a “Building awesome client-side web apps with AngularJS” Hands-on Lab on Tuesday, a “Re-imagining the browser with AngularJS” session on Thursday and a Testacular session on Tuesday.

I’ll have the privilege to help Ludo cover the Cloud content in the “What’s new with Google App Engine and Compute Engine” Thursday session. As the name implies, it’ll provide an update on AppEngine (lots of stuff happen in a year with the monthly releases) but also cover the newly introduced IaaS offering Compute Engine, and how the two play well together.

I also spotted a peculiar “The Future of Software Development Process Methodology Effectiveness” by Chet Haas’ homonym. Certainly a session that will get every agile practitioner happy that the conference is, after all, not agile-free!

Tim will be delivering the Google keynote on Thursday morning – “Life online”. That’s one keynote you don’t want to miss (demos included).

As part of the yearly innovation the Devoxx organizers have decided to bet on NFC Wristbands instead of the traditional conference badges. Google gladly provided a few Nexus devices. In addition to the Android applications for the conference (providing schedule and more) there’s one to interact with the Devoxx NFC Wristband. Check them out!

With all those great speakers around, you should also expect a series of interviews to be posted on the Google Developer YouTube Channel.

Finally, make sure you stop by the Google booth throughout the conference to meet the Googlers present ar Devoxx. The exhibition floor is open from Tuesday to Thursday. See you there!

Peut-être plus important encore que les sujets traités, les intervenants seront les directeurs de l’engineering Google responsable de ces produits. Une occasion donc de leur exposer vos problématiques techniques et stratégiques en matière de PaaS, IaaS et autres BigData.

N’oubliez pas de vous inscrire (gratuit) et de venir à l’heure ce vendredi matin, la salle n’étant pas la plus grande. Vous pouvez également indiqué votre venue sur ce Google+ Event.

With only 23% of people agreeing with the decision (on java.net) and with an “amount of disappointment, and even anger, as Project Jigsaw is deferred for a second time”, I was eager to read the alternate options Oracle would propose.

The part of the Q&A on Maven and OSGi makes for a good read. They’re not related to the Jigsaw change in plans per say but go check them out if you haven’t already. As for the rest, it turns out that everyone loves the new plan…

(Picture removed)

So here’s a short list of additional questions.

Is modularizing the JDK really the best way to prove Jigsaw works?
One of the top questions in the Q&A puts the modularization of the JDK itself as a pre-requisite for jigsaw’s integration in Java 8. While it’s a neat feature, a modular JDK would really mostly serve the JavaME camp, something Oracle, not the broader Java community, is generally interested in. There are many ways to validate the design and the implementation of Jigsaw with real-life Java applications and the JDK is not (by far) the best example of such an app. Modularization of the JDK, an implementation detail, can come later.

How much more time do you need?
The Q&A states that “a lot of progress” was made on Jigsaw, and I trust that to be very true, but what would have been really useful is to assess how much extra time was required to complete the work. Failing to do so simply slams the door on any alternate proposal based on a different release schedule.

Does longer JDK cycles really mean a later Jigsaw?
Speaking of the release cadence, those arguing for longer cycles are really asking for a Java 8 delay because they’re still trying to move to Java 7. So it’s probably safe to say that both those people asking for more frequent releases of Java and those calling for a delayed Java 8 all want Jigsaw earlier than the current 2015 plan. A lot of options would become possible if only Oracle was to reconsider the train model (one that has yet to be implemented anyhow).

By the way, as it stands, DateTime (JSR 310) has become a top-level feature of Java 8. As much as I appreciate its value I can’t help but think about the irony of the situation.

I don’t want to speak for the JavaEE camp but I also don’t believe modularity dropped off of their list of requirements (it was initially slated for Java EE 7). It seems that the requirements of Java EE, arguably one of JavaSE’s very top user and customer, have been ignored. Maybe it will comfort those in the community to know that being a colleague and a top customer comes with no privilege.

This is not a democracy
Of course, whether you and I like it or not, this is not a democracy and just like Twitter can upset its developer ecosystem, Oracle has the right to put its engineering cycles wherever it feels is right. I was hoping that the JDK team at Oracle would try its best to address the community concerns given the promise made less than 2 years ago but instead Java will be moving forward slowly. Very slowly.

(this is still of course my very personal opinion)

Les sujets traités vont de Android à Chrome en passant par Google+, AppEngine, YouTube, Maps et autres APIs Google.

Coté Cloud, il y a par exemple cette courte présentation des différentes solutions de stockage (Cloud Storage, Datastore et Cloud SQL) et de requêtage (REST, SQL, BigQuery). Il y a aussi des formats plus longs comme ce tutorial sur l’API Search d’AppEngine, un tutorial interactif sur l’API Google MAPS, cette session sur le language Dart couplée à une série de questions sur Google Moderator ou encore ces réflexions de Robert Scoble sur le monde des startups.

Coté Android, il y a les Office Hours (horaire Européen) pour poser ses questions et les Friday App Review (ici avec Reto Meier).

Vous trouverez un agenda complet sur le site Google Developer Live ainsi que tous le contenu archivé sur YouTube. Il se passe quelque chose tous les jours!

“Bon, et le contenu en français c’est pour quand?” Stay tuned!

L’API Google Maps est une des toutes premières API proposée par Google et probablement aussi une des plus populaire auprès des développeurs.

Cartes stylisées ou pas, l’usage gratuit de l’API est limité à 25 000 chargements de cartes par jour. Au delà il en coutera $0.50 pour 1000 chargements supplémentaires (après avoir initiallement été de $4). Les détails sont disponibles sur cette page. Il est important de comprendre qu’un chargement de carte (map load) est en réalité une instanciation de l’API Maps et non pas l’affichage de chaque tuile (tile). De telles limites existent également pour le geocoding, l’API Image Street View, etc.

Google estime à moins de 0,5% le nombre de sites concernés par cette règle des 25 000 chargements quotidiens. Dans les faits, les sites qui dépasseront cette limite tous les jours pendant plus de 90 jours consécutifs seront contactés par Google. Pas d’arrêt de service à prévoir en cas de popularité soudaine d’un site ou d’un service. Le meilleur moyen de mesurer sa consommation est de se connecter sur la Console Google API.

Tout ceci est applicable lorsque le site ou service qui utilise l’API Google Maps est librement accessible à tous. Les détails sont disponibles ici. Dans le cas contraire (éditeur de logiciel embarquant l’API par exemple), Google propose Maps API for Business.

Si vous avez besoin d’un “rafraichissement” sur l’API Google Maps, je vous invite à regarder cette présentation récente en français. Au rang des anecdotes, vous y apprendrez par exemple que Google Maps utilise une variante de la projection Mercator ou que ses tuiles sont des images 256×256 pixels. Si vous ne l’avez pas encore fait, la migration vers l’API v3 est fortement encouragée.

Comme pour toutes ses technologies, Google vous invite à poser vos question techniques sur StackOverflow et à suivre sa page Google+.

Enfin coté actualité produit, il y a désormais la possibilité de télécharger des cartes entières pour une utilisation hors-ligne, l’arrivée dans certaines villes du projet helicopter (vues à 45 degrés) et de nouvelles offres SaaS pour l’entreprise : Google Maps Engine, ou Google Maps Coordinate.

Runtime modularity in Java has been promised since JSR 277 was filed in 2005 and I wrote how excited I was about its potential back then. Seven (7!) years, a fair amount of OSGi lobbying and politics, Sun’s acquisition, and a plan B promise later, we’ve come to this day to learn that it’ll be pushed further out to 2015 which really means 2016 for a stable release and probably 2020 for a wide adoption. After being promised Java 8 with Jigsaw in late 2012 by Oracle, we’re now taking another 3-year hit because the project missed “the train”.

About resources and goals
Jigsaw has been Mark Reinhold’s baby project for all this time (Mark is the Chief Architect of Java) and I’m now hearing excuses about staffing issues. “Oracle failed to staff Java modularity effort for years”. Hey, now that’s a much better headline! The reality I believe is that Oracle still doesn’t know why it’s doing Jigsaw and thus giving it the proper priority is hard. Modularize the JRE itself to help with JavaME and JavaFX adoption? Offer a modules system for Java’s longer-term viability? A business case can certainly be put together to shrink down the JRE to get Oracle upper management on board. On the other hand, bringing the JVM, the compiler, and the language together around a modules system seems, sadly, to be falling off of Oracle’s radar.

About that train
The common wisdom is that the Eclipse way of shipping software is the best way to get a community of developers building on a platform. You’ve probably also heard of “release early release often”. Eclipse is a very special project which is really about providing a baseline for the Foundation members to build upon and I’d argue that Eclipse IDE users on the other side are not benefiting much from this release model. When it comes to Java, we’re talking about something that also has a diverse audience and I think developers remain far more important than vendors and that a cadenced release model is actually harmful. It’s easy to agree on shipping software when it’s fully baked but the two-year cycle is really the key issue here. Oracle should be able to declare Jigsaw a strategic goal and deliver it with an extra 6 to 12 months (which, by the way, would still mean 2+ years from now!).

About the community
Jigsaw has been presented for many many years by Sun and later Oracle as a key feature in numerous keynotes and conferences and promised in Java 7, Java 8 (in fact I’ve done my share of such promotion while at Oracle) and now Java 9. That has created a lot of expectations in the community. In fact, it’s not only about Java SE as a large portion of the Java ecosystem is also waiting for a standard modularity solution: JavaME, Java EE (see this sample IBM reaction when modularity had to be removed from EE 7), Groovy and other JVM languages and probably by many developers building non-trivial applications with Java. Surely there’s got to be a better way to convey bad news to the community than “sorry, we’ve missed the train!”. In retrospect, the plan A/plan B approach was a brilliant communication plan with Plan A really not being an option and the community rallying behind Plan B. It’s often about how things are conveyed, not only about what they convey.

About open source
I hear some say that this would not have happened if Java was truly open source with a community, not a company, overlooking its destiny. First, my definition of Open Source remains. IP and governance are (ideally) orthogonal to the license and no simple solution exists for all software projects. But more importantly, this is a sad case of a project’s failed risk mitigation (sadly a very common failure in our industry). To consider that a different governance model would have changed anything is wishful thinking. Innovative carefully crafted designs always come from a very small number of talented engineers and in fact, this may even be a case where going open source and transparent was not a good idea but rather a fatal distraction.

About what’s next
As I wrote above, Oracle has the resources to declare Jigsaw a strategic goal. I can agree that it may be hard to deliver by late 2013 but waiting for 2016 is effectively killing Jigsaw and encouraging everyone to look at alternatives which will jeopardize yet even more Jigsaw’s chances of ever seeing the light of day. In fact, even Oracle is considering profiles in Java 8, an ugly band-aid if you ask me. One you’ll need to painfully tear off to get proper modularity in the platform. Jigsaw really shouldn’t be seen as “a new feature”, to me it’s really the Java reboot some people have been calling for a long time. Only a compatible one.

Now of course this is all my personal take and I don’t pretend to know what’s good for Java nor represent the community at large. So getting some hard data about what the community expects from Jigsaw would be a good start before making any decision. I believe this has not been done so far. The closest I’ve seen is the recent JAXenter poll which isn’t very scientific (self-selected, somewhat biased questions).

So in the end, if the community wants Java 8 with its updated and stripped-down content (Lambda, maybe JSR 310, what else?) in 2013, Oracle and the JCP should deliver just that. Again, it’s about meeting expectations. But shipping a Java 8.5 with Jigsaw sooner than later should also be considered. And if there really needs to be a train release model, it has to be a yearly one and not every release needs to be a major one.

In a world where standing still is perceived as fossilization, bringing proper modularity to Java is what moving Java forward ™ is really about.

Avec ce nouveau programme, Google propose à des individus d’obtenir un titre d’expert à l’année pour l’un des domaines de prédilection de Google (Android, Cloud, HTML5, Chrome, Social, Geo, etc…).

Il ne s’agit bien entendu pas d’un rôle de porte-parole mais plus d’une reconnaissance apportée à une personne à la fois technique, experte et visible (présentations publiques, blog, commits, etc…). Ce titre lui permettra d’entretenir une relation avec Google (contact avec les developer advocates, access aux previews et plus encore) et de présenter lors de conférences développeurs.

Initiallement piloté en Israel et au Japon, le programme est désormais publique et actif en France comme l’indique la page des Experts actifs. Sa gestion est effectuée localement par Google France.

Maj: voici un billet sur GDE rédigé par le responsable du program au niveau mondial.

Pre-requisites

This paper assumes you have a CloudSQL database instance configured and (ideally) populated. You should have authorized your local machine using OAuth and the command-line tool and have the CloudSQL JDBC driver handy (it’s in the AppEngine SDK in lib/impl). If you need help on any of this, consider reading this Getting Started paper.

Here are the values used here :

1. Cloud SQL instance name : scott-tiger:scott
2. Database Name : jpetstore
3. JDBC Driver Class Name : com.google.cloud.sql.Driver
4. JDBC URL : jdbc:google:rdbms://scott-tiger:scott/jpetstore

By default the CloudSQL instance can be accessed with user root and an empty password.

This paper uses NetBeans (7.x) as the IDE and GlassFish (ships with NetBeans) as the local Java Application Server but everything should be easily adaptable for other tools such as Eclipse and other runtimes (tomcat, JBoss, etc).

NetBeans & CloudSQL

The NetBeans IDE offers a JDBC database explorer feature which you can use to access your CloudSQL database instance. In the NetBeans Services tab, chose Databases > Drivers and create a new driver configuration by pointing to the google_sql.jar archive and using com.google.cloud.sql.Driver as the JDBC driver name (should be auto-detected). Right-click this newly created JDBC driver and select “Connect With…” to create a new connection. Provide the username, the password and the full JDBC URL (jdbc:google:rdbms://scott-tiger:scott/jpetstore in my case) and test the connection.

You should now be able to navigate the database schema, view table content, manipulate data, and execute any SQL statement.

WebApp Project

We’ll now create a web application using JPA entities manipulating data from the Cloud SQL instance discussed above. We’ll deploy this application first to GlassFish, then to App Engine.

Within NetBeans, create a (Maven) Web Application project with GlassFish as the default target. Right-click on the project to select the “New Entity Classes from Database” wizard. Create a new data source using the JDBC connection defined in the previous step. Select the tables you want to create JPA entities for and do not check the “Create Persistence Unit” option (we’ll get back to this later). This generates standard JPA 2.0 @Entity-annotated classes for every table selected from CloudSQL.

Here’s a proper persistence.xml that will work with CloudSQL. Notice how this JPA persistence unit uses RESOURCE_LOCAL and not a JTA data source :

<persistence version="2.0">
  <persistence-unit name="CloudSQLPU" transaction-type="RESOURCE_LOCAL">
    <properties>
      <property name="javax.persistence.jdbc.url" value="jdbc:google:rdbms://scott-tiger:scott/jpetstore"/>
      <property name="javax.persistence.jdbc.user" value="user"/>
      <property name="javax.persistence.jdbc.password" value="pw"/>
      <property name="javax.persistence.jdbc.driver" value="com.google.cloud.sql.Driver"/>
    </properties>
  </persistence-unit>
</persistence>

Once this is setup, you can get a hold of this persistence unit in the servlet created by default the typical way you would in an servlet :

EntityManagerFactory emf = 
        Persistence.createEntityManagerFactory("CloudSQLPU");
EntityManager em = emf.createEntityManager();

A simple use to exercise the data could be to list all the names stored in the Category table (using its JPA entity representation) :

CriteriaQuery cq = em.getCriteriaBuilder().createQuery();
cq.select(cq.from(Category.class));
List<Category> categories = em.createQuery(cq).getResultList();

for (Category category : categories) {
    out.println(category.getName() + "<br/>");
}

Deploying this simple application to the GlassFish application server shouldn’t require any other changes. Obviously with this architecture, the performance is not ideal given the server is not exactly close to the data. Nevertheless, this demonstrates the standalone capabilities of CloudSQL

Ship it all to the cloud!

A better approach is to probably to use CloudSQL from a Google AppEngine-hosted application where all sorts of optimisations will quick in. To do so, only limited changes to the standard application described above are required.

The first simple change is to add the AppEngine-specific deployment descriptor appengine-web.xml :

<?xml version="1.0" encoding="UTF-8"?>
<appengine-web-app xmlns="http://appengine.google.com/ns/1.0"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <application>MyCloudSQLApp</application>
    <version>1</version>
    <threadsafe>true</threadsafe>
</appengine-web-app>

You’ll also need to change the name of the JDBC driver in persistence.xml (a more elegant solution could be to use Maven profiles to keep the project fully portable) :

- <property name="javax.persistence.jdbc.driver"
-          value="com.google.cloud.sql.Driver"/>
+ <property name="javax.persistence.jdbc.driver"
+         value="com.google.appengine.api.rdbms.AppEngineDriver"/>;

The JDBC URL remains the same.

Finally, you’ll need to bundle JPA / EclipseLink and BeanValidation / Hibernate Validator by making them runtime-scope dependencies. The Servlet and AppEngine SDK API artifacts should use the default scoping. Your mileage may vary when it comes to the implementation versions. Here is my complete set of Maven dependencies :

<dependencies>
        <dependency>
            <groupId>org.eclipse.persistence</groupId>
            <artifactId>eclipselink</artifactId>
            <version>2.3.2</version>
            <scope>compile</scope>
        </dependency>
        <dependency>
            <groupId>org.eclipse.persistence</groupId>
            <artifactId>javax.persistence</artifactId>
            <version>2.0.3</version>
            <scope>compile</scope>
        </dependency>
        <dependency>
            <groupId>javax.validation</groupId>
            <artifactId>validation-api</artifactId>
            <version>1.0.0.GA</version>
            <scope>compile</scope>
        </dependency>
        <dependency>
            <groupId>org.hibernate</groupId>
            <artifactId>hibernate-validator</artifactId>
            <version>4.2.0.Final</version>
            <scope>compile</scope>
        </dependency>
        <dependency>
            <groupId>javax.servlet</groupId>
            <artifactId>servlet-api</artifactId>
            <version>2.5</version>
        </dependency>
        <dependency>
            <groupId>com.google.appengine</groupId>
            <artifactId>appengine-api-1.0-sdk</artifactId>
            <version>1.7.0</version>
        </dependency>        
    </dependencies>

Make sure the AppEngine application is authorized to access the CloudSQL instance (use the API Console for that). Once this is all done, simply deploy the application to AppEngine :

$ appcfg.sh update target/MyCloudSQLApp-1.0.0-SNAPSHOT

You’ll find the CloudSQL developer documentation here.

Il y a tout d’abord l’arrivée d’AppEngine dans les data centers européens pour améliorer encore la latence des applications web mais aussi pour offrir une conformité en matière de localité des données aux entreprises qui le nécessitent. Cette fonctionnalité sera initialement offerte aux clients “Premier” et sera associée à une facturation en euros.

Le support de SSL sur des noms de domaine personnalisés est proposé avec deux variantes:
- SNI, partageant une même adresse IP pour plusieurs domaines, supporté par la plupart des navigateurs et disponible pour $9 par mois avec 5 certificats.
- VIP, une adresse IP dédiée à l’application permettant de servir un nom de serveur, un nom de domaine complet ou bien de multiples domaines pour $99 par mois.

D’autres nouveautés concernent :
- l’intégration du service PageSpeed pour les applications HRD pour un supplément de $0.39 le Go sortant
- un service intitulé “Cloud Enpoints” offrant une interface simple et authentifiée (Oauth2) en Rest pour des applications web et mobiles
- une limite de taille d’application désormais fixée à 1Go (contre 15Mo précédement)
- la possibilité de stocker et de chercher (rajout à la récente API de Search) selon des points géographiques

L’ensemble des nouveautés sont documentées dans les Release Notes et présentées en qq minutes dans cette vidéo de la conférence.

If you haven’t heard of or tried Cloud IDE yet, it’s a very fine IDE in a browser developed by eXo. While not on-par with your typical Eclipse/NetBeans/IntelliJ desktop solution it goes a long way offering multiple language support, code completion, syntax highlighting and integrated javadocs.

All of this goodness now integrates with AppEngine, both Java and Python. This means that you can start from Cloud IDE, seamlessly integrate with the AppEngine management tools to create the application, debug “locally” using the eXo infrastructure, and ship it to AppEngine. Here’s a short and sweet demo of this at work, all without ever leaving the browser:

Documentation for all of this is here.

Try it out for yourself!

With the new cloud.google.com website it should become clear that it’s much more than that with Google Cloud Storage, Google BigQuery, and more to come. Orthogonal, fully-managed services to built the best cloud apps.

The developer resources remain on : developers.google.com/appengine, developers.google.com/storage and developers.google.com/bigquery/.

Google I/O c’est la conférence Google pour les développeurs qui se tient à la fin du mois (du 27 au 29 juin 2012) à San Francisco.

Une seule keynote
Cette année la conférence dure 3 jours avec une keynote unique le mercredi 27 à 9h00 heure locale (18h en France). Celle-ci devrait durer 2h30 et comme chaque année de nombreuses annonces devraient y être faites.

Les Google Developer Groups de Paris et de Nantes et probablement d’autres encore seront partie prenante avec des événements locaux (connus sous le nom de I/O Extended) pour assister à la retransmission, pour échanger sur les annonces, regarder des sessions techniques, rencontrer des ingénieurs Google de Paris et participer à une session avec des ingénieurs Google en direct de San Francisco.

Inscriptions

* Inscriptions Paris, détails GDG Paris et PAUG.
* Détails et Inscriptions Nantes

En france, les “io-extended” sont organisés en partenariat avec les écoles du réseau Epitech. Toutes ces écoles devraient donc être connectées afin de retransmettre la keynote et les sessions qui suivent.

Posez vos questions!
Utilisez ce Google Moderator pour poser vos questions dès maintenant. La session avec des ingénieurs francophones en direct de I/O sera l’occasion de les passer en revue!

Tenez-vous au courant sur les événements I/O Extended en suivant la page Google+ de I/O Extended France.

The list of products and technologies community-supported on StackOverflow includes Google App Engine, Android, Google+, Maps, Google TV, Chrome, etc… Here are some of the product-specific tags tracked by Google employees :
google-app-engine
gae-datastore
google-maps
google-plus
android
google-tv
google-chrome
google-chrome-extension
google-chrome-devtools
google-drive-sdk

Part of the acceleration was the Devoxx conference for the first time in Paris after 10 yearly occurrences in Antwerp. It was my first time attending such a major developer conference in my home town and I took pride in having had the same shitty weather as in Belgium in November ;)

Joking aside, this 1200-participant event was a success by many metrics, not only was it sold out, but I believe it had the right level of content with labs, university sessions, inspiring keynotes (ok, not all of them), regular sessions, and of course socializing.

I’ve spent most of my time at the conference catching up with friends, meeting many new faces (quick, someone, give me glasses with face recognition!) and explaining my responsibilities in the new job.

Kudos to my colleague Martin Görner who had driven the project on the Google side for many weeks now. Speaking of Martin, you can look at his G+ page to see how active the Google booth was with PAUG and Paris GTUG-selected developer demos. Developers talking to developers!

On a somewhat more personal note, it felt great to see Ludo again (now working on AppEngine) as well as Romain Guy, Android Diva (in a good sense!). Meeting new colleagues (Petra, Nicolas, and others) was another highlight.

Devoxx is turning out to be a wild success across Europe. Can’t wait to spread more Google Developer love in future events!

Here are the highlights :
• It’s 5 GB of free space (and up to 16 TB)
• Client integration is available on Mac OS, Android and Windows (for now)
• It’s search-capable (supporting dozen’s of file formats) and thus much more than an online bunch of disks (OBOD)
• It has integration with Docs, Gmail, G+, Goggles, and more
• Maybe most importantly, it has an SDK

I feel very proud looking back at what we’ve achieved as a team with GlassFish in the past few years, including those past two years at Oracle. If you know anything about the history of application servers at Sun, you’ll recognize that building such a community around GlassFish and its amazing number of downloads is nothing short of a small miracle. The Java EE platform has also seen a strong resurgence, bringing it back to the forefront of effective enterprise Java development in many ways.

Having been hired by Sun some 13 years ago to sell NetDynamics I certainly feel that I leave the company’s application server in *much* better shape. Oracle has ambitious plans for GlassFish and has been in my opinion a good steward for this community. I see no reason for this to change and I do expect the community to keep on pushing Oracle to get even better with time.

This ride has been intense and the people I’ve met and worked with, both inside and outside Sun/Oracle, have made the experience the best one of my career.

My journey now continues here: alexismp.wordpress.com. See you there!

Rendez-vous ce mardi 13 mars 2012 pour une session intitulée Java.next() pour parler du futur de Java et plus précisément de Java SE 8, de Jigsaw et de Lambda (par Rémi Forax).

Ca fait un bail que je n’ai pas été au ParisJUG, ce sera un bon galop d’essai avant Devoxx France!

This is an Oracle event around Java where I’ll be a speaker together with my colleague Mike Keith.

Here are the details if you are interested in attending this free event :
• Oracle Canadian Java Briefing (English)
• Séance d’information sur Java (French)

The best (the only?) way to test both of these features without installing the JRockit JVM itself is to install Mission Control as an Eclipse (3.7) plugin using its update center.

Once you switch to the Mission Control perspective, locally running JVMs (Apple’s latest 1.6 JVM, the JDK 7 Developer Preview or OpenJDK) are all detected with “General”, “MBeans” and “Runtime” sections very much functional. It’s still early days with the Flight Recorder and Memory Leak Detector features not yet available.

Looking at a JVM running GlassFish 3.1.1, the application server AMX’s are available once you initiate a bootAMX operation.

Several folks asked me when my Java EE 6 session with Antonio Goncalves was scheduled (we’ve been covering this for the past two years in University sessions, hands-on labs and regular sessions). It turns out we didn’t team up this year (Antonio was crazy busy preparing for Devoxx France) and I had a regular GlassFish session. Instead, this year, Bert Ertman and Paul Bakker covered the 3-hour Java EE 6 University session (“Duke’s Duct Tape Adventures”) on the very first day (using GlassFish) with great success it seems. The Java EE 6 lab was also a hit with a full room of folks covering a lot of technical ground in 2.5 hours (with GlassFish of course).

GlassFish was also mentioned during Cameron Purdy’s keynote (pretty natural even if that surprised a number of folks that had not been closely following GlassFish) but also in Stephan Janssen‘s Keynote as the engine powering Parleys.com.

In fact Stephan was a speaker in the GlassFish session describing how they went from a single-instance Tomcat setup to a clustered GlassFish + MQ environment. Also in the session was Johan Vos (of Mollom fame, along other things). Both of these customer testimonials were made possible because GlassFish has been delivering full Java EE 6 implementations for almost two years now which is plenty of time to see serious production deployments on it.

The Java EE Gathering (BOF) was very well attended and very lively with many spec leads participating and discussing progress and also pain points with folks in the room. Thanks to all those attending this session, a good number of RFE’s, and priority points came out of this. While this wasn’t a GlassFish session by any means, it’s great to have the current RESTful Admin and upcoming Java EE 7 planned features be a satisfactory answer to some of the requests from the attendance.

Last but certainly not least, the GlassFish team is busy with Java EE 7 and version 4 of the product. This was discussed and shown during the Java EE keynote and in greater details in Jerome Dochez’ session. If any indication, the tweets on his demo (virtualization, provisioning, etc…) were very encouraging.

Java EE 6 adoption is doing great and GlassFish, being a production-quality reference implementation, is one of the first to benefit from this. And with GlassFish 4.0, we’re looking at increasing the product and community adoption by offering a pragmatic technical solution to Java EE PaaS deployments. Stay tuned ! (the impatient in you is encouraged to grab a 4.0 build and provide feedback).

GlassFish – Serveur Java EE Open Source et Opérationnel
Jeudi 3 novembre 2011
15h00 à Paris
10h00 à Montréal
S’enregister

jeudi 3 novembre 2010 de 9h30 à 16h30.
Oracle France – 15, boulevard du Général de Gaule 92715 Colombes

Au programme: présentation et labs (venir avec son portable).
Inscriptions en ligne (places limitées).

En parlant de GlassFish, voici un nouvel ouvrage en préparation.

Before I start I probably should say that while I don’t have hard data to back this up, I’ve seen a large number of JUG’s be created in the past 2-3 years, more than 10 years after Java was first introduced, accounting for maybe as much as half of today’s active JUGs. In France alone, there is more than a dozen active JUGs that were created, all in the last 3-4 years. There doesn’t seem to be a shortage of interest for Java, quite the opposite.

I don’t run a JUG nor am I really active in one but I’ve been visiting many of them in the past few years (they tend to be the format that I like best), I’ve seen a good number of them take off, some crash, and I interact with several JUG leaders on a regular basis, so I thought I’d share the ingredients that I believe are key to a successful JUG.

First, you need to have a venue. It may sound obvious but the lack of a regular (hopefully free-of-charge) room for your meetings is often the reason for JUG activity going down or simply disappearing. Universities seems to be the best solution after company meeting rooms.

Second, you need sponsors. While this can cover for Pizza & Beer (or Wine & Cheese, you decide), maybe more importantly this should help you cover for your speakers expenses (travel + hotel). While those speakers employed by large companies should be able to expense their entire travel, you don’t want to miss out on the independent consultants. Another option is to have formal JUG members paying a yearly fee. This works well once you have a well established set of events, including maybe a yearly (international) conference.

Third, last, and not least – you need good content. This is content that addresses your JUG’s interests and it doesn’t have to be always about bleeding edge technology of the latest and greatest JVM language. Some folks take JUG’s as a training, others mostly as a get-together, and probably also a good chunk as a way to stay on top of what’s new in the Java ecosystem. You need to balance different topics but my recommendation would be to have a small set of folks decide on the agenda. Voting or large groups of folks deciding don’t usually work too well.

While all of the above probably applies for any technology user group, JUG’s are a bit special because they are loosely federated by mailing lists and interactions are facilitated by Sun initially and now by Oracle. If you are starting a JUG, you probably want to read about it on this all-in-one page, be listed on java-user-groups and start chatting with fellow JUG leaders, they are a great bunch and will most certainly have tips for you.

I should of course not forget to mention that you’ll need energy and passion to keep a JUG running. Lot’s of it!