January 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3886) Document the usage of <web-identity-filter disabled="true"> to disable identity managment

by Denis Forveille (JIRA)

Document the usage of <web-identity-filter disabled="true"> to disable identity managment ----------------------------------------------------------------------------------------- Key: JBSEAM-3886 URL: https://jira.jboss.org/jira/browse/JBSEAM-3886 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.1.1.GA Reporter: Denis Forveille Priority: Minor Document the usage of <web-identity-filter disabled="true"> to disable identity managment in seam v2.1 as stated in jira JBSEAM-3629 Maybe this should be included in section 15.2 (Security/Disabling security) ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3890) Update the samples to user "credentials" instead of "identity"

by Denis Forveille (JIRA)

Update the samples to user "credentials" instead of "identity" -------------------------------------------------------------- Key: JBSEAM-3890 URL: https://jira.jboss.org/jira/browse/JBSEAM-3890 Project: Seam Issue Type: Bug Components: Documentation Issues, Security Affects Versions: 2.1.1.GA Reporter: Denis Forveille Priority: Minor In the security chapters, section 15.3.2 and 15.3.3, the code snippets use the "Credentials" class to store the username and the password of the user that is performing a login. The samples still use the "old" (?) way, ie use the identity class to store this data, at leat for the "blog", "booking", "dvdstore", etc... It seems that not one sample use the "Cedentials" class -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3738) Maven example for Seam

by Anthony Whitford (JIRA)

Maven example for Seam ---------------------- Key: JBSEAM-3738 URL: https://jira.jboss.org/jira/browse/JBSEAM-3738 Project: Seam Issue Type: Feature Request Components: Examples Affects Versions: 2.1.0.SP1 Reporter: Anthony Whitford In absence of a Maven Archetype for Seam, please add a Maven example project for Seam. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3606) Chatroom example does not work on Windows

by Jozef Hartinger (JIRA)

Chatroom example does not work on Windows ----------------------------------------- Key: JBSEAM-3606 URL: https://jira.jboss.org/jira/browse/JBSEAM-3606 Project: Seam Issue Type: Bug Components: Examples, Remoting Environment: JDK 5 JBoss AS 4.2.3 Windows XP Professional Reporter: Jozef Hartinger Fix For: 2.1.0.GA I connect from two different browser instances (IE and Firefox 3). Connection works fine and I can see the other user logged in but when I send a message it is not displayed in the other browser. All the sent messages are present in server log. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

5
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-728) Support "outside" authentication

by Gavin King (JIRA)

Support "outside" authentication -------------------------------- Key: JBSEAM-728 URL: http://jira.jboss.com/jira/browse/JBSEAM-728 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.2.0.BETA1 If the container has already authenticated the user outside of Seam, we should be able to still use Seam authorization. -- 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

12 years, 10 months

7
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2550) <s:fileUpload and immediate attribute

by David THIBAU (JIRA)

<s:fileUpload and immediate attribute ------------------------------------- Key: JBSEAM-2550 URL: http://jira.jboss.com/jira/browse/JBSEAM-2550 Project: JBoss Seam Issue Type: Feature Request Components: JSF Controls Affects Versions: 2.0.0.GA Environment: All OS, JBoss 4.2.1, JSF RI 1.2 Reporter: David THIBAU s:fileUpload doesn't support immediate="true" -- 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

12 years, 10 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2911) GWT-RPC fails with java.lang.SecurityException

by Rainer Schuster (JIRA)

GWT-RPC fails with java.lang.SecurityException ---------------------------------------------- Key: JBSEAM-2911 URL: http://jira.jboss.com/jira/browse/JBSEAM-2911 Project: Seam Issue Type: Bug Components: GWT, Remoting Affects Versions: 2.1.0.A1, 2.0.2.CR1, 2.0.1.GA, 2.0.1.CR2, 2.0.1.CR1, 2.0.0.GA, 2.0.0.CR3, 2.0.0.CR2, 2.0.0.CR1, 2.0.0.BETA1 Environment: WinXP Pro SP 2, Maven 2.0.9, GWT 1.5 Milestone 2, Seam 2.1 Revision 7916 Reporter: Rainer Schuster After http://jira.jboss.org/jira/browse/JBSEAM-2880 was fixed a new problem appeared: 2008-04-13 16:19:14,839 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/ASDF]] Exception while dispatching incoming RPC call java.lang.SecurityException: Unable to access a service method called [myservice] on class [com.myproject.asdf.server.MyServiceX] without the @WebRemote attribute. This may be a hack attempt, or someone simply neglected to use the @WebRemote attribute to indicate a method as remotely accessible. at org.jboss.seam.remoting.gwt.GWTToSeamAdapter.getMethod(GWTToSeamAdapter.java:128) at org.jboss.seam.remoting.gwt.GWTToSeamAdapter.callWebRemoteMethod(GWTToSeamAdapter.java:98) at org.jboss.seam.remoting.gwt.GWTService.processCall(GWTService.java:246) at org.jboss.seam.remoting.gwt.GWTService$1.process(GWTService.java:146) at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53) at org.jboss.seam.remoting.gwt.GWTService.getResource(GWTService.java:130) at org.jboss.seam.servlet.SeamResourceServlet.doGet(SeamResourceServlet.java:75) at org.jboss.seam.servlet.SeamResourceServlet.doPost(SeamResourceServlet.java:92) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:73) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) This error seams to occur independent of the content-type problem (http://jira.jboss.org/jira/browse/JBSEAM-2880), because it also occurs with older versions of GWT. -- 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

12 years, 10 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1250) Socket write error with Seam JMS Remoting

by Scott McNab (JIRA)

Socket write error with Seam JMS Remoting ----------------------------------------- Key: JBSEAM-1250 URL: http://jira.jboss.com/jira/browse/JBSEAM-1250 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 1.2.1.GA, 1.2.0.GA Environment: WindowsXP, JBossAS 4.2.0.CR1 Reporter: Scott McNab Assigned To: Shane Bryzak Full details are given in the corresponding forum topic, however a summary is: * Client-side javascript subscribes to a JMS topic by calling Seam.Remoting.subscribe(). * The client then navigates to a new page. * Approximately 30 seconds later, a SocketException (socket write error) occurs on the server within Seam Remoting (presumably because my Seam poll-timeout is set to 30 seconds). This occurs consistently with JBoss running under Windows, but does not seem to occur when the server is run on Linux. It is also not affected by browser type (i.e. it happens when using Firefox or IE). This bug did not occur previously when the same code was running with Seam 1.0.1.GA. -- 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

12 years, 10 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2935) Seam Remoting/GWT1.5M2, change to 'Long' behavior (impacts Date?)

by darren hartford (JIRA)

Seam Remoting/GWT1.5M2, change to 'Long' behavior (impacts Date?) ----------------------------------------------------------------- Key: JBSEAM-2935 URL: http://jira.jboss.com/jira/browse/JBSEAM-2935 Project: Seam Issue Type: Bug Components: GWT Affects Versions: 2.1.x Reporter: darren hartford From: 1.5M2 announcement post -- http://groups.google.com/group/Google-Web-Toolkit-Contributors/browse_thr... " - "long" emulation. The Java language defines "long" types to be 64-bit signed integers, whereas JavaScript only supports 64-bit floating point numbers, which cannot accurately represent the same whole-number range as a true "long" type. GWT 1.5 M2 transparently emulates long types properly to more faithfully maintain Java semantics in web mode. " Although this is from GWT 1.5M2, the risk/return of them changing this is unlikely. It appears that this also impacts Dates. This has been tested against Seam 2.1-snapshot (4/25/2008) and GWT 1.5M2 on jboss 4.2. Other datatypes are working correctly, Long and Dates are not. This seems to only impact the RPC mechanism. symptoms (on client side) for Long. Same symptoms for java.util.Date: ============== getLong had a failure: com.google.gwt.core.client.JavaScriptException: (TypeError): orig has no properties message: orig has no properties fileName: http://dhartford:8080/sample-ejb3-gwt-client/com.domain.app.gwt.SeamEjbRe... lineNumber: 7172 stack: java_lang_Long_parseLong__Ljava_lang_String_2I(undefined,16)@http://dhartford:8080/sample-ejb3-gwt-client/com.domain.app.gwt.SeamEjbRemote/0838C54E584391EEA8D10F2AD23CB3D5.cache.html:7172 com_google_gwt_user_client_rpc_core_java_lang_Long_1CustomFieldSerializer_instantiate__Lcom_google_gwt_user_client_rpc_SerializationStreamReader_2([object Object])@http://dhartford:8080/sample-ejb3-gwt-client/com.domain.app.gwt.SeamEjbRemote/0838C54E584391EEA8D10F2AD23CB3D5.cache.html:4258 com_domain_app_gwt_client_SeamGwtStandardDataService_1TypeSerializer_instantiate__Lcom_google_gwt_user_client_rpc_SerializationStreamReader_2Ljava_lang_String_2([object Object],"java.lang.Long/4227064769")@http://dhartford:8080/sample-ejb3-gwt-client/com.domain.app.gwt.SeamEjbRemote/0838C54E584391EEA8D10F2AD23CB3D5.cache.html:2102 -- 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

12 years, 10 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-729) support container authorization

by Gavin King (JIRA)

support container authorization ------------------------------- Key: JBSEAM-729 URL: http://jira.jboss.com/jira/browse/JBSEAM-729 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.2.0.BETA1 We should re-authenticate on each request, so that you can use container authorization as well as Seam authorization, -- 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

12 years, 10 months

8
19
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2009