[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-423) seam-poker: Type cannot be determined for component [Component(playerAction)]. Please ensure that it has a local interface.

[Shane Bryzak (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-423?page=all ]

Shane Bryzak closed JBSEAM-423.
-------------------------------

    Resolution: Rejected

This example is under construction.

> seam-poker: Type cannot be determined for component [Component(playerAction)]. Please ensure that it has a local interface.
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-423
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-423
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Examples
>    Affects Versions: 1.1.0.BETA1
>            Reporter: jarkko Lietolahti
>
> 56160 00:11:40,539 ERROR [STDERR] 16.10.2006 21:11:40 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/home/jarkko/jboss/jboss-4.0.5.CR1/server/default/tmp/deploy/tmp60979seam-poker.ear-contents/seam-poker-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
> 256610 00:11:40,989 ERROR [SeamServletFilter] Error
> java.lang.RuntimeException: Type cannot be determined for component [Component(playerAction)]. Please ensure that it has a local interface.
> 	at org.jboss.seam.remoting.InterfaceGenerator.appendComponentSource(InterfaceGenerator.java:283)
> 	at org.jboss.seam.remoting.InterfaceGenerator.generateComponentInterface(InterfaceGenerator.java:130)
> 	at org.jboss.seam.remoting.InterfaceGenerator.handle(InterfaceGenerator.java:100)
> 	at org.jboss.seam.remoting.SeamRemotingServlet.doPost(SeamRemotingServlet.java:76)
> 	at org.jboss.seam.remoting.SeamRemotingServlet.doGet(SeamRemotingServlet.java:62)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> 	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
> 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
> 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
> 	at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:153)
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
> 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
> 	at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
> 	at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
> 	at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
> 	at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira