July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9049) [GSS](7.1.0) Elements defined in 'jboss-ejb-security_1_1.xsd' must be optional

by Jörg Bäsner (JIRA)

Jörg Bäsner created WFLY-9049: --------------------------------- Summary: [GSS](7.1.0) Elements defined in 'jboss-ejb-security_1_1.xsd' must be optional Key: WFLY-9049 URL: https://issues.jboss.org/browse/WFLY-9049 Project: WildFly Issue Type: Bug Affects Versions: 11.0.0.Alpha1 Reporter: Jörg Bäsner Assignee: Jason Greene Wildfly does not validate the 'jboss-ejb3.xml' file during startup, but when trying do validate a 'jboss-ejb3.xml' file externally the following elements are mandatory, even though they aren't: * {{security-domain}} * {{run-as-principal}} * {{missing-method-permissions-deny-access}} The [jboss-ejb-security_1_1.xsd|http://www.jboss.org/schema/jbossas/jboss-ejb-...] should be changed to have these elements optional. Like: {noformat} ... <xs:element name="security-domain" type="xs:string" minOccurs="0"/> <xs:element name="run-as-principal" type="xs:string" minOccurs="0"/> <xs:element name="missing-method-permissions-deny-access" type="xs:boolean" minOccurs="0"> ... {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9047) Elements defined in 'jboss-ejb-security_1_1.xsd' must be optional

by Jörg Bäsner (JIRA)

[ https://issues.jboss.org/browse/WFLY-9047?page=com.atlassian.jira.plugin.... ] Jörg Bäsner updated WFLY-9047: ------------------------------ Steps to Reproduce: Validate the following 'jboss-ejb3.xml' file: {noformat} <?xml version="1.0" encoding="UTF-8"?> <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns:jee="http://java.sun.com/xml/ns/javaee" xmlns:s="urn:security:1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd urn:security:1.1 http://www.jboss.org/schema/jbossas/jboss-ejb-security_1_1.xsd" version="3.1" impl-version="2.0"> <jee:assembly-descriptor> <s:security> <jee:ejb-name>*</jee:ejb-name> <s:security-domain>SomeSecurityDomain</s:security-domain>  <s:missing-method-permissions-deny-access>true</s:missing-method-permissions-deny-access> </s:security> </jee:assembly-descriptor> </jboss:ejb-jar> {noformat} was: Validate the following 'jboss-ejb3.xml' file: {{<?xml version="1.0" encoding="UTF-8"?>}} {{<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"}} {{xmlns:jee="http://java.sun.com/xml/ns/javaee"}} {{ xmlns:s="urn:security:1.1"}} {{ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"}} {{ xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd}} {{ http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd}} {{ urn:security:1.1 http://www.jboss.org/schema/jbossas/jboss-ejb-security_1_1.xsd"}} {{ version="3.1" impl-version="2.0">}} {{ <jee:assembly-descriptor>}} {{ <s:security>}} {{ <jee:ejb-name>*</jee:ejb-name>}} {{ <s:security-domain>SomeSecurityDomain</s:security-domain>}} {{ }} {{ <s:missing-method-permissions-deny-access>true</s:missing-method-permissions-deny-access>}} {{ </s:security>}} {{ </jee:assembly-descriptor>}} {{</jboss:ejb-jar>}} > Elements defined in 'jboss-ejb-security_1_1.xsd' must be optional > ----------------------------------------------------------------- > > Key: WFLY-9047 > URL: https://issues.jboss.org/browse/WFLY-9047 > Project: WildFly > Issue Type: Bug > Affects Versions: 11.0.0.Alpha1 > Reporter: Jörg Bäsner > Assignee: Jason Greene > > Wildfly does not validate the 'jboss-ejb3.xml' file during startup, but when trying do validate a 'jboss-ejb3.xml' file externally the following elements are mandatory, even though they aren't: > * {{security-domain}} > * {{run-as-principal}} > * {{missing-method-permissions-deny-access}} > The [jboss-ejb-security_1_1.xsd|http://www.jboss.org/schema/jbossas/jboss-ejb-...] should be changed to have these elements optional. > Like: > {{ > ... > <xs:element name="security-domain" type="xs:string" minOccurs="0"/> > <xs:element name="run-as-principal" type="xs:string" minOccurs="0"/> > <xs:element name="missing-method-permissions-deny-access" type="xs:boolean" minOccurs="0"> > ... > }} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9047) Elements defined in 'jboss-ejb-security_1_1.xsd' must be optional

by Jörg Bäsner (JIRA)

[ https://issues.jboss.org/browse/WFLY-9047?page=com.atlassian.jira.plugin.... ] Jörg Bäsner updated WFLY-9047: ------------------------------ Description: Wildfly does not validate the 'jboss-ejb3.xml' file during startup, but when trying do validate a 'jboss-ejb3.xml' file externally the following elements are mandatory, even though they aren't: * {{security-domain}} * {{run-as-principal}} * {{missing-method-permissions-deny-access}} The [jboss-ejb-security_1_1.xsd|http://www.jboss.org/schema/jbossas/jboss-ejb-...] should be changed to have these elements optional. Like: {noformat} ... <xs:element name="security-domain" type="xs:string" minOccurs="0"/> <xs:element name="run-as-principal" type="xs:string" minOccurs="0"/> <xs:element name="missing-method-permissions-deny-access" type="xs:boolean" minOccurs="0"> ... {noformat} was: Wildfly does not validate the 'jboss-ejb3.xml' file during startup, but when trying do validate a 'jboss-ejb3.xml' file externally the following elements are mandatory, even though they aren't: * {{security-domain}} * {{run-as-principal}} * {{missing-method-permissions-deny-access}} The [jboss-ejb-security_1_1.xsd|http://www.jboss.org/schema/jbossas/jboss-ejb-...] should be changed to have these elements optional. Like: {{ ... <xs:element name="security-domain" type="xs:string" minOccurs="0"/> <xs:element name="run-as-principal" type="xs:string" minOccurs="0"/> <xs:element name="missing-method-permissions-deny-access" type="xs:boolean" minOccurs="0"> ... }} > Elements defined in 'jboss-ejb-security_1_1.xsd' must be optional > ----------------------------------------------------------------- > > Key: WFLY-9047 > URL: https://issues.jboss.org/browse/WFLY-9047 > Project: WildFly > Issue Type: Bug > Affects Versions: 11.0.0.Alpha1 > Reporter: Jörg Bäsner > Assignee: Jason Greene > > Wildfly does not validate the 'jboss-ejb3.xml' file during startup, but when trying do validate a 'jboss-ejb3.xml' file externally the following elements are mandatory, even though they aren't: > * {{security-domain}} > * {{run-as-principal}} > * {{missing-method-permissions-deny-access}} > The [jboss-ejb-security_1_1.xsd|http://www.jboss.org/schema/jbossas/jboss-ejb-...] should be changed to have these elements optional. > Like: > {noformat} > ... > <xs:element name="security-domain" type="xs:string" minOccurs="0"/> > <xs:element name="run-as-principal" type="xs:string" minOccurs="0"/> > <xs:element name="missing-method-permissions-deny-access" type="xs:boolean" minOccurs="0"> > ... > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9047) Elements defined in 'jboss-ejb-security_1_1.xsd' must be optional

by Jörg Bäsner (JIRA)

[ https://issues.jboss.org/browse/WFLY-9047?page=com.atlassian.jira.plugin.... ] Jörg Bäsner updated WFLY-9047: ------------------------------ Steps to Reproduce: Validate the following 'jboss-ejb3.xml' file: {{<?xml version="1.0" encoding="UTF-8"?>}} {{<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"}} {{xmlns:jee="http://java.sun.com/xml/ns/javaee"}} {{ xmlns:s="urn:security:1.1"}} {{ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"}} {{ xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd}} {{ http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd}} {{ urn:security:1.1 http://www.jboss.org/schema/jbossas/jboss-ejb-security_1_1.xsd"}} {{ version="3.1" impl-version="2.0">}} {{ <jee:assembly-descriptor>}} {{ <s:security>}} {{ <jee:ejb-name>*</jee:ejb-name>}} {{ <s:security-domain>SomeSecurityDomain</s:security-domain>}} {{ }} {{ <s:missing-method-permissions-deny-access>true</s:missing-method-permissions-deny-access>}} {{ </s:security>}} {{ </jee:assembly-descriptor>}} {{</jboss:ejb-jar>}} was: Validate the following 'jboss-ejb3.xml' file: {{<?xml version="1.0" encoding="UTF-8"?>}} {{<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"}} {{ xmlns:jee="http://java.sun.com/xml/ns/javaee"}} {{ xmlns:s="urn:security:1.1"}} {{ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"}} {{ xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd}} {{ http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd}} {{ urn:security:1.1 http://www.jboss.org/schema/jbossas/jboss-ejb-security_1_1.xsd"}} {{ version="3.1" impl-version="2.0">}} {{ <jee:assembly-descriptor>}} {{ <s:security>}} {{ <jee:ejb-name>*</jee:ejb-name>}} {{ <s:security-domain>SomeSecurityDomain</s:security-domain>}} {{ }} {{ <s:missing-method-permissions-deny-access>true</s:missing-method-permissions-deny-access>}} {{ </s:security>}} {{ </jee:assembly-descriptor>}} {{</jboss:ejb-jar>}} > Elements defined in 'jboss-ejb-security_1_1.xsd' must be optional > ----------------------------------------------------------------- > > Key: WFLY-9047 > URL: https://issues.jboss.org/browse/WFLY-9047 > Project: WildFly > Issue Type: Bug > Affects Versions: 11.0.0.Alpha1 > Reporter: Jörg Bäsner > Assignee: Jason Greene > > Wildfly does not validate the 'jboss-ejb3.xml' file during startup, but when trying do validate a 'jboss-ejb3.xml' file externally the following elements are mandatory, even though they aren't: > * {{security-domain}} > * {{run-as-principal}} > * {{missing-method-permissions-deny-access}} > The [jboss-ejb-security_1_1.xsd|http://www.jboss.org/schema/jbossas/jboss-ejb-...] should be changed to have these elements optional. > Like: > {{ > ... > <xs:element name="security-domain" type="xs:string" minOccurs="0"/> > <xs:element name="run-as-principal" type="xs:string" minOccurs="0"/> > <xs:element name="missing-method-permissions-deny-access" type="xs:boolean" minOccurs="0"> > ... > }} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9048) MDB20TopicTestCase fails with security manager

by Ondrej Kotek (JIRA)

[ https://issues.jboss.org/browse/WFLY-9048?page=com.atlassian.jira.plugin.... ] Ondrej Kotek moved JBEAP-11950 to WFLY-9048: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9048 (was: JBEAP-11950) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: 11.0.0.Beta1 (was: 7.1.0.ER1) > MDB20TopicTestCase fails with security manager > ---------------------------------------------- > > Key: WFLY-9048 > URL: https://issues.jboss.org/browse/WFLY-9048 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 11.0.0.Beta1 > Reporter: Ondrej Kotek > Assignee: Tomaz Cerar > > MDB20TopicTestCase fails with security manager: > {noformat} > java.io.IOException: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("org.jboss.remoting3.security.RemotingPermission" "createEndpoint")" in code source "(vfs:/content/MDB20TopicTestCase.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.MDB20TopicTestCase.jar" from Service Module Loader") > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75) > at org.jboss.as.test.integration.ejb.mdb.ejb2x.MDB20TopicTestCase.getNumberOfAllSubscriptions(MDB20TopicTestCase.java:171) > ... > {noformat} > There are missing permissions {{RemotingPermission("createEndpoint")}}, {{RemotingPermission("connect")}}, and possibly others, and missing dependency on {{org.jboss.remoting3}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9047) Elements defined in 'jboss-ejb-security_1_1.xsd' must be optional

by Jörg Bäsner (JIRA)

[ https://issues.jboss.org/browse/WFLY-9047?page=com.atlassian.jira.plugin.... ] Jörg Bäsner updated WFLY-9047: ------------------------------ Steps to Reproduce: Validate the following 'jboss-ejb3.xml' file: {{<?xml version="1.0" encoding="UTF-8"?>}} {{<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" }} {{ xmlns:jee="http://java.sun.com/xml/ns/javaee"}} {{ xmlns:s="urn:security:1.1"}} {{ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"}} {{ xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd}} {{ http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd}} {{ urn:security:1.1 http://www.jboss.org/schema/jbossas/jboss-ejb-security_1_1.xsd"}} {{ version="3.1" impl-version="2.0">}} {{ <jee:assembly-descriptor>}} {{ <s:security>}} {{ <jee:ejb-name>*</jee:ejb-name>}} {{ <s:security-domain>SomeSecurityDomain</s:security-domain>}} {{ }} {{ <s:missing-method-permissions-deny-access>true</s:missing-method-permissions-deny-access>}} {{ </s:security>}} {{ </jee:assembly-descriptor>}} {{</jboss:ejb-jar>}} was: Validate the following 'jboss-ejb3.xml' file: {{<?xml version="1.0" encoding="UTF-8"?>}} {{<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns:jee="http://java.sun.com/xml/ns/javaee" xmlns:s="urn:security:1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd urn:security:1.1 http://www.jboss.org/schema/jbossas/jboss-ejb-security_1_1.xsd" version="3.1" impl-version="2.0"> <jee:assembly-descriptor> <s:security> <jee:ejb-name>*</jee:ejb-name> <s:security-domain>SomeSecurityDomain</s:security-domain>  <s:missing-method-permissions-deny-access>true</s:missing-method-permissions-deny-access> </s:security> </jee:assembly-descriptor> </jboss:ejb-jar> }} > Elements defined in 'jboss-ejb-security_1_1.xsd' must be optional > ----------------------------------------------------------------- > > Key: WFLY-9047 > URL: https://issues.jboss.org/browse/WFLY-9047 > Project: WildFly > Issue Type: Bug > Affects Versions: 11.0.0.Alpha1 > Reporter: Jörg Bäsner > Assignee: Jason Greene > > Wildfly does not validate the 'jboss-ejb3.xml' file during startup, but when trying do validate a 'jboss-ejb3.xml' file externally the following elements are mandatory, even though they aren't: > * {{security-domain}} > * {{run-as-principal}} > * {{missing-method-permissions-deny-access}} > The [jboss-ejb-security_1_1.xsd|http://www.jboss.org/schema/jbossas/jboss-ejb-...] should be changed to have these elements optional. > Like: > {{ > ... > <xs:element name="security-domain" type="xs:string" minOccurs="0"/> > <xs:element name="run-as-principal" type="xs:string" minOccurs="0"/> > <xs:element name="missing-method-permissions-deny-access" type="xs:boolean" minOccurs="0"> > ... > }} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9047) Elements defined in 'jboss-ejb-security_1_1.xsd' must be optional

by Jörg Bäsner (JIRA)

[ https://issues.jboss.org/browse/WFLY-9047?page=com.atlassian.jira.plugin.... ] Jörg Bäsner updated WFLY-9047: ------------------------------ Steps to Reproduce: Validate the following 'jboss-ejb3.xml' file: {{<?xml version="1.0" encoding="UTF-8"?>}} {{<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"}} {{ xmlns:jee="http://java.sun.com/xml/ns/javaee"}} {{ xmlns:s="urn:security:1.1"}} {{ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"}} {{ xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd}} {{ http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd}} {{ urn:security:1.1 http://www.jboss.org/schema/jbossas/jboss-ejb-security_1_1.xsd"}} {{ version="3.1" impl-version="2.0">}} {{ <jee:assembly-descriptor>}} {{ <s:security>}} {{ <jee:ejb-name>*</jee:ejb-name>}} {{ <s:security-domain>SomeSecurityDomain</s:security-domain>}} {{ }} {{ <s:missing-method-permissions-deny-access>true</s:missing-method-permissions-deny-access>}} {{ </s:security>}} {{ </jee:assembly-descriptor>}} {{</jboss:ejb-jar>}} was: Validate the following 'jboss-ejb3.xml' file: {{<?xml version="1.0" encoding="UTF-8"?>}} {{<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" }} {{ xmlns:jee="http://java.sun.com/xml/ns/javaee"}} {{ xmlns:s="urn:security:1.1"}} {{ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"}} {{ xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd}} {{ http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd}} {{ urn:security:1.1 http://www.jboss.org/schema/jbossas/jboss-ejb-security_1_1.xsd"}} {{ version="3.1" impl-version="2.0">}} {{ <jee:assembly-descriptor>}} {{ <s:security>}} {{ <jee:ejb-name>*</jee:ejb-name>}} {{ <s:security-domain>SomeSecurityDomain</s:security-domain>}} {{ }} {{ <s:missing-method-permissions-deny-access>true</s:missing-method-permissions-deny-access>}} {{ </s:security>}} {{ </jee:assembly-descriptor>}} {{</jboss:ejb-jar>}} > Elements defined in 'jboss-ejb-security_1_1.xsd' must be optional > ----------------------------------------------------------------- > > Key: WFLY-9047 > URL: https://issues.jboss.org/browse/WFLY-9047 > Project: WildFly > Issue Type: Bug > Affects Versions: 11.0.0.Alpha1 > Reporter: Jörg Bäsner > Assignee: Jason Greene > > Wildfly does not validate the 'jboss-ejb3.xml' file during startup, but when trying do validate a 'jboss-ejb3.xml' file externally the following elements are mandatory, even though they aren't: > * {{security-domain}} > * {{run-as-principal}} > * {{missing-method-permissions-deny-access}} > The [jboss-ejb-security_1_1.xsd|http://www.jboss.org/schema/jbossas/jboss-ejb-...] should be changed to have these elements optional. > Like: > {{ > ... > <xs:element name="security-domain" type="xs:string" minOccurs="0"/> > <xs:element name="run-as-principal" type="xs:string" minOccurs="0"/> > <xs:element name="missing-method-permissions-deny-access" type="xs:boolean" minOccurs="0"> > ... > }} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9047) Elements defined in 'jboss-ejb-security_1_1.xsd' must be optional

by Jörg Bäsner (JIRA)

[ https://issues.jboss.org/browse/WFLY-9047?page=com.atlassian.jira.plugin.... ] Jörg Bäsner updated WFLY-9047: ------------------------------ Steps to Reproduce: Validate the following 'jboss-ejb3.xml' file: {{<?xml version="1.0" encoding="UTF-8"?>}} {{<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns:jee="http://java.sun.com/xml/ns/javaee" xmlns:s="urn:security:1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd urn:security:1.1 http://www.jboss.org/schema/jbossas/jboss-ejb-security_1_1.xsd" version="3.1" impl-version="2.0"> <jee:assembly-descriptor> <s:security> <jee:ejb-name>*</jee:ejb-name> <s:security-domain>SomeSecurityDomain</s:security-domain>  <s:missing-method-permissions-deny-access>true</s:missing-method-permissions-deny-access> </s:security> </jee:assembly-descriptor> </jboss:ejb-jar> }} was: Validate the following 'jboss-ejb3.xml' file: {{<?xml version="1.0" encoding="UTF-8"?> <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns:jee="http://java.sun.com/xml/ns/javaee" xmlns:s="urn:security:1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd urn:security:1.1 http://www.jboss.org/schema/jbossas/jboss-ejb-security_1_1.xsd" version="3.1" impl-version="2.0"> <jee:assembly-descriptor> <s:security> <jee:ejb-name>*</jee:ejb-name> <s:security-domain>SomeSecurityDomain</s:security-domain>  <s:missing-method-permissions-deny-access>true</s:missing-method-permissions-deny-access> </s:security> </jee:assembly-descriptor> </jboss:ejb-jar> }} > Elements defined in 'jboss-ejb-security_1_1.xsd' must be optional > ----------------------------------------------------------------- > > Key: WFLY-9047 > URL: https://issues.jboss.org/browse/WFLY-9047 > Project: WildFly > Issue Type: Bug > Affects Versions: 11.0.0.Alpha1 > Reporter: Jörg Bäsner > Assignee: Jason Greene > > Wildfly does not validate the 'jboss-ejb3.xml' file during startup, but when trying do validate a 'jboss-ejb3.xml' file externally the following elements are mandatory, even though they aren't: > * {{security-domain}} > * {{run-as-principal}} > * {{missing-method-permissions-deny-access}} > The [jboss-ejb-security_1_1.xsd|http://www.jboss.org/schema/jbossas/jboss-ejb-...] should be changed to have these elements optional. > Like: > {{ > ... > <xs:element name="security-domain" type="xs:string" minOccurs="0"/> > <xs:element name="run-as-principal" type="xs:string" minOccurs="0"/> > <xs:element name="missing-method-permissions-deny-access" type="xs:boolean" minOccurs="0"> > ... > }} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9047) Elements defined in 'jboss-ejb-security_1_1.xsd' must be optional

by Jörg Bäsner (JIRA)

Jörg Bäsner created WFLY-9047: --------------------------------- Summary: Elements defined in 'jboss-ejb-security_1_1.xsd' must be optional Key: WFLY-9047 URL: https://issues.jboss.org/browse/WFLY-9047 Project: WildFly Issue Type: Bug Affects Versions: 11.0.0.Alpha1 Reporter: Jörg Bäsner Assignee: Jason Greene Wildfly does not validate the 'jboss-ejb3.xml' file during startup, but when trying do validate a 'jboss-ejb3.xml' file externally the following elements are mandatory, even though they aren't: * {{security-domain}} * {{run-as-principal}} * {{missing-method-permissions-deny-access}} The [jboss-ejb-security_1_1.xsd|http://www.jboss.org/schema/jbossas/jboss-ejb-...] should be changed to have these elements optional. Like: {{ ... <xs:element name="security-domain" type="xs:string" minOccurs="0"/> <xs:element name="run-as-principal" type="xs:string" minOccurs="0"/> <xs:element name="missing-method-permissions-deny-access" type="xs:boolean" minOccurs="0"> ... }} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1648) Maven dependency resolution through "LATEST" and "RELEASE" version labels using "KieServices.newKieContainer(ReleaseId releaseId)" method fails

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1648?page=com.atlassian.jira.plugi... ] Kris Verlaenen moved JBIDE-24644 to DROOLS-1648: ------------------------------------------------ Project: Drools (was: Tools (JBoss Tools)) Key: DROOLS-1648 (was: JBIDE-24644) Docs QE Status: NEW Component/s: core engine (was: drools) Affects Version/s: (was: LATER) QE Status: NEW > Maven dependency resolution through "LATEST" and "RELEASE" version labels using "KieServices.newKieContainer(ReleaseId releaseId)" method fails > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1648 > URL: https://issues.jboss.org/browse/DROOLS-1648 > Project: Drools > Issue Type: Bug > Components: core engine > Environment: OS: macOS Sierra (10.12.5) > Hardware: MacBook Pro (13-inch, 2017) > Reporter: Pyit Phyo Aung > Assignee: Kris Verlaenen > Priority: Minor > > I tried to use KieScanner for automatic business rule deployment through kjar modules setup in private maven repository. For that, I tried to specify getting latest kjar modules using "LATEST" and "RELEASE" version labels. They failed for three drools versions I tried (6.5.0.Final, 7.0.0.Final and 7.1.0.Beta3). However, when I tried open-ended version label, solution works. So, I believe that there is issue in dependency resolution related to KieContainer through KieServices.newKieContainer(ReleaseId releaseId) method. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
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 July 2017