March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-429) StatefulKnowledgeSession.fireAllRules(AgendaFilter a) and StatefulKnowledgeSession.fireAllRules(new RuleNameMatchesAgendaFilter("Rule")) are not working in the version drools 6.0.0 and 6.0.1 which was working in 5.x.It throws UnsupportedOperationException

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-429?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-429: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > StatefulKnowledgeSession.fireAllRules(AgendaFilter a) and StatefulKnowledgeSession.fireAllRules(new RuleNameMatchesAgendaFilter("Rule")) are not working in the version drools 6.0.0 and 6.0.1 which was working in 5.x.It throws UnsupportedOperationException > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-429 > URL: https://issues.jboss.org/browse/DROOLS-429 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final, 6.0.1.Final > Reporter: Revathi P > Assignee: Mario Fusco > Labels: jboss > Fix For: 6.0.0.Final, 6.0.1.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-429) StatefulKnowledgeSession.fireAllRules(AgendaFilter a) and StatefulKnowledgeSession.fireAllRules(new RuleNameMatchesAgendaFilter("Rule")) are not working in the version drools 6.0.0 and 6.0.1 which was working in 5.x.It throws UnsupportedOperationException

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-429?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-429. -------------------------------- Resolution: Done > StatefulKnowledgeSession.fireAllRules(AgendaFilter a) and StatefulKnowledgeSession.fireAllRules(new RuleNameMatchesAgendaFilter("Rule")) are not working in the version drools 6.0.0 and 6.0.1 which was working in 5.x.It throws UnsupportedOperationException > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-429 > URL: https://issues.jboss.org/browse/DROOLS-429 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final, 6.0.1.Final > Reporter: Revathi P > Assignee: Mario Fusco > Labels: jboss > Fix For: 6.0.1.Final, 6.0.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-436) Cannot access to remote kie maven repository - Access denied

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-436?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-436. -------------------------------- Resolution: Rejected This is not a bug. See the linked bugzilla ticket explaining how to resolve this problem > Cannot access to remote kie maven repository - Access denied > ------------------------------------------------------------ > > Key: DROOLS-436 > URL: https://issues.jboss.org/browse/DROOLS-436 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Environment: - Windows 7 64 bits > - JDK 1.7.0.45 > - Drools 6.0.1.Final > Reporter: Rogério Disciolli > Assignee: Mario Fusco > > - Start JBPM 6.0.1.Final binding a specific IP 192.168.0.10 > - Run maven in a remote machine with the pom.xml like this > <repository> > <id>guvnor-m2-repo</id> > <name>Guvnor M2 Repo</name> > <url>http://192.168.0.10:8080/jbpm-console/maven2/</url> > </repository> > Also having username/password in ~/.m2/settings.xml > <servers> > <server> > <id>guvnor-m2-repo</id> > <username>admin</username> > <password>admin</password> > </server> > </servers> > And returned "Access denied (401)" when try get maven-metadata.xml from project. > Can not authenticate at kie maven repository. > The same happens when try run Java Project with VM arguments "-Dkie.maven.settings.custom=settings.xml" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-436) Cannot access to remote kie maven repository - Access denied

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-436?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-436: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > Cannot access to remote kie maven repository - Access denied > ------------------------------------------------------------ > > Key: DROOLS-436 > URL: https://issues.jboss.org/browse/DROOLS-436 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Environment: - Windows 7 64 bits > - JDK 1.7.0.45 > - Drools 6.0.1.Final > Reporter: Rogério Disciolli > Assignee: Mario Fusco > > - Start JBPM 6.0.1.Final binding a specific IP 192.168.0.10 > - Run maven in a remote machine with the pom.xml like this > <repository> > <id>guvnor-m2-repo</id> > <name>Guvnor M2 Repo</name> > <url>http://192.168.0.10:8080/jbpm-console/maven2/</url> > </repository> > Also having username/password in ~/.m2/settings.xml > <servers> > <server> > <id>guvnor-m2-repo</id> > <username>admin</username> > <password>admin</password> > </server> > </servers> > And returned "Access denied (401)" when try get maven-metadata.xml from project. > Can not authenticate at kie maven repository. > The same happens when try run Java Project with VM arguments "-Dkie.maven.settings.custom=settings.xml" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-436) Cannot access to remote kie maven repository - Access denied

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-436?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-436: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1059584 > Cannot access to remote kie maven repository - Access denied > ------------------------------------------------------------ > > Key: DROOLS-436 > URL: https://issues.jboss.org/browse/DROOLS-436 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Environment: - Windows 7 64 bits > - JDK 1.7.0.45 > - Drools 6.0.1.Final > Reporter: Rogério Disciolli > Assignee: Mark Proctor > > - Start JBPM 6.0.1.Final binding a specific IP 192.168.0.10 > - Run maven in a remote machine with the pom.xml like this > <repository> > <id>guvnor-m2-repo</id> > <name>Guvnor M2 Repo</name> > <url>http://192.168.0.10:8080/jbpm-console/maven2/</url> > </repository> > Also having username/password in ~/.m2/settings.xml > <servers> > <server> > <id>guvnor-m2-repo</id> > <username>admin</username> > <password>admin</password> > </server> > </servers> > And returned "Access denied (401)" when try get maven-metadata.xml from project. > Can not authenticate at kie maven repository. > The same happens when try run Java Project with VM arguments "-Dkie.maven.settings.custom=settings.xml" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-439) Package builder unable to find declared array class

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-439?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-439: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > Package builder unable to find declared array class > --------------------------------------------------- > > Key: DROOLS-439 > URL: https://issues.jboss.org/browse/DROOLS-439 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Reporter: Mark Sullivan > Assignee: Mario Fusco > > When declaring a fact type with an array field, where the array type is declared in the same package, for example: > {code} > declare Owner > name : String > end > declare Pet > owners : Owner[] > end > {code} > The following build error occurs: > {code} > [Message [id=1, level=ERROR, path=pets.drl, line=5, column=0 > text=Unable to find class 'Owner']] > {code} > This error doesn't always occur when an array field is declared. It's dependent on the order in which each fact type is processed. > PackageBuilder attempts to order fact types for processing based on the declared super type and attribute types. > The following loop in *PackageBuilder.sortByHierarchy()* processes each field looking for field type dependencies: > {code} > for (TypeFieldDescr field : tdescr.getFields().values()) { > QualifiedName typeName = new QualifiedName(field.getPattern().getObjectType()); > if (!hasCircularDependency(name, typeName, taxonomy)) { > supers.add(typeName); > } > } > {code} > However I don't think it correctly spots the dependency when the field type is an array. > This issue can be worked around by declaring an unused field of the same type as the array: > {code} > declare Owner > name : String > end > declare Pet > owners : Owner[] > _unused: Owner > end > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-439) Package builder unable to find declared array class

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-439?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-439. -------------------------------- Resolution: Done > Package builder unable to find declared array class > --------------------------------------------------- > > Key: DROOLS-439 > URL: https://issues.jboss.org/browse/DROOLS-439 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Reporter: Mark Sullivan > Assignee: Mario Fusco > > When declaring a fact type with an array field, where the array type is declared in the same package, for example: > {code} > declare Owner > name : String > end > declare Pet > owners : Owner[] > end > {code} > The following build error occurs: > {code} > [Message [id=1, level=ERROR, path=pets.drl, line=5, column=0 > text=Unable to find class 'Owner']] > {code} > This error doesn't always occur when an array field is declared. It's dependent on the order in which each fact type is processed. > PackageBuilder attempts to order fact types for processing based on the declared super type and attribute types. > The following loop in *PackageBuilder.sortByHierarchy()* processes each field looking for field type dependencies: > {code} > for (TypeFieldDescr field : tdescr.getFields().values()) { > QualifiedName typeName = new QualifiedName(field.getPattern().getObjectType()); > if (!hasCircularDependency(name, typeName, taxonomy)) { > supers.add(typeName); > } > } > {code} > However I don't think it correctly spots the dependency when the field type is an array. > This issue can be worked around by declaring an unused field of the same type as the array: > {code} > declare Owner > name : String > end > declare Pet > owners : Owner[] > _unused: Owner > end > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-805) Overload SecurityVaultFactory.get() to be able to specify the classloader

by Peter Skopek (JIRA)

[ https://issues.jboss.org/browse/SECURITY-805?page=com.atlassian.jira.plug... ] Peter Skopek updated SECURITY-805: ---------------------------------- Fix Version/s: PicketBox_4_0_19.SP5 > Overload SecurityVaultFactory.get() to be able to specify the classloader > ------------------------------------------------------------------------- > > Key: SECURITY-805 > URL: https://issues.jboss.org/browse/SECURITY-805 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: PicketBox_4_0_21.Beta2, PicketBox_4_0_19.SP5 > > Attachments: SECURITY-805-2.diff, SECURITY-805.diff > > > To work better with modular class loading in WF -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-439) Package builder unable to find declared array class

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-439?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-439: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1079950 > Package builder unable to find declared array class > --------------------------------------------------- > > Key: DROOLS-439 > URL: https://issues.jboss.org/browse/DROOLS-439 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Reporter: Mark Sullivan > Assignee: Mark Proctor > > When declaring a fact type with an array field, where the array type is declared in the same package, for example: > {code} > declare Owner > name : String > end > declare Pet > owners : Owner[] > end > {code} > The following build error occurs: > {code} > [Message [id=1, level=ERROR, path=pets.drl, line=5, column=0 > text=Unable to find class 'Owner']] > {code} > This error doesn't always occur when an array field is declared. It's dependent on the order in which each fact type is processed. > PackageBuilder attempts to order fact types for processing based on the declared super type and attribute types. > The following loop in *PackageBuilder.sortByHierarchy()* processes each field looking for field type dependencies: > {code} > for (TypeFieldDescr field : tdescr.getFields().values()) { > QualifiedName typeName = new QualifiedName(field.getPattern().getObjectType()); > if (!hasCircularDependency(name, typeName, taxonomy)) { > supers.add(typeName); > } > } > {code} > However I don't think it correctly spots the dependency when the field type is an array. > This issue can be worked around by declaring an unused field of the same type as the array: > {code} > declare Owner > name : String > end > declare Pet > owners : Owner[] > _unused: Owner > end > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-439) Package builder unable to find declared array class

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-439?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-439: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1079950|https://bugzilla.redhat.com/show_bug.cgi?id=1079950] from NEW to ASSIGNED > Package builder unable to find declared array class > --------------------------------------------------- > > Key: DROOLS-439 > URL: https://issues.jboss.org/browse/DROOLS-439 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Reporter: Mark Sullivan > Assignee: Mark Proctor > > When declaring a fact type with an array field, where the array type is declared in the same package, for example: > {code} > declare Owner > name : String > end > declare Pet > owners : Owner[] > end > {code} > The following build error occurs: > {code} > [Message [id=1, level=ERROR, path=pets.drl, line=5, column=0 > text=Unable to find class 'Owner']] > {code} > This error doesn't always occur when an array field is declared. It's dependent on the order in which each fact type is processed. > PackageBuilder attempts to order fact types for processing based on the declared super type and attribute types. > The following loop in *PackageBuilder.sortByHierarchy()* processes each field looking for field type dependencies: > {code} > for (TypeFieldDescr field : tdescr.getFields().values()) { > QualifiedName typeName = new QualifiedName(field.getPattern().getObjectType()); > if (!hasCircularDependency(name, typeName, taxonomy)) { > supers.add(typeName); > } > } > {code} > However I don't think it correctly spots the dependency when the field type is an array. > This issue can be worked around by declaring an unused field of the same type as the array: > {code} > declare Owner > name : String > end > declare Pet > owners : Owner[] > _unused: Owner > end > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 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 March 2014