hi. can you tell me the detail about domain binding on the remote host?
if i develop an application named app1.war,should the client visit my web site by URL http://my domain/app1/ but that's no reasonable.
another question: suppose i have a application named app1.war , this is the web site system. now i want to add a bbs or blog module application to my web site. shall i package the module application to a bbs.war and deploy on the remote host?and what about the domain binding?
The host and domain names are defined for the machine as part of its network definition. You can only control them if you control the network. Additionally, the domain name has to be registered with one of the world's "telephone book" (DNS) if you want anyone anywhere on the Internet to be able to talk to that server by name.
The individual applications on a web application server are defined in terms of virtual hosts and contexts. Virtual hosts are simply alternate host names, so they also must be published in DNS. Some examples are "www.javaranch.com" and "saloon.javaranch.com", assuming that both the Javaranch website and the message board applications both reside on the same machine. There's also a reverse mechanism where multiple machines serve the same hostname, used when a cluster of servers is needed, but I'll leave that information for another day.
The actual webapp is published under a web application context URL. This is simply the part of the URL that is looked at to see where a given request will be routed. In this way, URLs going to http://www.some-server.com/accounting/ can be routed to the accounting app and http://www.some-server.com/registration can be routed to the user registration app (I made these apps up - don't expect to actually click on the links and find anything).
The application context named "/" is the default context, if one has been defined. So "http://www.javaranch.com/acounting" might be routed to the default context (since it's not spelled right), where the default context app would look in its web.xml file (assuming a J2EE default app) and attempt to resolve a relative URL of '/acounting'. The web.xml pattern matchers don't include the host, domain or context URL parts of the incoming URL when they attempt to resolve what part of an app will handle a request.
When you publish a webapp, you bind it to the application context. By default, a lot of appservers will assign a context name that's the same as your WAR name if you don't specify an explicit context, but that's not true for all appservers.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Aug 30, 2007
thanks Tim.please bear in mind i have no experience about it. but can the domain bind to a context (such as domain1.com to 220.127.116.11:80/app1) ? and the browser can visit domain1.com to visit the app?
and if i deploy another web site named app2.i bind domain2.org to 18.104.22.168:/80/app2.