May 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-4674) Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT

by Gaël Beaudoin (JIRA)

Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT --------------------------------------------------------------------- Key: JBSEAM-4674 URL: https://jira.jboss.org/browse/JBSEAM-4674 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 2.2.1.CR1 Environment: JBoss 4.2.3 Seam 2.2.1-SNAPSHOT Reporter: Gaël Beaudoin Securing resources like this : http://docs.jboss.org/seam/2.2.1.CR1/reference/en-US/html_single/#d0e22406 It works fine with the released seam 2.2.0 (RESTeasy 1.1x) but not with seam 2.2.1-SNAPSHOT (from a few days ago) (RESTeasy 2.0-beta). The authentication works, debugging the application I can see I am logged in, but then seam return a 401 http code, unauthorized. Switch to seam 2.2.0 without changing anything else makes the secured resource work as expected. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (JBSEAM-4551) iPhone does not show existed PDF attachment in the message

by Oleg Golitsin (JIRA)

iPhone does not show existed PDF attachment in the message ---------------------------------------------------------- Key: JBSEAM-4551 URL: https://jira.jboss.org/jira/browse/JBSEAM-4551 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.1.1.GA Reporter: Oleg Golitsin Assignee: Pete Muir Here is the simple test example with a pdf attachment: <m:message xmlns="http://www.w3.org/1999/xhtml" xmlns:m="http://jboss.com/products/seam/mail" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:s="http://jboss.com/products/seam/taglib" xmlns:p="http://jboss.com/products/seam/pdf" xmlns:c="http://java.sun.com/jstl/core" charset="UTF-8"> <m:header name="X-Sent-From" value="JBoss Seam"/> <m:from name="noreply" address="noreply(a)test.com"/> <m:to address="email(a)test.com"/> <m:subject><h:outputText value="Test msg" /></m:subject> <m:attachment fileName="tiny.pdf"> <p:document> A very tiny PDF </p:document> </m:attachment> <m:body> <p>Test</p> </m:body> </m:message> iPhone shows the paper clip for such message in the list but when the message is open - the attachment is hidden without any way to view it. -- 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

13 years, 5 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4456) Support for reloading classpath security.drl

by Miloslav Vlach (JIRA)

Support for reloading classpath security.drl -------------------------------------------- Key: JBSEAM-4456 URL: https://jira.jboss.org/jira/browse/JBSEAM-4456 Project: Seam Issue Type: Feature Request Components: Drools Affects Versions: 2.2.0.GA Environment: Drools without BRMS Reporter: Miloslav Vlach Attachments: RuleAgent.java.patch.zip I need to enable reloading *.drl files located in classpath. The attribute files load only files typed in absolute path form. <security:rule-based-permission-resolver security-rules="#{ruleAgent}" /> <security:identity authenticate-method="#{authenticator.authenticate}" remember-me="true" /> <drools:rule-agent name="ruleAgent" files="classpath:///security.drl classpath:///security2.drl" local-cache-dir="/tmp/" poll="5"/> <drools:managed-working-memory name="policyPricingWorkingMemory" auto-create="true" rule-base="#{ruleAgent}" /> More info at http://www.bpsolutions.cz/blog/-/blogs/reloadable-drools-jboss-rules-secu... -- 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

13 years, 5 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4326) Allow to specify a directory with rule resources to Seam RuleBase

by Tihomir Surdilovic (JIRA)

Allow to specify a directory with rule resources to Seam RuleBase ----------------------------------------------------------------- Key: JBSEAM-4326 URL: https://jira.jboss.org/jira/browse/JBSEAM-4326 Project: Seam Issue Type: Feature Request Affects Versions: 2.2.0.CR1 Reporter: Tihomir Surdilovic Currently org.jboss.seam.drools.RuleBase allows to add a list of rule resources individually, for example: -- 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

13 years, 5 months

4
9
0 / 0

[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

13 years, 5 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

13 years, 5 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

13 years, 5 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

13 years, 5 months

7
6
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

13 years, 5 months

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

13 years, 5 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2011