Gold sponsors

IBM Corporation

SAP

Sonatype

Cisco

JBoss

Intel logo

Oracle

Silver sponsors

bsi logo

Blackberry

Xored

Soyatec

agitar

amazon

Google

Instantiations

Actuate

Microsoft

Bronze sponsors

excelsior

Can't open sponsors/bronze/soyatec/soyatec.

Genuitec

Purple Scout

itemis

Sopera

objectivity

Paremus

froglogic

Activity sponsor

eclipsesource

Media sponsors

TSSJS

SD Times logo

Methods & Tools

GIF89ax-w!,x->;7mmdhI5 zxq}|u{x3tzyt !<wvxvv~~pt~w}u|zsy.~x- |}r/{D;ou/1~ m&]V"c0z2 Kg}Ve&S+,<=j2Msu~Cs~ } YozYVrrx`a.@AEGIzw |W pqq&}zy" ]}'H*\ȰÇD("ŋ3bܨ#ǏC)r"ɓ"S\JMʔs ͙6s܉͟:{ 3M47Atĥ>eiTVJz5+RXvUkUgMRV+wݪsֽ۴ W`z '~;U4HL˘4{B#[~9d^͚ Okm۸sͻ×  )$Iӻ3j"\hνâϾ{_ Ȍ˙'%gyI~G|q~6Zz 'Rև jG@u!^xF NaPAv肎<^@7S/r3 PF)%S,Bẍ$ ė`)f?|Wǘh@"ۑP!Y@vwN $Z.и]zDwp$ZPSv+Tw#Ng;T݉0LN.q%Sy'EK*무9>`p:DQ8]CT8vz,^%,nSZfy5ޙ:Pc,[骥G.:UWz'#_~QRuQO-B&A A&JbUCeRzjƺ1JСr2,0l.zBjkcӞ;+ Iq =s S-2J}p*^ ؙsQM~5״U |dvE1wuղzmUv'HcC-nohݢa7ޞBQ7`# x# @Ӈjx]֛*,WocS[Յ]-j 7!xVB֝f*T< A Ԣ_58Nmdȝfk aL&PiA[ܔǝo}t[Bg ŦEY1ά" ;8a"e>TZV;u]ϵ']j.&7"-t>X6p|>= PMFfoL\ld L$"yHEr,d x*| q$%:sfTVDRh}\W.(ZM7JRgI휪u0|2 l!xt1A,ꀋ)t {WANrhx FCT r,@$z[jIJt X"Vp PBVL},ͨF7ю` XaZTP=Klt!L\ЁNsE ( PJ׳U(`l PrLc]R\`_ á-"DZ7rUZZUNU0Yq \βW2ů_JkW367~倴D;

Be a Sponsor

Making Dependency Injection work for you

Joep Rottinghuis

Making For Eclipse · Standard (25 mins)
Thursday, 13:30, 25 minutes | Grand Ballroom

Tags: Emerging Technology , Java , OSGi DevCon , Tools
7
·
8
·
9
·
10
·
11
·
12
·
13
·
14
·
15
·
16
·
17
·
18

Joep Rottinghuis

By now just about everybody has heard about Dependency Injection (DI) and how cool it is. Yet not everybody has been able to use it in its full glory...

 

In this talk we will discuss how to create loosely coupled libraries that can be used as OSGi bundles, using with Spring Dependency Injection, or in “standalone” mode.

 

Declarative Services are the standard for OSGi and there are other approaches, but what some of the consumers of your library don’t use OSGi? What if you want to use DI in a plain Spring stack on the back-end? Of course you want your code to work in your Eclipse (RCP) application and who wants to write the same thing multiple times?!?

 

We will show an approach that works across all of these use cases.

 

Challenges:

When dealing with Dependency Injection there are several aspects that need to be solved, among which:

  • Coupling
  • Synchronization
  • Type Safety
  • Lifecycle
  • State Change Notification

We will show code how to deal with each of these challenges.

Best Practices:

We will show some best practices to avoid nasty pitfalls. After hearing this talk you too should be able to harness the power of Dependency Injection, no matter the challenges of your environment.

Joep Rottinghuis is Productivity Tools Architect at eBay, Inc.

He is responsible for the architecture and implementation of various tools that support thousands of developers in various steps of the software development lifecycle, including Source Control Managements Tools, Bug Tracking, Merge Coordination System, and Eclipse/RCP Tools.