July 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-4810) Migrate Seam build system to full maven

by Marek Novotny (JIRA)

Migrate Seam build system to full maven --------------------------------------- Key: JBSEAM-4810 URL: https://issues.jboss.org/browse/JBSEAM-4810 Project: Seam 2 Issue Type: Feature Request Components: Build Reporter: Marek Novotny Assignee: Marek Novotny Priority: Blocker Fix For: 2.3.0.ALPHA Migrate Seam build system and modules to Maven. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-4823) Migrate jsUnit usage to maven jasmine plugin

by Marek Novotny (JIRA)

Migrate jsUnit usage to maven jasmine plugin -------------------------------------------- Key: JBSEAM-4823 URL: https://issues.jboss.org/browse/JBSEAM-4823 Project: Seam 2 Issue Type: Task Components: Remoting Reporter: Marek Novotny Assignee: Marek Novotny Fix For: 2.3.0.ALPHA There is succesor of jsUnit framework which can be invoked by maven. jsUnit in current state doesn't work and more jsUnit is not any more maintained. Migration to Jasmine should be straight forward. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
2
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

14 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (JBSEAM-4556) Create 6.0.0.Alpha1 Release of jboss-seam-int AS project

by John Bailey (JIRA)

Create 6.0.0.Alpha1 Release of jboss-seam-int AS project -------------------------------------------------------- Key: JBSEAM-4556 URL: https://jira.jboss.org/jira/browse/JBSEAM-4556 Project: Seam Issue Type: Release Reporter: John Bailey Assignee: John Bailey Create a 6.0.0.Alpha1 release of the jboss-seam-int project. -- 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

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-4820) CLONE - Seam businessProcess and persistenceContexts are leaked when conversationTimeout occurs

by Keiichi Sato (JIRA)

CLONE - Seam businessProcess and persistenceContexts are leaked when conversationTimeout occurs ----------------------------------------------------------------------------------------------- Key: JBSEAM-4820 URL: https://issues.jboss.org/browse/JBSEAM-4820 Project: Seam 2 Issue Type: Bug Components: BPM, Core Affects Versions: 2.2.2.Final Reporter: Keiichi Sato Attachments: ConversationTimeoutWorkaround.java The following two objects are leaked, when conversationTimeout occurs. org.jboss.seam.bpm.businessProcess org.jboss.seam.persistence.persistenceContexts This is not a permanent leak, because if associated HTTP session is invalidated, the above objects are removed. The object size of the leaked objects are very small, so this is not a serious memory leak issue. This can be easily reproduced with the seam numberguess application. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-4506) Seam GWTService is incompatible with GWT 2.0

by Szaby GrÃ¼nwald (JIRA)

Seam GWTService is incompatible with GWT 2.0 -------------------------------------------- Key: JBSEAM-4506 URL: https://jira.jboss.org/jira/browse/JBSEAM-4506 Project: Seam Issue Type: Bug Components: GWT, Remoting Affects Versions: 2.2.0.GA Environment: Ubuntu 9.10 x64, Java 6, Seam 2.2.0 GA, GWT 2.0, Firefox 3.5.5 Reporter: Szaby GrÃ¼nwald The example application at examples/remoting/gwt throws IncompatibleRemoteServiceException There seem to be a hint here: http://seamframework.org/Community/GWTTrunkWithSeamRemoting ERROR An IncompatibleRemoteServiceException was thrown while processing this call. com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException: Parameter 0 of is of an unknown type 'java.lang.String/2004016611' at org.jboss.seam.remoting.gwt.GWTService.RPC_decodeRequest(GWTService.java:426) at org.jboss.seam.remoting.gwt.GWTService.processCall(GWTService.java:203) at org.jboss.seam.remoting.gwt.GWTService$1.process(GWTService.java:120) at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53) at org.jboss.seam.remoting.gwt.GWTService.getResource(GWTService.java:105) at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) 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.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) 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:178) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:368) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:495) 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:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at kiwi.extension.CheckSetupFilter.doFilter(CheckSetupFilter.java:111) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) 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 kiwi.servlet.FacebookUserFilter.doFilter(FacebookUserFilter.java:102) 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:182) 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:619) Caused by: java.lang.ClassNotFoundException: java.lang.String/2004016611 at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at org.jboss.seam.remoting.gwt.GWTService.RPC_getClassFromSerializedName(GWTService.java:479) at org.jboss.seam.remoting.gwt.GWTService.RPC_decodeRequest(GWTService.java:422) ... 50 more -- 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

14 years, 8 months

7
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4350) Enable/Disable a Role

by Sand Lee (JIRA)

Enable/Disable a Role --------------------- Key: JBSEAM-4350 URL: https://jira.jboss.org/jira/browse/JBSEAM-4350 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.2.0.GA Reporter: Sand Lee Enable/Disable a Role Is it possible to disable/enable a role by annotation configuration in the same way like @RoleConditional is configured. Adding a Boolean property in the role class and annote it with @RoleEnabled. This property holds the status of the role (active/inactive). If a role is disabled it should not be returned when JpaIdentityStore.listRoles() or JpaIdentityStore.getImpliedRoles() is called. that also requires a new method in getJpaIdentityStore().setRoleStatus(String roleName Boolean status) to set the Role status. If this Method is called, all permissions which have this role as recipient should be deactivated by setting a flag in each permission object. So that JpaPermissionStore.listPermissions() only returns permissions that not belongs to deactivated roles. It also raises an RoleDisabled event and the identity objects (from already loggedin users) are listen to this event and then it checks if the identity has this role. If an already loggedin user has this role it will be removed from identity object. Is it possible to include a mechanism like this? -- 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

14 years, 8 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4260) Drools5 API

by Tihomir Surdilovic (JIRA)

Drools5 API ----------- Key: JBSEAM-4260 URL: https://jira.jboss.org/jira/browse/JBSEAM-4260 Project: Seam Issue Type: Feature Request Reporter: Tihomir Surdilovic Seam components to use Drools5 API. -- 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

14 years, 8 months

3
5
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

14 years, 8 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

14 years, 8 months

7
15
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2011