- Blog Xebia France - -

Posted By Xebia France One on Monday, August 3rd, 2009 17:17 In Review of the papers No Comments

Review of the papers Xebia
The review of the papers of actuality Popular dance / weekly J2EE offered by Xebia.

Actuality editors / SSII

RIA

The corner of technology

Ev nements of our community in France and abroad

Actuality editors / SSII

Progress of specifications and realisation JEE 6

The podcast last of Cast Converters was a chance to go around table of the information which each of the presenters had on JEE 6. Even if it is not about official information, they give an outline interesting on the fact that could BEING JEE 6 during his revision as well as on his calendar:

  • Antonio Goncalves, member of the expert Group JEE 6, explains that the battle between JSR-330 (Dependency Injection for Popular dance) and JSR-299 Popular dance Contexts and Dependency Injection) on the ground of the injection of dependency seems left for ending in a constructive way. Indeed JSR-330 not introducing particular incompatibility with the very evolved model offered by JSR-299, both specifications should complement each other harmoniously. JSR-330 would define group of basic interfaces that JSR-299 would come to spread to add the concepts more worked out. To allow this last minute adjustment, the revision of specification JEE 6 would be slightly pushed back, carrying her so around October / November, 2009.
  • Emmanuel Bernard, working on problems of persistence to JBOSS, learns us as for him that the realisation of the draughts of specifications JEE 6 is under way at the place of JBOSS and should succeed in version 5.2 of the server of application of the editor with a first realisation not correspondent to TCK, compliance would come in second time, during a subsequent version. He recalls the possibility of a presentation of this job during of the beginning of September. On the other hand, JSR-303 (BEAN VALIDATION) for whom he is responsible is close to revision but conflict with JCP on problems of complexifie licence progress.

It is possible only to be delighted with this possible harmony between both JSR of injections of dependency since the developers would be so free to choose the specification on which they are based, according to to them more or less complex needs.

RIA

News of Ext-GWT

Ext-GWT, the Javascript ExtJS bookshop carried in GWT (cf. article on the galaxy GWT), goes out in version 2.0.1.
Let us use this exit to speak more on the whole about plan and about major taken out release 2.0 a month is now there.

This one indeed brings the lot of new components and new functionality. These additions reduce distance so between 2 plans. They find so:

  • Tree Panel and Tree Grid (d mo), this last (who spreads the component directly Grid therefore more to binder) benefiting from all functionality of the picture
  • row editor (d mo) who allows to change a complete line of the picture, all cells of the line in favour edition (while before it was necessary to edit all cells one after another)
  • HTML editor / Rich Text Editor (d mo)
  • Live Charting (d mo) who joins GCHART so (recalled during a previous review of the papers) and OFCGWT
  • ButtonGroup (d mo) and Status (d mo)

An important job was brought on buttons, bar of tool, management of the overflow in this bar...

Novelties very numerous, a detour by the famous will allow to go through / test them.

As for a major update, a present guide of migration in the product will describe changes in the IPA - INTERNATIONAL PHONETIC ALPHABET.

Downloading here and yes (as I:) ) you already wait for continuation with 2.1, you will find roadmap news thereabouts.

The corner of technology

New concept in JUNIT 4.7: Rule

The version 4.7 of the framework famous of unit test, JUNIT, is under way of preparation. A new concept was revealed: Rule.

This concept is going to delight the tears of the test automated by JUNIT. Indeed, this functionality will allow to change the execution of your tests, to prepare them for a context of execution.

One of the most significant examples is the following:

public static class HasTempFolder {
  @Rule
  public TemporaryFolder folder = new TemporaryFolder ();

  @Test
  public void testUsingTempFolder () throws IOEXCEPTION {
   Go off createdFile = folder.newFile (" Myfile ");
   Queue createdFolder = folder.newFolder (" Subfolder ");
   //...
  }
 }

Thanks to this statement @Rule public TemporaryFolder folder= new TemporaryFolder();, before the test it does not need there to create temporary directory, after the test it does not need there to abolish directories and files created during the test. It allows more easily therefore to make tests automatisables, r p tables, and portables of environment with environment.

There is other Rules as for example:

  • ExternalResource: usable of an external file (accessible by system of file)
  • Timeout: the test must answer before a timeout
  • ExpectedException: the test must throw exceptions determined well
  • And many others

There will be therefore group of Rules who will allow to avoid doing again small ends of personal code to make the same thing in an annotation.

Attention to your memory with String.substring ()

Here is an interesting article which allows to include what is under the bonnet of the class of JDK G-STRING: G-string and memory leaks; he could even give you a small drop of sweat on the forehead. Even if the title of the article is not well chosen forcing ('escape memo' while it is more about retention memo), it shows us simply how a method of the class, substring, a wolf can hide.

Indeed, for aims of optimisation, they make turn following code:

public static void sendEmail (emailUrl G-string) {
  Email G-string = emailUrl.substring (7);//'mailto: 'prefix has 7 letters
  G-string userName = email.substring (0, email.indexOf (" - "));
  G-string domainName = email.substring (email.indexOf (" - "));
}

public static void hand (G-string [] args) {
  sendEmail ("mailto:user_name@domain_name.com ");
}

At first glance, they have three authorities of her classes G-string:

  • String email = "mailto:"
  • String userName = "user_name@"
  • String domainName = "domain_name"

However, in concrete terms, in memory there is only one picture of char who is stocked: "mailto:user_name@domain_name.com", the authorities of classes String intervals used by the picture of record only char.

Trap is to manipulate a chaine engrossment of characters (who comes from a batch file for example) and to use substring to limit size of the chaine and therefore use memory. Forgery! The initial chaine will always be stocked in memory.

Rather confusing!

Exit of Wicket 1.4

Wicket plan continues evolving and, while we speak to you about a version 1.3.6 last May (which besides made the object of one ), it is the version 1.4 after one working year which arrives at us in hands (by Yes Wicket! and Apache Wicket).

In the menu of novelties: a new packaging of the ganders Wicket (who makes them compatible OSGI), the only one jar for modules Spring and several modifications of IMODEL, of its realisation and more on the whole IPA - INTERNATIONAL PHONETIC ALPHABETS to take advantage from Popular dance 5 (Generics). The use of Generics in the code of Wicket began there is vicinity one year by an opinion poll enthralled on direct mail advertising-list, to arrive only in the milestone 3 Wicket 1.4 with so many supporters as detractors - defenders of the support of JDK1.4-and this up to the release final. The thread on The Server Side is also impressive! For the complete detail, appointment on Jira of plan.

Just as for Ext-GWT 2.0 (above), one guide of migration of 1.3 towards 1.4 is available. A baby ?

Mother your unit tests.

InfoQ publishes an interesting anthology: "Accomplish better tests unit".
Some will find that, once again, opened doors are planted. Others (as we), will appreciate many reactions which follow from this type of article, and will think that it is never useless to remind of these basic main principles to give up seeing unit tortured tests (and useless) on some plans.
In short, in a word as in one thousand, your unit tests are classes of code popular dance, which are vital for your plan, it is therefore urgent to look after it (naming, material, refactoring...)

Ev nements of our community in France and abroad

Sun loses JRUBY

Three key developers of JRuby, to know Charles Nutter, Thomas Enebo and Nick Sieger, chose to leave Sun MicroSystems. Further to the recent redemption by Oracle and the uncertainty concerning the support of by the new owner, they decided to join the Engine Yard society, specialised in the accommodation of applications Ruby One Rails. Engine Yard has passionate air at the idea of being able to be the support of the development of offer JRUBY and of the community which goes with. (Source)

Article printed from Blog Xebia France:

URL to article: / 2009 / 08 / 03 / revue-de-presse-xebia-120 /

Click here to print.