From issues at jboss.org Tue May 31 12:35:00 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Tue, 31 May 2016 12:35:00 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (SEAMJCR-5) EntityListeners In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SEAMJCR-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Ament reassigned SEAMJCR-5: -------------------------------- Assignee: (was: John Ament) > EntityListeners > --------------- > > Key: SEAMJCR-5 > URL: https://issues.jboss.org/browse/SEAMJCR-5 > Project: Seam JCR > Issue Type: Feature Request > Components: CDI & Injection API > Reporter: John Ament > > We should provide JPA 2 compliant entity listeners. We should provide a PostLoad implementation that can bind Nodes to properties that contain UUIDs for node id's. These should be represented by a Seam JCR created annotation denoting that the field is actually a UUID, and it should denote the field that will receive the underlying javax.jcr.Node. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 31 12:35:00 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Tue, 31 May 2016 12:35:00 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (SEAMJCR-13) Seam Managed JCR Sessions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SEAMJCR-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Ament reassigned SEAMJCR-13: --------------------------------- Assignee: (was: John Ament) > Seam Managed JCR Sessions > ------------------------- > > Key: SEAMJCR-13 > URL: https://issues.jboss.org/browse/SEAMJCR-13 > Project: Seam JCR > Issue Type: Feature Request > Components: CDI & Injection API > Reporter: John Ament > > Similar to Seam Persistence's Seam Managed PersistenceContext & Hibernate Session, we should support JCR Sessions in the same manner. This should tie the injection of an object to be bound to a request level, or similar context, and tying in the session.save & logout methods to happen at the end of the request. > In the case of events, where they are triggered after logging out, to avoid a long loop or bad setup, developers will need to use dependent sessions if they want to modify node state as a part of an event. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 31 12:35:00 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Tue, 31 May 2016 12:35:00 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (SEAMJMS-22) Remoting support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SEAMJMS-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Ament reassigned SEAMJMS-22: --------------------------------- Assignee: (was: John Ament) > Remoting support > ---------------- > > Key: SEAMJMS-22 > URL: https://issues.jboss.org/browse/SEAMJMS-22 > Project: Seam JMS > Issue Type: Feature Request > Components: Injection > Reporter: John Ament > > Based on the spring support in Apache ActiveMQ ( http://activemq.apache.org/spring-support.html ) we should provide support for remote JMS providers. I'm proposing to have remoting basics in the main impl, with impls providing remote support for ActiveMQ and HornetQ. Remoting support should handle local configuration (in memory?) and instances running in a separate VM. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 31 12:36:00 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Tue, 31 May 2016 12:36:00 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (SEAMJMS-25) Add test cases for Glassfish 3.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SEAMJMS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Ament reassigned SEAMJMS-25: --------------------------------- Assignee: (was: John Ament) > Add test cases for Glassfish 3.1 > -------------------------------- > > Key: SEAMJMS-25 > URL: https://issues.jboss.org/browse/SEAMJMS-25 > Project: Seam JMS > Issue Type: Enhancement > Components: Injection > Reporter: John Ament > > Need to add some test cases for glassfish v3.1, based on weld 1.1.1. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 31 12:36:00 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Tue, 31 May 2016 12:36:00 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (SEAMJMS-66) Upgrade JBoss AS7 example/testsuite client script In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SEAMJMS-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Ament reassigned SEAMJMS-66: --------------------------------- Assignee: (was: John Ament) > Upgrade JBoss AS7 example/testsuite client script > ------------------------------------------------- > > Key: SEAMJMS-66 > URL: https://issues.jboss.org/browse/SEAMJMS-66 > Project: Seam JMS > Issue Type: Enhancement > Components: Test Suite > Reporter: Tomas Remes > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 31 12:36:00 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Tue, 31 May 2016 12:36:00 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (SEAMJCR-22) Seam JCR Documentation issues and comments In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SEAMJCR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Ament reassigned SEAMJCR-22: --------------------------------- Assignee: (was: John Ament) > Seam JCR Documentation issues and comments > ------------------------------------------ > > Key: SEAMJCR-22 > URL: https://issues.jboss.org/browse/SEAMJCR-22 > Project: Seam JCR > Issue Type: Bug > Affects Versions: 3.1.0.Beta3 > Reporter: Marek Schmidt > Fix For: Future > > > JCR > 1.2. Maven dependency configuration > * "Maven user-defined property" bad link, (href instead of url attribute in docbook?) > 2.1. ModeShape Integration Installation > * "Please consult the ModeShape getting stated guide for exact versions. " should link to the ModeShape guide or some place to get it. > 3.1. JackRabbit Integration Installation > * "Please review JackRabbit documentation to determine any additional dependencies. " should link to the JackRabbit documentation. > 4. Seam JCR - Event Mapping > * sections 4.1. event-mapping-intro and 4.2. event-mapping-activation are empty > * Description of any of the events missing > > 5. Seam JCR - Object Content Mapping > * It is not clear to me why the API to convert nodes to objects and vice versa is using CDI events instead of an ordinary interface, it feels a bit hacky, is there any use case for having more observers? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 31 12:36:00 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Tue, 31 May 2016 12:36:00 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (SEAMJMS-65) Ingress JMS bridging results in endless invocations of observer method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SEAMJMS-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Ament reassigned SEAMJMS-65: --------------------------------- Assignee: (was: John Ament) > Ingress JMS bridging results in endless invocations of observer method > ---------------------------------------------------------------------- > > Key: SEAMJMS-65 > URL: https://issues.jboss.org/browse/SEAMJMS-65 > Project: Seam JMS > Issue Type: Bug > Components: Event Bridging > Affects Versions: 3.1.0.CR1 > Environment: JBAS 7.1.0.Beta1b > Reporter: Thorsten Kunz > Attachments: EventGenerator.java, RoutingInterface.java, TestMessageConsumer.java > > > I have defined this interface method: > @Outbound public void routeStringToQueue(@Observes String string, @JmsDestination(jndiName = "queue/pegasusMessage") Queue queue); > @Inbound public void routeStringsFromQueue(@Observes String string, @JmsDestination(jndiName = "queue/pegasusMessage") Queue queue); > Then create this observer method: > public void inboundMessageTest(@Observes @Inbound String message) { ... } > Once a String type event is fired this is being logged: > 13:59:26,095 INFO [org.jboss.seam.jms.MessageManagerImpl] (http-localhost-127.0.0.1-8080-1) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT > 13:59:26,108 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message > 13:59:26,110 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT > 13:59:26,337 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message > 13:59:26,339 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT > 13:59:26,386 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message > 13:59:26,387 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT > 13:59:26,403 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message > 13:59:26,404 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT > 13:59:26,403 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message > 13:59:26,404 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT > [ ... and so on ... ] > It works just fine if I replace the observer method with a regular MDB for this destination. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 31 12:37:00 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Tue, 31 May 2016 12:37:00 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (SEAMSECURITY-84) identity.hasRole and identity.addRole do not seem to be interacting with JpaStore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SEAMSECURITY-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Ament reassigned SEAMSECURITY-84: -------------------------------------- Assignee: (was: John Ament) > identity.hasRole and identity.addRole do not seem to be interacting with JpaStore > --------------------------------------------------------------------------------- > > Key: SEAMSECURITY-84 > URL: https://issues.jboss.org/browse/SEAMSECURITY-84 > Project: Seam Security > 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: > > 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"> > > > NGOAuthenticator > > > > com.ngo.domain.IdentityPermission > > > > com.ngo.domain.IdentityObject > com.ngo.domain.IdentityObjectCredential > com.ngo.domain.IdentityObjectRelationship > com.ngo.domain.IdentityRoleName > com.ngo.domain.IdentityObjectAttribute > > > 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 was sent by Atlassian JIRA (v6.4.11#64026)