Hi, Has anyone tried to use Tapestry without a classic Servlet container + war setup? I am thinking of using Tapestry with Grizzly, where Tapestry IoC or Spring is used as a container that configures and instantiates Grizzly and supplies it with a light Tapestry application preferably packaged as an ordinary jar file. I have seen that Grizzly has a Servlet adapter, which for now only has a partial support for Servlet spec - is that partial support enough for Tapestry? I would even try to avoid servlets completely - what has to be done to acomplish that? Is it possible for tapestry Request/Response and other infrastructure elements to work without a full-blown Servlet implementation? -- View this message in context: http://www.nabble.com/Tapestry-and-Grizzly-tp19742313p19742313.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]
