[JBoss JIRA] (WFLY-6621) wildfly-spec-api:10.0.0.Final mismanages el-api, jsf-api
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6621?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-6621:
-----------------------------------
Not sure what tooling you are using that is showing you this, but looks like eclipse.
>From looking at maven's report on dependencies you can see this:
{noformat}
wildfly/spec-api> mvn dependency:tree
[INFO] Building WildFly: Exported Java EE Specification APIs 10.0.0.Final
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.10:tree (default-cli) @ wildfly-spec-api ---
[INFO] org.wildfly:wildfly-spec-api:pom:10.1.0.Final-SNAPSHOT
[INFO] +- org.glassfish:javax.json:jar:1.0.3:compile
[INFO] +- org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_2.0_spec:jar:1.0.0.Final:compile
[INFO] +- org.jboss.spec.javax.batch:jboss-batch-api_1.0_spec:jar:1.0.0.Final:compile
[INFO] | \- javax.inject:javax.inject:jar:1:compile
[INFO] +- org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:jar:1.0.0.Final:compile
[INFO] +- org.jboss.spec.javax.el:jboss-el-api_3.0_spec:jar:1.0.6.Final:compile
[INFO] +- org.jboss.spec.javax.enterprise.concurrent:jboss-concurrency-api_1.0_spec:jar:1.0.0.Final:compile
[INFO] +- org.jboss.spec.javax.faces:jboss-jsf-api_2.2_spec:jar:2.2.13:compile
[INFO] +- org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.2_spec:jar:1.0.0.Final:compile
[INFO] +- org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:jar:1.0.0.Final:compile
[INFO] +- org.jboss.spec.javax.resource:jboss-connector-api_1.7_spec:jar:1.0.0.Final:compile
[INFO] +- org.jboss.spec.javax.security.auth.message:jboss-jaspi-api_1.1_spec:jar:1.0.0.Final:compile
[INFO] +- org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.5_spec:jar:1.0.0.Final:compile
[INFO] +- org.jboss.spec.javax.servlet:jboss-servlet-api_3.1_spec:jar:1.0.0.Final:compile
[INFO] +- org.jboss.spec.javax.servlet.jsp:jboss-jsp-api_2.3_spec:jar:1.0.1.Final:compile
[INFO] +- org.jboss.spec.javax.servlet.jstl:jboss-jstl-api_1.2_spec:jar:1.1.2.Final:compile
[INFO] | \- xalan:xalan:jar:2.7.1.jbossorg-2:compile
[INFO] | \- xalan:serializer:jar:2.7.1.jbossorg-2:compile
[INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.0.0.Final:compile
[INFO] +- org.jboss.spec.javax.websocket:jboss-websocket-api_1.1_spec:jar:1.1.1.Final:compile
[INFO] +- org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec:jar:1.0.4.Final:compile
[INFO] +- org.jboss.spec.javax.xml.rpc:jboss-jaxrpc-api_1.1_spec:jar:1.0.1.Final:compile
[INFO] +- org.jboss.spec.javax.xml.soap:jboss-saaj-api_1.3_spec:jar:1.0.3.Final:compile
[INFO] +- org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.2.Final:compile
[INFO] +- org.hibernate.javax.persistence:hibernate-jpa-2.1-api:jar:1.0.0.Final:compile
[INFO] +- javax.enterprise:cdi-api:jar:1.2:compile
[INFO] +- com.sun.mail:javax.mail:jar:1.5.5:compile
[INFO] | \- javax.activation:activation:jar:1.1.1:compile
[INFO] +- org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar:1.0.0.Final:compile
[INFO] +- javax.validation:validation-api:jar:1.1.0.Final:compile
[INFO] +- org.jboss.spec.javax.management.j2ee:jboss-j2eemgmt-api_1.1_spec:jar:1.0.1.Final:compile
[INFO] \- org.wildfly.checkstyle:wildfly-checkstyle-config:jar:1.0.4.Final:compile
{noformat}
which would indicate el-api is at version 1.0.6.Final as well as jsf-api at 2.2.13.Final
> wildfly-spec-api:10.0.0.Final mismanages el-api, jsf-api
> --------------------------------------------------------
>
> Key: WFLY-6621
> URL: https://issues.jboss.org/browse/WFLY-6621
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.0.0.Final
> Reporter: Vsevolod Golovanov
> Assignee: Jason Greene
> Attachments: pom_el.png, pom_jsf.png
>
>
> Manages el-api to 1.0.4.Final, should be 1.0.5.Final: !pom_el.png|thumbnail!
> Manages jsf-api to 2.2.11, should be 2.2.12: !pom_jsf.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (DROOLS-1168) notify property change
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1168?page=com.atlassian.jira.plugi... ]
Mario Fusco resolved DROOLS-1168.
---------------------------------
Resolution: Rejected
Said that the modify statement is the preferred syntax to notify Drools of a change in a fact, when you write:
{code}
$entity.setUntMisVen($entity.getUntMisVen());
update($entity)
{code}
Drools compiler is still able to infer the name of the changed property and calculate the modification bitmask accordingly. Conversely when you write:
{code}
DroolsUtil.completeEntity($entity, fields, $untMis);
update($entity)
{code}
of course the method completeEntity() is totally opaque to Drools, so it is impossible to set that bitmask.
I'm afraid that property reactivity doesn't fit your use case so my suggestion is to avoid using it there. As an (ugly) workaround you could try to do the following:
{code}
DroolsUtil.completeEntity($entity, fields, $untMis);
$entity.setUntMisVen($entity.getUntMisVen());
update($entity)
{code}
where the setUntMisVen() won't have any practical effect on the $entity (the value is modified by the completeEntity() method) but will allow Drools to infer the correct bitmask.
> notify property change
> ----------------------
>
> Key: DROOLS-1168
> URL: https://issues.jboss.org/browse/DROOLS-1168
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Affects Versions: 6.4.0.Final
> Environment: java 6, eclipse 4, windows 8.1
> Reporter: Sante Stanisci
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: DroolsUtil.java, EntityBase.java, MtbLisvData.java, rules.drl
>
>
> in the then statement instead of modify use a custom function to change the field. This change does not notify the property even if the class is annotated with @PropertyReactive
> How can I manually notify the change?
> Use a stateless session
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6621) wildfly-spec-api:10.0.0.Final mismanages el-api, jsf-api
by Vsevolod Golovanov (JIRA)
Vsevolod Golovanov created WFLY-6621:
----------------------------------------
Summary: wildfly-spec-api:10.0.0.Final mismanages el-api, jsf-api
Key: WFLY-6621
URL: https://issues.jboss.org/browse/WFLY-6621
Project: WildFly
Issue Type: Bug
Affects Versions: 10.0.0.Final
Reporter: Vsevolod Golovanov
Assignee: Jason Greene
Attachments: pom_el.png, pom_jsf.png
Manages el-api to 1.0.4.Final, should be 1.0.5.Final: !pom_el.png|thumbnail!
Manages jsf-api to 2.2.11, should be 2.2.12: !pom_jsf.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ELY-544) Field clientCertUrl from EntitySaslClient is always null
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/ELY-544?page=com.atlassian.jira.plugin.sy... ]
Ondrej Lukas updated ELY-544:
-----------------------------
Labels: static_analysis (was: )
> Field clientCertUrl from EntitySaslClient is always null
> --------------------------------------------------------
>
> Key: ELY-544
> URL: https://issues.jboss.org/browse/ELY-544
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta5
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Minor
> Labels: static_analysis
>
> Field {{clientCertUrl}} from org.wildfly.security.sasl.entity.EntitySaslClient is always null which causes that method getClientCertificate() includes deadcode - condition {{clientCertUrl != null}} is always false. Is it intended? Feel free to close this issue as not a bug if this is currently intended behavior.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months