Code Alert! This is a part of our continuing series on Engineering at LinkedIn. If this isn’t your cup of Java, check back tomorrow for regular LinkedIn programming. In the meanwhile, check out some of our recent announcements, tips and tricks, or success stories.
When you start using OSGi, the very first problem you are going [...]
In my last post I talked about how the Spring-DM extender automatically recognizes new namespaces. In this post I’ll talk about how to configure the extender itself. First let’s talk a little bit about fragments (since it is the mechanism used by Spring-DM).
What is a fragment?
A fragment is a special kind of OSGi bundle. By [...]
LinkedIn has been extensively using the Spring Framework for wiring purposes and life cycle management (we seldom use other features like AOP, JDBC, Spring MVC, etc.). In other words we essentially use the IoC container. To give you an idea of how extensive we use it, as of this writing, we have over 1000 Spring [...]
In this post I will describe how I was able to make LinkedIn’s JSP compiler work within an OSGi container.
I guess the first question I need to answer is why on earth does LinkedIn has its own JSP compiler? The answer is partly for historical reasons and partly for feature reasons. The JSP compiler [...]
For about 2 months now, LinkedIn has been actively working on a new iteration of its architecture: one that scales both from a customer point of view, and from a developer point of view. Our desire for modularity, decoupling, and service discovery led LinkedIn to look at OSGi for its new platform/container. Currently we’re using [...]
We love to hear from you. So feel free to comment, but keep in mind the basics of blog etiquette — no spam, no profanity, no slander, etc. All comments are moderated.
The LinkedIn Blog is proudly powered by WordPress.com
