You've gotten it wrong. You don't find out the server name is from the application, you tell the the application what server name you want to use. In a generic case, it's impossible to know what the external server name is and there are almost always multiple aliases. Basically, you either configure the name in your container's webapp deployment description, you hardcode it in the appmodule or you provide it to the application as a parameter (environment variable, configuration file, etc.).
Kalle On Tue, Feb 14, 2012 at 11:29 AM, iberck <[email protected]> wrote: > I'm sorry > Hi mailing list ;) > > Where is the best plance to wait the first request in the AppModule ? > Sorry, I'm a newbie in Tap > > Thank you for your response Thiago > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Get-Server-Name-in-AppModule-tp5483475p5483541.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
