Odd question: Has any consideration/planning been made/done for including SIP Container/SIP Servlet (JSR 116) testing within Cactus?
SIP Servlets are based upon the javax.servlet, and pull many ideas from javax.servlet.http. However, there's a big gap between HTTP and SIP Servlets. One major issue is that SIP contains asynchronous requests/responses. I've seen that Cactus' ServletTestCase makes heavy HTTPServlet assumptions instead of targetting GenericServlet and providing a HTTPServletTestCase. This would allow for a hypothetical SIPServletTestCase to extend ServletTestCase. What's a conservative time estimate for what it would take to move the HTTP-specific pieces from ServletTestCase into a new HTTPServletTestCase? Please note that this isn't a complaint about Cactus' implementation, just an attempt to size how to tweak it to allow for non-HTTP Servlets. Thanks, Rhys __________________________________ Rhys Ulerich Telecommunications Solutions Software Development Email: [EMAIL PROTECTED] Office: 512-838-1428 IBM Software Group - Austin, TX --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
