Jean Deruelle wrote:
Hey Jason, I'm taking a look at the Web Subsystem and we actually need to extend it not create a new one since we need to tightly intergate with Web Applications to have SIP/HTTP Convergence so that applications can share data between their HTTP or SIP Sessions in the same meta session called SipApplicationSession.
Do you think it would be possible to have a new xml tag in the web subsytem xsd that would define the Service implementation class to use for JBossWeb, if not present just use the default StandardService if provided use the classname to create the instance ? So that it doesn't change anything in term of usability for the end user and still allow for flexibility/extension in term of configuration ?
Jean, it would be preferable to have a hook (internally) in the web subsystem which is used by a new/separate SIP subsystem in order to reconfigure the session type. This way the user does not have to put some class name or something into the web config; instead they just add a SIP subsystem and everything just works. Reiterating, we will probably never allow a name of an internal implementation class to ever appear in the configuration under normal conditions.