[JBoss JIRA] (DROOLS-3077) Enhance data type restrictions UX - Decision Table/properties
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3077?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3077:
-------------------------------------
[~manstis] +1, will discuss. I created another alternative for the discussion:
https://redhat.invisionapp.com/share/SFQT5JRMAQ4
It imposes some limitations:
* If the data type already has constraints, the user will either need to go to the Manage section to work with the data type, or they enter additional Input constraints inline, but only as an expression. Note: I don't think the input expression bit is correct in my mock, so please disregard for now. :)
* I removed the "Apply to Data Type" option in this round. Rather user would need to work with the data type directly in the Manage section.
> Enhance data type restrictions UX - Decision Table/properties
> -------------------------------------------------------------
>
> Key: DROOLS-3077
> URL: https://issues.jboss.org/browse/DROOLS-3077
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E...
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (WFLY-10448) Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh, appclient.sh
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFLY-10448?page=com.atlassian.jira.plugin... ]
Marek Kopecký updated WFLY-10448:
---------------------------------
Affects Version/s: 16.0.0.Final
> Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh, appclient.sh
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-10448
> URL: https://issues.jboss.org/browse/WFLY-10448
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 13.0.0.Final, 16.0.0.Final
> Reporter: R Searls
> Assignee: R Searls
> Priority: Minor
>
> bin\scripts domain.sh, standalone.sh and appclient.sh have a section of code that uses java option -d32 and -d64 when calling java to check the HotSpot type. These 2 options have been removed from JDK-10. They are marked as deprecated in JDK-9 but still function.
> These options are used in determining if '-server' is added to JAVA_OPTS. Enhancements need to be made to the scripts to check the JDK version and take appropriate action is assigning the value '-server'.
> The code affected
> {code:java}
> # Check for -d32/-d64 in JAVA_OPTS
> JVM_OPTVERSION="-version"
> JVM_D64_OPTION=`echo $JAVA_OPTS | $GREP "\-d64"`
> JVM_D32_OPTION=`echo $JAVA_OPTS | $GREP "\-d32"`
> test "x$JVM_D64_OPTION" != "x" && JVM_OPTVERSION="-d64 $JVM_OPTVERSION"
> test "x$JVM_D32_OPTION" != "x" && JVM_OPTVERSION="-d32 $JVM_OPTVERSION"
> # If -server not set in JAVA_OPTS, set it, if supported
> SERVER_SET=`echo $JAVA_OPTS | $GREP "\-server"`
> if [ "x$SERVER_SET" = "x" ]; then
> # Check for SUN(tm) JVM w/ HotSpot support
> if [ "x$HAS_HOTSPOT" = "x" ]; then
> HAS_HOTSPOT=`"$JAVA" $JVM_OPTVERSION -version 2>&1 | $GREP -i HotSpot`
> fi
> # Check for OpenJDK JVM w/server support
> if [ "x$HAS_OPENJDK" = "x" ]; then
> HAS_OPENJDK=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i OpenJDK`
> fi
> # Check for IBM JVM w/server support
> if [ "x$HAS_IBM" = "x" ]; then
> HAS_IBM=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i "IBM J9"`
> fi
> # Enable -server if we have Hotspot or OpenJDK, unless we can't
> if [ "x$HAS_HOTSPOT" != "x" -o "x$HAS_OPENJDK" != "x" -o "x$HAS_IBM" != "x" ]; then
> # MacOS does not support -server flag
> if [ "$darwin" != "true" ]; then
> PROCESS_CONTROLLER_JAVA_OPTS="-server $PROCESS_CONTROLLER_JAVA_OPTS"
> HOST_CONTROLLER_JAVA_OPTS="-server $HOST_CONTROLLER_JAVA_OPTS"
> JVM_OPTVERSION="-server $JVM_OPTVERSION"
> fi
> fi
> else
> JVM_OPTVERSION="-server $JVM_OPTVERSION"
> fi
> {code}
> Here is the output of the currently supported java versions
> Doc for jdk-8 states
> > java -help
> where options include:
> -d32 use a 32-bit data model if available
> -d64 use a 64-bit data model if available
> Using these options tell if the version supports 32-bit or 64-bit
> > java -d32 -version
> Error: This Java instance does not support a 32-bit JVM.
> Please install the desired version.
> > java -d64 -version
> java version "1.8.0_72"
> Java(TM) SE Runtime Environment (build 1.8.0_72-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode)
> Doc for jdk-9 states
> > java -help
> where options include:
> -d32 Deprecated, will be removed in a future release
> -d64 Deprecated, will be removed in a future release
> > java -d32 -version
> Error: This Java instance does not support a 32-bit JVM.
> Please install the desired version.
> > java -d64 -version
> openjdk version "9.0.4"
> OpenJDK Runtime Environment (build 9.0.4+11)
> OpenJDK 64-Bit Server VM (build 9.0.4+11, mixed mode)
> Doc for jdk-10
> > java -help
> No documentation for these options listed
> > java -d32 -version
> Unrecognized option: -d32
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> > java -d64 -version
> Unrecognized option: -d64
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (WFLY-10156) Java EE 7 REST Service not called
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFLY-10156?page=com.atlassian.jira.plugin... ]
Marek Kopecký commented on WFLY-10156:
--------------------------------------
[~viggo.navarsete]: Any update?
> Java EE 7 REST Service not called
> ---------------------------------
>
> Key: WFLY-10156
> URL: https://issues.jboss.org/browse/WFLY-10156
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 12.0.0.Final
> Reporter: Viggo Navarsete
> Assignee: Alessio Soldano
> Priority: Major
>
> Current setup that works:
> Wildfly 10.0.0.Final
> Keycloak 3.4.3.Final
> - Deployed a REST endpoint (/zupplyio-orderservice/orders) to Wildfly 10.0.0.Final
> - Access the endpoint through a React app with a token received from Keycloak.
> - Returns a 200 http response with payload
> - undertow server.log:
> 19:35:33,356 INFO [io.undertow.accesslog] (default task-1) 127.0.0.1 [30/Mar/2018:19:35:33 +0200] "OPTIONS /zupplyio-orderservice/orders HTTP/1.1" 200 "Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Mobile Safari/537.36"
> 19:35:33,994 INFO [stdout] (default task-2) *** Calling getOrders ***
> 19:35:34,121 INFO [io.undertow.accesslog] (default task-2) 127.0.0.1 [30/Mar/2018:19:35:34 +0200] "GET /zupplyio-orderservice/orders HTTP/1.1" 200 "Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Mobile Safari/537.36"
> Setup that doesn't work:
> Wildfly 12.0.0.Final
> Keycloak 3.4.3.Final
> - Deployed a REST endpoint (/zupplyio-orderservice/orders) to Wildfly 10.0.0.Final
> - Access the endpoint through a React app with a token received from Keycloak.
> - Returns a 200 http response with NO payload
> - undertow server.log:
> 19:25:22,707 INFO [io.undertow.accesslog] (default task-1) 127.0.0.1 [30/Mar/2018:19:25:22 +0200] "OPTIONS /zupplyio-orderservice/orders HTTP/1.1" 200 "Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Mobile Safari/537.36"
> 19:25:23,491 INFO [io.undertow.accesslog] (default task-1) 127.0.0.1 [30/Mar/2018:19:25:23 +0200] "GET /zupplyio-orderservice/orders HTTP/1.1" 200 "Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Mobile Safari/537.36"
> As you can see from the server.log, my endpoint is probably not called in Wildfly 12.0.0.Final since the log output isn't written to server.log
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (WFLY-11804) Galleon is not provisioning com.h2database.h2 module
by Yeray Borges (Jira)
[ https://issues.jboss.org/browse/WFLY-11804?page=com.atlassian.jira.plugin... ]
Yeray Borges reassigned WFLY-11804:
-----------------------------------
Assignee: Yeray Borges (was: ehsavoie Hugonnet)
> Galleon is not provisioning com.h2database.h2 module
> ----------------------------------------------------
>
> Key: WFLY-11804
> URL: https://issues.jboss.org/browse/WFLY-11804
> Project: WildFly
> Issue Type: Bug
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Major
>
> We need to ensure that Galleon provision is correct. By default, we are currently using the following data source feature group:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <feature-group-spec name="datasources" xmlns="urn:jboss:galleon:feature-group:1.0">
> <feature spec="subsystem.datasources">
> <feature spec="subsystem.datasources.jdbc-driver">
> <param name="jdbc-driver" value="h2"/>
> <param name="driver-name" value="h2"/>
> <param name="driver-module-name" value="com.h2database.h2"/>
> <param name="driver-xa-datasource-class-name" value="org.h2.jdbcx.JdbcDataSource"/>
> </feature>
> <feature spec="subsystem.datasources.data-source">
> <param name="data-source" value="ExampleDS"/>
> <param name="enabled" value="true"/>
> <param name="use-java-context" value="true"/>
> <param name="jndi-name" value="java:jboss/datasources/ExampleDS"/>
> <param name="data-source" value="ExampleDS"/>
> <param name="connection-url" value=""jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE""/>
> <param name="driver-name" value="h2"/>
> <param name="user-name" value="sa"/>
> <param name="password" value="sa"/>
> <param name="statistics-enabled" value="${wildfly.datasources.statistics-enabled:${wildfly.statistics-enabled:false}}" />
> </feature>
> </feature>
> <feature spec="subsystem.ee.service.default-bindings">
> <param name="datasource" value="java:jboss/datasources/ExampleDS"/>
> </feature>
> </feature-group-spec>
> {code}
> The default driver-module-name is com.h2database.h2, that means com.h2database.h2 must be provisioned by default.
> However, if we use the following Galleon provision, the provision fails:
> {code:xml}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
> <script/>
> <modelVersion>4.0.0</modelVersion>
> <groupId>org.jboss.galleon.demo</groupId>
> <artifactId>galleon-demo</artifactId>
> <packaging>pom</packaging>
> <version>1.0.0-SNAPSHOT</version>
> <name>galleon demo</name>
> <properties>
> <!-- Galleon -->
> <galleon.fork.embedded>true</galleon.fork.embedded>
> <version.org.jboss.galleon>3.0.1.Final</version.org.jboss.galleon>
> </properties>
> <dependencies>
> <dependency>
> <groupId>org.jboss.galleon</groupId>
> <artifactId>galleon-core</artifactId>
> <version>${version.org.jboss.galleon}</version>
> </dependency>
> </dependencies>
> <build>
> <pluginManagement>
> <plugins>
> <plugin>
> <groupId>org.jboss.galleon</groupId>
> <artifactId>galleon-maven-plugin</artifactId>
> <version>${version.org.jboss.galleon}</version>
> </plugin>
> </plugins>
> </pluginManagement>
> <plugins>
> <plugin>
> <groupId>org.jboss.galleon</groupId>
> <artifactId>galleon-maven-plugin</artifactId>
> <executions>
> <execution>
> <id>server-provisioning</id>
> <goals>
> <goal>provision</goal>
> </goals>
> <configuration>
> <install-dir>${project.build.directory}/wildfly</install-dir>
> <record-state>false</record-state>
> <log-time>true</log-time>
> <plugin-options>
> <jboss-maven-dist/>
> <jboss-fork-embedded>${galleon.fork.embedded}</jboss-fork-embedded>
> </plugin-options>
> <feature-packs>
> <feature-pack>
> <groupId>org.wildfly</groupId>
> <artifactId>wildfly-galleon-pack</artifactId>
> <version>16.0.0.Beta1</version>
> <inherit-packages>false</inherit-packages>
> <included-packages>
> <name>org.wildfly.openssl</name>
> <!-- <name>com.h2database.h2</name> -->
> </included-packages>
> <inherit-configs>false</inherit-configs>
> <included-configs>
> <config>
> <model>standalone</model>
> <name>standalone.xml</name>
> </config>
> </included-configs>
> </feature-pack>
> </feature-packs>
> </configuration>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
> <repositories>
> <repository>
> <releases>
> <enabled>true</enabled>
> <updatePolicy>never</updatePolicy>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> <updatePolicy>never</updatePolicy>
> </snapshots>
> <id>jboss-public-repository-group</id>
> <name>JBoss Public Repository Group</name>
> <url>
> http://repository.jboss.org/nexus/content/groups/public/
> </url>
> <layout>default</layout>
> </repository>
> </repositories>
> <pluginRepositories>
> <pluginRepository>
> <releases>
> <enabled>true</enabled>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> <id>jboss-public-repository-group</id>
> <name>JBoss Public Repository Group</name>
> <url>
> http://repository.jboss.org/nexus/content/groups/public/
> </url>
> </pluginRepository>
> </pluginRepositories>
> </project>
> {code}
> org.wildfly.openssl seems to have also a similar issue. Currently we have to explicitely include them
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (WFLY-11804) Galleon is not provisioning com.h2database.h2 module
by Yeray Borges (Jira)
Yeray Borges created WFLY-11804:
-----------------------------------
Summary: Galleon is not provisioning com.h2database.h2 module
Key: WFLY-11804
URL: https://issues.jboss.org/browse/WFLY-11804
Project: WildFly
Issue Type: Bug
Reporter: Yeray Borges
Assignee: ehsavoie Hugonnet
We need to ensure that Galleon provision is correct. By default, we are currently using the following data source feature group:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<feature-group-spec name="datasources" xmlns="urn:jboss:galleon:feature-group:1.0">
<feature spec="subsystem.datasources">
<feature spec="subsystem.datasources.jdbc-driver">
<param name="jdbc-driver" value="h2"/>
<param name="driver-name" value="h2"/>
<param name="driver-module-name" value="com.h2database.h2"/>
<param name="driver-xa-datasource-class-name" value="org.h2.jdbcx.JdbcDataSource"/>
</feature>
<feature spec="subsystem.datasources.data-source">
<param name="data-source" value="ExampleDS"/>
<param name="enabled" value="true"/>
<param name="use-java-context" value="true"/>
<param name="jndi-name" value="java:jboss/datasources/ExampleDS"/>
<param name="data-source" value="ExampleDS"/>
<param name="connection-url" value=""jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE""/>
<param name="driver-name" value="h2"/>
<param name="user-name" value="sa"/>
<param name="password" value="sa"/>
<param name="statistics-enabled" value="${wildfly.datasources.statistics-enabled:${wildfly.statistics-enabled:false}}" />
</feature>
</feature>
<feature spec="subsystem.ee.service.default-bindings">
<param name="datasource" value="java:jboss/datasources/ExampleDS"/>
</feature>
</feature-group-spec>
{code}
The default driver-module-name is com.h2database.h2, that means com.h2database.h2 must be provisioned by default.
However, if we use the following Galleon provision, the provision fails:
{code:xml}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<script/>
<modelVersion>4.0.0</modelVersion>
<groupId>org.jboss.galleon.demo</groupId>
<artifactId>galleon-demo</artifactId>
<packaging>pom</packaging>
<version>1.0.0-SNAPSHOT</version>
<name>galleon demo</name>
<properties>
<!-- Galleon -->
<galleon.fork.embedded>true</galleon.fork.embedded>
<version.org.jboss.galleon>3.0.1.Final</version.org.jboss.galleon>
</properties>
<dependencies>
<dependency>
<groupId>org.jboss.galleon</groupId>
<artifactId>galleon-core</artifactId>
<version>${version.org.jboss.galleon}</version>
</dependency>
</dependencies>
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.jboss.galleon</groupId>
<artifactId>galleon-maven-plugin</artifactId>
<version>${version.org.jboss.galleon}</version>
</plugin>
</plugins>
</pluginManagement>
<plugins>
<plugin>
<groupId>org.jboss.galleon</groupId>
<artifactId>galleon-maven-plugin</artifactId>
<executions>
<execution>
<id>server-provisioning</id>
<goals>
<goal>provision</goal>
</goals>
<configuration>
<install-dir>${project.build.directory}/wildfly</install-dir>
<record-state>false</record-state>
<log-time>true</log-time>
<plugin-options>
<jboss-maven-dist/>
<jboss-fork-embedded>${galleon.fork.embedded}</jboss-fork-embedded>
</plugin-options>
<feature-packs>
<feature-pack>
<groupId>org.wildfly</groupId>
<artifactId>wildfly-galleon-pack</artifactId>
<version>16.0.0.Beta1</version>
<inherit-packages>false</inherit-packages>
<included-packages>
<name>org.wildfly.openssl</name>
<!-- <name>com.h2database.h2</name> -->
</included-packages>
<inherit-configs>false</inherit-configs>
<included-configs>
<config>
<model>standalone</model>
<name>standalone.xml</name>
</config>
</included-configs>
</feature-pack>
</feature-packs>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
<repositories>
<repository>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</snapshots>
<id>jboss-public-repository-group</id>
<name>JBoss Public Repository Group</name>
<url>
http://repository.jboss.org/nexus/content/groups/public/
</url>
<layout>default</layout>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
<id>jboss-public-repository-group</id>
<name>JBoss Public Repository Group</name>
<url>
http://repository.jboss.org/nexus/content/groups/public/
</url>
</pluginRepository>
</pluginRepositories>
</project>
{code}
org.wildfly.openssl seems to have also a similar issue. Currently we have to explicitely include them
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (WFLY-11803) Capabilities registered when the model is being populated are not recorded in the Galleon feature-spec
by Yeray Borges (Jira)
Yeray Borges created WFLY-11803:
-----------------------------------
Summary: Capabilities registered when the model is being populated are not recorded in the Galleon feature-spec
Key: WFLY-11803
URL: https://issues.jboss.org/browse/WFLY-11803
Project: WildFly
Issue Type: Bug
Reporter: Yeray Borges
Assignee: Yeray Borges
Specifically, capabilities registered in recordCapabilitiesAndRequirements are not recorded in the Galleon feature-specs.
The reason is Galleon generates the feature specs using the metamodel instead of the effective model. The metamodel is the resource definitions and the effective model is the current configuration created once the model is populated with all the attribute values.
recordCapabilitiesAndRequirements is executed when the model is populated, then, capabilities defined there are not exposed in the Galleon feature-specs.
The goal here is to identify which capabilities are affected and rework them, for example moving them to the resource definition itself, to allow Galleon to record them in the feature-specs.
Some capabilities could require a different work if they cannot be moved out from recordCapabilitiesAndRequirements.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months