April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4417) permissions for security roles are not redefined by jboss-ejb3.xml

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/AS7-4417?page=com.atlassian.jira.plugin.s... ] Jason Greene reassigned AS7-4417: --------------------------------- Assignee: John Bailey (was: Stuart Douglas) > permissions for security roles are not redefined by jboss-ejb3.xml > ------------------------------------------------------------------ > > Key: AS7-4417 > URL: https://issues.jboss.org/browse/AS7-4417 > Project: Application Server 7 > Issue Type: Bug > Reporter: Radim Hatlapatka > Assignee: John Bailey > Labels: descriptor, security > Fix For: 7.1.2.Final-redhat1 > > > When I have defined permissions using security roles in ejb-jar.xml (ejb-spec) for certain methods and if I define them differently in jboss-ejb3.xml (jboss-spec) the permissions remain as their are defined in ejb-jar.xml. But I would expect that ejb-spec will redefine the permissions (because merging is not possible). > For details see written tests here: https://github.com/rhatlapa/jboss-as/commit/62adba59b288a53672a6b08c8a710... -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3457) Marshalling error: InvalidClassException on MVELDialectRuntimeData when getting changeset from guvnor.

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBRULES-3457: ----------------------------------------- Summary: Marshalling error: InvalidClassException on MVELDialectRuntimeData when getting changeset from guvnor. Key: JBRULES-3457 URL: https://issues.jboss.org/browse/JBRULES-3457 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Mark Proctor {code} 2012-04-12 16:32:26,956:info] KnowledgeAgent applying ChangeSet [2012-04-12 16:32:26,973:debug] KnowledgeAgent notifier subscribing to resource=[UrlResource path='http://127.0.0.1:8888/org.drools.guvnor.Guvnor/package/mortgages/LATEST'] [2012-04-12 16:32:26,973:debug] ResourceChangeNotification subscribing listener=org.drools.agent.impl.KnowledgeAgentImpl@1de9ac4 to resource=[UrlResource path='http://127.0.0.1:8888/org.drools.guvnor.Guvnor/package/mortgages/LATEST'] [2012-04-12 16:32:26,973:debug] ResourceChangeScanner subcribing notifier=org.drools.io.impl.ResourceChangeNotifierImpl@182bcde to resource=[UrlResource path='http://127.0.0.1:8888/org.drools.guvnor.Guvnor/package/mortgages/LATEST'] [2012-04-12 16:32:26,973:debug] KnowledgeAgent rebuilding KnowledgeBase using ChangeSet [2012-04-12 16:32:27,157:exception] java.lang.RuntimeException: KnowledgeAgent exception while trying to deserialize KnowledgeDefinitionsPackage at org.drools.agent.impl.KnowledgeAgentImpl.createPackageFromResource(KnowledgeAgentImpl.java:761) at org.drools.agent.impl.KnowledgeAgentImpl.addResourcesToKnowledgeBase(KnowledgeAgentImpl.java:1020) at org.drools.agent.impl.KnowledgeAgentImpl.rebuildResources(KnowledgeAgentImpl.java:803) at org.drools.agent.impl.KnowledgeAgentImpl.buildKnowledgeBase(KnowledgeAgentImpl.java:672) at org.drools.agent.impl.KnowledgeAgentImpl.applyChangeSet(KnowledgeAgentImpl.java:203) at org.drools.agent.impl.KnowledgeAgentImpl.applyChangeSet(KnowledgeAgentImpl.java:182) at org.drools.integrationtests.BrmsClient.applyChangeSet(BrmsClient.java:87) at org.drools.integrationtests.BrmsClient.main(BrmsClient.java:76) 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.intellij.rt.execution.application.AppMain.main(AppMain.java:120) Caused by: java.io.InvalidClassException: org.drools.rule.MVELDialectRuntimeData; local class incompatible: stream classdesc serialVersionUID = 8808844570772337501, local class serialVersionUID = -64624826351992706 at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:562) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1582) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1495) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1731) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at java.util.HashMap.readObject(HashMap.java:1030) 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 java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1848) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at org.drools.rule.DialectRuntimeRegistry.readExternal(DialectRuntimeRegistry.java:59) at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1791) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1750) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at org.drools.rule.Package.readExternal(Package.java:208) at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1791) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1750) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at org.drools.core.util.DroolsStreamUtils.streamIn(DroolsStreamUtils.java:205) at org.drools.core.util.DroolsStreamUtils.streamIn(DroolsStreamUtils.java:174) at org.drools.agent.impl.KnowledgeAgentImpl.createPackageFromResource(KnowledgeAgentImpl.java:747) ... 12 more {code} -- 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

14 years, 2 months

1
5
0 / 0

[JBoss JIRA] (AS7-4434) CLONE - It's impossible to add more than 1 custom workmanager to JCA subsystem

by Vladimir Rastseluev (JIRA)

[ https://issues.jboss.org/browse/AS7-4434?page=com.atlassian.jira.plugin.s... ] Vladimir Rastseluev commented on AS7-4434: ------------------------------------------ Test case added. See org.jboss.as.connector.subsystems.jca.ComplexJcaSubsystemTestCase.java in /connector directory. > CLONE - It's impossible to add more than 1 custom workmanager to JCA subsystem > ------------------------------------------------------------------------------ > > Key: AS7-4434 > URL: https://issues.jboss.org/browse/AS7-4434 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, JCA > Affects Versions: 7.1.1.Final > Reporter: Vladimir Rastseluev > Assignee: Brian Stansberry > Fix For: 7.1.2.Final-redhat1 > > > 09:45:35,526 ERROR [org.jboss.as.server] JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.server.ServerService.boot(ServerService.java:266) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_23] > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[200,13] > Message: JBAS014789: Unexpected element '{urn:jboss:domain:jca:1.1}workmanager' encountered > at org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:85) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.readElement(JcaExtension.java:311) > at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.readElement(JcaExtension.java:176) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:897) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:332) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:128) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:100) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > ... 3 more -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-2203) Add Arquillian Container support for AS 7 domain controller

by Dimitris Andreadis (JIRA)

[ https://issues.jboss.org/browse/AS7-2203?page=com.atlassian.jira.plugin.s... ] Dimitris Andreadis commented on AS7-2203: ----------------------------------------- I've just asked if this could have some priority in reviewing. > Add Arquillian Container support for AS 7 domain controller > ------------------------------------------------------------ > > Key: AS7-2203 > URL: https://issues.jboss.org/browse/AS7-2203 > Project: Application Server 7 > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 7.1.0.CR1 > Reporter: Ondrej Zizka > Assignee: Aslak Knutsen > Priority: Blocker > Labels: arq_qe_blocker > > A container for AS 7 domain controller would be very helpful for it's integration testsuite. > Such container should support: > * Attaching hosts to a domain > * Start, stop a domain with multiple hosts > * Configuration (creation) of the domain using domain config file > * Configuration (creation) of a profile using a CLI batch > * Configuration (creation) of a profile using a callback class which would handle communication with Java API > More requirements to come. -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4434) CLONE - It's impossible to add more than 1 custom workmanager to JCA subsystem

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4434?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reassigned AS7-4434: ------------------------------------- Assignee: Brian Stansberry (was: Stefano Maestri) > CLONE - It's impossible to add more than 1 custom workmanager to JCA subsystem > ------------------------------------------------------------------------------ > > Key: AS7-4434 > URL: https://issues.jboss.org/browse/AS7-4434 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, JCA > Affects Versions: 7.1.1.Final > Reporter: Vladimir Rastseluev > Assignee: Brian Stansberry > Fix For: 7.1.2.Final-redhat1 > > > 09:45:35,526 ERROR [org.jboss.as.server] JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.server.ServerService.boot(ServerService.java:266) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_23] > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[200,13] > Message: JBAS014789: Unexpected element '{urn:jboss:domain:jca:1.1}workmanager' encountered > at org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:85) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.readElement(JcaExtension.java:311) > at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.readElement(JcaExtension.java:176) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:897) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:332) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:128) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:100) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > ... 3 more -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4484) Remove <discovery-initial-wait-timeout> from connection-factory type def

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-4484: -------------------------------- Summary: Remove <discovery-initial-wait-timeout> from connection-factory type def Key: AS7-4484 URL: https://issues.jboss.org/browse/AS7-4484 Project: Application Server 7 Issue Type: Sub-task Reporter: Jeff Mesnil Assignee: Jeff Mesnil the connection-factory only needs to reference a discovery-group. It is that discovery-group element that define its initial wait timeout -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4482) synchronize jboss-as-messaging XSD with HornetQ schema

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-4482: -------------------------------- Summary: synchronize jboss-as-messaging XSD with HornetQ schema Key: AS7-4482 URL: https://issues.jboss.org/browse/AS7-4482 Project: Application Server 7 Issue Type: Sub-task Reporter: Jeff Mesnil I diffed jboss-as-messaging_1_2.xsd with hornetq-configuration.xsd + hornetq-jms.xsd (@git commit 4f2c2802c9c2acb77179f696833ba3271e86da80) and the following elements are missing: * [ ] <page-max-concurrent-io> * [ ] in <bridgeType>: min-large-message-size, check-period, connection-ttl, max-retry-interval * [ ] in <cluster-connectionType>: check-period, connection-ttl, min-large-message-size, call-timeout, retry-interval-multiplier, max-retry-interval, reconnect-attempts -- 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

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] (AS7-4483) Factorize <connection-factory> & <pooled-connection-factory> type defs

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-4483: -------------------------------- Summary: Factorize <connection-factory> & <pooled-connection-factory> type defs Key: AS7-4483 URL: https://issues.jboss.org/browse/AS7-4483 Project: Application Server 7 Issue Type: Sub-task Reporter: Jeff Mesnil Assignee: Jeff Mesnil do something similar to connector/acceptorType with a base-connection-factoryType for common element/attributes + 2 types which extend the base one with additional elements -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4246) Attribute passivate-events-on-replicate of cluster-passivation-store can't be change via drm or cli

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created AS7-4246: ------------------------------------- Summary: Attribute passivate-events-on-replicate of cluster-passivation-store can't be change via drm or cli Key: AS7-4246 URL: https://issues.jboss.org/browse/AS7-4246 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.1.Final Reporter: Ondřej Chaloupka Assignee: jaikiran pai Setting attribute passivate-events-on-replicate via drm or cli does not take affect until operation :reload is used. In case that the attribute ( <cluster-passivation-store name="infinispan" cache-container="ejb" passivate-events-on-replicate="false" />) is set directly in standalone*.xml configuration file the supposed functionality is working. The test for this could be checked on: https://github.com/ochaloup/jboss-as/blob/JBQA-5855-test-migration-passiv... -- 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

14 years, 2 months

3
4
0 / 0

[JBoss JIRA] (AS7-4477) The element 'security-domain' in jboss-app.xml is ignored

by Luis Barreiro (JIRA)

Luis Barreiro created AS7-4477: ---------------------------------- Summary: The element 'security-domain' in jboss-app.xml is ignored Key: AS7-4477 URL: https://issues.jboss.org/browse/AS7-4477 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.1.Final Reporter: Luis Barreiro Assignee: Stuart Douglas A WAR file with a secure servlet but without a security-domain defined in jboss-web.xml, defaults to 'other'. When that WAR file is deployed within a EAR that has a security-domain defined in jboss-app.xml, it is ignored and 'other' is used instead. -- 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

14 years, 2 months

3
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2012