[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.
by 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
17 years, 11 months
[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-424) stories example failes to compile
by Shane Bryzak (JIRA)
[ http://jira.jboss.com/jira/browse/JBSEAM-424?page=all ]
Shane Bryzak closed JBSEAM-424.
-------------------------------
Resolution: Rejected
This example is under construction
> stories example failes to compile
> ---------------------------------
>
> Key: JBSEAM-424
> URL: http://jira.jboss.com/jira/browse/JBSEAM-424
> Project: JBoss Seam
> Issue Type: Bug
> Components: Examples
> Affects Versions: 1.1.0.BETA1
> Environment: Seam CVS / JBoss 4.0.5.CR1 / EJB 3 RC9
> Reporter: jarkko Lietolahti
>
> Buildfile: /home/jarkko/seam-workspace/jboss-seam/examples/remoting/stories/build.xml
> init:
> [echo] Build Seam Stories Example 1.1
> [mkdir] Created dir: /home/jarkko/seam-workspace/jboss-seam/examples/remoting/stories/build/classes
> compile:
> [javac] Compiling 6 source files to /home/jarkko/seam-workspace/jboss-seam/examples/remoting/stories/build/classes
> [javac] /home/jarkko/seam-workspace/jboss-seam/examples/remoting/stories/src/stories/ProjectsBean.java:5: cannot find symbol
> [javac] symbol : class Interceptors
> [javac] location: package javax.ejb
> [javac] import javax.ejb.Interceptors;
> [javac] ^
> [javac] /home/jarkko/seam-workspace/jboss-seam/examples/remoting/stories/src/stories/StoriesBean.java:3: cannot find symbol
> [javac] symbol : class Interceptors
> [javac] location: package javax.ejb
> [javac] import javax.ejb.Interceptors;
> [javac] ^
> [javac] /home/jarkko/seam-workspace/jboss-seam/examples/remoting/stories/src/stories/ProjectsBean.java:18: cannot find symbol
> [javac] symbol: class Interceptors
> [javac] @Interceptors(SeamInterceptor.class)
> [javac] ^
> [javac] /home/jarkko/seam-workspace/jboss-seam/examples/remoting/stories/src/stories/StoriesBean.java:13: cannot find symbol
> [javac] symbol: class Interceptors
> [javac] @Interceptors(SeamInterceptor.class)
> [javac] ^
> [javac] Note: /home/jarkko/seam-workspace/jboss-seam/examples/remoting/stories/src/stories/Project.java uses unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 4 errors
> BUILD FAILED
> /home/jarkko/seam-workspace/jboss-seam/build.xml:314: Compile failed; see the compiler error output for details.
> Total time: 1 second
--
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
17 years, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-791) Restful paramameter values are not URL encoded
by John Ray (JIRA)
Restful paramameter values are not URL encoded
----------------------------------------------
Key: JBSEAM-791
URL: http://jira.jboss.com/jira/browse/JBSEAM-791
Project: JBoss Seam
Issue Type: Bug
Environment: Latest seam from CVS
Reporter: John Ray
I have an application that using restful URLs like the blog example. The problem is that the parameter values are not URL encoded. So if a user does a search for "books+records" then the url ends up being
/search.seam?searchPattern=books+records
After the redirect the plus ends up being decoded to a space and you end up searching for "books records". The correct URL should be
/search.seam?searchPattern=books%2Brecords
The problem is in org.jboss.seam.core.Manager.encodeParameters()
Line 902 - builder.append(value);
Needs to be changed to something like
try {
builder.append(URLEncoder.encode(String.valueOf(value),"UTF-8"));
}
catch (UnsupportedEncodingException e)
{
// This should never happen because we hard coded the encoding to UTF-8
throw new RuntimeException(e);
}
Line 913 - builder.append(parameterValue);
Needs to be changed to something like
try {
builder.append(URLEncoder.encode(String.valueOf(parameterValue),"UTF-8"));
}
catch (UnsupportedEncodingException e)
{
// This should never happen because we hard coded the encoding to UTF-8
throw new RuntimeException(e);
}
If I make the above 2 changes then everything works fine for me.
It also seems that the encodeConversationId() method would have a similar problem if an explicit conversation id was used that has characters that should be URL encoded.
--
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
17 years, 11 months