A virtual host is nothing more than an address space that may or may not correspond to a physical network address. It does belong in this discussion because all network capable services need to delegate their network address settings and port to the virtual host they belong to. This includes web services where your understanding of the term is directly applicable.
I'm looking at the JSR77 draft where it shows the J2EEManagement model. This does correpond to the notion of Domain as I am thinking of it. Likewise, the J2EEServer is related to the VirtuHost notion through the Node[] and Port[] attributes, but it cannot be used as a containing service from which the contained services inherit their VirtualHost information. The JSR77 stuff is too passive of a view for that. That is why I am suggesting that the JSR77 components be views into the true management components of the deployment process. > > Either I don't understand what you are saying about VirtualHost but isn't > the > VirtualHost a term from a web-server and does not belong in this discussion. > > JSR-77 defines at the top a "management domain" which contains a list of > logical servers (in a cluster it is what the cluster represents) and each of > this > server can contain several nodes which represents the physical server. > > I decided to run the JSR-77 beside JBoss because it allows us to map JBoss > to JSR-77 without many changes to the JBoss core code. Thus I can use > the JSR-77 MBeans ObjectName directly to what they client expects. Otherwise > the JSR-77 provider would need to do that. > > Andy > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
