January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7847) [GSS](7.1.0) jboss-web.xml overlay option not honroed

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-7847: ---------------------------------- Summary: [GSS](7.1.0) jboss-web.xml overlay option not honroed Key: WFLY-7847 URL: https://issues.jboss.org/browse/WFLY-7847 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 10.1.0.Final Reporter: Brad Maxwell Assignee: Stuart Douglas The overlay option in jboss-web_10_0.xsd not honored: {code} The overlay element specifies additional static files overlays for this web application. The content of the element should be a folder in the filesystem containing the static files that will overlay the webapp's static files, similar to what happens with regular JAR overlays. {code} {code} <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_10_0.xsd" version="10.0"> <overlay>/home/web/content</overlay> </jboss-web> {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7846) jboss-web.xml overlay option not honroed

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-7846: ---------------------------------- Summary: jboss-web.xml overlay option not honroed Key: WFLY-7846 URL: https://issues.jboss.org/browse/WFLY-7846 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 10.1.0.Final Reporter: Brad Maxwell Assignee: Stuart Douglas The overlay option in jboss-web_10_0.xsd not honored: {code} The overlay element specifies additional static files overlays for this web application. The content of the element should be a folder in the filesystem containing the static files that will overlay the webapp's static files, similar to what happens with regular JAR overlays. {code} {code} <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_10_0.xsd" version="10.0"> <overlay>/home/web/content</overlay> </jboss-web> {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1392) Boolean cells in decision tables are not correctly formatted with Apache POI 3.15

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1392?page=com.atlassian.jira.plugi... ] Mario Fusco edited comment on DROOLS-1392 at 1/2/17 11:59 AM: -------------------------------------------------------------- Fixed on branch 6.5.x by https://github.com/droolsjbpm/drools/commit/156d8ed00457ac3651bc556386689... This fix cannot be forward ported to master yet because it uses a method introduced with POI 3.15 and master is still using 3.13. was (Author: mfusco): Fixed on branch 6.5.x by https://github.com/droolsjbpm/drools/commit/156d8ed00457ac3651bc556386689... This fix cannot be forwarded port to master yet because it uses a method introduced with POI 3.15 and master is still using 3.13. > Boolean cells in decision tables are not correctly formatted with Apache POI 3.15 > --------------------------------------------------------------------------------- > > Key: DROOLS-1392 > URL: https://issues.jboss.org/browse/DROOLS-1392 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > > Using Apache POI 3.15 cells of type Boolean are formatted as "TRUE" or "FALSE" instead of "true" or "false" and this leads to generate an invalid drl that will raise compilation errors like the following > {code} > Rule Compilation error : [Rule name='Spreadsheet Example_11'] > rule_table/Rule_Spreadsheet_Example_11413427566.java (7:503) : FALSE cannot be resolved to a variable > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1392) Boolean cells in decision tables are not correctly formatted with Apache POI 3.15

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1392?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1392: ------------------------------------- Fixed on branch 6.5.x by https://github.com/droolsjbpm/drools/commit/156d8ed00457ac3651bc556386689... This fix cannot be forwarded port to master yet because it uses a method introduced with POI 3.15 and master is still using 3.13. > Boolean cells in decision tables are not correctly formatted with Apache POI 3.15 > --------------------------------------------------------------------------------- > > Key: DROOLS-1392 > URL: https://issues.jboss.org/browse/DROOLS-1392 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > > Using Apache POI 3.15 cells of type Boolean are formatted as "TRUE" or "FALSE" instead of "true" or "false" and this leads to generate an invalid drl that will raise compilation errors like the following > {code} > Rule Compilation error : [Rule name='Spreadsheet Example_11'] > rule_table/Rule_Spreadsheet_Example_11413427566.java (7:503) : FALSE cannot be resolved to a variable > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1392) Boolean cells in decision tables are not correctly formatted with Apache POI 3.15

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1392: ----------------------------------- Summary: Boolean cells in decision tables are not correctly formatted with Apache POI 3.15 Key: DROOLS-1392 URL: https://issues.jboss.org/browse/DROOLS-1392 Project: Drools Issue Type: Bug Reporter: Mario Fusco Assignee: Mario Fusco Using Apache POI 3.15 cells of type Boolean are formatted as "TRUE" or "FALSE" instead of "true" or "false" and this leads to generate an invalid drl that will raise compilation errors like the following {code} Rule Compilation error : [Rule name='Spreadsheet Example_11'] rule_table/Rule_Spreadsheet_Example_11413427566.java (7:503) : FALSE cannot be resolved to a variable {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-599) kjar archertype

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-599?page=com.atlassian.jira.plugin... ] Matteo Mortari commented on DROOLS-599: --------------------------------------- Hi [~mbiarnes] , in reference to my previous comment above, and now discussing with [~mfusco] , we would like to highlight the availability of the Kie Archetype to end users. However, [since this archetype was first proposed|https://github.com/droolsjbpm/droolsjbpm-knowledge/pull/74/files...], now [License file-headers are attached to all files|https://github.com/droolsjbpm/droolsjbpm-knowledge/commit/7172a50c4...]; with the actual consequence that once you use the archetype, as a user, your files are containing the Red Hat file-header license; and I believe this could be very confusing for the end-users, and also I believe is wrong. My proposal is to remove License file-headers, at least from all files which are serving as a template-generation. I have two question, please? # Do you agree with me reverting your change? # Did you notice the License file-headers are missing thanks to some automatic tool? Is there a way to manage exclusion, either in the tool or by adding a special header to the file itself? Thank you in advance for your feedback. > kjar archertype > --------------- > > Key: DROOLS-599 > URL: https://issues.jboss.org/browse/DROOLS-599 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.1.0.Final > Reporter: Matteo Mortari > Assignee: Mario Fusco > Fix For: 6.2.0.CR1 > > > I'm opening this JIRA as I will later open PR related to https://groups.google.com/d/msg/drools-development/uO17-kC4mvc/aBRunEcZ_b4J > The version of the archetype defaults for non-CEP, non-Eclipse plugin in pom. There are property which user can change default value to have CEP, and Eclipse plug-in. > For reference, > * Set-up the new project's pom: > ** Change Java version to 1.6 or greater, by including the maven-compiler-plugin > ** Add Drools dependencies > ** Change JUnit dependencies to version 4 > ** Add kie-maven-plugin > ** [option] Add plug-in org.eclipse.m2e/lifecycle-mapping settings, to avoid Eclipse ERROR at the pom.xml line defining the kie-maven-plugin > ** Set packaging to 'kjar' > * ( ALT + F5 in betweens ) > * Creation of an initial .drl file in src/main/resources > * Creation of minimal kmodule.xml in src/main/resources/META-INF directory > * Create a simple JUnit test for: > ** Creation of KieBase [option ->] with STREAM option for CEP features > ** Creation of KieSession [option ->] with pseudo-clock > ** [option: Advance] / Insert / Fire template > ** ... and other verification/output patterns > * Include SLF4J and LOG4J binding for logging, including a log4j.properties file in src/test/resources -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7841) ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context.

by Tibor Digana (JIRA)

[ https://issues.jboss.org/browse/WFLY-7841?page=com.atlassian.jira.plugin.... ] Tibor Digana commented on WFLY-7841: ------------------------------------ I have created a project in my public repository. https://github.com/Tibor17/issue-7841 > ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context. > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-7841 > URL: https://issues.jboss.org/browse/WFLY-7841 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: Tibor Digana > Assignee: Stuart Douglas > > The problem is that _EntityManager_ does not have managed delegate within a job executed by _ManagedScheduledExecutorService#scheduleAtFixedRate()_. > The _EntityManager_ is produced by CDI producer and entire web application is able to work with injected _EntityManager_ except for the jobs. > I tried to schedule executing the job in two ways and both finished with same issue (No managed context in _EntityManager_) : > * _@ApplicationScoped_ job instance was passed to executor from caller. > * The job was changed to _RequestScoped_ and _ContextProxy#createContextualProxy()_ created the Job bean instance and then I called _scheduleAtFixedRate(job, 5, 60, SECONDS)_ > It looks to me that _javax.enterprise.concurrent_ has a different _BeanManager_ and therefore has no notion about my CDI Producer of _EntityManager_. The producer is regular producer of _EntityManager_ in JavaEE. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7841) ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context.

by Tibor Digana (JIRA)

[ https://issues.jboss.org/browse/WFLY-7841?page=com.atlassian.jira.plugin.... ] Tibor Digana updated WFLY-7841: ------------------------------- Affects Version/s: 10.1.0.Final > ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context. > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-7841 > URL: https://issues.jboss.org/browse/WFLY-7841 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: Tibor Digana > Assignee: Stuart Douglas > > The problem is that _EntityManager_ does not have managed delegate within a job executed by _ManagedScheduledExecutorService#scheduleAtFixedRate()_. > The _EntityManager_ is produced by CDI producer and entire web application is able to work with injected _EntityManager_ except for the jobs. > I tried to schedule executing the job in two ways and both finished with same issue (No managed context in _EntityManager_) : > * _@ApplicationScoped_ job instance was passed to executor from caller. > * The job was changed to _RequestScoped_ and _ContextProxy#createContextualProxy()_ created the Job bean instance and then I called _scheduleAtFixedRate(job, 5, 60, SECONDS)_ > It looks to me that _javax.enterprise.concurrent_ has a different _BeanManager_ and therefore has no notion about my CDI Producer of _EntityManager_. The producer is regular producer of _EntityManager_ in JavaEE. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1391) Investigate why jcr2vfs migration tool needs gwt-user dependency

by Petr Široký (JIRA)

Petr Široký created DROOLS-1391: ----------------------------------- Summary: Investigate why jcr2vfs migration tool needs gwt-user dependency Key: DROOLS-1391 URL: https://issues.jboss.org/browse/DROOLS-1391 Project: Drools Issue Type: Task Reporter: Petr Široký Assignee: Petr Široký After the upgrade of JPA (2.0 -> 2.1) and Hibernate (4.x -> 5.x), the jcr2vfs-importer tests started to fail with {{WELD-ENV-000015: Unable to load annotation: jsinterop.annotations.JsType}}. This class is in {{gwt-user}} jar, so adding that "fixes" the issue. However, gwt-user is a huge library (~16MiB) and ideally should not be needed. We need to investigate if there is a way to get rid of it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1390) Inconsistent scanner state when using very small polling interval

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1390?page=com.atlassian.jira.plugi... ] Petr Široký resolved DROOLS-1390. --------------------------------- Fix Version/s: 7.0.0.CR1 Resolution: Done > Inconsistent scanner state when using very small polling interval > ----------------------------------------------------------------- > > Key: DROOLS-1390 > URL: https://issues.jboss.org/browse/DROOLS-1390 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta5 > Reporter: Petr Široký > Assignee: Petr Široký > Priority: Minor > Fix For: 7.0.0.CR1 > > > Using KIE Scanner state with very small polling interval (e.g. 20ms) may lead to inconsistent scanner state (race condition). Using such a small interval is not recommended, but the scanner state needs to be consistent even is such cases. > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2017