Spring Extension Factory now on Github

Two years ago I wrote a tiny little piece of software that lets you combine Spring Dynamic Modules and the Equinox Extension Registry in an easy way. Now I found the time to put this SpringExtensionFactory on Github. So if you ever wanted to use Spring Dynamic Modules to inject dependencies into your RCP view and editors - take a look, its quite simple to use... :-)

Two years ago I wrote a tiny little piece of software that lets you combine Spring Dynamic Modules and the Equinox Extension Registry in an easy way. Now I found the time to put this SpringExtensionFactory on Github. So if you ever wanted to use Spring Dynamic Modules to inject dependencies into your RCP view and editors - take a look, its quite simple to use... :-)

Spring Extension Factory now on Github

Two things...

The end of September is approaching fast, so its time for me to announce two things...

First the sad part of the story: I will leave it-agile at the end of this month. The reason behind this is basically that I am sick of traveling. Don't misunderstand me, I always tried to make my traveling as comfortable as possible (and it was quite comfortable). But I wish to spent more time being in my home town, being with the family, with my two wonderful kids.

I founded it-agile about six years ago, together with great colleagues and friends to start something new, something great about agile software development, something with true employee participation, where transparency becomes reality, something open for cooperations and with honesty to all our customers. We wanted to build a company that makes a real difference, that doesn't promise everything just to get the contract, that isn't focussed and dogmatic on some religion, a consulting company that doesn't know it better just because we are consultants.

And today, looking back over the past six years, I am so proud that we got it all to work. All wishes became true - and we built a really great company. I learned a lot over the past years and I have to thank all of my colleagues within it-agile and within the projects I was involved in for this absolutely awesome and unforgettable time.

What comes next? I got the chance to join the people at the SpringSource devision of VMware to become part of the STS (SpringSource Tool Suite) team. These are the guys behind the STS, AJDT and the Eclipse Groovy tooling and I am looking forward to work with this great team on amazing developer tooling - and I think (and hope) that I will have some more time to work on some open-source projects, including Equinox Weaving. And last but not least, I will mostly work in Hamburg, my lovely home town... :-)

See you at WJAX in Munich this year!

The end of September is approaching fast, so its time for me to announce two things...

First the sad part of the story: I will leave it-agile at the end of this month. The reason behind this is basically that I am sick of traveling. Don't misunderstand me, I always tried to make my traveling as comfortable as possible (and it was quite comfortable). But I wish to spent more time being in my home town, being with the family, with my two wonderful kids.

I founded it-agile about six years ago, together with great colleagues and friends to start something new, something great about agile software development, something with true employee participation, where transparency becomes reality, something open for cooperations and with honesty to all our customers. We wanted to build a company that makes a real difference, that doesn't promise everything just to get the contract, that isn't focussed and dogmatic on some religion, a consulting company that doesn't know it better just because we are consultants.

And today, looking back over the past six years, I am so proud that we got it all to work. All wishes became true - and we built a really great company. I learned a lot over the past years and I have to thank all of my colleagues within it-agile and within the projects I was involved in for this absolutely awesome and unforgettable time.

What comes next? I got the chance to join the people at the SpringSource devision of VMware to become part of the STS (SpringSource Tool Suite) team. These are the guys behind the STS, AJDT and the Eclipse Groovy tooling and I am looking forward to work with this great team on amazing developer tooling - and I think (and hope) that I will have some more time to work on some open-source projects, including Equinox Weaving. And last but not least, I will mostly work in Hamburg, my lovely home town... :-)

See you at WJAX in Munich this year!

Two things...

SE-Radio Episode with Kent Beck is Online

The latest episode on Software Engineering Radio went online yesterday and covers an interview I did with Kent Beck on the history of JUnit and the future of testing and software engineering. I am pretty excited that we got Kent on the show and have him talk about these topics. He is definitely one of the most influential guys in software engineering these days - father of extreme programming, inventor of unit testing, co-creator of JUnit, co-creator of the agile movement, created test-driven development - to name just a few things he created/invented that changed the daily life of many software developers across the planet. I don't know why it took more than 160 episodes to have him on the show, but I think this was not the last episode on SE-Radio talking with Kent Beck... :-)

The latest episode on Software Engineering Radio went online yesterday and covers an interview I did with Kent Beck on the history of JUnit and the future of testing and software engineering. I am pretty excited that we got Kent on the show and have him talk about these topics. He is definitely one of the most influential guys in software engineering these days - father of extreme programming, inventor of unit testing, co-creator of JUnit, co-creator of the agile movement, created test-driven development - to name just a few things he created/invented that changed the daily life of many software developers across the planet. I don't know why it took more than 160 episodes to have him on the show, but I think this was not the last episode on SE-Radio talking with Kent Beck... :-)

SE-Radio Episode with Kent Beck is Online

Some More Thoughts on Software Architectures

Some month ago I wrote a blog post about some of my thoughts on software architecture and why I think the metaphor of a cathedral is no longer very useful for todays software development. I don't mean that you don't need an architecture when you do agile software development. A good software architecture is absolutely necessary to survive. It is an essential part of each system.

Nevertheless agile software development is based on the idea of embracing change. "Inspect and Adapt" is the secret of success in agile development. The structure of your software emerges over time when you constantly refactor your code. But is this also true for the architecture of the system? Does this architecture emerge over time as well? Or is it adaptable when life changes?

I discussed this a lot over the past years with various people. We typically found two basic contrasting (for this posting simplified) opinions:

• Opinion 1: The architecture includes the most important technical decisions. It is hard to change those things later on. Therefore the architecture should be defined at the beginning of a project and should experience only minor changes. Major changes in the architecture are considered a bad thing and should be avoided.
• Opinion 2: The architecture of a system is an artifact that emerges over time. It reacts to change by embracing it. Changing the architecture of a system is considered a good thing and part may be part of your daily live.

While I was always an opinion-2-guy, I always had to admit that some parts of the architecture of a system are hard to change. So changing a large rich-client app to a web-based app might be expensive. The same might be true for changing the implementation language or refactoring a classical three-tier app into a Quasar-like structure.

Then I recorded SE-Radio podcast episode 166 with John Wiegand and listened to him talking about what he calls "Living Architectures":

• SE-Radio Episode 166: Living Architectures with John Wiegand

During the episode he explains the basic architectural decisions behind the Eclipse platform and the Jazz project at IBM. Both architectures are surprisingly simple. They define the general idea of how parts of the system are built and interact. And both don't contain a single word about those things I mentioned above. Even the language is an implementation detail.

The Jazz system is, for example, built around the idea of the web. RESTful services define the heart of the structure. It doesn't matter how those services are implemented, which frameworks they use or how they are internally structured. The whole system might consists out of various languages, various runtime platforms, various infrastructure settings. Even object-orientation becomes an implementation detail of individual services. All things I often thought of being part of the general architecture. But now I know that I was terribly wrong about this.

Of course there are things that are expensive to change. Reimplementing a huge system with a different language might cost you a lot. But the question is: Why do you need to reimplement everything if you switch to another implementation language? The RESTful style, for example, doesn't require such a tight language binding. Its just an example, but it made me think. And it convinced me that "the definition of architecture as the set of things that are hard or expensive to change" leads into the wrong direction.

Architectures are living things. Don't treat them as dead artifacts. And don't be afraid of change. Its a good thing. It reflects your learning. It helps you build better systems.

Some month ago I wrote a blog post about some of my thoughts on software architecture and why I think the metaphor of a cathedral is no longer very useful for todays software development. I don't mean that you don't need an architecture when you do agile software development. A good software architecture is absolutely necessary to survive. It is an essential part of each system.

Nevertheless agile software development is based on the idea of embracing change. "Inspect and Adapt" is the secret of success in agile development. The structure of your software emerges over time when you constantly refactor your code. But is this also true for the architecture of the system? Does this architecture emerge over time as well? Or is it adaptable when life changes?

I discussed this a lot over the past years with various people. We typically found two basic contrasting (for this posting simplified) opinions:

• Opinion 1: The architecture includes the most important technical decisions. It is hard to change those things later on. Therefore the architecture should be defined at the beginning of a project and should experience only minor changes. Major changes in the architecture are considered a bad thing and should be avoided.
• Opinion 2: The architecture of a system is an artifact that emerges over time. It reacts to change by embracing it. Changing the architecture of a system is considered a good thing and part may be part of your daily live.

While I was always an opinion-2-guy, I always had to admit that some parts of the architecture of a system are hard to change. So changing a large rich-client app to a web-based app might be expensive. The same might be true for changing the implementation language or refactoring a classical three-tier app into a Quasar-like structure.

Then I recorded SE-Radio podcast episode 166 with John Wiegand and listened to him talking about what he calls "Living Architectures":

• SE-Radio Episode 166: Living Architectures with John Wiegand

During the episode he explains the basic architectural decisions behind the Eclipse platform and the Jazz project at IBM. Both architectures are surprisingly simple. They define the general idea of how parts of the system are built and interact. And both don't contain a single word about those things I mentioned above. Even the language is an implementation detail.

The Jazz system is, for example, built around the idea of the web. RESTful services define the heart of the structure. It doesn't matter how those services are implemented, which frameworks they use or how they are internally structured. The whole system might consists out of various languages, various runtime platforms, various infrastructure settings. Even object-orientation becomes an implementation detail of individual services. All things I often thought of being part of the general architecture. But now I know that I was terribly wrong about this.

Of course there are things that are expensive to change. Reimplementing a huge system with a different language might cost you a lot. But the question is: Why do you need to reimplement everything if you switch to another implementation language? The RESTful style, for example, doesn't require such a tight language binding. Its just an example, but it made me think. And it convinced me that "the definition of architecture as the set of things that are hard or expensive to change" leads into the wrong direction.

Architectures are living things. Don't treat them as dead artifacts. And don't be afraid of change. Its a good thing. It reflects your learning. It helps you build better systems.

Some More Thoughts on Software Architectures

Slides from Java-Forum-Stuttgart 2010

I gave a talk about some lessons learned when using OSGi in various settings at this years Java-Forum-Stuttgart. It's pretty much the talk I gave together with Chris Anisczcyk, Jeff McAffer and Paul VanderLei at this years EclipseCon. Here are the slides we used:

• OSGi Lessons Learned: Best and Worst Practices (pdf)

Enjoy!

I gave a talk about some lessons learned when using OSGi in various settings at this years Java-Forum-Stuttgart. It's pretty much the talk I gave together with Chris Anisczcyk, Jeff McAffer and Paul VanderLei at this years EclipseCon. Here are the slides we used:

• OSGi Lessons Learned: Best and Worst Practices (pdf)

Enjoy!

Slides from Java-Forum-Stuttgart 2010

Eclipse Demo Camp in Hamburg on July 9th - Don't miss it!!!

The upcoming Eclipse Helios Demp Camp in Hamburg on July 9th will be really amazing. Peter and myself are working on a great program for this event and we already have good ideas and suggestions. Apart from that we have organized a new location. The demo camp will take place in the Magazin-Kino in Hamburg, a cinema just for us for this evening. As you can imagine, popcorn, ice-cream, and soft-drinks will be ready for you as well as some more surprises! So don't miss it!!! Join us on July 9th, register here: Helios Demo Camp Hamburg Wiki Page.

See you at the cinema!!!

P.S.: There is no soccer game (FIFA World Cup) that evening. So there is no reason not to come... :-)

The upcoming Eclipse Helios Demp Camp in Hamburg on July 9th will be really amazing. Peter and myself are working on a great program for this event and we already have good ideas and suggestions. Apart from that we have organized a new location. The demo camp will take place in the Magazin-Kino in Hamburg, a cinema just for us for this evening. As you can imagine, popcorn, ice-cream, and soft-drinks will be ready for you as well as some more surprises! So don't miss it!!! Join us on July 9th, register here: Helios Demo Camp Hamburg Wiki Page.

See you at the cinema!!!

P.S.: There is no soccer game (FIFA World Cup) that evening. So there is no reason not to come... :-)

Eclipse Demo Camp in Hamburg on July 9th - Don't miss it!!!

Slides from JAX-2010

I gave a bunch of talks together with colleagues at the JAX 2010 conference last week in Mainz, Germany. Aside of the fact that I enjoyed the conference a lot this year (again), it was fun presenting there. For those of you interested in the slideware:

• Was wird aus dem Projektleiter in agilen Projekten (in german, together with Henning Wolf)
• Was können Unternehmen von Open-Source lernen (in german, together with Bernd Kolb)
• Wie Modulsysteme Architekturen beeinflussen (mostly english slides)

Sorry for this bulk of German titles. The slides are mostly Presentation Zen style, so not many German words here. Hope you enjoy it anyway! :-)

I gave a bunch of talks together with colleagues at the JAX 2010 conference last week in Mainz, Germany. Aside of the fact that I enjoyed the conference a lot this year (again), it was fun presenting there. For those of you interested in the slideware:

• Was wird aus dem Projektleiter in agilen Projekten (in german, together with Henning Wolf)
• Was können Unternehmen von Open-Source lernen (in german, together with Bernd Kolb)
• Wie Modulsysteme Architekturen beeinflussen (mostly english slides)

Sorry for this bulk of German titles. The slides are mostly Presentation Zen style, so not many German words here. Hope you enjoy it anyway! :-)

Slides from JAX-2010

Sessionfire Continues to Innovate

A few days ago the team at Sessionfire published its second beta build. Interestingly this new build does not add these basic features you might expect from a presentation tool like direct graphical editing or so. In contrast to that it innovates. Its adds real new stuff to the world of presentations. Things that helps you to improve your presentations, to visualize things for your audience. The big new feature in this build is "Non-Linear Presentations". You no longer need to put your slides in a linear sequence - they aren't anyway. Many of my talks contain different sections and details, sometimes I decide to skip a section, sometimes I just want to show the topics while speaking. This is now directly supported in Sessionfire, giving you the option to create sections and visualize those sections for your audience. You can go into the details on demand or just jump from section to section at your fingertip. Watch the teaser case at YouTube, it shows non-linear presentations among the other new features in a quick overview:

The current Sessionfire beta builds are free. You can download your copy for Windows XP/Vista/7, Mac OS X or Linux from http://www.sessionfire.com/. Just make sure you have the latest Java6 installed... :-)

A few days ago the team at Sessionfire published its second beta build. Interestingly this new build does not add these basic features you might expect from a presentation tool like direct graphical editing or so. In contrast to that it innovates. Its adds real new stuff to the world of presentations. Things that helps you to improve your presentations, to visualize things for your audience. The big new feature in this build is "Non-Linear Presentations". You no longer need to put your slides in a linear sequence - they aren't anyway. Many of my talks contain different sections and details, sometimes I decide to skip a section, sometimes I just want to show the topics while speaking. This is now directly supported in Sessionfire, giving you the option to create sections and visualize those sections for your audience. You can go into the details on demand or just jump from section to section at your fingertip. Watch the teaser case at YouTube, it shows non-linear presentations among the other new features in a quick overview:

The current Sessionfire beta builds are free. You can download your copy for Windows XP/Vista/7, Mac OS X or Linux from http://www.sessionfire.com/. Just make sure you have the latest Java6 installed... :-)

Sessionfire Continues to Innovate

OSGi Best and Worst Practices at EclipseCon 2010

Together with Jeff McAffer, Chris Anisczcyk and Paul VanderLei I gave a talk on OSGi Best and Worst Practices here at Eclipse 2010. Here are the slides:

• OSGi Best and Worst Practices (pdf)

Enjoy!

Together with Jeff McAffer, Chris Anisczcyk and Paul VanderLei I gave a talk on OSGi Best and Worst Practices here at Eclipse 2010. Here are the slides:

• OSGi Best and Worst Practices (pdf)

Enjoy!

OSGi Best and Worst Practices at EclipseCon 2010

Slides on OSGi Best and Worst Practices from Java-User-Group-Meeting in Karlsruhe

I gave a talk at the Java User Group Karlsruhe last week on best and worst practices using OSGi for building business applications (thanks to David for inviting me). You can get the slides from the user group or directly here:

• OSGi Best and Worst Practices (pdf)

Thanks again for joining! The room was full of people and I especially enjoyed all the great questions and discussions during and after the talk. Thanks again, it was a pleasure to be a guest at the event!

I gave a talk at the Java User Group Karlsruhe last week on best and worst practices using OSGi for building business applications (thanks to David for inviting me). You can get the slides from the user group or directly here:

• OSGi Best and Worst Practices (pdf)

Thanks again for joining! The room was full of people and I especially enjoyed all the great questions and discussions during and after the talk. Thanks again, it was a pleasure to be a guest at the event!

Slides on OSGi Best and Worst Practices from Java-User-Group-Meeting in Karlsruhe

Slides on OSGi Lessons Learned from OOP-2010 Conference

A few weeks ago I gave a talk at the OOP-2010 conference in Munich about the lessons I learned from building business apps on top of OSGi during the past five years. Finally I put the slides online:

• OSGi - Lessons Learned (pdf)

Sorry for the delay!

A few weeks ago I gave a talk at the OOP-2010 conference in Munich about the lessons I learned from building business apps on top of OSGi during the past five years. Finally I put the slides online:

• OSGi - Lessons Learned (pdf)

Sorry for the delay!

Slides on OSGi Lessons Learned from OOP-2010 Conference

A Big Thank You for the Feedback

Feedback is an essential force and of priceless value for many things you do in your daily life. It is one of the central elements of agile software development and it is absolutely priceless to get honest and constructive feedback for the work you do. Sometimes its hard to get this feedback, sometimes not. Some of you might know that I am part of the podcast team at Software Engineering Radio, a podcast for professional software developers that publishes a new episode every 14 days under a creative commons license. I don't do as much episodes as I wish, but regularly people write emails to the team saying "thank you for the great work" and telling us that they really like what we do. Now its time for me to say a big THANK YOU back to those guys. Especially this blog entry that I read today is really nice (many many thanks) and gives a lot of motivation!

Thank you!!!

Feedback is an essential force and of priceless value for many things you do in your daily life. It is one of the central elements of agile software development and it is absolutely priceless to get honest and constructive feedback for the work you do. Sometimes its hard to get this feedback, sometimes not. Some of you might know that I am part of the podcast team at Software Engineering Radio, a podcast for professional software developers that publishes a new episode every 14 days under a creative commons license. I don't do as much episodes as I wish, but regularly people write emails to the team saying "thank you for the great work" and telling us that they really like what we do. Now its time for me to say a big THANK YOU back to those guys. Especially this blog entry that I read today is really nice (many many thanks) and gives a lot of motivation!

Thank you!!!

A Big Thank You for the Feedback

Sessionfire is available as public beta

Some of you might know, Matthias and myself are working on a new kind of presentation tool, called Sessionfire. After a period of private alpha testing we are pretty happy that it has left this period just a few days ago and started its public beta stage. So everybody is invited to grab a copy of it and give it a try. Its not open source (maybe it will be some day in the future), but its free to download and free to use (as well as the next beta builds).

The current beta version has a quite limited set of features, so you don't get a replacement for your favorite presentation tool right away. We start with something small, far far away from being feature complete, move forward in small steps while always trying to do something useful in a gorgeous way. So you won't be able to create your presentation completely with Sessionfire at the moment, for example. But you can run your show with Sessionfire, using images, animations, timers, three-dimentional optics, reflections, visual fast-forward and -backward, different 3D-layoutings and some more stuff.

Try it! - Enjoy it!

Some of you might know, Matthias and myself are working on a new kind of presentation tool, called Sessionfire. After a period of private alpha testing we are pretty happy that it has left this period just a few days ago and started its public beta stage. So everybody is invited to grab a copy of it and give it a try. Its not open source (maybe it will be some day in the future), but its free to download and free to use (as well as the next beta builds).

The current beta version has a quite limited set of features, so you don't get a replacement for your favorite presentation tool right away. We start with something small, far far away from being feature complete, move forward in small steps while always trying to do something useful in a gorgeous way. So you won't be able to create your presentation completely with Sessionfire at the moment, for example. But you can run your show with Sessionfire, using images, animations, timers, three-dimentional optics, reflections, visual fast-forward and -backward, different 3D-layoutings and some more stuff.

Try it! - Enjoy it!

Sessionfire is available as public beta

Some Thoughts on Cathedrals and Software Architectures

While preparing a talk on module systems and architectures I remembered some old talks I listened to talking about architectures and arguing why an explicit software architect is necessary within professional projects. Many of them used the analogy of building a dog-house versus building a cathedral. For a small dog house, you don't need an architecture. But for the cathedral you do. Hm, agree, but where is the point?

I think the world has changed. Today for most software systems the analogy of building something like a cathedral is no longer a good choice. And I hope that people no longer have a cathedral in mind when designing software. We have learned that building software is a learning process, that requirements change all the time, that we need a short time-to-market, and most of all that we need feedback all the time - and react to this feedback quickly. Agile methods reflect this and allows us to move forward to modern ways of software development.

But our view on architectures need to reflect this. Modern software architectures need to be build for flexibility, for changing requirements all the time, for changing even fundamental layers of our software in a flexible way without causing tremendous costs. Having a cathedral in mind don't help you here. But if you still like the analogy of building real buildings (even though I think this is not always a good analogy to building software at all), you should take a look at some modern office buildings. Maybe they are not as beautiful as some of the old cathedrals, but they are built for flexibility.

But building flexible architectures is not an easy task. We need to build a flexible architecture and at the same time just what we need without designing all possible stuff upfront. Sounds like contradictory goals, eh? Hm, in some way, they are. I think modularity can help you to solve this conflict. Modularity (and I mean modularity on a higher level than individual classes or packages, but more something like Bundles in OSGi) helps you to think about dependencies, coupling, cohesion, and many of these nice design principles. And I think we all agree on having a good, decoupled design makes life easier when things change - and they will change.

While preparing a talk on module systems and architectures I remembered some old talks I listened to talking about architectures and arguing why an explicit software architect is necessary within professional projects. Many of them used the analogy of building a dog-house versus building a cathedral. For a small dog house, you don't need an architecture. But for the cathedral you do. Hm, agree, but where is the point?

I think the world has changed. Today for most software systems the analogy of building something like a cathedral is no longer a good choice. And I hope that people no longer have a cathedral in mind when designing software. We have learned that building software is a learning process, that requirements change all the time, that we need a short time-to-market, and most of all that we need feedback all the time - and react to this feedback quickly. Agile methods reflect this and allows us to move forward to modern ways of software development.

But our view on architectures need to reflect this. Modern software architectures need to be build for flexibility, for changing requirements all the time, for changing even fundamental layers of our software in a flexible way without causing tremendous costs. Having a cathedral in mind don't help you here. But if you still like the analogy of building real buildings (even though I think this is not always a good analogy to building software at all), you should take a look at some modern office buildings. Maybe they are not as beautiful as some of the old cathedrals, but they are built for flexibility.

But building flexible architectures is not an easy task. We need to build a flexible architecture and at the same time just what we need without designing all possible stuff upfront. Sounds like contradictory goals, eh? Hm, in some way, they are. I think modularity can help you to solve this conflict. Modularity (and I mean modularity on a higher level than individual classes or packages, but more something like Bundles in OSGi) helps you to think about dependencies, coupling, cohesion, and many of these nice design principles. And I think we all agree on having a good, decoupled design makes life easier when things change - and they will change.

Some Thoughts on Cathedrals and Software Architectures

Slides from Meet-The-Experts on Architecture

Last friday I was invited to give a talk at the Meet-the-Experts event in Solingen. I talked about my view on architectures in an agile world and how module systems drive those architectures for a flexible future. Here are the slides:

• How Module Systems Drive Architectures (pdf)

Enjoy!

Last friday I was invited to give a talk at the Meet-the-Experts event in Solingen. I talked about my view on architectures in an agile world and how module systems drive those architectures for a flexible future. Here are the slides:

• How Module Systems Drive Architectures (pdf)

Enjoy!

Slides from Meet-The-Experts on Architecture

2nd Eclipse DemoCamp Hamburg in 2009

I organized a number of demo camps over the past years (always together with my colleague and friend Peter Friese), but the last one was different. I was overwhelmed by the huge number of registered attendees for the 2nd Eclipse Demo Camp in Hamburg this year. We had over 110 people registered on the wiki - around twice as much as for the other camps in the past. And nearly all of them showed up at the event. This was absolutely amazing! Thanks again to all of you making this event such a big success!!!

Peter posted some notes on the program and what happened during the demo camp, so I don't repeat all this and instead direct you to his nice summary of the event. And I have to say many many thanks to all the wonderful speakers who all gave funny and entertaining talks and made the evening not just full-packed with information and details on Eclipse stuff, but also a fun event. I enjoyed it very very much!

Looking forward to organizing the next demo camps and hoping to see you all there!!!

I organized a number of demo camps over the past years (always together with my colleague and friend Peter Friese), but the last one was different. I was overwhelmed by the huge number of registered attendees for the 2nd Eclipse Demo Camp in Hamburg this year. We had over 110 people registered on the wiki - around twice as much as for the other camps in the past. And nearly all of them showed up at the event. This was absolutely amazing! Thanks again to all of you making this event such a big success!!!

Peter posted some notes on the program and what happened during the demo camp, so I don't repeat all this and instead direct you to his nice summary of the event. And I have to say many many thanks to all the wonderful speakers who all gave funny and entertaining talks and made the evening not just full-packed with information and details on Eclipse stuff, but also a fun event. I enjoyed it very very much!

Looking forward to organizing the next demo camps and hoping to see you all there!!!

2nd Eclipse DemoCamp Hamburg in 2009

OSGi for Eclipse Developers Webinar

Today I gave an Eclipse webinar on "OSGi for Eclipse Developers" together with Chris Aniszczyk and Bernd Kolb. We talked about various OSGi things that might sound strange and/or unfamiliar to you if you come from the Eclipse way of developing applications. We talked about the relationship of Eclipse and OSGi, dependency management and why you should use Import-Package instead of Require-Bundle, dynamics with OSGi, services vs. extensions, versioning, some compendium services and tooling for OSGi. If you missed the live broadcast, you can watch the entire webinar from here again. Enjoy!

Today I gave an Eclipse webinar on "OSGi for Eclipse Developers" together with Chris Aniszczyk and Bernd Kolb. We talked about various OSGi things that might sound strange and/or unfamiliar to you if you come from the Eclipse way of developing applications. We talked about the relationship of Eclipse and OSGi, dependency management and why you should use Import-Package instead of Require-Bundle, dynamics with OSGi, services vs. extensions, versioning, some compendium services and tooling for OSGi. If you missed the live broadcast, you can watch the entire webinar from here again. Enjoy!

OSGi for Eclipse Developers Webinar

Coming Up: Eclipse Demo Camp in Hamburg at December, 4th

The Eclipse Demo Camp in Hamburg is coming up on 4th of December (its a Friday) from 6:30pm - 10pm at the stylish EAST hotel (like the past demo camps in Hamburg). And I am pretty impressed about the number of participants: We already have more than 70 people registered for the event. Wow... Maybe one of the reasons is the exciting program we put together... :-)

• Tom Schindl will talk about Eclipse e4
• Jan Köhnlein talks about building graphical and textual editors for your domain-specific language.
• Jochen Krause will showcase Eclipse RAP and how you can build your rich AJAX apps using the Eclipse UI metaphors.
• Nils Hartmann and Gerd Wütherich will share some insights into the various ways of how to realize an automated build process for OSGi and Eclipse applications.
• And Ekkehard Gentz will show us "redview", a technology to build dynamic views for enterprise applications based on Riena, EMF and CDO.

Thanks to all the speakers who have agreed to join us in Hamburg to give demos on cool technologies - some of them travelling to Hamburg especially for the camp. Thank you all very very very much!!!

If you haven't registered yet, go to the wiki page and put your name on the list (if you have no account for the wiki, just create one or send me an email and I will put you on the list). There is no fee or ticket you need to pay for, itemis and it-agile will sponsor the event. Thank you guys for that!!!

Its a great opportunity to see the technology in action, meet with the guys building that stuff and have a chat. See you at the Demo Camp in Hamburg. Don't miss it!

The Eclipse Demo Camp in Hamburg is coming up on 4th of December (its a Friday) from 6:30pm - 10pm at the stylish EAST hotel (like the past demo camps in Hamburg). And I am pretty impressed about the number of participants: We already have more than 70 people registered for the event. Wow... Maybe one of the reasons is the exciting program we put together... :-)

• Tom Schindl will talk about Eclipse e4
• Jan Köhnlein talks about building graphical and textual editors for your domain-specific language.
• Jochen Krause will showcase Eclipse RAP and how you can build your rich AJAX apps using the Eclipse UI metaphors.
• Nils Hartmann and Gerd Wütherich will share some insights into the various ways of how to realize an automated build process for OSGi and Eclipse applications.
• And Ekkehard Gentz will show us "redview", a technology to build dynamic views for enterprise applications based on Riena, EMF and CDO.

Thanks to all the speakers who have agreed to join us in Hamburg to give demos on cool technologies - some of them travelling to Hamburg especially for the camp. Thank you all very very very much!!!

If you haven't registered yet, go to the wiki page and put your name on the list (if you have no account for the wiki, just create one or send me an email and I will put you on the list). There is no fee or ticket you need to pay for, itemis and it-agile will sponsor the event. Thank you guys for that!!!

Its a great opportunity to see the technology in action, meet with the guys building that stuff and have a chat. See you at the Demo Camp in Hamburg. Don't miss it!

Coming Up: Eclipse Demo Camp in Hamburg at December, 4th

Slides from WJAX Talk on Building Web-Apps with OSGi

I uploaded the slides of my talk on building web applications on top of OSGi that I gave yesterday at WJAX 2009 together with Gerd Wütherich and Peter Roßbach:

• Mit OSGi Webanwendungen entwickeln - Was geht, was nicht? (pdf)

The slides are German only. Sorry about that... Hope you enjoy it anyway... :-)

I uploaded the slides of my talk on building web applications on top of OSGi that I gave yesterday at WJAX 2009 together with Gerd Wütherich and Peter Roßbach:

• Mit OSGi Webanwendungen entwickeln - Was geht, was nicht? (pdf)

The slides are German only. Sorry about that... Hope you enjoy it anyway... :-)

Slides from WJAX Talk on Building Web-Apps with OSGi

Slides from OSGi Best Practices and OSGi Performance Bloopers talks at WJAX 2009

Here are the slides of my two talks that I gave today at the WJAX conference in Munich:

• OSGi Best Practices (pdf) (together with Matthias Lübken)
• OSGi Performance Bloopers (pdf)

Enjoy!

Here are the slides of my two talks that I gave today at the WJAX conference in Munich:

• OSGi Best Practices (pdf) (together with Matthias Lübken)
• OSGi Performance Bloopers (pdf)

Enjoy!

Slides from OSGi Best Practices and OSGi Performance Bloopers talks at WJAX 2009