January 2012 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAM-96) identity.hasRole and identity.addRole do not seem to be interacting with JpaStore

by Bill Elliot (JIRA)

identity.hasRole and identity.addRole do not seem to be interacting with JpaStore --------------------------------------------------------------------------------- Key: SEAM-96 URL: https://issues.jboss.org/browse/SEAM-96 Project: Seam 3 Distribution Issue Type: Bug Affects Versions: 3.0.0.Final Environment: Windows 7, MySQL 5.1, AS6 Reporter: Bill Elliot I am trying to use Roles with Seam Security. I have added the following to my MySQL DB. insert into IdentityRoleName(id, name) values (1, 'admin'); insert into IdentityRoleName(id, name) values (2, 'manager'); insert into IdentityObjectType(id, name) values (1, 'USER'); insert into IdentityObjectType(id, name) values (2, 'GROUP'); insert into IdentityObject (id, name, identity_object_type_id) values (1, 'shane', 1); insert into IdentityObject (id, name, identity_object_type_id) values (2, 'demo', 1); insert into IdentityObject (id, name, identity_object_type_id) values (3, 'ROOT', 2); insert into IdentityObject (id, name, identity_object_type_id) values (4, 'USERS', 2); insert into IdentityObjectCredentialType (id, name) values (1, 'PASSWORD'); insert into IdentityObjectCredential (id, identity_object_id, credential_type_id, value) values (1, 1, 1, 'password'); insert into IdentityObjectCredential (id, identity_object_id, credential_type_id, value) values (2, 2, 1, 'demo'); insert into IdentityObjectRelationshipType (id, name) values (1, 'JBOSS_IDENTITY_MEMBERSHIP'); insert into IdentityObjectRelationshipType (id, name) values (2, 'JBOSS_IDENTITY_ROLE'); insert into IdentityObjectRelationship (id, name, relationship_type_id, from_identity_id, to_identity_id) values (1, 'admin', 2, 3, 2); insert into IdentityObjectRelationship (id, name, relationship_type_id, from_identity_id, to_identity_id) values (2, 'admin', 2, 4, 2); And my seam-beans.xml has the following: <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:s="urn:java:ee" xmlns:drools="urn:java:org.jboss.seam.drools:org.jboss.seam.drools.config" xmlns:auth="urn:java:org.jboss.seam.security" xmlns:security="urn:java:org.jboss.seam.security.permission" xmlns:plidm="urn:java:org.jboss.seam.security.management.picketlink" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://jboss.org/schema/cdi/beans_1_0.xsd"> <auth:Identity> <s:modifies /> <auth:authenticatorName>NGOAuthenticator</auth:authenticatorName> </auth:Identity> <security:JpaPermissionStore> <s:replaces /> <security:identityPermissionClass>com.ngo.domain.IdentityPermission</security:identityPermissionClass> </security:JpaPermissionStore> <plidm:JpaIdentityStoreConfiguration> <s:replaces /> <plidm:identityClass>com.ngo.domain.IdentityObject</plidm:identityClass> <plidm:credentialClass>com.ngo.domain.IdentityObjectCredential</plidm:credentialClass> <plidm:relationshipClass>com.ngo.domain.IdentityObjectRelationship</plidm:relationshipClass> <plidm:roleTypeClass>com.ngo.domain.IdentityRoleName</plidm:roleTypeClass> <plidm:attributeClass>com.ngo.domain.IdentityObjectAttribute</plidm:attributeClass> </plidm:JpaIdentityStoreConfiguration> </beans> When I try to execute the following "identity.getRoles()" I get no roles and therefore when I execute identity.hasRole( "admin", "ROOT", "GROUP" ) it returns false. What am I missing? I have also tried removing the relationship entries and executing identity.addRole( "admin", "ROOT", "GROUP" ) just before the hasRole and it says I now have the Role. But, the values are not added to the DB. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
6
0 / 0

[JBoss JIRA] (SOLDER-313) ServletEventBridgeFilter should support Async operations

by Cody Lerum (Created) (JIRA)

ServletEventBridgeFilter should support Async operations -------------------------------------------------------- Key: SOLDER-313 URL: https://issues.jboss.org/browse/SOLDER-313 Project: Solder Issue Type: Enhancement Components: Servlet Affects Versions: 3.1.0.Final Reporter: Cody Lerum -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] (SEAMJCR-25) Publish the 3.1.0.Final release of seam-jcr-impl

by Simon Gunzenreiner (JIRA)

Simon Gunzenreiner created SEAMJCR-25: ----------------------------------------- Summary: Publish the 3.1.0.Final release of seam-jcr-impl Key: SEAMJCR-25 URL: https://issues.jboss.org/browse/SEAMJCR-25 Project: Seam JCR Issue Type: Bug Reporter: Simon Gunzenreiner Priority: Minor Please publisth the publish the 3.1.0.Final release of seam-jcr-impl at https://repository.jboss.org/nexus/content/groups/public/org/jboss/seam/j... as documented in http://seamframework.org/Seam3/JCRModule -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
3
0 / 0

[JBoss JIRA] (SEAMSPRING-12) Support for production of multiple Spring beans of the same type (via @Named and @Qualifier)

by Marius Bogoevici (JIRA)

Marius Bogoevici created SEAMSPRING-12: ------------------------------------------ Summary: Support for production of multiple Spring beans of the same type (via @Named and @Qualifier) Key: SEAMSPRING-12 URL: https://issues.jboss.org/browse/SEAMSPRING-12 Project: Seam Spring Issue Type: Feature Request Components: Core Affects Versions: 3.1.0.Final Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 3.2.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
1
0 / 0

[JBoss JIRA] (SEAMWICKET-45) SeamWicketTester does not associate conversation context with request

by Jozef Hartinger (Created) (JIRA)

SeamWicketTester does not associate conversation context with request --------------------------------------------------------------------- Key: SEAMWICKET-45 URL: https://issues.jboss.org/browse/SEAMWICKET-45 Project: Seam for Apache Wicket Issue Type: Bug Affects Versions: 3.1.0.Beta3 Reporter: Jozef Hartinger Priority: Blocker Fix For: 3.1.0.CR1 When running org.jboss.seam.wicket.examples.numberguess.test.HomePageTest the conversation context is not associated with the request. In a non-mock environment, the request is associated by WeldListener. When using SeamWicketTester, only the request context seems to be associated with the request causing the following exception: Marked as blocker since it probably causes any testing using SeamWicketTester to fail. {noformat} java.lang.IllegalStateException: Must call associate() before calling activate() at org.jboss.weld.context.AbstractConversationContext.activate(AbstractConversationContext.java:277) at org.jboss.seam.wicket.SeamRequestCycle.onRequestTargetSet(SeamRequestCycle.java:68) at org.apache.wicket.RequestCycle$1.add(RequestCycle.java:260) at org.apache.wicket.RequestCycle$1.add(RequestCycle.java:276) at org.apache.wicket.util.collections.ArrayListStack.push(ArrayListStack.java:73) at org.apache.wicket.RequestCycle.request(RequestCycle.java:587) at org.apache.wicket.protocol.http.MockWebApplication.processRequestCycle(MockWebApplication.java:501) at org.apache.wicket.protocol.http.MockWebApplication.processRequestCycle(MockWebApplication.java:413) at org.apache.wicket.util.tester.BaseWicketTester.startPage(BaseWicketTester.java:302) at org.jboss.seam.wicket.examples.numberguess.test.HomePageTest.testRestart(HomePageTest.java:71) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:246) at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:82) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:239) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:202) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:290) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:45) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:216) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:161) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:290) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:45) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:175) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:123) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at org.junit.runner.JUnitCore.run(JUnitCore.java:136) at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:128) at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:107) at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:203) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at org.jboss.as.jmx.tcl.TcclMBeanServer.invoke(TcclMBeanServer.java:214) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427) at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1360) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) at sun.reflect.GeneratedMethodAccessor638.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

6
6
0 / 0

[JBoss JIRA] Created: (SEAMREST-49) String response not rendered by @ResponseTemplate

by Jozef Hartinger (JIRA)

String response not rendered by @ResponseTemplate ------------------------------------------------- Key: SEAMREST-49 URL: https://issues.jboss.org/browse/SEAMREST-49 Project: Seam REST Issue Type: Bug Components: Templating Affects Versions: 3.0.0.Final Reporter: Jozef Hartinger Assignee: Jozef Hartinger {code:JAVA} @Path("string") @GET @Produces("text/plain") @ResponseTemplate("/string.ftl") public String string() { return "Jozef"; } {code} won't be rendered. "Jozef" is returned instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
4
0 / 0

[JBoss JIRA] (SEAMTRANSACTION-13) @DefaultTransaction should be supported on parameters

by Cody Lerum (JIRA)

Cody Lerum created SEAMTRANSACTION-13: ----------------------------------------- Summary: @DefaultTransaction should be supported on parameters Key: SEAMTRANSACTION-13 URL: https://issues.jboss.org/browse/SEAMTRANSACTION-13 Project: Seam Transaction Issue Type: Bug Affects Versions: 3.1.0.Final Reporter: Cody Lerum Assignee: Stuart Douglas Fix For: Future -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
2
0 / 0

[JBoss JIRA] (SEAMJMS-64) Bad readme.md in testsuite

by John Ament (Created) (JIRA)

Bad readme.md in testsuite -------------------------- Key: SEAMJMS-64 URL: https://issues.jboss.org/browse/SEAMJMS-64 Project: Seam JMS Issue Type: Bug Reporter: John Ament the readme.md has the following information which is not correct #Seam Solder Test Suite ##Running the testsuite on the default container (Embedded Weld) mvn clean verify clean verify doesn't work and this isn't solder. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-4667) Using JSF 2 And Seam - conversation Id

by varun shaji (JIRA)

Using JSF 2 And Seam - conversation Id -------------------------------------- Key: JBSEAM-4667 URL: https://jira.jboss.org/browse/JBSEAM-4667 Project: Seam Issue Type: Bug Affects Versions: 2.2.1.CR1 Environment: JBoss-6.0 M2 , Seam 2.2.0 & Seam 2.2.1 CR1, JSF 2(Mojarro - 2.0.2) Reporter: varun shaji During Postback from a JSF page , the conversation id cannot be retored. The debug logs that i obtained for JSF 1.2 and JSF 2.0 are as shown for the same postback in a pageflow are as shown JSF 1.2 ******************************************************************************************************************** 06-15@23:18:50 (JbpmContextInfo.java:145) DEBUG - creating jbpm context with service factories '[]' 06-15@23:18:50 (JbpmContext.java:124) DEBUG - creating org.jbpm.JbpmContext@7b3555 06-15@23:18:50 (Pageflow.java:470) DEBUG - new pageflow instance for definition: hello 06-15@23:18:50 (GraphElement.java:170) DEBUG - event 'process-start' on 'ProcessDefinition(hello)' for 'Token(/)' 06-15@23:18:50 (JbpmContext.java:133) DEBUG - closing jbpmContext org.jbpm.JbpmContext@7b3555 ******************************************************************************************************* JSF 2.0 ********************************************************************************************** 06-15@22:38:27 (Pageflow.java:470) DEBUG - new pageflow instance for definition: hello ********************************************************************************************** I debuged and found the FacesPage from which the conversation Id is returning..Is returning null in JSF2 ..ConversationId is returning null in FacesPage returned by Seam when Using JSF2 -- 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

12 years, 11 months

3
8
0 / 0

[JBoss JIRA] (SEAMSPRING-11) NPE from CdiBeanFactoryBean.getObjectType()

by Marius Bogoevici (JIRA)

Marius Bogoevici created SEAMSPRING-11: ------------------------------------------ Summary: NPE from CdiBeanFactoryBean.getObjectType() Key: SEAMSPRING-11 URL: https://issues.jboss.org/browse/SEAMSPRING-11 Project: Seam Spring Issue Type: Bug Components: Core Affects Versions: 3.1.0.Final Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: Future When constructing the object graph, Spring invokes CdiBeanFactoryBean before injecting the lookup and bean manager. As a result, an annoying NPE is produced. The application works correctly afterwards, but the exception must be avoided. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2012