Wicket is my first exposure to web server programming. I don't have the usual background in spring, hibernate, tomcat, jetty, or even maven.
The Wicket I've written is for the configuration of a distributed application. Now I need server functionality that, based on this configuration data, will communicate with clients and other servers, do scheduling, etc. Can/should this server live within my Wicket app, perhaps started by creating threads in my WebApplication's constructor or init() ?? Or should this server live in a separate process and only communicate with the configuration data store? Thanks, -troy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
