October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBREM-1339) CLI with 2-way SSL often hangs/times out

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/JBREM-1339?page=com.atlassian.jira.plugin... ] Panagiotis Sotiropoulos updated JBREM-1339: ------------------------------------------- Git Pull Request: https://github.com/jboss-remoting/jboss-remoting/pull/146, https://github.com/jboss-remoting/jboss-remoting/pull/147 > CLI with 2-way SSL often hangs/times out > ---------------------------------------- > > Key: JBREM-1339 > URL: https://issues.jboss.org/browse/JBREM-1339 > Project: JBoss Remoting > Issue Type: Bug > Affects Versions: External_issues > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > > Ref : https://bugzilla.redhat.com/show_bug.cgi?id=1491965 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBREM-1339) CLI with 2-way SSL often hangs/times out

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/JBREM-1339?page=com.atlassian.jira.plugin... ] Panagiotis Sotiropoulos commented on JBREM-1339: ------------------------------------------------ https://github.com/jboss-remoting/jboss-remoting/pull/146 this reverts 83c882697d8b01f8262c8efb17e1b0e2eb3a7c61 + fdenise's fix > CLI with 2-way SSL often hangs/times out > ---------------------------------------- > > Key: JBREM-1339 > URL: https://issues.jboss.org/browse/JBREM-1339 > Project: JBoss Remoting > Issue Type: Bug > Affects Versions: External_issues > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > > Ref : https://bugzilla.redhat.com/show_bug.cgi?id=1491965 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBREM-1339) CLI with 2-way SSL often hangs/times out

by Panagiotis Sotiropoulos (JIRA)

Panagiotis Sotiropoulos created JBREM-1339: ---------------------------------------------- Summary: CLI with 2-way SSL often hangs/times out Key: JBREM-1339 URL: https://issues.jboss.org/browse/JBREM-1339 Project: JBoss Remoting Issue Type: Bug Affects Versions: External_issues Reporter: Panagiotis Sotiropoulos Assignee: Panagiotis Sotiropoulos Ref : https://bugzilla.redhat.com/show_bug.cgi?id=1491965 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBRULES-1273) Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-1273?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-1273. --------------------------------------- Resolution: Out of Date This issue is out of date and discarded. If you disagree, feel free to reopen this issue in the DROOLS, OPTAPLANNER or JBPM jira projects. > Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task) > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBRULES-1273 > URL: https://issues.jboss.org/browse/JBRULES-1273 > Project: JBRULES > Issue Type: Feature Request > Reporter: Rainer Langbehn > Assignee: Geoffrey De Smet > Attachments: maven-drools-plugins.zip > > > I already created the requested maven2 plugin and i would like to contribute it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBRULES-3319) Update JDT compiler ECJ from 3.5.1 to 3.7.1 or higher

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3319?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-3319. --------------------------------------- Resolution: Out of Date This issue is out of date and discarded. If you disagree, feel free to reopen this issue in the DROOLS, OPTAPLANNER or JBPM jira projects. > Update JDT compiler ECJ from 3.5.1 to 3.7.1 or higher > ----------------------------------------------------- > > Key: JBRULES-3319 > URL: https://issues.jboss.org/browse/JBRULES-3319 > Project: JBRULES > Issue Type: Task > Components: drools-compiler > Affects Versions: 5.4.0.Beta1 > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > Priority: Minor > Fix For: FUTURE > > > Currently not possible because: > Only 3.7 and 3.7.1 are available on maven central at this time: > http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.eclipse.jdt.core.c... > And both of them have no OSGi information (while 3.5.1 does have it), so upgrading is not straightforward. > I 've asked on eclipse.org about this issue: > http://www.eclipse.org/forums/index.php/mv/msg/269046/769548/#msg_769548 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBRULES-2740) drools-core: Use mojo's antlr-maven-plugin or antlr3-maven-plugin (instead of the antrun plugin with a custom task) so the jar versions are always up to date

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2740?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-2740. --------------------------------------- Resolution: Out of Date This issue is out of date and discarded. If you disagree, feel free to reopen this issue in the DROOLS, OPTAPLANNER or JBPM jira projects. > drools-core: Use mojo's antlr-maven-plugin or antlr3-maven-plugin (instead of the antrun plugin with a custom task) so the jar versions are always up to date > ------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBRULES-2740 > URL: https://issues.jboss.org/browse/JBRULES-2740 > Project: JBRULES > Issue Type: Task > Components: drools-core > Affects Versions: 5.1.1.FINAL > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > Priority: Optional > Fix For: FUTURE > > > - so the jar versions are always up to date > - output to the target directory, as it's generated code and we don't want that in svn. (following antlr maven plugin conventions which following maven's generated code conventions) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBRULES-3259) Full build gives a strange warning "[WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory."

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3259?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-3259. --------------------------------------- Resolution: Out of Date This issue is out of date and discarded. If you disagree, feel free to reopen this issue in the DROOLS, OPTAPLANNER or JBPM jira projects. > Full build gives a strange warning "[WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory." > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBRULES-3259 > URL: https://issues.jboss.org/browse/JBRULES-3259 > Project: JBRULES > Issue Type: Bug > Affects Versions: 5.3.0.Final > Reporter: Toni Rikkola > Assignee: Geoffrey De Smet > Priority: Minor > > Happens on several modules, here is an example of the log: > [INFO] ------------------------------------------------------------------------ > [INFO] Building Drools distribution 5.3.0.Final > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ drools-distribution --- > [INFO] Deleting /Users/rikkola/Codes/drools/drools/drools-distribution/target > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-distribution --- > [INFO] > [INFO] >>> maven-source-plugin:2.1.2:jar (default) @ drools-distribution >>> > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-distribution --- > [INFO] > [INFO] <<< maven-source-plugin:2.1.2:jar (default) @ drools-distribution <<< > [INFO] > [INFO] --- maven-source-plugin:2.1.2:jar (default) @ drools-distribution --- > [INFO] > [INFO] >>> maven-source-plugin:2.1.2:test-jar (default) @ drools-distribution >>> > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-distribution --- > [INFO] > [INFO] <<< maven-source-plugin:2.1.2:test-jar (default) @ drools-distribution <<< > [INFO] > [INFO] --- maven-source-plugin:2.1.2:test-jar (default) @ drools-distribution --- > [INFO] > [INFO] --- maven-javadoc-plugin:2.7:jar (default) @ drools-distribution --- > [INFO] Not executing Javadoc as the project is not a Java classpath-capable package > [INFO] > [INFO] --- maven-assembly-plugin:2.2.1:single (default) @ drools-distribution --- > [INFO] Reading assembly descriptor: src/main/assembly/assembly-drools.xml > [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. > [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. > [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. > [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. > [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. > [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. > [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. > [INFO] Copying files to /Users/rikkola/Codes/drools/drools/drools-distribution/target/drools-distribution-5.3.0.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBRULES-3520) CamelServerApp.class missing, camel-client.xml wrong for Drools and jBPM integration camel server war on Tomcat

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3520?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-3520. --------------------------------------- Resolution: Out of Date This issue is out of date and discarded. If you disagree, feel free to reopen this issue in the DROOLS, OPTAPLANNER or JBPM jira projects. > CamelServerApp.class missing, camel-client.xml wrong for Drools and jBPM integration camel server war on Tomcat > --------------------------------------------------------------------------------------------------------------- > > Key: JBRULES-3520 > URL: https://issues.jboss.org/browse/JBRULES-3520 > Project: JBRULES > Issue Type: Release > Components: drools-camel > Affects Versions: 5.4.0.CR1, 5.4.0.Final > Environment: Tomcat 6.x > Reporter: Ryley Gahagan > Assignee: Geoffrey De Smet > Priority: Minor > Fix For: 5.4.0.CR1, 5.4.0.Final > > Attachments: CamelServerApp.class, CamelServerApp.java, camel-client.xml > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The CamelServerApp.class file is missing from the war. Also, the camel-client.xml has, as default: > <to uri="cxfrs://http://localhost:8080/drools-server/kservice/rest"/> > <to uri="cxfrs://http://localhost:8080/drools-server/kservice/soap"/> > Which Tomcat deploys out of the box as > <to uri="cxfrs://http://localhost:8080/drools-camel-server-5.4.0.Final/kservice/rest"/> > <to uri="cxfrs://http://localhost:8080/drools-camel-server-5.4.0.Final/kservice/soap"/> > (...5.4.0.CR1 for that dist) > Has existed for awhile, apparently. Documentation indicates test.jsp working out of the box. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBRULES-2811) Javadocs should aggregate all javadocs of all modules, but should use groups to distinguish the modules in the overview

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2811?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-2811. --------------------------------------- Resolution: Out of Date This issue is out of date and discarded. If you disagree, feel free to reopen this issue in the DROOLS, OPTAPLANNER or JBPM jira projects. > Javadocs should aggregate all javadocs of all modules, but should use groups to distinguish the modules in the overview > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBRULES-2811 > URL: https://issues.jboss.org/browse/JBRULES-2811 > Project: JBRULES > Issue Type: Task > Components: drools-api > Affects Versions: 5.1.1.FINAL > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > Priority: Optional > Fix For: FUTURE > > > Aggregate: > http://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html > Groups: > http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#gr... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBRULES-1917) JBRMS does not support business rules with non ascii characters

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-1917?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-1917. --------------------------------------- Resolution: Out of Date This issue is out of date and discarded. If you disagree, feel free to reopen this issue in the DROOLS, OPTAPLANNER or JBPM jira projects. > JBRMS does not support business rules with non ascii characters > --------------------------------------------------------------- > > Key: JBRULES-1917 > URL: https://issues.jboss.org/browse/JBRULES-1917 > Project: JBRULES > Issue Type: Bug > Affects Versions: 4.0.7 > Reporter: Gregory Chazalon > Assignee: Geoffrey De Smet > Attachments: drools-latin-rule-support.zip > > > A very simple rule containing some Latin1 characters (e.g. 'é', 'à'..), is not compiled correctly when using the JBRMS web app. > The exact same rule defined in a DRL file, and compiled with the drools compiler API is well handled (no characters mismatch). > Actually, the rule defined both ways is : > rule "latin_message" > when > Let information message > then > information message containing latin characters léger problème à résoudre hôpital > end > I strongly suspect a poor character encoding scheme inside the JBRMS code, but I haven't been able to identify it. > The problem is illustrated by the LatinMessageTest test case, bundled inside the small eclipse project provided. > It has two test methods, one building the rule using the drools compiler API, and the other using a binary package built with JBRMS. > The second one fails as of the poor character encoding suspected inside JBRMS web app. > Any help is appreciated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

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 October 2017