[JBoss JIRA] (DROOLS-582) Have all declared type instance implement a helper interface
by Benoit Voisin (JIRA)
[ https://issues.jboss.org/browse/DROOLS-582?page=com.atlassian.jira.plugin... ]
Benoit Voisin commented on DROOLS-582:
--------------------------------------
I could work on an implementation if this Feature request is accepted
> Have all declared type instance implement a helper interface
> ------------------------------------------------------------
>
> Key: DROOLS-582
> URL: https://issues.jboss.org/browse/DROOLS-582
> Project: Drools
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Benoit Voisin
> Assignee: Mark Proctor
>
> Following DROOLS-546, and to provide simple and safe access to FactType instances in Java code, we could have each instance implement an interface looking like :
> interface DeclaredFact {
> boolean hasField(String name);
> void setFieldValue(String name, Object value);
> Object getFieldValue(String name);
> FactType getKieFactType(); //RQ: possible on name collisions with existing kieFactType field
> }
> The setField/getField should throw proper exceptions for unknown fields.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (DROOLS-582) Have all declared type instance implement a helper interface
by Benoit Voisin (JIRA)
Benoit Voisin created DROOLS-582:
------------------------------------
Summary: Have all declared type instance implement a helper interface
Key: DROOLS-582
URL: https://issues.jboss.org/browse/DROOLS-582
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Benoit Voisin
Assignee: Mark Proctor
Following DROOLS-546, and to provide simple and safe access to FactType instances in Java code, we could have each instance implement an interface looking like :
interface DeclaredFact {
boolean hasField(String name);
void setFieldValue(String name, Object value);
Object getFieldValue(String name);
FactType getKieFactType(); //RQ: possible on name collisions with existing kieFactType field
}
The setField/getField should throw proper exceptions for unknown fields.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (DROOLS-546) FactType.get/set throws an NPE for unknown fields
by Davide Sottara (JIRA)
[ https://issues.jboss.org/browse/DROOLS-546?page=com.atlassian.jira.plugin... ]
Davide Sottara updated DROOLS-546:
----------------------------------
Summary: FactType.get/set throws an NPE for unknown fields (was: FactType.get/set should throw specific exception (not NPE) for unknown fields)
> FactType.get/set throws an NPE for unknown fields
> -------------------------------------------------
>
> Key: DROOLS-546
> URL: https://issues.jboss.org/browse/DROOLS-546
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 6.1.0.CR1
> Reporter: Benoit Voisin
> Assignee: Mario Fusco
> Fix For: 6.1.0.Final, 6.2.0.Beta1
>
>
> *WARNING : the committed fix does not implement the behavior intended by the title or description : the code now simply ignore without any error the unknown field*
> factType.get(instance, "unknownField") is currently throwing an NPE. This gives improper information to the user/developper.
> I propose that it throws a new UnknownFactFieldException giving improved information giving good hints for debugging or enabling specific exception management.
> See pull request for test-case and proposed fix
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (DROOLS-546) FactType.get/set should throw specific exception (not NPE) for unknown fields
by Benoit Voisin (JIRA)
[ https://issues.jboss.org/browse/DROOLS-546?page=com.atlassian.jira.plugin... ]
Benoit Voisin updated DROOLS-546:
---------------------------------
Description:
*WARNING : the committed fix does not implement the behavior intended by the title or description : the code now simply ignore without any error the unknown field*
factType.get(instance, "unknownField") is currently throwing an NPE. This gives improper information to the user/developper.
I propose that it throws a new UnknownFactFieldException giving improved information giving good hints for debugging or enabling specific exception management.
See pull request for test-case and proposed fix
was:
factType.get(instance, "unknownField") is currently throwing an NPE. This gives improper information to the user/developper.
I propose that it throws a new UnknownFactFieldException giving improved information giving good hints for debugging or enabling specific exception management.
See pull request for test-case and proposed fix
> FactType.get/set should throw specific exception (not NPE) for unknown fields
> -----------------------------------------------------------------------------
>
> Key: DROOLS-546
> URL: https://issues.jboss.org/browse/DROOLS-546
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 6.1.0.CR1
> Reporter: Benoit Voisin
> Assignee: Mario Fusco
> Fix For: 6.1.0.Final, 6.2.0.Beta1
>
>
> *WARNING : the committed fix does not implement the behavior intended by the title or description : the code now simply ignore without any error the unknown field*
> factType.get(instance, "unknownField") is currently throwing an NPE. This gives improper information to the user/developper.
> I propose that it throws a new UnknownFactFieldException giving improved information giving good hints for debugging or enabling specific exception management.
> See pull request for test-case and proposed fix
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (ELY-78) Move all classes to org.wildfly.sasl package
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-78?page=com.atlassian.jira.plugin.sys... ]
Darran Lofthouse moved SASL-62 to ELY-78:
-----------------------------------------
Project: WildFly Elytron (was: WildFly SASL Provider)
Key: ELY-78 (was: SASL-62)
Workflow: GIT Pull Request workflow (was: classic default workflow)
Component/s: Build
(was: Build)
Fix Version/s: 1.0.0.Beta1
(was: 2.0.0.Alpha1)
> Move all classes to org.wildfly.sasl package
> --------------------------------------------
>
> Key: ELY-78
> URL: https://issues.jboss.org/browse/ELY-78
> Project: WildFly Elytron
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.0.0.Beta1
>
>
> Will retain 'org.jboss.sasl.JBossSaslProvider' for backwards compatibility.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (ELY-73) Make JBoss SASL an OSGi bundle
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-73?page=com.atlassian.jira.plugin.sys... ]
Darran Lofthouse moved SASL-41 to ELY-73:
-----------------------------------------
Project: WildFly Elytron (was: WildFly SASL Provider)
Key: ELY-73 (was: SASL-41)
Workflow: GIT Pull Request workflow (was: classic default workflow)
Affects Version/s: (was: 1.0.3.Final)
Fix Version/s: 1.0.0.Beta1
(was: 2.0.0.Alpha1)
> Make JBoss SASL an OSGi bundle
> ------------------------------
>
> Key: ELY-73
> URL: https://issues.jboss.org/browse/ELY-73
> Project: WildFly Elytron
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Philippe Marschall
> Assignee: Darran Lofthouse
> Labels: osgi
> Fix For: 1.0.0.Beta1
>
>
> We'd like to deploy JBoss SASL in an OSGi environment (Equinox). For this is would be convenient for us if JBoss SASL was already an OSGi bundle and we don't have to wrap it.
> Pull request will follow shortly
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months