[JBoss JIRA] (DROOLS-2623) Stabilize xls tables backend tests
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2623?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2623:
--------------------------------
Story Points: 3
Sprint: 2019 Week 02-04
> Stabilize xls tables backend tests
> ----------------------------------
>
> Key: DROOLS-2623
> URL: https://issues.jboss.org/browse/DROOLS-2623
> Project: Drools
> Issue Type: Task
> Components: XLS Decision Table Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
>
> The xls tables backend tests fails in the way described bellow:
> {code:shell}
> [drools-wb-dtable-xls-editor-backend] mvn clean install
> ...
> Failed tests:
> DTCellValueUtilitiesTest.conversion:120->lambda$conversion$0:123 null
> DTCellValueUtilitiesTest.conversion:120->lambda$conversion$0:123 null
> {code}
> The problem occurs just if whole backend module run. Separate tests are passing.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11584) Legacy Web migrate op fails if a connector has scheme https and no SSL config
by Teresa Miyar (Jira)
[ https://issues.jboss.org/browse/WFLY-11584?page=com.atlassian.jira.plugin... ]
Teresa Miyar updated WFLY-11584:
--------------------------------
Affects Version/s: 15.0.1.Final
> Legacy Web migrate op fails if a connector has scheme https and no SSL config
> -----------------------------------------------------------------------------
>
> Key: WFLY-11584
> URL: https://issues.jboss.org/browse/WFLY-11584
> Project: WildFly
> Issue Type: Bug
> Components: Migration
> Affects Versions: 15.0.1.Final
> Reporter: Teresa Miyar
> Assignee: Teresa Miyar
> Priority: Major
> Attachments: standalone.xml
>
>
> If we set an attribute 'scheme' of 'http' connector as 'https' [ scheme="https" ] and no SSL config, in 'web' subsystem, then migrate op fails:
> {code}
> [standalone@localhost:9990 /] /subsystem=web:migrate
> {
> "outcome" => "failed",
> "result" => {"[(\"extension\" => \"org.wildfly.extension.undertow\")]" => {
> "outcome" => "failed",
> "result" => [("undertow" => "4.0.0")],
> "rolled-back" => true
> }},
> "failure-description" => "WFLYWEB0004: Could not migrate SSL connector as no SSL config is defined",
> "rolled-back" => true
> }
> {code}
> Steps to Reproduce:
> 1. Replace EAP 7.1 default standalone.xml configuration with the one attached
> 2. Start JBoss EAP 7.1 in mode admin-only
> 3. Start CLI and invoke web subsystem migrate op [^standalone.xml]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3373) [DMN Designer] Need Palette glyph/icon and Canvas shape for Decision Service
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3373?page=com.atlassian.jira.plugi... ]
Michael Anstis reassigned DROOLS-3373:
--------------------------------------
Assignee: Michael Anstis (was: Brian Dellascio)
> [DMN Designer] Need Palette glyph/icon and Canvas shape for Decision Service
> ----------------------------------------------------------------------------
>
> Key: DROOLS-3373
> URL: https://issues.jboss.org/browse/DROOLS-3373
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: VisualDesign, drools-tools, ux_needed, visualdesign
> Attachments: DMN_palette_icons.png, decision-service-expanded.svg, decision-service.svg, decision.svg, decision_palette.svg, decision_service_expanded_palette.svg, decision_service_palette.svg
>
>
> We need a new "Palette" icon and Canvas shape for "Decision Services".
> See Table 1: DRD components in the [DMN 1.2 Specification|https://www.omg.org/spec/DMN/1.2/Beta1/PDF].
> See also 6.2.5 Decision service for some narrative regarding the shape.
> {quote}
> A Decision Service is represented in a DRD as rectangle with rounded corners, drawn with a heavy solid border.... the Decision Service SHALL be divided into two parts with a straight solid line.
> {quote}
> We are currently adding support for the _expanded_ form however we will also require (at some stage) a Palette glyph/icon and Canvas shape for the _collapsed_ form too.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11406) Reflection exception at org.jboss.classfilewriter.ClassFile on JDK12
by Matej Novotny (Jira)
[ https://issues.jboss.org/browse/WFLY-11406?page=com.atlassian.jira.plugin... ]
Matej Novotny commented on WFLY-11406:
--------------------------------------
For the record, the API David mentioned ({{ClassDefiner}}) is not yet available in WFLY. The issue (MODULES-360) is targeted for 1.9.0 release which didn't happen yet and 1.8.x branch doesn't contain the commit.
> Reflection exception at org.jboss.classfilewriter.ClassFile on JDK12
> --------------------------------------------------------------------
>
> Key: WFLY-11406
> URL: https://issues.jboss.org/browse/WFLY-11406
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, EJB
> Reporter: Richard Opalka
> Assignee: Matej Novotny
> Priority: Critical
> Labels: jdk12
> Fix For: 16.0.0.Beta1
>
>
> When running WildFly on JDK12 I'm observing this exception due to Unsafe changes in recent JDK Early Access builds:
> [0m[31m16:47:17,739 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."ws-endpoint-example.war".IN
> <------>at org.jboss.as.server@7.0.0.CR1-SNAPSHOT//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
> <------>at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
> <------>at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
> <------>at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
> <------>at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> <------>at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> <------>at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> <------>at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> <------>at java.base/java.lang.Thread.run(Thread.java:835)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0024: Could not configure component TestService
> <------>at org.jboss.as.ee@15.0.0.CR1-SNAPSHOT//org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:106)
> <------>at org.jboss.as.server@7.0.0.CR1-SNAPSHOT//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
> <------>... 8 more
> Caused by: java.lang.Error: java.lang.NoSuchFieldException: override
> <------>at org.jboss.classfilewriter@1.2.3.Final//org.jboss.classfilewriter.ClassFile$1.run(ClassFile.java:394)
> <------>at org.jboss.classfilewriter@1.2.3.Final//org.jboss.classfilewriter.ClassFile$1.run(ClassFile.java:385)
> <------>at java.base/java.security.AccessController.doPrivileged(AccessController.java:551)
> <------>at org.jboss.classfilewriter(a)1.2.3.Final//org.jboss.classfilewriter.ClassFile.<clinit>(ClassFile.java:385)
> <------>at org.jboss.invocation(a)1.5.1.Final//org.jboss.invocation.proxy.AbstractClassFactory.<init>(AbstractClassFactory.java:97)
> <------>at org.jboss.invocation(a)1.5.1.Final//org.jboss.invocation.proxy.AbstractSubclassFactory.<init>(AbstractSubclassFactory.java:87)
> <------>at org.jboss.invocation(a)1.5.1.Final//org.jboss.invocation.proxy.AbstractProxyFactory.<init>(AbstractProxyFactory.java:69)
> <------>at org.jboss.invocation(a)1.5.1.Final//org.jboss.invocation.proxy.ProxyFactory.<init>(ProxyFactory.java:256)
> <------>at org.jboss.as.ee@15.0.0.CR1-SNAPSHOT//org.jboss.as.ee.component.DefaultComponentViewConfigurator.configure(DefaultComponentViewConfigurator.java:86)
> <------>at org.jboss.as.ee@15.0.0.CR1-SNAPSHOT//org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:92)
> <------>... 9 more
> Caused by: java.lang.NoSuchFieldException: override
> <------>at java.base/java.lang.Class.getDeclaredField(Class.java:2410)
> <------>at org.jboss.classfilewriter@1.2.3.Final//org.jboss.classfilewriter.ClassFile$1.run(ClassFile.java:392)
> <------>... 18 more
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3484) Data type constraints: Date range Include/Exclude actions.
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3484?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-3484:
----------------------------------------
[~uxdlc] Looks good to me.
> Data type constraints: Date range Include/Exclude actions.
> ----------------------------------------------------------
>
> Key: DROOLS-3484
> URL: https://issues.jboss.org/browse/DROOLS-3484
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: date-rangeC.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> *Use Cases:*
> As a user I want the ability to define constraints for the Date data type, that enable me to specify if the start and end value is included/excluded in a selected date range.
> *Note, selection options:*
> Include/ Include [ .. ]
> Include/ Exclude [ .. )
> Exclude / Include ( .. ]
> Exclude / Exclude ( .. )
> *Verification conditions:*
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3505) Parse error with executable-model, java dialect, modify block and comma
by Toshiya Kobayashi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3505?page=com.atlassian.jira.plugi... ]
Toshiya Kobayashi commented on DROOLS-3505:
-------------------------------------------
Unit test PR
https://github.com/kiegroup/drools/pull/2212
> Parse error with executable-model, java dialect, modify block and comma
> -----------------------------------------------------------------------
>
> Key: DROOLS-3505
> URL: https://issues.jboss.org/browse/DROOLS-3505
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.16.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Luca Molteni
> Priority: Major
> Labels: support
>
> With the conditions:
> - Build by executable-model (-DgenerateModel=YES)
> - java dialect
> - Connect expressions with "comma" inside a modify block
> You get a parse error.
> {noformat}
> [ERROR] testCommaInModify[PATTERN_DSL](org.drools.modelcompiler.CompilerTest) Time elapsed: 0.033 s <<< ERROR!
> org.drools.javaparser.ParseProblemException:
> (line 1,col 10) Parse error. Found ",", expected one of "%=" "&=" "*=" "++" "+=" "--" "-=" "/=" ";" "<<=" "=" ">>=" ">>>=" "^=" "|="
> Problem stacktrace :
> org.drools.javaparser.GeneratedJavaParser.generateParseException(GeneratedJavaParser.java:11597)
> org.drools.javaparser.GeneratedJavaParser.jj_consume_token(GeneratedJavaParser.java:11456)
> org.drools.javaparser.GeneratedJavaParser.StatementExpression(GeneratedJavaParser.java:4160)
> org.drools.javaparser.GeneratedJavaParser.Statement(GeneratedJavaParser.java:3798)
> org.drools.javaparser.GeneratedJavaParser.BlockStatement(GeneratedJavaParser.java:3977)
> org.drools.javaparser.GeneratedJavaParser.Statements(GeneratedJavaParser.java:1606)
> org.drools.javaparser.GeneratedJavaParser.Block(GeneratedJavaParser.java:3893)
> org.drools.javaparser.GeneratedJavaParser.BlockParseStart(GeneratedJavaParser.java:5193)
> org.drools.javaparser.JavaParser.parse(JavaParser.java:131)
> org.drools.javaparser.JavaParser.simplifiedParse(JavaParser.java:337)
> org.drools.javaparser.JavaParser.parseBlock(JavaParser.java:321)
> org.drools.modelcompiler.builder.generator.Consequence.rewriteConsequenceBlock(Consequence.java:255)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3505) Parse error with executable-model, java dialect, modify block and comma
by Toshiya Kobayashi (Jira)
Toshiya Kobayashi created DROOLS-3505:
-----------------------------------------
Summary: Parse error with executable-model, java dialect, modify block and comma
Key: DROOLS-3505
URL: https://issues.jboss.org/browse/DROOLS-3505
Project: Drools
Issue Type: Bug
Components: executable model
Affects Versions: 7.16.0.Final
Reporter: Toshiya Kobayashi
Assignee: Luca Molteni
With the conditions:
- Build by executable-model (-DgenerateModel=YES)
- java dialect
- Connect expressions with "comma" inside a modify block
You get a parse error.
{noformat}
[ERROR] testCommaInModify[PATTERN_DSL](org.drools.modelcompiler.CompilerTest) Time elapsed: 0.033 s <<< ERROR!
org.drools.javaparser.ParseProblemException:
(line 1,col 10) Parse error. Found ",", expected one of "%=" "&=" "*=" "++" "+=" "--" "-=" "/=" ";" "<<=" "=" ">>=" ">>>=" "^=" "|="
Problem stacktrace :
org.drools.javaparser.GeneratedJavaParser.generateParseException(GeneratedJavaParser.java:11597)
org.drools.javaparser.GeneratedJavaParser.jj_consume_token(GeneratedJavaParser.java:11456)
org.drools.javaparser.GeneratedJavaParser.StatementExpression(GeneratedJavaParser.java:4160)
org.drools.javaparser.GeneratedJavaParser.Statement(GeneratedJavaParser.java:3798)
org.drools.javaparser.GeneratedJavaParser.BlockStatement(GeneratedJavaParser.java:3977)
org.drools.javaparser.GeneratedJavaParser.Statements(GeneratedJavaParser.java:1606)
org.drools.javaparser.GeneratedJavaParser.Block(GeneratedJavaParser.java:3893)
org.drools.javaparser.GeneratedJavaParser.BlockParseStart(GeneratedJavaParser.java:5193)
org.drools.javaparser.JavaParser.parse(JavaParser.java:131)
org.drools.javaparser.JavaParser.simplifiedParse(JavaParser.java:337)
org.drools.javaparser.JavaParser.parseBlock(JavaParser.java:321)
org.drools.modelcompiler.builder.generator.Consequence.rewriteConsequenceBlock(Consequence.java:255)
{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-9450) NPE on jaxrs subsystem of FAILED deployment
by Bartosz Baranowski (Jira)
[ https://issues.jboss.org/browse/WFLY-9450?page=com.atlassian.jira.plugin.... ]
Bartosz Baranowski reassigned WFLY-9450:
----------------------------------------
Assignee: Bartosz Baranowski (was: Alessio Soldano)
> NPE on jaxrs subsystem of FAILED deployment
> --------------------------------------------
>
> Key: WFLY-9450
> URL: https://issues.jboss.org/browse/WFLY-9450
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Reporter: Claudio Miranda
> Assignee: Bartosz Baranowski
> Priority: Major
>
> read deployment resources of a server, where one deployment is in failed status, throws a NPE and doesn't return the list of deployed applications.
> To reproduce, get the kitchensink from quickstarts, change the persistence.xml to point to ExampleDS datasource, deploy and assign to main-server-group. Then disable ExampleDS, restart server-one.
> Run the following command:
> {code}
> /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {code}
> The exception in server.log
> {code}
> 2017-10-17 17:08:02,778 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "jaxrs"),
> ("rest-resource" => "org.jboss.as.quickstarts.kitchensink.rest.MemberResourceRESTService")
> ]): java.lang.NullPointerException
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.getDeployment(UndertowDeploymentService.java:170)
> at org.jboss.as.jaxrs.DeploymentRestResourcesDefintion$AbstractRestResReadHandler.execute(DeploymentRestResourcesDefintion.java:183)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:172)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:135)
> at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:231)
> {code}
> The CLI results doesn't display the error message
> {code}
> [domain@localhost:9990 /] /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {
> "outcome" => "success",
> "result" => undefined,
> "failure-description" => undefined
> }
> {code}
> There is a similar problem while reading a specific deployment,
> {code}
> /host=master/server=server-one/deployment=kitchensink.war:read-children-resources(child-type=subsystem,recursive)
> {code}
> results in the following error in server.log
> {code}
> 2017-10-17 17:16:09,857 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "ejb3"),
> ("stateless-session-bean" => "MemberRegistration")
> ]) - failure description: "WFLYEJB0370: EJB component for address [
> (\"deployment\" => \"kitchensink.war\"),
> (\"subsystem\" => \"ejb3\"),
> (\"stateless-session-bean\" => \"MemberRegistration\")
> ] is in
> state DOWN, must be in state UP"
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11584) Legacy Web migrate op fails if a connector has scheme https and no SSL config
by Teresa Miyar (Jira)
[ https://issues.jboss.org/browse/WFLY-11584?page=com.atlassian.jira.plugin... ]
Teresa Miyar moved JBEAP-16140 to WFLY-11584:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-11584 (was: JBEAP-16140)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Migration
(was: Migration)
(was: Web (JBoss Web))
(was: Web (Undertow))
> Legacy Web migrate op fails if a connector has scheme https and no SSL config
> -----------------------------------------------------------------------------
>
> Key: WFLY-11584
> URL: https://issues.jboss.org/browse/WFLY-11584
> Project: WildFly
> Issue Type: Bug
> Components: Migration
> Reporter: Teresa Miyar
> Assignee: Teresa Miyar
> Priority: Major
> Attachments: standalone.xml
>
>
> If we set an attribute 'scheme' of 'http' connector as 'https' [ scheme="https" ] and no SSL config, in 'web' subsystem, then migrate op fails:
> {code}
> [standalone@localhost:9990 /] /subsystem=web:migrate
> {
> "outcome" => "failed",
> "result" => {"[(\"extension\" => \"org.wildfly.extension.undertow\")]" => {
> "outcome" => "failed",
> "result" => [("undertow" => "4.0.0")],
> "rolled-back" => true
> }},
> "failure-description" => "WFLYWEB0004: Could not migrate SSL connector as no SSL config is defined",
> "rolled-back" => true
> }
> {code}
> Steps to Reproduce:
> 1. Replace EAP 7.1 default standalone.xml configuration with the one attached
> 2. Start JBoss EAP 7.1 in mode admin-only
> 3. Start CLI and invoke web subsystem migrate op [^standalone.xml]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFCORE-4269) Multiple <socket> elements inside an http-interface parsed wrongly
by Jörg Bäsner (Jira)
[ https://issues.jboss.org/browse/WFCORE-4269?page=com.atlassian.jira.plugi... ]
Jörg Bäsner updated WFCORE-4269:
--------------------------------
Description:
The definition of the _http-interface_ for the _management-interface_ in the {{wildfly-config_5_0.xsd}} is defined as:
{code}
<xs:complexType name="host-http-management-interfaceType">
<xs:annotation>
<xs:documentation>
Configuration of a host's exposed HTTP management interface.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="http-management-interfaceType">
<xs:sequence>
<xs:element name="socket" type="host-http-management-socketType"/>
</xs:sequence>
<xs:attribute name="console-enabled" type="xs:boolean" use="optional" default="true"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
{code}
Where _xs:sequence_ has a default definition of:
* *maxOccurs* _Optional._ Specifies the maximum number of times the sequence element can occur in the parent element. The value can be any number >= 0, or if you want to set no limit on the maximum number, use the value "unbounded". Default value is 1
* *minOccurs* _Optional._ Specifies the minimum number of times the sequence element can occur in the parent element. The value can be any number >= 0. Default value is 1
But the parser allows to configure multiple sockets like this:
{code}
...
<security-realm name="ManagementRealm">
<server-identities>
<ssl>
<keystore path="server.keystore" relative-to="jboss.domain.config.dir" keystore-password="******" alias="server"/>
</ssl>
</server-identities>
<authentication>
<properties path="mgmt-users.properties" relative-to="jboss.domain.config.dir"/>
</authentication>
</security-realm>
...
<http-interface security-realm="ManagementRealm">
<http-upgrade enabled="true"/>
<socket interface="local" port="${jboss.management.local.http.port:9990}"/>
<socket interface="management" secure-port="${jboss.management.https.port:9443}"/>
</http-interface>
...
<interfaces>
<interface name="local">
<inet-address value="${jboss.bind.address.local.management:127.0.0.1}"/>
</interface>
<interface name="management">
<inet-address value="${jboss.bind.address.management:jbaesner.remote.csb}"/>
</interface>
</interfaces>
...
{code}
was:
The definition of the _http-interface_ for the _management-interface_ in the wildfly-config_5_0.xsd is defined as:
{code}
<xs:complexType name="host-http-management-interfaceType">
<xs:annotation>
<xs:documentation>
Configuration of a host's exposed HTTP management interface.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="http-management-interfaceType">
<xs:sequence>
<xs:element name="socket" type="host-http-management-socketType"/>
</xs:sequence>
<xs:attribute name="console-enabled" type="xs:boolean" use="optional" default="true"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
{code}
Where _xs:sequence_ has a default definition of:
* *maxOccurs* _Optional._ Specifies the maximum number of times the sequence element can occur in the parent element. The value can be any number >= 0, or if you want to set no limit on the maximum number, use the value "unbounded". Default value is 1
* *minOccurs* _Optional._ Specifies the minimum number of times the sequence element can occur in the parent element. The value can be any number >= 0. Default value is 1
But the parser allows to configure multiple sockets like this:
{code}
...
<security-realm name="ManagementRealm">
<server-identities>
<ssl>
<keystore path="server.keystore" relative-to="jboss.domain.config.dir" keystore-password="******" alias="server"/>
</ssl>
</server-identities>
<authentication>
<properties path="mgmt-users.properties" relative-to="jboss.domain.config.dir"/>
</authentication>
</security-realm>
...
<http-interface security-realm="ManagementRealm">
<http-upgrade enabled="true"/>
<socket interface="local" port="${jboss.management.local.http.port:9990}"/>
<socket interface="management" secure-port="${jboss.management.https.port:9443}"/>
</http-interface>
...
<interfaces>
<interface name="local">
<inet-address value="${jboss.bind.address.local.management:127.0.0.1}"/>
</interface>
<interface name="management">
<inet-address value="${jboss.bind.address.management:jbaesner.remote.csb}"/>
</interface>
</interfaces>
...
{code}
> Multiple <socket> elements inside an http-interface parsed wrongly
> ------------------------------------------------------------------
>
> Key: WFCORE-4269
> URL: https://issues.jboss.org/browse/WFCORE-4269
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 8.0.0.Beta2
> Reporter: Jörg Bäsner
> Assignee: Jeff Mesnil
> Priority: Major
>
> The definition of the _http-interface_ for the _management-interface_ in the {{wildfly-config_5_0.xsd}} is defined as:
> {code}
> <xs:complexType name="host-http-management-interfaceType">
> <xs:annotation>
> <xs:documentation>
> Configuration of a host's exposed HTTP management interface.
> </xs:documentation>
> </xs:annotation>
> <xs:complexContent>
> <xs:extension base="http-management-interfaceType">
> <xs:sequence>
> <xs:element name="socket" type="host-http-management-socketType"/>
> </xs:sequence>
> <xs:attribute name="console-enabled" type="xs:boolean" use="optional" default="true"/>
> </xs:extension>
> </xs:complexContent>
> </xs:complexType>
> {code}
> Where _xs:sequence_ has a default definition of:
> * *maxOccurs* _Optional._ Specifies the maximum number of times the sequence element can occur in the parent element. The value can be any number >= 0, or if you want to set no limit on the maximum number, use the value "unbounded". Default value is 1
> * *minOccurs* _Optional._ Specifies the minimum number of times the sequence element can occur in the parent element. The value can be any number >= 0. Default value is 1
> But the parser allows to configure multiple sockets like this:
> {code}
> ...
> <security-realm name="ManagementRealm">
> <server-identities>
> <ssl>
> <keystore path="server.keystore" relative-to="jboss.domain.config.dir" keystore-password="******" alias="server"/>
> </ssl>
> </server-identities>
> <authentication>
> <properties path="mgmt-users.properties" relative-to="jboss.domain.config.dir"/>
> </authentication>
> </security-realm>
> ...
> <http-interface security-realm="ManagementRealm">
> <http-upgrade enabled="true"/>
> <socket interface="local" port="${jboss.management.local.http.port:9990}"/>
> <socket interface="management" secure-port="${jboss.management.https.port:9443}"/>
> </http-interface>
> ...
> <interfaces>
> <interface name="local">
> <inet-address value="${jboss.bind.address.local.management:127.0.0.1}"/>
> </interface>
> <interface name="management">
> <inet-address value="${jboss.bind.address.management:jbaesner.remote.csb}"/>
> </interface>
> </interfaces>
> ...
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months