December 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-982) Make SeamText parser more flexible

by Christian Bauer (JIRA)

Make SeamText parser more flexible ---------------------------------- Key: JBSEAM-982 URL: http://jira.jboss.com/jira/browse/JBSEAM-982 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer We need a more flexible seam-text.g - possibly several stages with an AST in the middle. This is needed for - generating PDF output from seam text - implementing a diff algorithm -- 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

15 years

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3939) Seam's Resteasy implementation does not support multiple applications using resteasy on same server

by John Sublette (JIRA)

Seam's Resteasy implementation does not support multiple applications using resteasy on same server --------------------------------------------------------------------------------------------------- Key: JBSEAM-3939 URL: https://jira.jboss.org/jira/browse/JBSEAM-3939 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Environment: SEAM 2.1.1.GA with seam-resteasy patch described in https://jira.jboss.org/jira/browse/JBSEAM-3449, and RestEasy 1.0.1.GA. Running 2 Resteasy applications on Tomcat server. Reporter: John Sublette Priority: Minor Seam's Resteasy implementation does not support multiple applications using resteasy on same server. Problem is with ResteasyDispatcher.onStartup() where there is a call to ResteasyProviderFactory.setInstance() that register's the provider factory. When the second application calls this, it sets the static variable - thus overwriting the first application's. I have patched it to set a custom ResteasyProviderFactory subclass based on ThreadLocalResteasyProviderFactory instead. This subclass is a STATELESS Seam object that grabs the web-app appropriate providerFactory through a Seam Component.getInstance() call (injection may have worked too). -- 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

15 years

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4167) Complete the RESTEasy integration test matrix

by Christian Bauer (JIRA)

Complete the RESTEasy integration test matrix --------------------------------------------- Key: JBSEAM-4167 URL: https://jira.jboss.org/jira/browse/JBSEAM-4167 Project: Seam Issue Type: Task Components: WS Reporter: Christian Bauer Assignee: Christian Bauer The restbay example currently only tests the bare minimum of Seam/JAX-RS/EJB component variations, this is the test matrix we need to complete. All ? should be tested, otherwise assume they don't work: {code} | EVENT | CONVERSATION | SESSION | APPLICATION | STATELESS --------------------------------------------------------------------------------------------- Plain JAX-RS Resource | OK | - | - | - | - --------------------------------------------------------------------------------------------- POJO Seam Component Resource | OK | ? | ? | ? | ? --------------------------------------------------------------------------------------------- POJO interface-annotated Component | ? | ? | ? | ? | ? --------------------------------------------------------------------------------------------- EJB Plain SLSB Resource | - | - | - | - | OK --------------------------------------------------------------------------------------------- EJB SLSB Seam Component Resource | - | - | - | - | ? --------------------------------------------------------------------------------------------- EJB SFSB Seam Component Resource | ? | ? | ? | ? | - --------------------------------------------------------------------------------------------- {code} -- 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

15 years

1
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4020) Custom RESTEasy StringConverter provider classes need special registration

by Christian Bauer (JIRA)

Custom RESTEasy StringConverter provider classes need special registration -------------------------------------------------------------------------- Key: JBSEAM-4020 URL: https://jira.jboss.org/jira/browse/JBSEAM-4020 Project: Seam Issue Type: Task Components: WS Reporter: Christian Bauer Assignee: Christian Bauer RESTEasy offers a custom StringConverter provider extension. Unlike normal providers, the SPI in RESTEasy for registration of these providers is different: if (StringConverter.class.isAssignableFrom(providerClass)) { providerFactory.addStringConverter(providerClass); } else { providerFactory.registerProvider(providerClass); } This needs to be fixed in RestEasyDispatcher.java -- 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

15 years

1
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1973) Serialization error on FullTextEntityManagerImpl

by Norman Richards (JIRA)

Serialization error on FullTextEntityManagerImpl ------------------------------------------------ Key: JBSEAM-1973 URL: http://jira.jboss.com/jira/browse/JBSEAM-1973 Project: JBoss Seam Issue Type: Bug Reporter: Norman Richards Fix For: 2.0.0.CR2 We're seeing serialization issues with hibernate search sessions: 3:59:22,080 WARN [Component] Exception calling component @Destroy method: categories java.lang.RuntimeException: org.jboss.serial.exception.SerializationException: Could not create instance of org.hibernate.search.jpa.impl.FullTextEntityManagerImpl - org.hibernate.search.jpa.impl.FullTextEntityManagerImpl See the forums posting for full stack trace. I noticed this exception today while testing on tomcat. -- 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

15 years

3
6
0 / 0

[JBoss JIRA] Created: (JBSEAM-4494) Authorization is not working when using drools based security in Seam 2.2

by Parvathy V (JIRA)

Authorization is not working when using drools based security in Seam 2.2 ------------------------------------------------------------------------- Key: JBSEAM-4494 URL: https://jira.jboss.org/jira/browse/JBSEAM-4494 Project: Seam Issue Type: Bug Components: Drools, Security Affects Versions: 2.2.0.GA Environment: Windows XP,Drools 5.0.1, Seam 2.2.0, JDK1.6, JBoss AS 5 Reporter: Parvathy V I am using Seam 2.2 with drools based security for authentication and authorization in my application. During the security check for CRUD persistence at Entity Level, I get "org.jboss.seam.security.AuthorizationException: Authorization check failed" message when accessing functionality for all the roles when the EntitySecurityListener is on. The authentication works, but authorization is not working as expected. The rule in my security.drl file is as follows: rule "Entity View" no-loop activation-group "permissions" when check: PermissionCheck( target == "entity1", action == "read" ) then check.grant(); end All other configuration such as additions in component.xml and orm.xml seemed to be correct. I used drools:rule-base & RuleBasedPermissionResolver for authorization. So I debugged using the source code of Seam 2.2. Inside RuleBasedPermissionResolver, the method hasPermission(Object target, String action) is invoked to decide whether permission should be allowed. The target passed in is an instance of the entity com.entity.Entity1, which has the seam component name "entity1". Since no role was mentioned in the security.drl, I expect the hasPermission method to return true when I try to perform a read operation on an Entity1. However, it returns false,causing the AuthorizationException to be thrown. The execution flow inside the hasPermission method is as follows: 1. The securityContext is obtained and checked for null value. It is not null. 2. The synchronized block is entered. 3. The target is an instance of Entity1. It is not an instance of String or Class. Hence it enters the first loop. 4. A new instance of PermissionCheck is created, which has the granted attribute set to false. 5. securityContext.fireAllRules() is invoked. The target which is an instance of Entity1 does not match with the Seam component name, which is a String, given in security.drl file; hence the above mentioned rule is not fired. 6. The check.isGranted() method returns false. I made a change in the first if construct of hasPermission method as follows, similar to the code in the second if construct. After this, my application's security works just fine: public boolean hasPermission(Object target, String action) { ....................... ....................... ....................... synchronized( securityContext ) { if (!(target instanceof String) && !(target instanceof Class)) { //commented out the existing one line of code below //handles.add( securityContext.insert(target) ); //added the following two lines of code String componentName = Seam.getComponentName(target.getClass()); target = componentName != null ? componentName : target.getClass().getName(); } else if (target instanceof Class) { ....................... ....................... ....................... } ....................... ....................... ....................... } return check.isGranted(); } I would like to know whether the above is a bug in the framework, or whether my target is supposed to enter this method as a String or an instance of Class. Alternately, should I change the way the rule is defined in security.drl? -- 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

15 years, 1 month

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2009