Today you can write a new web application and just run it with Equinox/Jetty or Felix http services. However, what if you need to keep evolving an existing web application and can't just stop and spend months rewriting everything to OSGi architecture? This article explores how you can build on an existing web application and adopt OSGi for web components without first having to rewrite the whole application. An example is provided using Tomcat 6 and Equinox. Read article

Link is not working

<A href="http://www.buzzle.com/articles/tattoo-designs-where-to-find-the-largest-selection.html">Tattoo Designs</a>

The previous night, Polo Outlet with the ground soaked after a daylong rainstorm, Marc Jacobs had held an extravagant runway show on a Hudson River Polo Ralph Lauren Kids pier near the West Village that culminated in an enormous outdoor party celebrating his latest fragrance. On Tuesday morning, Ms. Lange’s show was the 53rd, and last, Polo Ralph Lauren Pants to take place before Fashion Week was called off, the tents evacuated and the 73 remaining events canceled.In the days that followed, Polo Ralph Lauren Shirts many designers, as they struggled to make sense of their world and resume the daily business of fashion, arranged simple presentations in their showrooms.

Step 1, cut a hole in a box

Is it just me, or is that statement slightly offputting? I mean, as soon as it goes over something like SEVEN steps, it's no longer truly easy -- esp. when it wants Eclipse Web Tools experience in the first place. Ruckelshaus Petrie

Is it just me, or is that statement slightly offputting? I mean, as soon as it goes over something like SEVEN steps, it's no longer truly easy -- esp. when it wants Eclipse Web Tools experience in the first place.

Yes, especially when you can do the same in one step: pax-run "--profiles=war" war:mvn:org.apache.wicket/wicket-examples/1.3.0/war you have to wait for a while as the WAR gets downloaded - when you see Jetty output scroll past the console, surf to: http://127.0.0.1:8080/mvn_org.apache.wicket_wicket-examples_1.3.0_war just a short demo, but it shows this can be much simpler. for more details about Pax-Runner see: http://wiki.ops4j.org/display/ops4j/Pax+Runner (disclaimer: I'm a member of the OPS4J community)

The article states : "In a classic WAR, you can isolate the module's classes in their own JARs but you can not keep the module's web resources in the JAR." This is not correct. Apps built with the web4j tool are allowed (and encouraged) to place JSP snippets directly beside the code that uses them. Why? Because its more modular, and allows package-by-feature. I think Wicket follows a similar style as well.

Uh... You can put resources in jars just fine. You could put them in the same jar or separate for that matter. You could put each class/resource set in their own jars. Or each class in its own jar and each resource in its own jar. The possibilities are endless! I can't believe someone who's trying to get OSGi working in a webapp wouldn't know that. The world's a strange place and gets stranger every day...

The article states :
"In a classic WAR, you can isolate the module's classes in their own JARs but you can not keep the module's web resources in the JAR."

This is not correct.

Apps built with the web4j tool are allowed (and encouraged) to place JSP snippets directly beside the code that uses them. Why? Because its more modular, and allows package-by-feature.

I think Wicket follows a similar style as well.

Today you can write a new web application and just run it with Equinox/Jetty or Felix http services. However, what if you need to keep evolving an existing web application and can't just stop and spend months rewriting everything to OSGi architecture?

One thing that I still fail to see is why anyone would *want* to run everything in an OSGi architecture? And I am fairly sure that I will still need to reboot the container rather sooner than later - and the fact that Eclipse encourages me to restart Eclipse after installing a plugin does not make me more optimistic. The whole "using OSGi as an end user technology" smells a lot like reinvention of the wheel yet again.

Today you can write a new web application and just run it with Equinox/Jetty or Felix http services. However, what if you need to keep evolving an existing web application and can't just stop and spend months rewriting everything to OSGi architecture?

One thing that I still fail to see is why anyone would *want* to run everything in an OSGi architecture? And I am fairly sure that I will still need to reboot the container rather sooner than later - and the fact that Eclipse encourages me to restart Eclipse after installing a plugin does not make me more optimistic.

The whole "using OSGi as an end user technology" smells a lot like reinvention of the wheel yet again.

This "reboot not required" meme dilutes what I see as the key benefit of OSGi: modularity. By looking at a bundle's metadata I can immediately see what it needs and what it provides, compared to the current "hit and miss" approach to building the classpath for large applications (this really caused a lot of grief at one of my previous workplaces). The metadata also helps automate and verify deployments. When done right you shouldn't really be aware of OSGi at all, it should just be there in the background helping you manage your application - and hopefully maybe encourage re-use. And ideally any library that becomes OSGi-enabled can still be used in a classic app without requiring OSGi, at least that's what we managed to do with Guice... I also like the OSGi service model, though not the raw API. Disclaimer: I provide an open-source project that builds on top of OSGi services and I'm co-writing a book on OSGi in general - so feel free to take what I say with a pinch of salt :)

I agree with what Stuart says about true modularity with the help of bundle metadata being the key benefit of OSGi versus old-style JARs. I guess in my article I should have at least referred to the great work done at ops4j with PAX. The example in the article shows that - thanks to the plug-in provided with it - I can RUN the app with one press of a button - the green "Run" button in Eclipse - no scripts to execute, no manual redeployment and certainly no 12 steps. Among other things, the servletbridge allows for tight integration of bundelized and non-bundelized JSPs. I used Wicket for two years with OSGi and having the html directly in the code directory was nice. I still prefer my JSPs in a WebContent folder though. In the sample app I am making web-enabled OSGi bundle look and behave like "mini-WARs". That means that it should be easy to bring such bundles to work with the upcoming OSGi RFC-66 specification, once it is finalized and implemented.

The ability to dynamically replace one part of application (demonstrated on switching CSS modules) looks very interesting, I must say. Unfortunately, the last point (#12) doesn't work for me. After stopping or uninstalling the org.rsp.example.http.jsp2_1.1.0 bundle I got 404 code on main page refresh, with no hint in Tomcat console what's wrong (no stacktraces in the console, perhaps the fact that it is also OSGi console blocks printing stacktraces).

Disclaimer: I provide an open-source project that builds on top of OSGi services and I'm co-writing a book on OSGi in general - so feel free to take what I say with a pinch of salt :)

What's the project and what will the book be called. Come on man, plug away. This is TSS.

Is there any way to apply OSGi on EJB applications? It would be nice if you could put business code in modules (OSGi bundles) and reload them at runtime without application restart. Our clients would appreciate if we didn't have to restart application (or server) for every installation. We're using WAS and I haven't found any examples of EJB+OSGi. Regards, Stipe

nice article.

<!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:PunctuationKerning/> <w:ValidateAgainstSchemas/> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:Compatibility> <w:BreakWrappedTables/> <w:SnapToGridInCell/> <w:WrapTextWithPunct/> <w:UseAsianBreakRules/> <w:DontGrowAutofit/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" LatentStyleCount="156"> </w:LatentStyles> </xml><![endif]--> <!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> <!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]-->

Nothing can ruin your day like a cold sore. If you want to kick this condition now and forever, check out this site to know more about cold sore treatment

Normally it does it automatically if it doesn't click on the Apps/Games stab in iTunes when your iPod touch is connected and make sure that the Sync Apps box is checked and that any new apps or games are checked to be synced then click APPLY at the bottom of the window

herve leger sale

Its all BS so I will continue eating steak and having milk with my cereal. Enjoy your lower standard of living that you CHOOSE.

hermes birkin

Just walk up to her smile and say Hi, then talk about whatever comes to mind be friendly and nice hope this helps

jordans shoes

This is helpful in maintaining our website. Visit us at Hotel South Africa

Web Counters are totally FREE!