Comment #11 on issue 239 by mathias.bogaert: Integrate Warp-Servlet as  
com.google.inject.servlet
http://code.google.com/p/google-guice/issues/detail?id=239

Then why do I still see this error?

2009-01-21 16:28:44.142::WARN:  Failed startup of context
org.mortbay.jetty.plugin.jetty6pluginwebappcont...@594560cf{/,jar:file:/C:/Java/projects/pia
zza/trunk/java/server/target/piazza-server-1-SNAPSHOT.war!/}
javax.servlet.ServletException: Servlets must be bound as singletons.
Key[type=org.apache.shindig.gadgets.servlet.JsServlet, annotation=[none]]  
was no
t bound in singleton scope.
         at  
com.google.inject.servlet.ServletDefinition.init(ServletDefinition.java:67)
         at
com.google.inject.servlet.ManagedServletPipeline.init(ManagedServletPipeline.java:75)
         at
com.google.inject.servlet.ManagedFilterPipeline.initPipeline(ManagedFilterPipeline.java:102)
         at com.google.inject.servlet.GuiceFilter.init(GuiceFilter.java:168)
         at  
org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
         at  
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
         at  
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:620)
         at org.mortbay.jetty.servlet.Context.startContext(Context.java:

Binding it manually to the singleton scope avoids this error, but isn't too  
nice
either (bind(JsServlet.class).in(Scopes.SINGLETON);).

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"google-guice-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/google-guice-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to