On Mar 30, 2010, at 2:04 AM, Sahoo <[email protected]> wrote: > Looking at the code, I see WebConsole gets bound to whichever > HttpService it encounters first. > > Virtual Hosts are used by many and is supported in many containers, > e.g, Tomcat, GlassFish, etc.
Right, but in order for what you are describing to be an issue, it means that all vhosts are sharing a single OSGi framework. This is the pattern I was asking about. At minimum, it seems like you should be using nested frameworks or something like dmServer/Virgo's notion of regions. Justin > > Thanks, > Sahoo > > Justin Edelson wrote: >> Actually, I would expect web console to register itself with ALL >> HttpService services, but I don't know if that's the current >> behavior. >> >> That said, using multiple HttpServices for virtual hosting seems like >> a bad idea to me (then again, vhosts at the app tier in general seems >> like a bad idea to me). Out of curiosity, is this actually done? >> >> Justin >> >> On Mar 29, 2010, at 8:51 PM, Sahoo <[email protected]> wrote: >> >> >>> Should not there be a way to select an HTTP Service among multiple >>> ones? In environment supporting multiple "virtual servers [1]," an >>> HTTPService maps to a virtual server. In such an environment, this >>> feature will be useful. We can actually take a filter criteria as a >>> configuration. Any comments? >>> >>> Thanks, >>> Sahoo >>> >>> [1] http://www.ex-parrot.com/pete/tomcat-vhost.html >>>
