[JBoss JIRA] (WFLY-11818) wildfly-16.0.0.Final: "From address" is no more used as default from in email
by Wolfgang Mayer (Jira)
[ https://issues.jboss.org/browse/WFLY-11818?page=com.atlassian.jira.plugin... ]
Wolfgang Mayer commented on WFLY-11818:
---------------------------------------
I've now made 3 more tests using mail example from the Quickstarts.
Test1: message.setFrom(new InternetAddress(from));
Result:
mail.user: Null
user.name: Correct
message.getFrom(): Correct
Test2: message.setFrom(new InternetAddress());
Result:
mail.user: Null
user.name: Correct
message.getFrom(): Null
Test3: no message.setFrom() (This approach was used in WildFly 15)
Result:
mail.user: Null
user.name: Correct
message.getFrom(): NullPointerException
> wildfly-16.0.0.Final: "From address" is no more used as default from in email
> -----------------------------------------------------------------------------
>
> Key: WFLY-11818
> URL: https://issues.jboss.org/browse/WFLY-11818
> Project: WildFly
> Issue Type: Bug
> Components: Mail
> Affects Versions: 16.0.0.Final
> Environment: mvn -v
> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T20:41:47+02:00)
> Maven home: /apps/apache-maven-3.6.0
> Java version: 11.0.2, vendor: Oracle Corporation, runtime: /usr/java/jdk-11.0.2
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux", version: "4.12.14-lp150.12.48-default", arch: "amd64", family: "unix"
> Reporter: Wolfgang Mayer
> Assignee: Tomaz Cerar
> Priority: Major
>
> As mentioned in the Help (description) of 'Mail Session' configuration:
> From: *From address that is used as default from, if not set when sending*
> Apparently this is not the case anymore in wildfly-16.0.0.Final.
> For example I made a test with quickstart-16.0/mail/.
> When omitting the line
> *message.setFrom(new InternetAddress(from));*
> Sending mail fails with:
> com.sun.mail.smtp.SMTPSendFailedException: 554-Transaction failed
> 554 Unauthorized sender address.
> I have the same issue when replacing the line above with
> message.setFrom(new InternetAddress());
> I am pretty sure that this is working in wildfly-15
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (DROOLS-1481) Validate function signature at compile time and improve error message
by Matteo Mortari (Jira)
[ https://issues.jboss.org/browse/DROOLS-1481?page=com.atlassian.jira.plugi... ]
Matteo Mortari updated DROOLS-1481:
-----------------------------------
Story Points: 8
> Validate function signature at compile time and improve error message
> ---------------------------------------------------------------------
>
> Key: DROOLS-1481
> URL: https://issues.jboss.org/browse/DROOLS-1481
> Project: Drools
> Issue Type: Feature Request
> Components: dmn engine
> Affects Versions: 7.0.0.Beta7
> Reporter: Edson Tirelli
> Assignee: Matteo Mortari
> Priority: Major
>
> Function signatures as of now are only validated in runtime. We can improve it to add static validation as well. For instance, in the expression:
> {code}"$"+ (if Payment < 1000 then string(Payment) else (substring(string(Payment),1,1) + "," + substring(string(decimal(Payment,2),2)))){code}
> In runtime I get:
> {quote}Unable to find function 'string( class java.math.BigDecimal, class java.math.BigDecimal )'{quote}
> Because of:
> {code}...string(decimal(Payment,2),2)...{code}
> Instead of (see the misplaced parenthesis):
> {code}...string(decimal(Payment,2)),2...{code}
> I think we can also improve the error message to say:
> {quote}Unable to find function 'string( number, number )'{quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (DROOLS-2513) Add support for embedded test execution
by Matteo Mortari (Jira)
[ https://issues.jboss.org/browse/DROOLS-2513?page=com.atlassian.jira.plugi... ]
Matteo Mortari commented on DROOLS-2513:
----------------------------------------
Estimated as 5 as even on TCK test value deseriaization rely on DMN typeref which may not always be available.
> Add support for embedded test execution
> ---------------------------------------
>
> Key: DROOLS-2513
> URL: https://issues.jboss.org/browse/DROOLS-2513
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Affects Versions: 7.7.0.Final
> Reporter: Edson Tirelli
> Assignee: Matteo Mortari
> Priority: Major
>
> TCK test cases can be embedded in the DMN model under the extension elements (e.g., see Trisotech generated models).
> Add a public API to allow execution of embedded test cases.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (DROOLS-1400) Comparison of DRL changes should not consider comments during incremental compilation
by Matteo Mortari (Jira)
[ https://issues.jboss.org/browse/DROOLS-1400?page=com.atlassian.jira.plugi... ]
Matteo Mortari reassigned DROOLS-1400:
--------------------------------------
Assignee: Luca Molteni (was: Matteo Mortari)
> Comparison of DRL changes should not consider comments during incremental compilation
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-1400
> URL: https://issues.jboss.org/browse/DROOLS-1400
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.0.0.Beta5
> Reporter: Matteo Mortari
> Assignee: Luca Molteni
> Priority: Minor
>
> Same as [DROOLS-1399] but concerning comments; in full below:
> During incremental compilation the equivalent DRL file contains only a modification +within a comment+. Currently, this triggers the incremental compilation to rebuild all the resources associated in that DRL file anyway. Consequently, a rule in that DRL file might be actually UNchanged; but following the explanation above, it will match and fire again, like it's a new/modified rule.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (DROOLS-1400) Comparison of DRL changes should not consider comments during incremental compilation
by Matteo Mortari (Jira)
[ https://issues.jboss.org/browse/DROOLS-1400?page=com.atlassian.jira.plugi... ]
Matteo Mortari commented on DROOLS-1400:
----------------------------------------
Reassigning to [~volothamp] as I believe more related to his current activities ;)
> Comparison of DRL changes should not consider comments during incremental compilation
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-1400
> URL: https://issues.jboss.org/browse/DROOLS-1400
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.0.0.Beta5
> Reporter: Matteo Mortari
> Assignee: Luca Molteni
> Priority: Minor
>
> Same as [DROOLS-1399] but concerning comments; in full below:
> During incremental compilation the equivalent DRL file contains only a modification +within a comment+. Currently, this triggers the incremental compilation to rebuild all the resources associated in that DRL file anyway. Consequently, a rule in that DRL file might be actually UNchanged; but following the explanation above, it will match and fire again, like it's a new/modified rule.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months