java - Is OSGi overkill for modularized Web projects? -
i develop big web project java, maven, , spring. however, there different flavors of web project created specific customer needs. instance, if 1 customer wants twitter page, not, need able build flavor of web project or without twitter page.
i have been looking maven overlays , osgi 2 options. maven overlays tend take long time build when copying resources base overlay. looking @ spring osgi web option because seem on right track modularizing small chuncks (controllers, views, js/resources/images) web projects.
is osgi overkill? need use? there better?
osgi great if need add/remove unforeseen features (and code) @ runtime (and not enable or disable it), time not needed web apps.
so in case recommend use configuration (file) enable or disable features long possible. have advantage, need 1 war.
to handle problem of: "how put configuration file in war", have several ways ( different files packaged in maven war project ):
- use maven environements - (ok have several wars, differn in config file, , build process becomes not slow, because war packaging process done each environment)
- store configuration outside of war
- store configuration outside of war example in database
Comments
Post a Comment