[JBoss JIRA] (WFLY-11062) No Multi-Release infinispan-commons-9.3.3.Final-redhat-00001.jar
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/WFLY-11062?page=com.atlassian.jira.plugin... ]
Paul Ferraro commented on WFLY-11062:
-------------------------------------
[~tommaso-borgato] Unless you've already identified a specific team member, direct issues/questions to [~NadirX].
> No Multi-Release infinispan-commons-9.3.3.Final-redhat-00001.jar
> ----------------------------------------------------------------
>
> Key: WFLY-11062
> URL: https://issues.jboss.org/browse/WFLY-11062
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 14.0.1.Final, 15.0.0.Alpha1
> Reporter: tommaso borgato
> Priority: Major
>
> Project {{org.infinispan:infinispan-commons:9.3.3.Final}} contains classes specific for JDK-10.
> In the {{pom.xml}} file there is a {{jdk10-compile}} profile for the multi-release compilation.
> The MANIFEST in jar {{infinispan-commons-9.3.3.Final-redhat-00001.jar}} shipped with {{jboss-eap-7.2.0.CD14.CR1.zip}} does not contain line {{Multi-Release: true}}.
> Note this may be related to JBEAP-15502.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-10241) -secmgr property doesn't work in wsprovide&&wsconsume scripts
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFLY-10241?page=com.atlassian.jira.plugin... ]
Marek Kopecký commented on WFLY-10241:
--------------------------------------
[~jamezp] Security manager support was originally added as a bug-fix in WFLY-9539.
If there is no reason for SM support in wsconsume and wsprovide, current wrong SM support needs to be removed from these scripts. If there is some reason, wrong SM support needs to be fixed. Right?
> -secmgr property doesn't work in wsprovide&&wsconsume scripts
> -------------------------------------------------------------
>
> Key: WFLY-10241
> URL: https://issues.jboss.org/browse/WFLY-10241
> Project: WildFly
> Issue Type: Bug
> Components: Scripts, Web Services
> Reporter: Marek Kopecký
> Assignee: R Searls
> Priority: Major
>
> standalone&&domain&&appclient scripts support {{-secmgr}} command line argument or {{SECMGR=true}} env property, see the details [here|https://github.com/wildfly/wildfly-core/blob/master/core-feature-pac...]
> wsprovide&&wsconsume scripts should be able to use the same configuration settings.
> But scripts behaviour is different in these two scenarios, so {{-secmgr}} command line argument is not handled correctly:
> {noformat}
> [mkopecky@dhcp-10-40-5-128 bin]$ java -version
> java version "1.8.0_162"
> Java(TM) SE Runtime Environment (build 1.8.0_162-b12)
> Java HotSpot(TM) 64-Bit Server VM (build 25.162-b12, mixed mode)
> [mkopecky@dhcp-10-40-5-128 bin]$ export SECMGR=""
> [mkopecky@dhcp-10-40-5-128 bin]$ ./wsconsume.sh -secmgr https://raw.githubusercontent.com/jbossws/jbossws-cxf/master/modules/test...
> Could not find log4j.properties or log4j.xml configuration, logging to console.
> Loading FrontEnd jaxws ...
> Loading DataBinding jaxb ...
> wsdl2java -compile -exsh false -d /home/mkopecky/playground/wf/wfly.23/wfly.23/bin/output/tmp5356716 -verbose -classdir /home/mkopecky/playground/wf/wfly.23/wfly.23/bin/output -allowElementReferences https://raw.githubusercontent.com/jbossws/jbossws-cxf/master/modules/test...
> wsdl2java - Apache CXF 3.2.4
> [mkopecky@dhcp-10-40-5-128 bin]$ export SECMGR="true"
> [mkopecky@dhcp-10-40-5-128 bin]$ ./wsconsume.sh https://raw.githubusercontent.com/jbossws/jbossws-cxf/master/modules/test... not find log4j.properties or log4j.xml configuration, logging to console.
> Loading FrontEnd jaxws ...
> Loading DataBinding jaxb ...
> wsdl2java -compile -exsh false -d /home/mkopecky/playground/wf/wfly.23/wfly.23/bin/output/tmp1569691 -verbose -classdir /home/mkopecky/playground/wf/wfly.23/wfly.23/bin/output -allowElementReferences https://raw.githubusercontent.com/jbossws/jbossws-cxf/master/modules/test...
> wsdl2java - Apache CXF 3.2.4
> JBWS024002: Failed to invoke org.apache.cxf.tools.wsdlto.WSDLToJava
> org.apache.cxf.tools.common.ToolException: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/home/mkopecky/playground/wf/wfly.23/wfly.23/bin/output/tmp1569691/org/openuri/_2004/_04/helloworld/EndpointInterface.java" "read")" in code source "(file:/home/mkopecky/base/jdk1.8.0_162/lib/tools.jar <no signer certificates>)" of "java.net.FactoryURLClassLoader@6fd5717c")
> at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:420)
> at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:105)
> at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113)
> at org.jboss.wsf.stack.cxf.tools.CXFConsumerImpl.consume(CXFConsumerImpl.java:313)
> at org.jboss.ws.tools.cmd.WSConsume.importServices(WSConsume.java:298)
> at org.jboss.ws.tools.cmd.WSConsume.mainInternal(WSConsume.java:108)
> at org.jboss.ws.tools.cmd.WSConsume.main(WSConsume.java:96)
> at org.jboss.modules.Module.runMainMethod(Module.java:348)
> at org.jboss.modules.Module.run(Module.java:328)
> at org.jboss.modules.Main.main(Main.java:557)
> Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/home/mkopecky/playground/wf/wfly.23/wfly.23/bin/output/tmp1569691/org/openuri/_2004/_04/helloworld/EndpointInterface.java" "read")" in code source "(file:/home/mkopecky/base/jdk1.8.0_162/lib/tools.jar <no signer certificates>)" of "java.net.FactoryURLClassLoader@6fd5717c")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:295)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:192)
> at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
> at org.wildfly.security.manager.WildFlySecurityManager.checkRead(WildFlySecurityManager.java:360)
> at java.io.File.isDirectory(File.java:844)
> at com.sun.tools.javac.file.RegularFileObject.<init>(RegularFileObject.java:69)
> at com.sun.tools.javac.file.RegularFileObject.<init>(RegularFileObject.java:64)
> at com.sun.tools.javac.file.JavacFileManager.getJavaFileObjectsFromFiles(JavacFileManager.java:785)
> at com.sun.tools.javac.file.JavacFileManager.getJavaFileObjectsFromStrings(JavacFileManager.java:185)
> at org.apache.cxf.common.util.Compiler.useJava6Compiler(Compiler.java:202)
> at org.apache.cxf.common.util.Compiler.compileFiles(Compiler.java:141)
> at org.apache.cxf.tools.common.ClassUtils.compile(ClassUtils.java:123)
> at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:303)
> at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:164)
> at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:412)
> ... 9 more
> [mkopecky@dhcp-10-40-5-128 bin]$
> {noformat}
> In first example, secmgr is not activated (wrong behaviour, that should be fixed by this jira). In second example, secmgr is activated, exception should be handled in WFLY-10240.
> cc: [~jbliznak]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11221) Agroal datasource cannot be used as DefaultDataSource without connector subsystem
by Martin Simka (Jira)
Martin Simka created WFLY-11221:
-----------------------------------
Summary: Agroal datasource cannot be used as DefaultDataSource without connector subsystem
Key: WFLY-11221
URL: https://issues.jboss.org/browse/WFLY-11221
Project: WildFly
Issue Type: Bug
Components: Agroal, EE, JCA
Affects Versions: 14.0.0.Final
Reporter: Martin Simka
Assignee: Stefano Maestri
If {{datasources}} subsystem is removed and {{Example}} datasource is created in {{datasources-agroal}} subsystem it is expected that Example datasource ({{java:jboss/datasources/ExampleDS}}) is bound to {{java:comp/DefaultDataSource}}, but it is not.
{noformat}
12:33:17,605 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "testwebapplication.war")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.module.testwebapplication.testwebapplication.DefaultDataSource"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.testwebapplication.testwebapplication.env.\"org.jboss.qa.msimka.testwebapp.TestBean\".myDS is missing [jboss.naming.context.java.module.testwebapplication.testwebapplication.DefaultDataSource]"]
}
{noformat}
JNDI of datasource that should be bound to default datasource can be defined in [ee subsystem|http://wildscribe.github.io/WildFly/14.0/subsystem/ee/service/default-bindings/index.html]
Datasources subsystem is currently responsible for DefaultDatasource [binding|https://github.com/wildfly/wildfly/blob/master/connector/src/main...].
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11062) No Multi-Release infinispan-commons-9.3.3.Final-redhat-00001.jar
by tommaso borgato (Jira)
[ https://issues.jboss.org/browse/WFLY-11062?page=com.atlassian.jira.plugin... ]
tommaso borgato updated WFLY-11062:
-----------------------------------
Summary: No Multi-Release infinispan-commons-9.3.3.Final-redhat-00001.jar (was: Missing "Multi-Release: true" in MANIFEST for multirelease jar infinispan-commons jar)
> No Multi-Release infinispan-commons-9.3.3.Final-redhat-00001.jar
> ----------------------------------------------------------------
>
> Key: WFLY-11062
> URL: https://issues.jboss.org/browse/WFLY-11062
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 14.0.1.Final, 15.0.0.Alpha1
> Reporter: tommaso borgato
> Priority: Major
>
> Project {{org.infinispan:infinispan-commons:9.3.3.Final}} contains classes specific for JDK-10.
> In the {{pom.xml}} file there is a {{jdk10-compile}} profile for the multi-release compilation.
> The MANIFEST in jar {{infinispan-commons-9.3.3.Final-redhat-00001.jar}} shipped with {{jboss-eap-7.2.0.CD14.CR1.zip}} does not contain line {{Multi-Release: true}}.
> Note this may be related to JBEAP-15502.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3095) Grid with multiple data/domain object instances
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3095?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-3095:
-------------------------------------
Description:
As user I want to use multiple instances of my DO in a test scenario.
*Implementation specs:*
Implement "Instance" concept on the GIVEN/EXPECTED columns.
Given/Expected columns should have three headers:
# the top one is the group (GIVEN/EXPECTED),
# the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
# the third one is the specific property of the instance.
Below every instance header there could be one ore more property header - each of them belonging to that instance.
The workflow to define template creation is going to change because of the new header level: the user may define the type/name of the instance *before* mapping the final properties, *OR* s/he may define directly a property, in which case the instance is automatically inferred and populated.
When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
When clicking on a Property header, *if* the instance is already defined, user should see only first-level properties of the instance it belongs to; *otherwise* s/he should see every properties of every data objects.
Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.
These issue is related to https://issues.jboss.org/browse/DROOLS-2788
was:
As user I want to use multiple instances of my DO in a test scenario.
*Implementation specs:*
Implement "Instance" concept on the GIVEN/EXPECTED columns.
Given/Expected columns should have three headers:
# the top one is the group (GIVEN/EXPECTED),
# the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
# the third one is the specific property of the instance.
Below every instance header there could be one ore more property header - each of them belonging to that instance.
The workflow to define template creation is going to change because of the new header level: now user must define the type/name of the instance *before* mapping the final properties.
When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
When clicking on a Property header, user should see only first-level properties of the Instance it belongs to.
When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.
These issue is related to https://issues.jboss.org/browse/DROOLS-2788
> Grid with multiple data/domain object instances
> -----------------------------------------------
>
> Key: DROOLS-3095
> URL: https://issues.jboss.org/browse/DROOLS-3095
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
>
> As user I want to use multiple instances of my DO in a test scenario.
> *Implementation specs:*
> Implement "Instance" concept on the GIVEN/EXPECTED columns.
> Given/Expected columns should have three headers:
> # the top one is the group (GIVEN/EXPECTED),
> # the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
> # the third one is the specific property of the instance.
> Below every instance header there could be one ore more property header - each of them belonging to that instance.
> The workflow to define template creation is going to change because of the new header level: the user may define the type/name of the instance *before* mapping the final properties, *OR* s/he may define directly a property, in which case the instance is automatically inferred and populated.
> When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
> When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
> When clicking on a Property header, *if* the instance is already defined, user should see only first-level properties of the instance it belongs to; *otherwise* s/he should see every properties of every data objects.
> Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.
> These issue is related to https://issues.jboss.org/browse/DROOLS-2788
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3154) Minor UI improvements/bugfixes for Scenario
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3154?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi commented on DROOLS-3154:
------------------------------------------
[~uxdlc] [~danielezonca] [~Rikkola]
I've created a specific task for the color modification: https://issues.jboss.org/browse/DROOLS-3164
and updated references with it.
For the future, please do not use jira ticket as placeholder/notebook of every improvement/fix requests, especially ticket marked as "Bug" : it creates a lot of confusion and makes hard to track specific issues.
> Minor UI improvements/bugfixes for Scenario
> -------------------------------------------
>
> Key: DROOLS-3154
> URL: https://issues.jboss.org/browse/DROOLS-3154
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Toni Rikkola
> Priority: Critical
> Labels: UX-CSS
>
> This item contains a list of general UI bugs to be fixed:
> - Use grey borders for all the grid and not only for the header
> - Add some padding to the cells of the grid
> - Add some padding to right panel the tab titles
> - Remove scrolling bar from right panel
> - Review expression editor component HTML/CSS (paddings, indents, etc)
> - Review right panel padding (now it is hardcoded)
> - Use text area inputs instead of text box for inline editing
> - Reduce the width of Index column
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months