I have an .ear. Inside it is a .war. That .war has a Vaadin application
under WEB-INF/classes. The Vaadin application is marked as a @SessionScoped
bean. beans.xml is present in WEB-INF in the .war. This application has
been running fine for months with this setup, through all Glassfish builds
from about b19 onwards.
b30 now tells me this:
[#|2010-11-21T13:24:25.060-0500|WARNING|glassfish3.1|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=193;_ThreadName=http-thread-pool-8080(3);|StandardWrapperValve[LEADServlet]:
PWC1406: Servlet.service() for servlet LEADServlet threw exception
org.jboss.weld.exceptions.UnsatisfiedResolutionException: WELD-001308 Unable
to resolve any beans for Types: [class com.foo.bar.FooApplication]; Bindings:
[@javax.enterprise.inject.Default()]
at
org.jboss.weld.manager.BeanManagerImpl.getBean(BeanManagerImpl.java:779)
at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:78)
at com.foo.bar.VaadinServlet.getNewApplication(VaadinServlet.java:61)
at
com.vaadin.terminal.gwt.server.AbstractApplicationServlet.createApplication(AbstractApplicationServlet.java:940)
at
com.vaadin.terminal.gwt.server.AbstractApplicationServlet.findApplicationInstance(AbstractApplicationServlet.java:768)
at
com.vaadin.terminal.gwt.server.AbstractApplicationServlet.service(AbstractApplicationServlet.java:431)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1534)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:281)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:98)
at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:91)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:162)
at
org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:326)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:227)
at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:170)
at
com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:817)
at
com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:718)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1007)
at
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
at
com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at
com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at
com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at
com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at
com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:680)
What fundamental error have I been committing that is just now being
caught? Or what severe bug in Weld is responsible for this behavior?
Once I figure out how to work around this, I'll put together a test case
that demonstrates the problem.
Thanks,
Laird
--
[Message sent by forum member 'ljnelson']
View Post: http://forums.java.net/node/721450