• issue #33 Enable uploaded photo title modification
• issue #41 Malformed Gallery 2 URL leads to G2Android forced close
• issue #37 Uploaded photo looses .jpg file extension
• issue #42 Feature Suggestion: Provide automatic login when started
• issue #20 Share via camera app?
• issue #15 Enhancement: Add multiple photo uploading

The major new feature is clearly the « add photo to gallery » feature : I created a new Activity, UploadPhoto , which can be called from 2 external intents :

AndroidManifest.xml

 <activity android:name=".activity.UploadPhoto" android:label="@string/upload_photo_title" >
                        <intent -filter>
                                        <action android:name="android.intent.action.SEND" />
                                        <action android:name="android.intent.action.SEND_MULTIPLE" />
                                        <category android:name="android.intent.category.DEFAULT" />
                                        <data android:mimeType="image/*" />
                        </intent>
 </activity>

So now the user can send a new photo or a batch of photos from another application, the android gallery app for example; the big work was then to decode the URIs of the photos to find the photo file on the phone, and then send it to the gallery; also I had to make sure that the user is still connected to the gallery, if not, he must login again.

Also, the user is now able to take a picture and send it to his gallery, without leaving g2android; this has been done adding the camera permission in the AndroidManifest.xml :

<uses -permission android:name="android.permission.CAMERA"></uses>

This is the easy part
Then, when your app receive a photo from the Camera, it does not receive an URI pointing to a photo file; nope, you get a Bitmap object you have transform into a file, to be able to send it to the remote gallery :

UploadPhoto

                                                Bundle extras = intent.getExtras();
                                                Bitmap bm = null;
                                                Object o = extras.get("data");
                                                if (o != null && o instanceof Bitmap) {
                                                        bm = (Bitmap) o;
                                                        try {
                                                                StringBuilder stringBuilder = new StringBuilder();
                                                                stringBuilder.append(Settings
                                                                                .getG2AndroidPath(this));
                                                                stringBuilder.append("/");
                                                                StringBuilder stringBuilderFileName = new StringBuilder();
                                                                stringBuilderFileName.append(fileName);
                                                                stringBuilderFileName
                                                                                .append(System.currentTimeMillis());
                                                                stringBuilderFileName.append(".jpg");
                                                                stringBuilder.append(stringBuilderFileName);
                                                                imageFromCamera = new File(
                                                                                stringBuilder.toString());
                                                                FileOutputStream fos = new FileOutputStream(
                                                                                imageFromCamera);
                                                                bm.compress(CompressFormat.JPEG, 100, fos);
                                                                fos.flush();
                                                                fos.close();
 
                                                                mImageUri=Uri.fromFile(imageFromCamera);
                                                                fileName = stringBuilderFileName.toString();
 
                                                        } catch (FileNotFoundException e) {
                                                                ShowUtils.getInstance().alertFileProblem(e.getMessage(),this);
                                                        } catch (IOException e) {
                                                                ShowUtils.getInstance().alertFileProblem(e.getMessage(),this);
                                                        }
 
                                                }

I also optimized the application, issue #37 (Uploaded photo looses .jpg file extension) was in fact due to the fact that I re created the photo file before sending it; instead of using a projection of the URI to get its path on the phone :

UriUtils

public static String getFileNameFromUri(Uri uri, Activity activity) {
                String[] projection = { MediaStore.Images.ImageColumns.DISPLAY_NAME };
                String fileName=null;
                Cursor c = activity.managedQuery(uri, projection, null, null, null);
                if (c != null && c.moveToFirst()) {
                        fileName = c.getString(0);
                }
                return fileName;
}

Also shipping with this new version, Chinese i18n thanks to the chinese android market, GoAPK and also new art from Dan, who just posted a comment to the blog proposing to add new art; thanks again to you both ! You make the application richer !

So now, what remains to be done ? well, the compatibility with Gallery3, as the G3 remote API is almost stable now, thanks to the work of Bharat, Tim, and many others; a java implementation is already under work, I will check if I can use it instead of… re inventing the wheel !
More details to come, for sure !

You can download G2Android from the Android Market, SlideMe, Applibs, etc.. and also from the G2Android project homepage
.
Enjoy this app as much as I enjoy working on it, and if you like it, don’t forget to flattr me !

-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y

So for example, if you want to debug an ant launch (launched via « ant -f myBuild.xml » for example), you simply have to set ANT_OPTS; on windows :

set ANT_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y

Another example, with JBoss :

set JAVA_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y

and then you can debug your launch with Eclipse, for example, creating a new debug configuration (remote java application on port 8787) !
Option : you can choose whether or not the application should wait for your debugger setting suspend to y or n.

• Wireshark (anciennement ethereal) / Linux
  Cet outil, c’est le couteau suisse de l’analyse réseau; et pas simplement HTTP : il peut analyser les trames TCP, UDP et tout ce qu’il y a au dessus (HTTP, FTP, SMTP, etc…)
• TCPTrace / Windows
  Comme son nom l’indique, il permet d’analyser les trames TCP : spécifier un port d’écoute sur votre machine locale, un port de destination, une hôte de destination, configurer votre client HTTP que vous désirez tester; et le tour est joué : tous vos échanges seront loggés !
• HttpViewer , en ligne
  Il ne permet que d’analyser les trames HTTP, mais son gros avantage c’est qu’il n’y a aucune installation à effectuer, c’est un outil en ligne !

• No more automatic connection at startup, the user has to push a button to connect to the gallery

• Galleries with port different than 80 now work

• I18n : the app now provide new languages, today only english and french are supported, I’m expecting the community to provide new translations

That’s all folks, expect better UIs and possibility to download pictures from the gallery to the phone soon.
Have fun browsing your galleries !

Now, you can still see your albums and pictures, but you can also :

• upload photos
• create new albums

The ergonomy is not yet perfect, as you may have already noticed, even though almost everything is multi threaded (using AsyncTask), meaning the ui won’t freeze anymore; the next features will probably will allow the user to insert a photo to his gallery from every picture context on the android platform (declaring a « share image » intent)

Stay tuned !

• The main reason I Started this project was because there isn’t yet any gallery2 clients for the android platform and I needed one to access my galleries where I share photos with my family and friends

Gallery2 is an open source project to easily share your photos with your friends and family : you can install it on Php/MySql enabled server : be it a shared server or dedicates server; Gallery2 is maybe the most popular project in this category ! (I know, Picasa and FlickR exist but… I’m not the kind of guy to upload 7 Gb of photos to companies I don’t know and I don’t trust…)

Well, there’s a client for uploading photos to a gallery2, picpush, but it’s not open source and it’s loaded with ads… And you can’t browse photos…

• I wanted to start a new Android project, to know better this platform !
• Iwanted to compete on the ADC (Android Developer Challenge) 2009 : given the current features, I’m not sure I have a chance to win the competition, but, hey, the important is to particpate as we isay !

As of version 1.0, G2Android can browse albums and pictures, for more details, you can check out the Features page of G2Android

Version 1.1, which will be out soon, will allow you to browse private galleries, ie gallery2 installations which need a password.

The project is open source, GPL v.2, so you want to join in, feel free to contact me !

Finally, you can download G2Android from the Android Market : just type « G2Android » in your search or simply click on this link if you’re browsing this page with an Android device .

You can also download it directly from the G2Android Google code site.

Have fun with it, and feel free to submit new issues on the bugtracker if you encounter a bug !

First Method : getting an input stream given a simple url from Android using HttpURLConnection

This method is the most basic one : it allows you, using the basic HttpUrlConnection, ( contained in java.net) to get an InputStream from an Url :

private InputStream downloadUrl(String url) {
		HttpURLConnection con = null;
		URL url;
		InputStream is=null;
		try {
			url = new URL(url);
			con = (HttpURLConnection) url.openConnection();
			con.setReadTimeout(10000 /* milliseconds */);
			con.setConnectTimeout(15000 /* milliseconds */);
			con.setRequestMethod("GET");
			con.setDoInput(true);
			con.addRequestProperty("Referer", "http://blog.dahanne.net");
			// Start the query
			con.connect();
			is = con.getInputStream();
		}catch (IOException e) {
                        //handle the exception !
			e.printStackTrace();
		}
		return is;
 
	}

You can also use the Post method, sending data in the HTTP POST payload :

private InputStream downloadUrl(String url) {
                InputStream myInputStream =null;
		StringBuilder sb = new StringBuilder();
                //adding some data to send along with the request to the server
		sb.append("name=Anthony");
		URL url;
		try {
			url = new URL(url);
			HttpURLConnection conn = (HttpURLConnection) url.openConnection();
			conn.setDoOutput(true);
			conn.setRequestMethod("POST");
			OutputStreamWriter wr = new OutputStreamWriter(conn
					.getOutputStream());
                        // this is were we're adding post data to the request
                        wr.write(sb.toString());
			wr.flush();
			myInputStream = conn.getInputStream();
			wr.close();
		} catch (Exception e) {
                        //handle the exception !
			Log.d(TAG,e.getMessage());
		}
                return myInputStream;
}

But there are better ways to achieve that, using Apache HttpClient, included in android.jar (no need to add another jar, it’s included in android core)

Second Method : getting an input stream given a simple url from Android using HttpClient

Why is it a better to do it ? because the simpler, the better ! See by yourself :

public static InputStream getInputStreamFromUrl(String url) {
		InputStream content = null;
		try {
			HttpGet httpGet = new HttpGet(url);
			HttpClient httpclient = new DefaultHttpClient();
			// Execute HTTP Get Request
			HttpResponse response = httpclient.execute(httpGet);
			content = response.getEntity().getContent();
                } catch (Exception e) {
			//handle the exception !
		}
		return content;
}

But you maybe wondering if it’s still easy with HTTP Post method ? You won’t be deceived !

public static InputStream getInputStreamFromUrl(String url) {
		InputStream content = null;
		try {
          		HttpClient httpclient = new DefaultHttpClient();
			HttpPost httpPost = new HttpPost(url);
			List nameValuePairs = new ArrayList(1);
                        //this is where you add your data to the post method
                        nameValuePairs.add(new BasicNameValuePair(
			"name", "anthony"));
			httpPost.setEntity(new UrlEncodedFormEntity(nameValuePairs));
			// Execute HTTP Post Request
			HttpResponse response = httpclient.execute(httpPost);
			content = response.getEntity().getContent();
		        return content;
	        }
}

But what if you want to read a cookie from the response ? And how can you send a cookie back to the server for the next request ?

Reading / Sending a cookie along with the requests

Using Apache HttpClient, it’s easy to retrieve cookies ! Everything is in the headers after all !

[...]
Cookie sessionCookie =null;
HttpResponse response = httpclient.execute(httpPost);
Header[] allHeaders = response.getAllHeaders();
CookieOrigin origin = new CookieOrigin(host, port,path, false);
for (Header header : allHeaders) {
			List parse = cookieSpecBase.parse(header, origin);
			for (Cookie cookie : parse) {
				// THE cookie
				if (cookie.getName().equals(COOKIE_I_WAS_LOOKING_FOR)
						&& cookie.getValue() != null && cookie.getValue() != "") {
					sessionCookie = cookie;
				}
			}
}

To send a cookie along with your request, keep it simple :

HttpPost httpPost = new HttpPost(url);
CookieSpecBase cookieSpecBase = new BrowserCompatSpec();
List cookies = new ArrayList();
cookies.add(sessionCookie);
List cookieHeader = cookieSpecBase.formatCookies(cookies);
// Setting the cookie
httpPost.setHeader(cookieHeader.get(0));

What about the resulting InputStream ? You definitely want to transform it into a String or an Drawable (to set it to an ImageView for example !) don’t you ?

Converting the InputStream into a Drawable in Android

The Drawable class already handles that for you :

Drawable d = Drawable.createFromStream(myInputStream, "nameOfMyResource");

Converting the InputStream into a String in Android

This is some classic java stuff (don’t tell about how easier it is in Ruby.. I know … but hey ! Java SE7 at the rescue with NIO !!! maybe one day in 2010 ! )

BufferedReader rd = new BufferedReader(new InputStreamReader(myInputStreamToReadIntoAString), 4096);
String line;
StringBuilder sb =  new StringBuilder();
while ((line = rd.readLine()) != null) {
		sb.append(line);
}
rd.close();
String contentOfMyInputStream = sb.toString()
 
That's it folks ! If you have any other methods to achieve these goals, feel free to share them sending a comment !

• -XX:+CMSPermGenSweepingEnabled : this setting enables garbage collection in the permgenspace
• -XX:+CMSClassUnloadingEnabled : allows the garbage collector to remove even classes from the memory
• -XX:PermSize=64M -XX:MaxPermSize=128M : raises the amount of memory allocated to the permgenspace

These options must be included in the JAVA_OPTS part of your Jboss run.bat or run.sh startup file.

Thank you Stephane for giving me the solution !

https://bugs.eclipse.org/bugs/show_bug.cgi?id=281472#c7

et en particulier, le moyen de contournement, à savoir ne pas utiliser Apache HTTPClient pour se connecter au réseau se trouve sur cette page :

http://wiki.eclipse.org/ECF_Filetransfer_Support_for_NTLMv2_Proxies

Il suffit de modifier son eclipse.ini et rajouter les valeurs suivantes :

-Dorg.eclipse.ecf.provider.filetransfer.excludeContributors=org.eclipse.ecf.provider.filetransfer.httpclient
-Dhttp.proxyPort=8080
-Dhttp.proxyHost=myproxy
-Dhttp.proxyUser=mydomain\myusername
-Dhttp.proxyPassword=mypassword
-Dhttp.nonProxyHosts=localhost|127.0.0.1

Vous n’etes pas obligés de rajouter un utilisateur/mot de passe si votre proxy n’en a pas besoin.
Attention ! bien placer ces propriétés juste en dessous de -vmargs !
Ainsi, au prochain redémarrage, vous aurez accès aux update sites eclipse à travers votre proxy (malgré 1 message d’erreur la première fois !)

The Changing Nature of Enterprise Java Application Development, 9:00 – 9:45 by Adrian Colyer

During his talk, the speaker described the audience the future of a Java platform, because it is actually going to be there for a long time now.
He mentioned the dynamic languages compatible with the JVM : Groovy, JRuby, Scala, and Clojure.
He mainly focused on Groovy (which belongs to SpringSource by the way), even if he was not sure if whether JRuby or Groovy would win the « war of dynamic languages ».
For the web platform, he mentioned Grails, built on top of Groovy, Rails running on top of Ruby, and Lift built on top of Scala.
He finished his talk introducing OSGi and Spring DM; the future of enterpise is application may be in the cloud : easily to deploy and scale applications are to come.

The android runtime environment, 10:30 – 11:20, by Joerg Pleumann

The speaker first made an introduction to the Android system, as a platform competing windows mobile and palm.
More technically speaking, it is based on a Linux kernel (along with necessary drivers : display, camera, sound, etc…).
On top of it come the Android Runtime and libraries; the talk is about the Android Runtime and its Dalvik VM.
Dalvik VM : CPU between 250 and 500 MHz, RAM >=64 (equivalent to a 1999 PC), but low power consumption is critical.
The Dalvik VM is really efficient, using explicit registers to keep temporary values: the immediate benefit is the number of lines of the bytecode resulting from the DalvikVM compilation : nearly 30% less than a standard VM compilation.
A dex file (Dalvik Executable) contains several files, and is not compressed.
JNI is ready, a sdk for using JNI is about to come out in the next days; also an Android Debug Bridge is available from the beginning.
The core libraries
dalvik vm specific libraries : dalvik.*
java compatibility libraries : java.* and javax.*
and some apache libraries(mainly for http) : org.apache.*
The core libraries are partly taken from Apache Harmony (a JDK implementation by Apache), partly written from scratch; and some of them have been optimized (using JNI)
The core libraries are mostly compatible to a subset of J2SE 5.0.
JDBC 2.0 is supported, but the SQLite driver is limited., but one can use the alternative in android.database.sqlite which are better integrated.
To conclude with, with Android you can reuse your java knowledge and tools.

Android Application Model, 11:30 – 12:20, by Dominik Gruntz

4 main components :activities, services, content providers and broadcast receivers.
A single class, uses intents to communicate with the other activities; when you launch an activity, you can (or not) expect a result; if this is the case, the method onIntentResult will be called.
You can also define intent filters to describe the intents an activity can handle.
An intent specification is on its way : http://www.openintents.org
An application is packaged using an APK (Android package).
Every activity has a lifecycle containing 4 steps : new, running, paused, stopped, killed and the corresponding methods (onCreate, onStop etc..)
For each activity a new process (with a single thread) is created.
The Looper.loop() dispathes the actions to a queue.
If an activity does not conume events in 5sec, the system issue a warning message.
A service is running background and can communicate with an activity (in process if it’s the same application (APK)) or via AIDL.
Finally, a content provider is the only way to share date between Android applications; it can using SQLite, a file, or a remote storage.

Scalable Agile Web Development: REST meets JCR meets OSGI, by Michael Marth

JCR : JSR 270 for accessing content repository : located on a file or database; can be versioned; node ahave read/write group properties, etc…
Apache Sling is a web framework, on top of REST/Scripting (Ruby, Groovy, etc…)/OSGi(in this case Apache Felix Container, to switch on/off part of the frameework live)/JCR.
So basically Apache Sling allows the user to create/edit/read/update content in a restful manner (http methods), the data being created is then stored on the JCR repository, organized in a very similar WebUrlFriendly way (and then you can manipulate the data through rest or webdav and so on, thanks to JCR)
The demo was really smooth and interesting !

The charm of Mockito: Test Spies in action, 14:30 – 15:20, by Szczepan Faber

The speaker begins asking who uses JMock : 2 or 3 people among an audience of 60 people, half of the audience using EasyMock.
So let’s start with EasyMock : coding in TDD a dictionnary, (and its history) depending on a translator : the translator is mocked.
With easymock the speaker keeps it old fadhioned : createMock/expect/replay/assert/verify , (his test extends Assert) and then refactor a bit in the @Before and @After test methods, nothing special here.
Then Mockito : mock/when/assert/verify : it’s a lighter syntax indeeed!
Szczepan insisted on the fact that usually developers using easymock create replayAll and verifyAll methods called in the @After method; which make Easymok fail when many behaviours are attached.
The speaker uses BDD style template (given/when/then) in eclipse, when creating a test.
Mockito eases the use of a given/when/then syntax when writing a test.
Has good point of failure ?
The failure trace in mockito is linked to the source code and more explicit about the error, it does not whow internal classes exceptions
Mockito or mockito-like for python, flex, javascript, C++; there are mockito extensions
He concluded with : « Do TDD and write great tests with whatever tools that work for you »
May the force be with you !

Eclipse Galileo and JBoss Tools, 16:30 – 16:50, by Max Andersen

Galileo (3.5) is a huge release.
Must-sees : Eclipse Memory Analyser (to see which plugin consumes all the memory for example), using jmap
XML and XSL editor is really better.
P2 (eclipse update manager) works for real; you shouldn’t use dropins anymore (single zip files to unpackage in /plugins and /features), for offline installation plugins providers should suggest copies of the update site, then you may use P2 to explore these files, as if you were online).

James Gosling keynote : 9:50 to 10:45

First a nice little video from Java One, introducing the history of Java ! Very funny how Java conquered the world !
Then James Gosling begins his speech.
Today there are more JREs installed than people on earth ! It can be be smart cards, desktops, phones… 6M Java developers today in the world … 15M JRE downloads / week.
You can now view Java as « Learn One, Work everywhere » because it’s really spread everywhere now !
James Gosling then describes the brazilian healthcare, where every piece of paper is now on the network : prescriptions, x rays, everything is now on the network (thanks to Java !), ebay, metropolitan networks cards, web apps, games… Java is everywhere !
But the main thing is not java as the language, but the JVM that now hosts Ruby, Scala, JavaScript, etc…
James then showed us a bit of java code : a servlet for Java EE6 running on GlashFish v3, changed, saved and instantly shown just refreshing the browser ! No more deployment bottleneck !
He also introduced Netbeans, as the best IDE ! version 6.7 now integrates with project kenai, a sourceforge like (you can check in/out merge your files, etc… from Netbeans to kenai), also some better maven support.
Java is also used in the real time world, even in a car that James turns into electric : a lincoln (lincvolt.org) which is hybrid, connected to the internet, running java code for measurement and control.
Now down to the performance part : Java is highly optimized, genrally beats C/C++, GC is a lot faster than malloc/free !
Multithreading is the future of software designing : because the processors speed is not evolving anymore, we’ve got to think multicore !
Java is also running on cellphones, JSR 248, Mobile Service Architecture aggregates all Java mobile specs.
JDK7 will be modular (see Mark Reinhold’s blog), dynamic language support will be available too (JSR 292?); waiting for Java 7, there are still Java SE 6 updates : better browser and desktop integration are on their way !
Of course, we got a few slides about JavaFX, which can run on desktops, mobile phones, set top boxes, etc…
To finish his speech, James reminded us with all the java communities : netbeans.org, java.net, glassfish.org, etc…

Java EE 6 11:00 – 11:50 by Roberto Chinnici from Sun

Java EE6 was too complicated, so they decided to make it more easy to use, more powerful, and more flexible.
That’s why they created the profiles, letting the users choose the features they need.
For example the web profile includes everything for the web development, including the EJB 3.1 lite, and bean validation.

Servlet 3.0

New annotations @WebServlet, @WebFilter, @WebListener, the possibility to register new web components just adding them to WEB-INF/lib directory, a new async mode using just a single thread for many requests

JAX-RS 1.1 : RestFul webservices

This API is there to abstract low level HTTP details : using @GET and @POST (etc..) you can define your retrieval and creation REST operations, JAX-RS translates the XML to the java entities (and back) automatically for you (you can also use JSON)

Bean Validation 1.0 (JSR-303)

This API is here to validate fields (text inputs for example)
Seems to be really verbose just to define constraints… We’ll see…

EJB 3.1

No intefaces anymore ! One source file per bean.
New timer annotation @Schedule allowing some cron-like scheduling in the container : a great example provided is the case of a cache refreshing ! No more Mbeans called externally with crons, everything can be integrated in the application code !
EJB 3.1 lite can run on Java SE, great for testing and also in a war file !
Oups, we’re running out of time, the speaker skipped JPA 2.0

« Design Patterns » in Dynamic Languages 12:00 – 12:50 by Neal Ford from ThoughtWorks (nealford.com)

After comparing mixing dynamic languages with whisky blending, Neal Ford reminded us about the history of Design Patterns : basically for « making C++ code suck less » !
But the point is : the design pattern designed in 1994 are not always useful today : for example the iterator is quite complicated, whereas today in dynamic languages, like Ruby a collection.each{[x| puts x} is so much more… efficient !
Command design pattern is already built in closures !
The same for strategy, template, interpreter (the example showed how easy it is to implement a DSL in Groovy, defining new behaviors in the Integer class), decorator, recorder, adapter
Then Neal described some other desgn pattern for dynamic languages : the null pattern (?. in groovy) and the aridifier pattern.
To conclude with, Neal suggest that we should try the tools provided with the languages we’re using instead of blindly trying to copy the patterns designed for older, other languages !

Gradle : A build system for Java 14:00 – 14:50, by Hans Dockter

First the speaker reminds us of Ant and Maven.
With Ant, it’s always been repetitive, with a lot of copy and paste when a new project starts, due to Ant limited domain model (resources, target, properties,)
There is no place for listener in an Ant build…
A gradle script can import old ant build scripts.
With Gradle, you can call ant tasks, and even implement listeners on your ant task… An ant task called in a gradle scrip can even be aware of the next task that will be called !
Maven, on its side is a build by convention framework, which has introduced dependency management.
But Maven uses XML, and 25 lines of XML are required to launch a simple build !
Maven uses transitive dependency whereas Gradle is able to skip tasks (which can be handy when a Maven dependency is broken…)
Gradle aims to be a build language rather than a build framework; because when a framework does not implement a functionality, you spend your time fighting against the framework to make him do something it was not intended to do.
You can define your maven build with a groovy script using gradle.
With gradle, it becomes easy to define usually manual and entreprise specific tasks like release management or deployment.
Grandle can use Apache Ivy or Maven dependencies, it can even deploy a build to a maven repository.
There is also a Gradle Wrapper to start using Gradle without installing it : the Continuous integration machine will download Gradle for you and execute the gradle script (which is a shell script downloading gradle) !
What’s next? Gradle 1.0 will be out in Autumn.
Q&A :
What open source projects are already using Gradle ?
Grails, but others are to come.

Next Generation Enterprise Builds: Maven, Mercury, and Tycho (for OSGi builds) by Jason van Zyl from Sonatype

Maven 3.0

Better integration in IDEs, faster, rewritten artifact resolution system, etc…
Maven 3.0 is more focused on integration tests, provides a new version of the plugin manager, a queryable lifecycle to make the tools able to predict what’s going to be done and also able to ask to execute a particular step.
Maven 3.0 uses Mercury : a new repository and transport layer, that can be used with others systems (Ruby gems, Eclipse P2 dependency management)

M2eclipse

M2eclipse has also been improved, now m2eclipse won’t call every maven tasks on a a save action, it will only call the appropriate ones.
The m2eclipse team would like the users to be able to resolve every maven operations from Eclipse,
M2eclipse is now compatible with Flex (out by october 2009).

Nexus

Only 5% of the maven users use a repository manager.
Nexus is also for binary sharing inside the enterprise, it a repository manager, it’s like a source control management, but for binaries !
Nexus main advantage is also the caching system it provides.
Nexus can be queryed through m2eclipse, Nexus API can be used through REST, which makes it very easy to use.

Hudson

For its next version, hudson will integrate :d rools workflow integration (with a workflow editor), a rest layer to query hudson, unifying hudson m2eclipse, nexus better maven integration

Testing Zen 16:00 – 16:20 by Thomas Mueller, Day

In this session Thomas gave us the reasons why we should test our code.
Then he continued giving us an example of fuzz testing (data generation to test)
Code coverage (with Emma) to find untested and dead code.
Database testing is often hard : a pain to install… so you can use a Java SQL Database like HSQL (a good one), H2 (the best, and also the one the speaker is working on ! ) or Derby (the worse).

Creating Performance Test Data with benerator, by Volker Bergmann

Usually performance testers prefer testing with production data, but sometimes it is not possible (for privacy reasons or if the system is new).
In those cases, you have to use a data generator, like Benerator that can create and anonymize data, to DB, file, LDAP, JCR, etc…

To finish the day, we had a really nice speech from Neal Ford, about technology predictability, that was real fun !

• Lundi (si j’y suis): Glassfish
• Mardi : Java EE6, groovy, Spring 3.0, GWT, iphone, maven , mobile java
• Mercredi : hudson, securing ajax,jsf 2,mule, android
• Jeudi : android, rest, mockito, openjdk

çà va être épuisant je sens !
Trop hâte d’y être !

Ecriture de ma première application Android

Ce qu’il faut sur le poste de développement :

De retour de vacances, je me dirige sur http://developer.android.com/sdk/1.1_r1/installing.html où je découvre que dans eclipse je peux installer le plugin de développement ADT, qui, une fois connectée au SDK installée sur ma machine (sous windows pour commencer ) me permet d’intéragir plus facilement avec ce SDK.
En résumé il vous faut :

• Eclipse 3.4 avec une JRE 6
• Le plugin ADT téléchargé via le « Software updates » d’Eclipse
• Le SDK Android

Ecriture du Hello Android : première application Android

Google fournit un tutorial très bien fait qui permet de se familiariser avec le concept d’activité et de création de vues via des fichiers XML (çà me rappelle une mission çà …), à l’adresse : http://developer.android.com/guide/tutorials/hello-world.html
Oups ! quand on (contrôle) clique sur du code Android (comme Activity.class par exemple), on se rend compte que les source sne sont pas fournies ! Plutôt dur à digérer quand on a l’habitude d’avoir les sources des frameworks que l’on utilise et que l’on sait qu’Android est un produit Open Source ! Heureusement, le « bug » est signalé et en supprimant la librairie Android (android.jar) dans le projet Eclipse et en la ré important en précisant le chemin du code source (téléchargeable ici), on a accès au code source du framework !
On lance un « Run » et on a le plaisir de voir l’application se lancer dans l’émulateur d’Android !

Déploiement de l’application Android sur le HTC Dream

Il faut tout d’abord télécharger et installer les drivers USB sur votre poste de développement.
Pour installer les pilotes, dézippez les dans le répertoire de votre choix, et connectez en USB votre téléphone (en ayant pris soin au préalable de le mettre en mode Debug USB dans Parametres -> Applications -> Développement); Windows va détecter votre téléphone et vous demandez d’installer les pilotes.
On y est presque !
Il n’y a plus qu’à déployer l’application, pour cela, retournez dans Eclipse, dans votre « Run Configuration… » qui lance votre application Android dans l’émulateur, sélectionner dans « Target » Selection « Manual », cliquez sur « Run » un dialogue apparaît, sélectionnez votre téléphone, et regardez votre application se lancer sur votre téléphone portable toujours connecté en USB bien sûr !
Maintenant, laissez place à votre imagination et codez !

Oups ! problème technique, on passe à la présentation du framework Web Wicket par Tarik Filiali Ansary.
Wicket utilise uniquement du code Java pour définir ses pages, on fait la liaison entre le modèle et la vue dans une classe Java par exemple !
On peut non seulement créer ses propres composants, par simple héritage (çà me fait penser à GWT çà d’ailleurs), mais on peut aussi rajouter des comportements à des composants.

A la fin de cette présentation technique, les jug leaders ont cette fois ci pu présenter leur activité et objectifs, dans une ambiance très décontractée ! : BreizhJug (60 participants en moyenne), RivieraJug (80 participants en moyenne, 1 mois d’existence), BordeauxJug (30 particiapans en moyenne), ToursJug (35 participants en moyenne), LorraineJug (tres récent, depuis le 29 Janvier 2009), YaJug (du Luxembourg, depuis 2006, 30 à 50 personne présentes par événement) JugToulouse (1ère soirée en Mars), Lyon Jug (1ère soirée en Avril), Nantes Jug (30 personnes en moyenne par soirée).

Un organisateur de Jazoon est venu présenter la conférence 2009 (22-25 Juin) , à Zurich compter 1100 € pour les 3 jours. (plutôt 700 euros si on s’y prend en avance et qu’on évoque ParisJug)
Juste avant le buffet, a eu lieu une séance de quizz (j’ai d’ailleurs gagné un bouquin sur Flex et Yannick un bouquin sur Java 6 SE !) et ensuite a été lancé la roue de la fortune JavaFX (!) pour gagner des licences IntelliJ Idea.

Après un buffet où les plus de 200 participants ont pu se retrouver, nous avons eu une présentation de parleys.com par le créateur de Devoxx; parleys.com (en Flex) qui contient des centaines de présentations techniques (avec vidéo et diapositives des présentations) de conférences comme Spring One, Devoxx, JavaOne, etc… Nous avons ensuite eu droit à la démonstration de parleys.com en Java FX (où l’on peut glisser l’applet sur le bureau, plutôt impressionnant), et enfin en GWT.

Avant de partir (il se faisait tard!) j’ai pu assister à la présentation de Java SE 7 : j’ai en l’occurrence retenu que

• les .getProp()!=null pourront etre etre remplacés par ?.getProp()
• nouveau garbage collector par segmentation
• simplifaction sur l’ecriture des génériques : HashMap,List> toto = new HashMap<>()
• nouvelles annotations pour poser des contraintes sur des champs (email par exemple)

etc… la présentation allait vite il faut dire difficile de tout voir !.

Dommage pour la présentation de JOGL à laquelle je n’ai pu assister (il se faisait tard… 22h45) !
L’ambiance était vraiment bonne, le nombre de participants impressionnant (plus de 200 entre 20h et 23h !), et comme d’habitude, la qualité des interventions était de très bonne facture ! Joyeux anniversaire ParisJug !

Un buffet vous sera également proposé pour la pause déjeuner, par les sponsors de l’événement : Valtech et Sun.
ParisJug est également partenaire de l’événement!
N’hésitez à diffuser l’info autour de vous, et n’oubliez pas de vous inscrire à JavaCampParis3 !
A Samedi !

Si vous n’êtes pas très saumon fumé ni champagne, mais plutôt Eclipse et Widget, je vous propose de réveillonner avec notre présentation mise à jour, ainsi que les workspaces d’execices et de correction !

Ces workspaces sont utilisables sous windows (avec un JDK 5 minimum).

Pour n’avoir aucun problème, vous devrez installer gwt et gwtext C:\dev, selon l’arborescence suivante (des chemins en dur sont présents dans les .launch entre autres) :

C:\dev\gwt\gwt-windows-1.5.3

C:\dev\gwt\gwtext-2.0.5

Pour Linux et MacOsX, le mieux est de récupérer les projets et de corriger les chemins de lancement (.launch).

Le succès était encore une fois au rendez vous, je remercie encore l’organisation côté Valtech Technology Consulting et côté Valtech Training !

Joyeux Noël à tous !

• Présentation AfterWork GWT
• Workspace AfterWork GWT

Ensuite, après une pause restauration, Jérôme Louvel nous a présenté un portage de restlet sur GWT.
Présentation de REST : utilisation du protocole HTTP (et autres) : GET,PUT,DELETE et POST.
Restlet présente une API qui permet de lancer des requêtes vers du SMTP (envoi de mails), POP3 (lire un mail), HTTP( charger une page web), d’une manière bien plus simple qu’avec l’api du JDK.
Il est aussi possible de créer des serveurs avec la même API. (exemple du reverse proxy trivial à écrire)
Restlet-GWT supporte JSON et XML, et dispose de toutes les propriétés client de Restlet.
A contrario, GWT-RPC n’est pas ouvert : un client GWT-RPC communique avec une appli serveur développée pour GWT; Restlet-GWT n’a pas de contraintes de ce côté là.
La démonstration consistait justement à la réécriture de l’exemple GWT Mail avec l’API GWT Restlet

C’était ma première soirée ParisJug, et les sujets et orateurs étaient très intéressants; d’ailleurs quand on voit l’affluence (plus de 150 personnes) il y a fort à croire que c’est souvent le cas !