[JBoss JIRA] (WFLY-9747) wildfly-arquillian-container-managed: java.lang.ClassNotFoundException: org.wildfly.security.permission.AbstractNameSetOnlyPermission
by Niels Bertram (JIRA)
[ https://issues.jboss.org/browse/WFLY-9747?page=com.atlassian.jira.plugin.... ]
Niels Bertram commented on WFLY-9747:
-------------------------------------
I could only get arquillian 1.4.0.Final to work with wildfly-elytron 1.1.10.Final when using Wildfly 13
{code:xml}
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss.arquillian</groupId>
<artifactId>arquillian-bom</artifactId>
<version>1.4.0.Final</version>
<scope>import</scope>
<type>pom</type>
</dependency>
<dependency>
<groupId>org.wildfly.arquillian</groupId>
<artifactId>wildfly-arquillian-container-managed</artifactId>
<version>2.1.1.Final</version>
</dependency>
<dependency>
<!-- TODO Workaround to fix wildfly-arquillian-container-managed https://issues.jboss.org/browse/WFLY-9747 -->
<groupId>org.wildfly.security</groupId>
<artifactId>wildfly-elytron</artifactId>
<version>1.1.10.Final</version>
</dependency>
</dependencies>
</dependencyManagement>
{code}
> wildfly-arquillian-container-managed: java.lang.ClassNotFoundException: org.wildfly.security.permission.AbstractNameSetOnlyPermission
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9747
> URL: https://issues.jboss.org/browse/WFLY-9747
> Project: WildFly
> Issue Type: Bug
> Reporter: Geoffrey De Smet
> Assignee: Jason Greene
>
> On a pretty vanilla war file with a bit JAX-RS and arquillian, I get this error when trying to run an arquillian test (that worked before we upgraded the wildfly version):
> {code}
> [INFO] Running org.optaplanner.openshift.employeerostering.webapp.skill.SkillRestServiceTest
> Jan 31, 2018 7:52:20 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal
> WARNING: Bundles path is deprecated and no longer used.
> Jan 31, 2018 7:52:20 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal
> INFO: Starting container with: [/usr/lib/jvm/java-openjdk/bin/java, -D[Standalone], -Djboss.socket.binding.port-offset=10000, -Xms512m, -Xmx1024m, -XX:MaxPermSize=512m, -ea, -Djboss.home.dir=/home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final, -Dorg.jboss.boot.log.file=/home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final/standalone/log/server.log, -Dlogging.configuration=file:/home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final/standalone/configuration/logging.properties, -jar, /home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final/jboss-modules.jar, -mp, /home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final, -Djboss.server.base.dir=/home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final/standalone, -Djboss.server.log.dir=/home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final/standalone/log, -Djboss.server.config.dir=/home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final/standalone/configuration]
> OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.449 s <<< FAILURE! - in org.optaplanner.openshift.employeerostering.webapp.skill.SkillRestServiceTest
> [ERROR] org.optaplanner.openshift.employeerostering.webapp.skill.SkillRestServiceTest Time elapsed: 0.448 s <<< ERROR!
> java.lang.NoClassDefFoundError: org/wildfly/security/permission/AbstractNameSetOnlyPermission
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> Caused by: java.lang.ClassNotFoundException: org.wildfly.security.permission.AbstractNameSetOnlyPermission
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> {code}
> With this parent pom:
> {code}
> <properties>
> <version.org.jboss.arquillian>1.2.1.Final</version.org.jboss.arquillian>
> <version.org.wildfly.arquillian>2.1.0.Final</version.org.wildfly.arquillian>
> <version.org.jboss.resteasy>3.1.4.Final</version.org.jboss.resteasy>
> </properties>
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.jboss.arquillian</groupId>
> <artifactId>arquillian-bom</artifactId>
> <version>${version.org.jboss.arquillian}</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> <dependency>
> <groupId>org.wildfly.arquillian</groupId>
> <artifactId>wildfly-arquillian-container-managed</artifactId>
> <version>${version.org.wildfly.arquillian}</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.resteasy</groupId>
> <artifactId>resteasy-client</artifactId>
> <version>${version.org.jboss.resteasy}</version>
> </dependency>
> ...
> {code}
> and this child pom:
> {code}
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.jboss.arquillian.junit</groupId>
> <artifactId>arquillian-junit-container</artifactId>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.jboss.shrinkwrap.resolver</groupId>
> <artifactId>shrinkwrap-resolver-depchain</artifactId>
> <type>pom</type>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.wildfly.arquillian</groupId>
> <artifactId>wildfly-arquillian-container-managed</artifactId>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.jboss.resteasy</groupId>
> <artifactId>resteasy-client</artifactId>
> <scope>test</scope>
> </dependency>
> {code}
> I am probably not using a correct version combination of arquillian and wildfly, but for mere mortals such as myself it takes days to find a working versions combination of arquillian and wildfly - everytime I need to upgrade wildfly. (The arquillian guides and arquillian-showcase-jaxrs are all hopelessly outdated in this aspect, they still mention jboss-as (= wildfly 7)).
> Solution proposal A)
> wildfly-arquillian-managed should automatically detect that it's a wrong version combination and give an error message like "I am not build to work with version x, but it seems like you're combining me with version y."
> Solution proposal B)
> Use the same version numbers for wildfly-arquillian-container-managed (currently 2.1.0.Final) as for wildfly.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2738) Create a simple, structured or compound data type
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2738?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2738:
--------------------------------
Description:
We're trying to solve two big issues with this dialog: I) the definition of a simple (basic) data type; and II) the definition of a structured data type.
The first one is kind of easy, we just need to provide to the user an input and a select, in order to capture the name and the type of a simple data type. Here some examples of four simple data types:
The second problem is a little bit more difficult. Because the user needs to be able to define complex data types, with nested structures. For example, the user can create a data type called Person with 3 nested fields (they are simple data types):
Person
name (Text)
age (Number)
email (Text)
Additionally, a structured data type can have other complex nested data types, like:
Person
name (Text)
age (Number)
email (Text)
address (Address)
street (Text)
city (Text)
country (Text)
The approach that you adopted to solve the scenario above was to express these nested levels using text:
..which is pretty interesting. But, the example that we're handling here has only one level of nesting (Address), and Edson is concerned about situations where we're going to have many levels of nesting and many fields. Something like this:
Person
name (Text)
age (Number)
email (Text)
address (Address)
Something (Something)
field1 (Text)
field2 (Text)
field3 (Text)
field4 (Text)
field5 (Text)
field6 (Text)
field7 (Text)
field8 (Text)
Something (Something)
field1 (Text)
field2 (Text)
field3 (Text)
field4 (Text)
field5 (Text)
field6 (Text)
field7 (Text)
field8 (Text)
Something (Something)
field1 (Text)
field2 (Text)
field3 (Text)
field4 (Text)
field5 (Text)
field6 (Text)
Something (Something)
field1 (Text)
Something (Something)
field1 (Text)
Edson thinks that the user should be able to: a) navigate between levels; b) expand/collapse nested types; c) create complex data structures easily.
That said, we need a different approach to handle this kind of complex structure. Maybe we could adopt the tree view prototypes and improve them, maybe we could use a breadcrumb to navigate between levels, or maybe we can have another idea
> Create a simple, structured or compound data type
> -------------------------------------------------
>
> Key: DROOLS-2738
> URL: https://issues.jboss.org/browse/DROOLS-2738
> Project: Drools
> Issue Type: Sub-task
> Reporter: Liz Clayton
> Assignee: Liz Clayton
>
> We're trying to solve two big issues with this dialog: I) the definition of a simple (basic) data type; and II) the definition of a structured data type.
> The first one is kind of easy, we just need to provide to the user an input and a select, in order to capture the name and the type of a simple data type. Here some examples of four simple data types:
> The second problem is a little bit more difficult. Because the user needs to be able to define complex data types, with nested structures. For example, the user can create a data type called Person with 3 nested fields (they are simple data types):
> Person
> name (Text)
> age (Number)
> email (Text)
> Additionally, a structured data type can have other complex nested data types, like:
> Person
> name (Text)
> age (Number)
> email (Text)
> address (Address)
> street (Text)
> city (Text)
> country (Text)
> The approach that you adopted to solve the scenario above was to express these nested levels using text:
> ..which is pretty interesting. But, the example that we're handling here has only one level of nesting (Address), and Edson is concerned about situations where we're going to have many levels of nesting and many fields. Something like this:
> Person
> name (Text)
> age (Number)
> email (Text)
> address (Address)
> Something (Something)
> field1 (Text)
> field2 (Text)
> field3 (Text)
> field4 (Text)
> field5 (Text)
> field6 (Text)
> field7 (Text)
> field8 (Text)
> Something (Something)
> field1 (Text)
> field2 (Text)
> field3 (Text)
> field4 (Text)
> field5 (Text)
> field6 (Text)
> field7 (Text)
> field8 (Text)
> Something (Something)
> field1 (Text)
> field2 (Text)
> field3 (Text)
> field4 (Text)
> field5 (Text)
> field6 (Text)
> Something (Something)
> field1 (Text)
> Something (Something)
> field1 (Text)
> Edson thinks that the user should be able to: a) navigate between levels; b) expand/collapse nested types; c) create complex data structures easily.
> That said, we need a different approach to handle this kind of complex structure. Maybe we could adopt the tree view prototypes and improve them, maybe we could use a breadcrumb to navigate between levels, or maybe we can have another idea
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2728:
--------------------------------
Sprint: 2018 Week 27-29
> UX for custom data-types
> ------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, Screen Shot 2018-07-13 at 11.26.43 AM.png, Screen Shot 2018-07-13 at 11.34.15 AM.png, nested.png, prop-panel.png
>
>
> As a practitioner I want to be able to:
> * select an existing data type
> * create a simple or structured data type
> * create a “compound” (or complex) data type, easily.
> *
expand/collapse views of compound data types, so that I can___
> *
navigate between levels in a compound data type, so that I can___
> * edit an existing data type
> * remove an existing data type
>
…so that I can use the data type when creating a decision related asset.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years