[JBoss JIRA] (WFLY-9189) Messaging queue operations are not flagged with read-only
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-9189:
---------------------------------
Summary: Messaging queue operations are not flagged with read-only
Key: WFLY-9189
URL: https://issues.jboss.org/browse/WFLY-9189
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 11.0.0.Beta1
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: 11.0.0.CR1
The operations in messaging-activemq's queue and jms-queue resources that are only listing or counting messages should be flagged as read-only to have correct metadata description.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9187) Messaging queue operations are not flagged with read-only
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-9187:
---------------------------------
Summary: Messaging queue operations are not flagged with read-only
Key: WFLY-9187
URL: https://issues.jboss.org/browse/WFLY-9187
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 11.0.0.Beta1
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: 11.0.0.CR1
The operations in messaging-activemq's queue and jms-queue resources that are only listing or counting messages should be flagged as read-only to have correct metadata description.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3148) Tests broken as part of WildFly Core 3.0.0.Beta16
by Ken Wills (JIRA)
Ken Wills created WFCORE-3148:
---------------------------------
Summary: Tests broken as part of WildFly Core 3.0.0.Beta16
Key: WFCORE-3148
URL: https://issues.jboss.org/browse/WFCORE-3148
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Ken Wills
Assignee: Ken Wills
These tests were moved to wildfly-core previously.
Tests shown here are going to be ignored or otherwise modified in order to get the core 3.0.0.Beta16 release integrated.
org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration
org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9185) NestedRemoteContextTestCase fails with security manager
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9185?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-9185:
---------------------------------
Assignee: (was: Tomaz Cerar)
> NestedRemoteContextTestCase fails with security manager
> -------------------------------------------------------
>
> Key: WFLY-9185
> URL: https://issues.jboss.org/browse/WFLY-9185
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Hynek Švábek
> Labels: security-manager
>
> NestedRemoteContextTestCase fails with security manager
> {code}
> Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed:
> JBOSS-LOCAL-USER: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/home/hsvabek/securityworkspace/VERIFICATION/2017_08_02_BEAP-7584/jboss-eap-7.1.0.ER3-src/testsuite/integration/basic/target/jbossas/standalone/tmp/auth/local8043870012544300330.challenge" "read")" in code source "(vfs:/content/ejb.ear/web.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.ejb.ear.web.war" from Service Module Loader")
> at org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:109)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:440)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:571)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:542)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:508)
> at org.jboss.remoting3.ConnectionInfo$None.getConnection(ConnectionInfo.java:83)
> at org.jboss.remoting3.ConnectionInfo.getConnection(ConnectionInfo.java:56)
> at org.jboss.remoting3.EndpointImpl.doGetConnection(EndpointImpl.java:459)
> at org.jboss.remoting3.EndpointImpl.getConnectedIdentity(EndpointImpl.java:405)
> at org.wildfly.naming.client.remote.SingleRemoteNamingProvider.lambda$new$0(SingleRemoteNamingProvider.java:82)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wildfly.naming.client.remote.SingleRemoteNamingProvider.getFuturePeerIdentity(SingleRemoteNamingProvider.java:117)
> at org.wildfly.naming.client.remote.SingleRemoteNamingProvider.getPeerIdentity(SingleRemoteNamingProvider.java:106)
> at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:65)
> ... 51 more
> Suppressed: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/home/hsvabek/securityworkspace/VERIFICATION/2017_08_02_BEAP-7584/jboss-eap-7.1.0.ER3-src/testsuite/integration/basic/target/jbossas/standalone/tmp/auth/local8043870012544300330.challenge" "read")" in code source "(vfs:/content/ejb.ear/web.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.ejb.ear.web.war" from Service Module Loader")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175)
> at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
> at org.wildfly.security.manager.WildFlySecurityManager.checkRead(WildFlySecurityManager.java:350)
> at java.io.FileInputStream.<init>(FileInputStream.java:127)
> at org.wildfly.security.sasl.localuser.LocalUserClient.evaluateMessage(LocalUserClient.java:93)
> at org.wildfly.security.sasl.util.AbstractSaslParticipant.evaluateMessage(AbstractSaslParticipant.java:180)
> at org.wildfly.security.sasl.util.AbstractSaslClient.evaluateChallenge(AbstractSaslClient.java:59)
> at org.wildfly.security.sasl.util.AbstractDelegatingSaslClient.evaluateChallenge(AbstractDelegatingSaslClient.java:54)
> at org.wildfly.security.sasl.util.PrivilegedSaslClient.lambda$evaluateChallenge$0(PrivilegedSaslClient.java:55)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wildfly.security.sasl.util.PrivilegedSaslClient.evaluateChallenge(PrivilegedSaslClient.java:55)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.lambda$handleEvent$0(ClientConnectionOpenListener.java:644)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:898)
> ... 3 more
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-5535) Create an OGM integration adapter so that OGM works better on WildFly
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-5535?page=com.atlassian.jira.plugin.... ]
Scott Marlow resolved WFLY-5535.
--------------------------------
Fix Version/s: (was: 11.0.0.CR1)
Resolution: Rejected
I think that the OGM team is working on the OGM integration adapter. At some point, when that is ready to merge into WildFly, we can reopen this or a new jira.
> Create an OGM integration adapter so that OGM works better on WildFly
> ---------------------------------------------------------------------
>
> Key: WFLY-5535
> URL: https://issues.jboss.org/browse/WFLY-5535
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Reporter: Scott Marlow
> Assignee: Scott Marlow
>
> OGM needs to use the same integration on WildFly as Hibernate ORM uses. As an implementation detail, the OGM integration will extend the ORM integration, so that OGM gets bug fixes automatically and also shows hibernate (ORM) statistics in the WildFly console.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (DROOLS-1694) Inherited kbases, across multiple modules, fails to build via the kie-maven-plugin
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1694?page=com.atlassian.jira.plugi... ]
Mario Fusco reassigned DROOLS-1694:
-----------------------------------
Assignee: Massimiliano Dessi (was: Mario Fusco)
> Inherited kbases, across multiple modules, fails to build via the kie-maven-plugin
> ----------------------------------------------------------------------------------
>
> Key: DROOLS-1694
> URL: https://issues.jboss.org/browse/DROOLS-1694
> Project: Drools
> Issue Type: Bug
> Components: decision tables
> Affects Versions: 6.3.0.Final
> Reporter: Alistair Black
> Assignee: Massimiliano Dessi
>
> I am working on a multi-module BRMS project, with each module encapsulating a set of rules forming a single knowledge base. There is a "packaging" module which inherits each of these modules in order to generate a KJAR for deployment purposes. The application then utilises this KJAR via the KieScanner/ReleaseId approach to facilitate dynamic rule loading at runtime and decoupling of application/rules.
> Having taken the above approach I have encountered an issue where the master build fails when building the "packaging" module as part of the main project build. If the module is built on it's own, then it completes without error.
> The error reported is:
> {{[ERROR] Failed to execute goal org.kie:kie-maven-plugin:6.3.0.Final:build (default-build) on project rules: Execution default-build of goal org.kie:kie-maven-plugin:6.3.0.Final:build failed: Illegal class for global. Expected [org.drools.template.parser.DefaultGenerator], found [org.drools.template.parser.DefaultGenerator]. -> [Help 1]}}
> Having liased with Maciej Swiderski he has asked me to report it as a bug.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months