emiliobruceqo

First day of the conference today, the keynote commenced at around9.45. The whole room was packed and a bozo named roxorloops maked some beat boxing
to entertain the attendees. Quirte impressive I 'd tell.

Next Stephan Janssen
welcomed everyone and denoted a couple of facts and updates about Devoxx. This is the first edition of Devoxx ( after it holds been renamed Devoxx from JavaPolis ) which is sold out with3.200 attendees ( from 35 lands concluded the creation ), 160 verbaliser, more suites ( 6 suites this times, as opposed to five in last twelvemonth ). There are 40 spouses at the exhibition flooring, 40 assort Java User Groups and likewise 400 educatees holded the chance to come inwards free of charge in the first two years of the university.

Stephan stated a BIG thank you to Devoxx program commission and the to Devoxx disposal squad. As a side note he inquired us to be soft with the locus and take attention of it. Make not litter it, make not ill-use it, and hold the spot clean and quiet. Besides be soft with the wireless web and make not download large files ( to day somehow the web is in no time, compared with the old eld and the fist two years. Goodly maked ). Stephan likewise denoted that this afternoon they will be functioning free beer ( hope not equally strong as the one I holded in the jug leaders and talkers dinner last nighttime, 10 % intoxicant! ) and free chips.

He too stated that people kick that the Belgian JUG
apart from Devoxx is not organising anything else. Stephan explicated that he maked n't hold decent clip since the readyings for Devoxx begin 8 to 9 months before Dec. But he holds discontinued his current line and holds more clip to devote now. As a ersult of this BeJUG will organize fortnightly eventide session for 150 maximum throughout Belgium. This is 18 meetings in totality ( no meeting during Dec and Summertime vacations ). Fro more info visit the BeJUG site.

After Stephan stepped downwardly Danny Coward
from Sun Microsystems tread on and spoke about JavaFX
He too denoted that Sun is consecrated to ever be sending last production package justly.

Next he spoke about the 10 things we involve to cognise about JavaFX

1 ) JavaFX is here, it was relinquished on the 4th of Dec. Sun relinquished a prevue in July this wear, a prevue of the SDK. JavaFX SDK ( which includes the runtime for the desktop and the copycat which lets to deploy on desktop, on browser or cell ). NetBeans6.5 holds support for JavaFX. He likewise cited the JavaFX production suite which is a aggregation of tools that allows the JavaFX developer to work with artworks to make RIA. JavaFX besides transports with 75+ sample applications

2 ) JavaFX delimitates a cool new language. Why make we involve a new language? Languages are germinating rapidly. People in Sun larn from their experience and they layed the best best features of the language they hold worked so far. JavaFX playscript was design constructed for merely RIA in nous, nil else. It Holds declaratory, holds a Java like syntax, supports data binding and event triggers.

3 ) JavaFX supports beautiful artworks. They take vantage of the Java bed for artworks. JavaFX furnishes support for artworks acceleration, javaFX scene graph, alivenesses and light. At this point Richard Bair showed a demonstration of a picture mystifier. The picture was playing and it got a jigsaw and they shoulded set the pieces together. After this little picture they explicated the relevant root codification.

4 ) JavaFX holds a rich Apis set. They hold maked a simple to utilize JavaFX book. The API likewise supports scene graph, media, web services ( RESTFUL ) and... any Java API.

5 ) Greater developer tools. The NetBeans plugin for JavaFX includes first category tasks, JavaFX book redaction, codification completion, compile and save, debugging, arts peeview, incorporated corroboration, deploy to desktop/browser/mobile.

6 ) JavaFX incorporates into arts designing tools. JavaFX production suite includes tools for developer/designer workflow, exportation designing from adobe tools, importation and integrate into JavaFX. So they demonstrated a demonstration of the JavaFX production suite.

7 ) JavaFX runs on multiple devices. So one more demonstration followed by a JavaFX application running on a cellphone.

It is rest on Java. Great vantage since you can depend on 13 eld of JVM execution. You can depend on this hardiness and scalability of the inherent engineering.

9 ) Encode once, play anyplace media. Developers hold been inviting eld for better media support. They support the native media models ( mack aboriginal and windows native ). The added a new cross platoform formatting ( FXM ) which intends if they apply this formatting the media will play in any JavaFX-enabled device. Another demonstration by Joshua Marinacci followed, the Fox Box which was essentially amovie site with several movies playing at the same clip and Joshua could play with video belongings and the picture could be dragged outside the browser to watch it as standalone application.

10 ) JavaFX deploys itself. Anyplace there is a JRE the JavaFX runtime will deploy. JRE is installled on 9/10 new PC. More 30-50 million downloads per month. Full-of-the-moon FX roving release will be in Mar.

At this point there was another interruption with the beatboxing bozo again making some astonishing sounds.

Following was Bart Donn, Christophe Delaware marlie, Redbreast Mulkers from IBM
They spoke about RFID
@ Devoxx 2008 ( this is I consider the same engineering utilized in JavaOne last yr ).

RFID is a new labor installled at Devoxx. But why make we take a undertaking during Devoxx? Alternatively of giving delicacies during Devoxx they determined to pass this money to begin a undertaking and benefit everyone. The spouses of this task are: IBM, Intermec
and SkillTeam

So they demoed the followingvideo that gives an entry to the RFID conception. Nice advertising.

The balance of the talking was passed by speaking about the RFID engineering you said it IBM holds developed it.

From Concurrent to Parallel

( by Brian Goetz

This was really the same talking Brian Goetz gave at JavaOne in May I wo n't locomote into points since I hold write of that in this post

Effective pairing: the good the bad and the ugly

( by Dave Nicolette

This was an synergistic session again when people begined coupling ahead of the audience and played different pair-programming scenarios. This session spoke about brace programing, its jobs you said it we can defeat them.

We got with a pair-programming scenario where one impersonated a senior developer and the other a junior developer. The job showed was that the senior developer maked n't desire to permit the junior bash anything. The senior e'er holded the whip hand and maked n't allow the junior bash anything and was e'er picking on the junior bozo.

Squads are most affectional when everyone can acquire about the engineerings and the job. If the senior hombre but maintains the keyboard and makes his ain material it Holds not a good thing. Junior developers larn by typewriting and rehearsing. The junior should make the typewriting and the senior the drive. But the senior conceives that sometimes the labor travels a trifle snowfall and desires to take over things. But the deceleration of the task is a normal thing if you desire the junior developers to larn. You unloosen a little in task clip but you derive afterward in the task. The tip is to hold the less experient individual on the keyboard

Another scenario is the soloist. People who desire to make this themselves because they believe they cognise the job advertising therefore the solution and can work better on their ain. Everyone in the squad holds trouble acquiring the job they 're handling with. The solution is everyone to cognize the job and cognize how the system works you said it to cover with it. This is the double-decker and squad job, if the lead developer is hit by a jitney, how many people can take over the undertaking? Everyone in the squad should seek to hold equal noesis of the job and the system in exercise.

Another scenario, one makes n't follow the other while they 're discourse thoughts. This can be because one holds far more noesis than the other or because one e'er alters his psyche about thoughts and package forms. Jobs grow because one might experience stupid. Another job is that when soul modifies e'er his psyche, they might step offly from the job the client asks licked. People take to acquire how to work with different types of personalities. In brace programming one should do the other stay in touching with the original job. And both of them can scratch each other 's jobs and/or expose their abilities. Besides we should involve to give accent on the simplest designing ( this is nimble development ). Sometimes when we hold many thoughts and we modify our brain day in and day out we do the solution more complex than necessary.

4th scenario, one of the someones in the brace holds extra obligations and can do coupling hard because he can be disrupt day in and day out. The squad should be commited to the task, it should not be disrupt because one of the members of the squad is designated to other things. This usually when the examiners are besides the concern analysts. There is another descriptor of gap overly: when mortal outside the squad comes in and gets taking about nonsensicality that is not colligated to the labor. This disrupts the brace when they essay to work.

Union is verily a sort of a study art. It Holds not but sitting there speaking with your friends. It rattlingly is work.

5th scenario. Physical working conditions in the squad room. Mating is usually neutralise an nimble way. The squad is located in the same room, coupling wheer the squad is located in different locations is not a good thought. Or the mode the office is setted out. For example desks and chairs for union might be placed out correctly but they there might but be one proctor. By making this the pairt is freing clip because the 2nd somebody can not follow the codification. A solution is to enquire the director to purchase more proctors ( proctors are less expensive than people ). As a logical decision the working environment should be positioned upwardly equally to be easy for people to brace.

Scenario six. How to keep the system and bushel the bugs if the original application was not developed in an quick mode. If the application was developed by applying nimble methods there are belike trial suites. The brace can check out the application and their tryout ( the opening to restore the bug ). So they need to reproduce the bug. If the barroom is greenish so it intends that soul forgot to compose the trials, or that individual setted codification into production without proving it. They can employ the same techniques that the development squad employed. But if the bug names to some sort of bequest application where there are no test suit the attack is different. Therein situation you need to direct soul in who cognise the system and can restore the bug. This is not really a coupling scenario but good to name in the coupling context.

Scenario seven, the Fearful Freddie, person who Holds afraid to alter the codification or ca n't be troubled ( overmuchly of a fuss ). This is a bequest scenario from old bequest systems where they holded no test suit and if you altered something you most certainly holded interrupted it too. Now things hold altered. Even if you interrupt something you can ever turn it by employing the version control system. You make n't should be afraid to alter things. It Holds better to alter little things at once instead than make a large modification. Like banks and measure payments, you make n't pay the measures at once but with little installments. Make n't permit the complexness of the codification construct upward over clip, because you hold jobs holding the codification and bushel it. You do the application 's life less. Because of the complexness of the codification you really take to implement a new one. And all this because people make n't desire to modify the codification and they are afraid to touch it.

8th scenario, the withdrawn. One someone that makes the work and the other mortal is withdrawn. The occupied soul seeks to get the other somebody interested in the codification they are working on. In that situation you should withdraw the option from the other bozo, only posed the keyboard ahead of him and enquire him to make the business. What if the mates determine to make a major refactoring that will take 20 transactions and simply one can utilize the keyboard? You make n't should both apply the keyboard, you simply need to position your psyche into work. Justly one can typewrite at the same clip, but both of them can believe. What if they desire to make refactoring but they both hold different thoughts of how to refactor? A good thought is to enquire the other squad members about their thoughts. You might interrupt them a trifle but the benefits you derive are more.

9th scenario, the obstinate brace, when they both desire to follow their thoughts and they wo n't alter their nous. Another facet of nimble development is self-organisation. Every clip there is a bit conflict from the squad you can not run upward to the director to work it because passably presently the director is attending take charge. That might not be desirable, it might not be what you desire. You take it to the director and one mortal wins and the other liberates ( or both loose ). The best thing to make when you hold a job like that is to take a interruption and unclutter your psyche. A 2nd solution is to alter mate. Make n't allow things get personal.

The Siamese twins scenario. Constituent of brace scheduling is that you alter braces ( the original writers of brace scheduling named it promiscuous brace ). Different braces work differently, when one brace is completed the other brace is still working. So they should take vantage of the trim clip. There is a Pomodoro technique; a brace works together for a specific time period and so they halt. So take a interruption and get another period with different mates.

The Thai twins scenario kicking in when two people are really prosecuted in the shop they 're working on and they make n't desire to divide. They work together goodly and they make n't desire to exchange. People should be able to exchange, if they ca n't they are likelily deposited and they demand a new brace of eyes to look in the job they are looking into, a fresh brace. Sometimes people cognise they hold job, they cognize that the undertaking falls behind but they make n't desire to give upwardly. The director should not inquire `` how much longer will it take to lick the job '', but depute new people to look into the job.

The Ping niff scenario. One someone composes the unit tryout and the other soul composes the codification to do the trial walk. The mortal who composes the tryout leaves and allows the other hombre to pen the codification. They are not speaking about designing, he merely forces the incumbrance of designing to the other soul. This attack boost individual programing, but sometimes you can bring awhile in order to do the experience of programming a trifle spot different.

Q & Angstrom:

What Holds the wagers manner to larn brace scheduling? If ne'er roll in the hay earlierly so get mentors, outside people who hold bedded before

Should people couple day in and day out? No, there are some projects that make n't rattlingly gain from it. Sometimes the best style for the squad to lick the job is to hold one somebody tour and conceive about it and lick how to roll in the hay. In an 8 hr day the brace should be around five-five and a one-half.

Behaviour driven development in Java with easyb
( by John Ferguson Smart

This was a talking about the easyb
model and behavior driven development.

The talking commenced by explicating that TDD is not about trials, but about deforming good package. In the same fashion behaviour-driven development is not about behavior, it Holds about presenting package that assists the end-user. TDD generally tends to do better codification, by the application being more flexible, more better contrived and more maintainable.

BDD is a recent development of TDD. The thought is to aid to ascertain what to prove. In order to prove employment examples it applies words like `` should '' to depict the wanted behavior of the category, eg should verify that client can refund before sanctioning loan, should reassign money from story a to account bacillus As with TDD you should likewise revolve around demands not on execution.

The model to make BDD is easyb which is an os testing model for Java ( but indited in Groovy
It does trying clearer and easier to compose. It does tryouts self-documenting and it raises communicating between the development squad and the terminal user. There is another BDD tryout model for Java named JBehave
but on the verbalizer 's personal sentiment it Holds cumbrous to apply. easyb is based on groovy but it holds Java like syntax, it Holds speedy to indite and you hold full entree to Java families and Apis.

easyb in action trial demand by composing easyb tales which:

• utilize a narrative attack


• depict a precise demands


• can be understood by a stakeholder


• usually done upwardly of a set of scenarios


• utilize an easy to understand construction

Lashkar-e-Toiba look at an instance user narrative: opening a bank history. `` As a client I desire to open a bank story so that I can pose my money into a safe spot ''. We come upwardly with a listing of projects. Unfastened history, do initial alluviationetc. Lets center the initial sedimentation demand:

Do initial alluviation:

• given a freshly create story


• when a alluviation is done


• so the story balance should be adequate to money stuck.

You implement the scenario in a trial test suit indited in Groovy which can apply all Java Apis.

If we need to compare easyb to JUnit

• more boilerplate codification demanded in JUnit


• not rattlingly self-explanatory


• the aim is less clear.

With easyb you can hold multiple station and pre conditions.

In easyb you hold shouldBe
syntax alternatively of assert. Fluctuations of the shouldBe
syntax include shouldBeEqualTo
shouldNotBe
shouldHave
etc. Too there is another manner to verify outcome, the ensure
syntax, which is much like Java assert

Fixtures in easyb; you can utilize before
and before_each
( similar to @Before
and @BeforeClass
in JUnit ). Very utile for laying upwards database and trial waiters. You an besides employ after
after_each
( similar to @After
and @AfterClass

Fixtures are good at

• holding substructure codification out of the test suit.


• doing test suit more decipherable and graspable.

As for easydb plugins, but one is available, the dbunit. But more to come for Grails and Excel.

easyb produces tryout specs in user-friendly formatting and flags pending ( unimplemented ) tales. Too renders clear fault messages. When trials neglect easyb will state you why by a more decipherable way than JUnit.

As for IDE support for easyb. There are three option options: IntelliJ, Occultation, NetBeans, but simply IntelliJ holds a really good support for Groovy.

Some upcoming easyb features

• HTML studies


• grails plugin


• Curie desegregation


• Relaxation - a fitnesse
  fashion web application ( stake-holders make narratives in normal text )

The talking shutted with an easyb demonstration and stepping through the rootage codification of the test suit.

What's new in Spring Framework 3.0
( by Arjen Poutsma
and Alef Arendsen

New features in the forthcoming3.0 release and likewise some that already be in2.5 release.

@Controller
for Springtime MVC.

@RequestMapping methods.

@RequestMapping("/vets")

public List<Vet> vets()

{

return clinic.getVets();

}



Constantly simplifying, LoC for sample application PetClinic over clip, it dropped significantly from Leaping2.0 to Bounding2.5.

Springtime integrating now in1.0 version. relinquished last hebdomad in SpringOne.

@PathVariable

@RequestMapping("/pets/{petId}")

public Visit visit{

@PathVariable long petId

New Perspectives with new Mummer types:

• application/xml usage MashallingView in3.0M2/SWS1.5


• application/atom+xml usage AtomFeedView3.0M1


• application/rss+xml utilization RssFeedView3.0M1


• application/json utilization JsonView Spring-JS

ShallowEtagHeaderFilter

• introduces in Leaping3.0M1


• makes ETag heading based on MD5 of rendered perspective


• saves bandwidth simply


• Deep ETag support comes in M2 ( through @ RequestHeader )

At this point they demonstrated a demonstration with URI support and ATOM provender by utilise Springtime MVC.

Acquainting aspects Leaping3.0 will include full support for looks.

Bounding3.0 will simply be available for people who apply Java 5. It will support the Portlet2.0 spec. And dependent on specifications finalising ( if they are relinquished not late ) it will support Java EE6, the Servlet3.0, JSF2.0, JAX-RS and JPA2.0. It will likewise support Web Beans notes.

Leaping3.0 will deprecate/remove several material:

• traditional Springtime MVC accountant jierarchy


• Commons Properties support


• Traditional TopLink support


• Traditional JUnit3.8 category hierarchy.

but it will still be

• 95 % backwards compatible with regards to Apis


• 99 % backwards compatible in the programing framework.

Bounding3.0M1 relinquished last hebdomad.
Leaping3.0 Milestones Janurary/February 2009
Leaping3.0 Release Candidates March/April 2009

Related posts:
Personal Liability Insurance

Overseas Insurance

Brand Rails lumberjack available in codification normally outside of feller reach

Yeah yeah ( Comedy Composition )

Installation Microsoft Office 2007 utilizing vino