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

Overcoming sticker shock: addressing the unexpected costs of moving to OSGi in the enterprise.

Eric Johnson

Making With Eclipse · Standard (25 mins)
Wednesday, 16:15, 25 minutes | Winchester

Tags: Build and Continuous Integration , OSGi DevCon , Tools
7
·
8
·
9
·
10
·
11
·
12
·
13
·
14
·
15
·
16
·
17
·
18

In moving our enterprise software to an OSGi environment, we encountered unexpected hurdles. While an OSGi runtime promises better decomposition of our code for more reuse, and a more dynamic execution environment, it also brings along costs.  Unfortunately, some of those costs are non-functional costs, that have nothing to do with whether or not the underlying Java code was written correctly.  This talk will identify and explore issues that lead to these costs, and what we've done about them.

The areas of concern include metadata for features and bundles, build system architecture, deployment, code that runs both within Eclipse and within pure OSGi environments, and a common development platform. Within each of these areas of concern, what have we encountered?  What solutions can we share? Why do these problems exist in the first place? Are there tools out there to help, or do you need to roll your own solution for your particular needs?  If you need to roll your own solution, what can you build upon?

I'll conclude the talk with a discussion of issues that we cannot resolve on our own.  Specifically, what are the opportunities that we see that might be addressed by the OSGi and Eclipse communities?  When the communities tackle these problems, what suggestions or ideas do we have?  What are the communities already doing to address these problems?
 

Eric Johnson has been doing professional software development since the late 80's, and Java development since 2000. He has been working at TIBCO Software Inc. since 2001, and is now a principal architect. Eric's role at TIBCO includes looking broadly at strategic engineering questions. Eric's specific areas of focus include governance, Service Component Architecture (SCA), XML, OSGi, Eclipse, open source software, and build architecture.

Slides