February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2338) MemoryFileSystem losts contents of files all DRL scripts become "empty" if directory contains a space character

by Alexander Kotikhov (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2338?page=com.atlassian.jira.plugi... ] Alexander Kotikhov updated DROOLS-2338: --------------------------------------- Steps to Reproduce: Create directory with space character. Put any *.drl files there. {code:java} private KieContainer createKieContainer() throws IOException { final KieServices kieServices = KieServices.get(); final KieFileSystem fs = kieServices.newKieFileSystem(); // iterate all files ResourcePatternResolver resourcePatternResolver = new PathMatchingResourcePatternResolver(); final Resource[] resources = resourcePatternResolver.getResources(baseDirectory + "*.drl"); for (Resource res : resources) { logger.info("Add file to build " + res.getFilename()); fs.write(ResourceFactory.newUrlResource(res.getURL())); } KieBuilder kieBuilder = kieServices.newKieBuilder(fs); kieBuilder.buildAll(); KieModule kieModule = kieBuilder.getKieModule(); return kieServices.newKieContainer(kieModule.getReleaseId()); } {code} then try to use createKieContainer() - no rules exists. was: Create directory with space character. Put any *.drl files there. {code:java} private KieContainer createKieContainer() throws IOException { final KieServices kieServices = KieServices.get(); final KieFileSystem fs = kieServices.newKieFileSystem(); // iterate all files ResourcePatternResolver resourcePatternResolver = new PathMatchingResourcePatternResolver(); final Resource[] resources = resourcePatternResolver.getResources(baseDirectory + "*.drl"); for (Resource res : resources) { logger.info("Add file to build " + res.getFilename()); fs.write(ResourceFactory.newUrlResource(res.getURL())); } KieBuilder kieBuilder = kieServices.newKieBuilder(fs); kieBuilder.buildAll(); KieModule kieModule = kieBuilder.getKieModule(); return kieServices.newKieContainer(kieModule.getReleaseId()); } {code} > MemoryFileSystem losts contents of files all DRL scripts become "empty" if directory contains a space character > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2338 > URL: https://issues.jboss.org/browse/DROOLS-2338 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.4.1.Final, 7.5.0.Final, 7.6.0.Final > Environment: any > Reporter: Alexander Kotikhov > Assignee: Mario Fusco > Attachments: Снимок экрана от 2018-02-19 18-08-49.png > > > If a directory where any files are placed contains spaces > MemoryFileSystem.getFile(String path) returns object with truncated name. > To fix this error (in version 7.4.0) it is nessassary line 107 > *String name = decode( path ).substring( lastSlashPos + 1 );* > replace with > *String name = decode( path.substring( lastSlashPos + 1 ) );* -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2338) MemoryFileSystem losts contents of files all DRL scripts become "empty" if directory contains a space character

by Alexander Kotikhov (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2338?page=com.atlassian.jira.plugi... ] Alexander Kotikhov updated DROOLS-2338: --------------------------------------- Steps to Reproduce: Create directory with space character. Put any *.drl files there. {code:java} private KieContainer createKieContainer() throws IOException { final KieServices kieServices = KieServices.get(); final KieFileSystem fs = kieServices.newKieFileSystem(); // iterate all files ResourcePatternResolver resourcePatternResolver = new PathMatchingResourcePatternResolver(); final Resource[] resources = resourcePatternResolver.getResources(baseDirectory + "*.drl"); for (Resource res : resources) { logger.info("Add file to build " + res.getFilename()); fs.write(ResourceFactory.newUrlResource(res.getURL())); } KieBuilder kieBuilder = kieServices.newKieBuilder(fs); kieBuilder.buildAll(); KieModule kieModule = kieBuilder.getKieModule(); return kieServices.newKieContainer(kieModule.getReleaseId()); } {code} then try to use createKieContainer() - no rules exist. was: Create directory with space character. Put any *.drl files there. {code:java} private KieContainer createKieContainer() throws IOException { final KieServices kieServices = KieServices.get(); final KieFileSystem fs = kieServices.newKieFileSystem(); // iterate all files ResourcePatternResolver resourcePatternResolver = new PathMatchingResourcePatternResolver(); final Resource[] resources = resourcePatternResolver.getResources(baseDirectory + "*.drl"); for (Resource res : resources) { logger.info("Add file to build " + res.getFilename()); fs.write(ResourceFactory.newUrlResource(res.getURL())); } KieBuilder kieBuilder = kieServices.newKieBuilder(fs); kieBuilder.buildAll(); KieModule kieModule = kieBuilder.getKieModule(); return kieServices.newKieContainer(kieModule.getReleaseId()); } {code} then try to use createKieContainer() - no rules exists. > MemoryFileSystem losts contents of files all DRL scripts become "empty" if directory contains a space character > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2338 > URL: https://issues.jboss.org/browse/DROOLS-2338 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.4.1.Final, 7.5.0.Final, 7.6.0.Final > Environment: any > Reporter: Alexander Kotikhov > Assignee: Mario Fusco > Attachments: Снимок экрана от 2018-02-19 18-08-49.png > > > If a directory where any files are placed contains spaces > MemoryFileSystem.getFile(String path) returns object with truncated name. > To fix this error (in version 7.4.0) it is nessassary line 107 > *String name = decode( path ).substring( lastSlashPos + 1 );* > replace with > *String name = decode( path.substring( lastSlashPos + 1 ) );* -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2338) MemoryFileSystem losts contents of files all DRL scripts become "empty" if directory contains a space character

by Alexander Kotikhov (JIRA)

Alexander Kotikhov created DROOLS-2338: ------------------------------------------ Summary: MemoryFileSystem losts contents of files all DRL scripts become "empty" if directory contains a space character Key: DROOLS-2338 URL: https://issues.jboss.org/browse/DROOLS-2338 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.6.0.Final, 7.5.0.Final, 7.4.1.Final Environment: any Reporter: Alexander Kotikhov Assignee: Mario Fusco Attachments: Снимок экрана от 2018-02-19 18-08-49.png If a directory where any files are placed contains spaces MemoryFileSystem.getFile(String path) returns object with truncated name. To fix this error (in version 7.4.0) it is nessassary line 107 *String name = decode( path ).substring( lastSlashPos + 1 );* replace with *String name = decode( path.substring( lastSlashPos + 1 ) );* -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6375) Identify colliding JBoss modules WRT JEP 200, section 6

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6375?page=com.atlassian.jira.plugin.... ] Tomaz Cerar resolved WFLY-6375. ------------------------------- Fix Version/s: 13.0.0.Beta1 Resolution: Done JDK 11 doesn't contain jave.se.ee modules anymore. > Identify colliding JBoss modules WRT JEP 200, section 6 > ------------------------------------------------------- > > Key: WFLY-6375 > URL: https://issues.jboss.org/browse/WFLY-6375 > Project: WildFly > Issue Type: Sub-task > Affects Versions: 10.0.0.Final > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 13.0.0.Beta1 > > > JKD9 with jigsaw throws ClassNotFound exception if we're trying to 'override/enrich' JDK9 exported packages. This is collision with JEP 200, section 6: *A non-standard module must not export any standard API packages. A non-standard module may grant implied readability to a standard module.* -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9851) Remove security dependency on clustering subsystem / infinispan

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9851?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9851: --------------------------------- Summary: Remove security dependency on clustering subsystem / infinispan (was: Remove secuity dependancy on clustering subsystem / infinispan) > Remove security dependency on clustering subsystem / infinispan > --------------------------------------------------------------- > > Key: WFLY-9851 > URL: https://issues.jboss.org/browse/WFLY-9851 > Project: WildFly > Issue Type: Task > Components: Clustering, Domain Management, Security > Reporter: Tomaz Cerar > Assignee: Paul Ferraro > Priority: Critical > > Currently security subsystem depends on clustering subsystem modules which bring in a big transitive dependency tree (that cannot be broken). > Dependency is there only to establish capability requirements. > Please change code to use string constants instead of enums from clustering subsystem to break down the dependency tree. Whole reason for capabilities was to not have tightly coupled subsystems. > current sip from security subsystem dependency tree > {noformat} > [INFO] +- org.wildfly:wildfly-clustering-infinispan-spi:jar:12.0.0.Beta2-SNAPSHOT:compile > [INFO] | +- org.wildfly:wildfly-clustering-common:jar:12.0.0.Beta2-SNAPSHOT:compile > [INFO] | | +- org.wildfly:wildfly-clustering-service:jar:12.0.0.Beta2-SNAPSHOT:compile > [INFO] | | \- org.wildfly:wildfly-naming:jar:12.0.0.Beta2-SNAPSHOT:compile > [INFO] | | +- org.wildfly:wildfly-naming-client:jar:1.0.7.Final:compile > [INFO] | | | +- org.wildfly.client:wildfly-client-config:jar:1.0.0.Final:compile > [INFO] | | | \- org.jboss.marshalling:jboss-marshalling-river:jar:2.0.2.Final:compile > [INFO] | | \- org.wildfly.wildfly-http-client:wildfly-http-naming-client:jar:1.0.9.Final:compile > [INFO] | | +- org.wildfly.wildfly-http-client:wildfly-http-client-common:jar:1.0.9.Final:compile > [INFO] | | +- org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:jar:1.0.1.Final:compile > [INFO] | | \- org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.1.1.Final:compile > [INFO] | +- org.wildfly:wildfly-clustering-marshalling-spi:jar:12.0.0.Beta2-SNAPSHOT:compile > [INFO] | | \- org.wildfly:wildfly-clustering-marshalling-api:jar:12.0.0.Beta2-SNAPSHOT:compile > [INFO] | +- org.infinispan:infinispan-core:jar:9.1.6.Final:compile > [INFO] | | \- org.infinispan:infinispan-commons:jar:9.1.6.Final:compile > [INFO] | \- com.github.ben-manes.caffeine:caffeine:jar:2.6.1:compile > {noformat} > we even bring in inifinspan, as otherwise it does not compile. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-180) Update all spec artifacts to be compatible with JDK9

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/JBEE-180?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar resolved JBEE-180. ------------------------------ Resolution: Done > Update all spec artifacts to be compatible with JDK9 > ---------------------------------------------------- > > Key: JBEE-180 > URL: https://issues.jboss.org/browse/JBEE-180 > Project: JBoss JavaEE Spec APIs > Issue Type: Task > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > Currently JBMS fails to create automodule name out of our artifacts as we have version of the spec in the name of the jar. > Elegant solution would be to add Automatic-Module-Name manifest entry to the artifacts. > Biggest question is what name of the module should be. > One of suggestions was that until we have offical EG guidline what module name for such spec jars should be, we could use "beta." prefix to note that this name wont be there to stay. > If spec API is one that is upgradable in JDK itself (such as java.transaction) we should use same name that is already used in JDK. > But before we go on and do that, we should make sure that such jars work with jdk9 at all, as there is already known issue with JTA see http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-July/008779.html for more details. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-24) Request Access to Openshift Organization on Github

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-24?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo updated SWSQE-24: ----------------------------------------- Description: Cucushift is a "closed" repository on Openshift.org We need access to play with it. > Request Access to Openshift Organization on Github > -------------------------------------------------- > > Key: SWSQE-24 > URL: https://issues.jboss.org/browse/SWSQE-24 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Peter Ruan > > Cucushift is a "closed" repository on Openshift.org > We need access to play with it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-24) Request Access to Openshift Organization on Github

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-24?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo updated SWSQE-24: ----------------------------------------- Summary: Request Access to Openshift Organization on Github (was: Request Access on Openshift org on Github) > Request Access to Openshift Organization on Github > -------------------------------------------------- > > Key: SWSQE-24 > URL: https://issues.jboss.org/browse/SWSQE-24 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Peter Ruan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3619) the endpoint configuration w/o parameters is not persisted in the configuration

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3619?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3619: ------------------------------------------ Looks like there's a minor persistence issue related to the 'endpoint' attributes resulting from WFCORE-3327. Either we shouldn't include an empty 'endpoint' element in our standard configs are we should persist one regardless of whether any of the attributes in the group that xml element represents are defined. I believe the latter is non-standard behavior so I think the fix is the former. > the endpoint configuration w/o parameters is not persisted in the configuration > ------------------------------------------------------------------------------- > > Key: WFCORE-3619 > URL: https://issues.jboss.org/browse/WFCORE-3619 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Reporter: Alexey Loubyansky > Assignee: Brian Stansberry > > This looks like a regression. Creating a server config from scratch by executing operations I see that the endpoint configuration has disappeared from the config although the add operation is executed. In fact I noticed that I can execute the add operations as many times as I want w/o an error. The config file is re-written after every add but the endpoint element is not added. > {code:java} > [standalone@localhost:9990 /] /subsystem=remoting/configuration=endpoint:add > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=remoting/configuration=endpoint:add > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=remoting/configuration=endpoint:add > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=remoting/configuration=endpoint:add > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=remoting/configuration=endpoint:add > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=remoting/configuration=endpoint:add > {"outcome" => "success"} > {code} > {code:java} > <subsystem xmlns="urn:jboss:domain:remoting:4.0"> > <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/> > </subsystem> > {code} > Note, that if I add a worker as a param, it will persist the endpoint config. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-24) Request Access on Openshift org on Github

by Guilherme Baufaker Rêgo (JIRA)

Guilherme Baufaker Rêgo created SWSQE-24: -------------------------------------------- Summary: Request Access on Openshift org on Github Key: SWSQE-24 URL: https://issues.jboss.org/browse/SWSQE-24 Project: Swift Sunshine QE Issue Type: Task Reporter: Guilherme Baufaker Rêgo Assignee: Peter Ruan -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 February 2018