java - Embedded OSGi or Application Bundle -

I have just spent reading OSGI content in the last two days, so that I can get my hand and in the end I think That's got my head around it.

Now I am trying to integrate it with an existing application for a variety of reasons, such as 3rd party plugins, automatic updates, do not mention that SOA makes me happy. / P>

Now I have a decision that I am struggling to make, which is the weather

1. My entire app should be the default OSGI bundle installed in the container ; Or
2. My application should launch an embedded OSGI container and for all plug-in services it should be interacted with.

I like 1, because it allows me to update the application easily and the architecture will be consistent, of course, I hope that the application has to be re-implemented in many small bundles . Although 2 makes things very easy in the short run, but it will be weird in the future.

for option 1) You do not really want to have your whole application in a bundle - You will lose all the benefits - but in reality it depends on the size of your application.

It really depends on where you want to run, besides the application and what you want to do, you may want to use some of the exposed services.

in option 1) you need to enable any kind of http / servlet bundle (option has a bridge that exists) 2) You can apply within an application server so that you can Do not worry about

The first question that you want to ask yourself is about the operating environment. Who is going to run the application? Do they need to be trained on OSGi? Are they more comfortable with the J2 EEE stack?

I think the best option for you is to keep your options open, there is no real difference between 1) and 2) but what is staging the OSGI structure, either your code or framework code Your application, i.e. the bundle that constitutes your application, will be exactly the same.

My advice would not be to worry too much about starting with the time of OSGI - but starting from the development of the OSG - nothing is preventing you from developing "OSGi-style" and a Running in standard JRE environment.