[jira] [Commented] (DELTASPIKE-1472) htmlunit3 dependency of deltaspike-jsf-module-impl has compile scope
[
https://issues.apache.org/jira/browse/DELTASPIKE-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839112#comment-17839112
]
ASF subversion and git services commented on DELTASPIKE-1472:
-
Commit 9a53cc95f6e2d5f2839d16685376c43482773d45 in deltaspike's branch
refs/heads/master from Thomas Andraschko
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=9a53cc95f ]
Merge pull request #159 from cmunier/DELTASPIKE-1472
DELTASPIKE-1472: Fixed: htmlunit3 dependency of deltaspike-jsf-module-impl has
compile scope
> htmlunit3 dependency of deltaspike-jsf-module-impl has compile scope
>
>
> Key: DELTASPIKE-1472
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1472
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JSF-Module
>Affects Versions: 2.0.0
>Reporter: Christian Munier
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Since version 2.0.0, {{deltaspike-jsf-module-impl}} has a compile dependency
> to {{htmlunit3-driver}}.
> This includes a subtree of several other transitive dependencies, including
> Selenium, OpenTelemetry and Jetty Components, which are then also packaged in
> an application (e.g. WAR or EAR) that uses the DeltaSpike JSF Module.
> {noformat}
> +- org.apache.deltaspike.modules:deltaspike-jsf-module-impl:jar:2.0.0:runtime
>\- org.seleniumhq.selenium:htmlunit3-driver:jar:4.18.1:runtime
> +- org.seleniumhq.selenium:selenium-api:jar:4.18.1:runtime
> +- org.seleniumhq.selenium:selenium-support:jar:4.18.1:runtime
> | +- com.google.auto.service:auto-service-annotations:jar:1.1.1:runtime
> | +- org.seleniumhq.selenium:selenium-json:jar:4.18.1:runtime
> | \- org.seleniumhq.selenium:selenium-remote-driver:jar:4.18.1:runtime
> | +-
> io.opentelemetry.semconv:opentelemetry-semconv:jar:1.23.1-alpha:runtime
> | +- io.opentelemetry:opentelemetry-api:jar:1.35.0:runtime
> | +- io.opentelemetry:opentelemetry-context:jar:1.35.0:runtime
> | +-
> io.opentelemetry:opentelemetry-exporter-logging:jar:1.35.0:runtime
> | +- io.opentelemetry:opentelemetry-sdk-common:jar:1.35.0:runtime
> | +-
> io.opentelemetry:opentelemetry-sdk-extension-autoconfigure-spi:jar:1.35.0:runtime
> | +-
> io.opentelemetry:opentelemetry-sdk-extension-autoconfigure:jar:1.35.0:runtime
> | | \-
> io.opentelemetry:opentelemetry-api-events:jar:1.35.0-alpha:runtime
> | +- io.opentelemetry:opentelemetry-sdk-trace:jar:1.35.0:runtime
> | | \-
> io.opentelemetry:opentelemetry-extension-incubator:jar:1.35.0-alpha:runtime
> | +- io.opentelemetry:opentelemetry-sdk:jar:1.35.0:runtime
> | | +-
> io.opentelemetry:opentelemetry-sdk-metrics:jar:1.35.0:runtime
> | | \- io.opentelemetry:opentelemetry-sdk-logs:jar:1.35.0:runtime
> | +- org.seleniumhq.selenium:selenium-http:jar:4.18.1:runtime
> | | \- dev.failsafe:failsafe:jar:3.3.2:runtime
> | +- org.seleniumhq.selenium:selenium-manager:jar:4.18.1:runtime
> | \- org.seleniumhq.selenium:selenium-os:jar:4.18.1:runtime
> |\- org.apache.commons:commons-exec:jar:1.3:runtime
> \- org.htmlunit:htmlunit:jar:3.11.0:runtime
> +- org.apache.httpcomponents:httpmime:jar:4.5.14:runtime
> | \- org.apache.httpcomponents:httpclient:jar:4.5.14:runtime
> | \- org.apache.httpcomponents:httpcore:jar:4.4.16:runtime
> +- org.htmlunit:htmlunit-core-js:jar:3.11.0:runtime
> +- org.htmlunit:neko-htmlunit:jar:3.11.2:runtime
> +- org.htmlunit:htmlunit-cssparser:jar:3.11.0:runtime
> +- org.htmlunit:htmlunit-xpath:jar:3.11.0:runtime
> +- org.htmlunit:htmlunit-csp:jar:3.11.0:runtime
> +- commons-io:commons-io:jar:2.15.0:runtime
> +- commons-logging:commons-logging:jar:1.3.0:runtime
> +- commons-net:commons-net:jar:3.10.0:runtime
> +- commons-codec:commons-codec:jar:1.16.1:runtime
> +- org.brotli:dec:jar:0.1.2:runtime
> \-
> org.eclipse.jetty.websocket:websocket-client:jar:9.4.53.v20231009:runtime
> +- org.eclipse.jetty:jetty-client:jar:9.4.53.v20231009:runtime
> | \- org.eclipse.jetty:jetty-http:jar:9.4.53.v20231009:runtime
> +- org.eclipse.jetty:jetty-util:jar:9.4.53.v20231009:runtime
> +- org.eclipse.jetty:jetty-io:jar:9.4.53.v20231009:runtime
> \-
> org.eclipse.jetty.websocket:websocket-common:jar:9.4.53.v20231009:runtime
>\-
> org.eclipse.jetty.websocket:websocket-api:jar:9.4.53.v20231009:runtime
>
[jira] [Commented] (DELTASPIKE-1472) htmlunit3 dependency of deltaspike-jsf-module-impl has compile scope
[
https://issues.apache.org/jira/browse/DELTASPIKE-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839111#comment-17839111
]
ASF subversion and git services commented on DELTASPIKE-1472:
-
Commit e71ddfa8855de9991e63989b1a1b34a0221a0d8f in deltaspike's branch
refs/heads/master from Christian Munier
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=e71ddfa88 ]
DELTASPIKE-1472: Changed scope of htmlunit3-driver dependency of
deltaspike-jsf-module-impl from "compile" to "test" so that the resulting tree
of transitive dependencies is not included in runtime.
> htmlunit3 dependency of deltaspike-jsf-module-impl has compile scope
>
>
> Key: DELTASPIKE-1472
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1472
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JSF-Module
>Affects Versions: 2.0.0
>Reporter: Christian Munier
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Since version 2.0.0, {{deltaspike-jsf-module-impl}} has a compile dependency
> to {{htmlunit3-driver}}.
> This includes a subtree of several other transitive dependencies, including
> Selenium, OpenTelemetry and Jetty Components, which are then also packaged in
> an application (e.g. WAR or EAR) that uses the DeltaSpike JSF Module.
> {noformat}
> +- org.apache.deltaspike.modules:deltaspike-jsf-module-impl:jar:2.0.0:runtime
>\- org.seleniumhq.selenium:htmlunit3-driver:jar:4.18.1:runtime
> +- org.seleniumhq.selenium:selenium-api:jar:4.18.1:runtime
> +- org.seleniumhq.selenium:selenium-support:jar:4.18.1:runtime
> | +- com.google.auto.service:auto-service-annotations:jar:1.1.1:runtime
> | +- org.seleniumhq.selenium:selenium-json:jar:4.18.1:runtime
> | \- org.seleniumhq.selenium:selenium-remote-driver:jar:4.18.1:runtime
> | +-
> io.opentelemetry.semconv:opentelemetry-semconv:jar:1.23.1-alpha:runtime
> | +- io.opentelemetry:opentelemetry-api:jar:1.35.0:runtime
> | +- io.opentelemetry:opentelemetry-context:jar:1.35.0:runtime
> | +-
> io.opentelemetry:opentelemetry-exporter-logging:jar:1.35.0:runtime
> | +- io.opentelemetry:opentelemetry-sdk-common:jar:1.35.0:runtime
> | +-
> io.opentelemetry:opentelemetry-sdk-extension-autoconfigure-spi:jar:1.35.0:runtime
> | +-
> io.opentelemetry:opentelemetry-sdk-extension-autoconfigure:jar:1.35.0:runtime
> | | \-
> io.opentelemetry:opentelemetry-api-events:jar:1.35.0-alpha:runtime
> | +- io.opentelemetry:opentelemetry-sdk-trace:jar:1.35.0:runtime
> | | \-
> io.opentelemetry:opentelemetry-extension-incubator:jar:1.35.0-alpha:runtime
> | +- io.opentelemetry:opentelemetry-sdk:jar:1.35.0:runtime
> | | +-
> io.opentelemetry:opentelemetry-sdk-metrics:jar:1.35.0:runtime
> | | \- io.opentelemetry:opentelemetry-sdk-logs:jar:1.35.0:runtime
> | +- org.seleniumhq.selenium:selenium-http:jar:4.18.1:runtime
> | | \- dev.failsafe:failsafe:jar:3.3.2:runtime
> | +- org.seleniumhq.selenium:selenium-manager:jar:4.18.1:runtime
> | \- org.seleniumhq.selenium:selenium-os:jar:4.18.1:runtime
> |\- org.apache.commons:commons-exec:jar:1.3:runtime
> \- org.htmlunit:htmlunit:jar:3.11.0:runtime
> +- org.apache.httpcomponents:httpmime:jar:4.5.14:runtime
> | \- org.apache.httpcomponents:httpclient:jar:4.5.14:runtime
> | \- org.apache.httpcomponents:httpcore:jar:4.4.16:runtime
> +- org.htmlunit:htmlunit-core-js:jar:3.11.0:runtime
> +- org.htmlunit:neko-htmlunit:jar:3.11.2:runtime
> +- org.htmlunit:htmlunit-cssparser:jar:3.11.0:runtime
> +- org.htmlunit:htmlunit-xpath:jar:3.11.0:runtime
> +- org.htmlunit:htmlunit-csp:jar:3.11.0:runtime
> +- commons-io:commons-io:jar:2.15.0:runtime
> +- commons-logging:commons-logging:jar:1.3.0:runtime
> +- commons-net:commons-net:jar:3.10.0:runtime
> +- commons-codec:commons-codec:jar:1.16.1:runtime
> +- org.brotli:dec:jar:0.1.2:runtime
> \-
> org.eclipse.jetty.websocket:websocket-client:jar:9.4.53.v20231009:runtime
> +- org.eclipse.jetty:jetty-client:jar:9.4.53.v20231009:runtime
> | \- org.eclipse.jetty:jetty-http:jar:9.4.53.v20231009:runtime
> +- org.eclipse.jetty:jetty-util:jar:9.4.53.v20231009:runtime
> +- org.eclipse.jetty:jetty-io:jar:9.4.53.v20231009:runtime
> \-
> org.eclipse.jetty.websocket:websocket-common:jar:9.4.53.v20231009:runtime
>\-
>
[jira] [Commented] (DELTASPIKE-1471) Remove @EnableInterceptors in favor of CDI InterceptionFactory
[ https://issues.apache.org/jira/browse/DELTASPIKE-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821324#comment-17821324 ] ASF subversion and git services commented on DELTASPIKE-1471: - Commit 80a09955db24432b596345021c6997339d587958 in deltaspike's branch refs/heads/master from Thomas Andraschko [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=80a09955d ] DELTASPIKE-1471 Remove @EnableInterceptors in favor of CDI InterceptionFactory > Remove @EnableInterceptors in favor of CDI InterceptionFactory > -- > > Key: DELTASPIKE-1471 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1471 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko >Priority: Major > Fix For: 2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1469) WindowIdHtmlRenderer loads wrong Javascript file
[ https://issues.apache.org/jira/browse/DELTASPIKE-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807225#comment-17807225 ] ASF subversion and git services commented on DELTASPIKE-1469: - Commit 4530d147dcc6a895ff29a5b2d3401d341647411b in deltaspike's branch refs/heads/master from Thomas Andraschko [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=4530d147d ] DELTASPIKE-1469 > WindowIdHtmlRenderer loads wrong Javascript file > > > Key: DELTASPIKE-1469 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1469 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0 >Reporter: Peter Nimmervoll >Assignee: Thomas Andraschko >Priority: Major > > At least in the latest Mojarra release (4.0.5) the jsf.js was renamed to > faces.js but WindowIdHtmlRenderer still loads jsf.js. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1468) AuditProvider (PrincipalProvider/TimestampsProvider) not working
[ https://issues.apache.org/jira/browse/DELTASPIKE-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805344#comment-17805344 ] ASF subversion and git services commented on DELTASPIKE-1468: - Commit e7357d14309b30e019ee46e6a73d507d04138b1e in deltaspike's branch refs/heads/master from Thomas Andraschko [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=e7357d143 ] Merge pull request #138 from phillipross/topic/fix/DELTASPIKE-1468 add explicit dependent scope to PrincipalProvider and TimestampsProvider beans > AuditProvider (PrincipalProvider/TimestampsProvider) not working > > > Key: DELTASPIKE-1468 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1468 > Project: DeltaSpike > Issue Type: New Feature > Security Level: public(Regular issues) > Components: JPA-Module >Affects Versions: 2.0 > Environment: symptom exhibited on Payara6 WELD >Reporter: Phillip Ross >Priority: Blocker > > PrincipalProvider and TimestampsProvider stop working in v2.0 (probably since > DELTASPIKE-1466) as they lack an explicit CDI scope annotation. Since they > are loaded/referenced programmatically, no error is thrown by the bean > container explicitly, but rather they are just never resolved and effectively > ignored. > A simple fix is to add @Dependent CDI scope annotation (probably an oversight > from the CDI-3 refactor). > I'll open a GitHub PR with this fix next. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1437) DeltaSpike-2.0 umbrella ticket
[ https://issues.apache.org/jira/browse/DELTASPIKE-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787949#comment-17787949 ] ASF subversion and git services commented on DELTASPIKE-1437: - Commit fd13102bca5aade74f08fe41af2cb6d3663d6fe0 in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=fd13102bc ] DELTASPIKE-1437 temporarily disable last broken test > DeltaSpike-2.0 umbrella ticket > -- > > Key: DELTASPIKE-1437 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1437 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > This is an umbrella ticket for various DeltaSpike 2.0 tasks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1466) move beans.xml to CDI-3.0 style
[
https://issues.apache.org/jira/browse/DELTASPIKE-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785288#comment-17785288
]
ASF subversion and git services commented on DELTASPIKE-1466:
-
Commit 3be1a101249805caa81ffa15abc360b6d8030db0 in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=3be1a1012 ]
DELTASPIKE-1466 move to CDI-3.0 style beans.xml
Also explicitly define a bean-discovery-mode to prevent backward compat issues
with non backward compatible CDI-4.0 spec changes.
> move beans.xml to CDI-3.0 style
> ---
>
> Key: DELTASPIKE-1466
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1466
> Project: DeltaSpike
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Core
>Affects Versions: 2.0
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 2.0
>
>
> Since we now target EE9 at least we also have to update our beans.xml.
> This has mainly to do with CDI-4.0 in JakartaEE10 re-defined the behaviour of
> empty beans.xml files from bean-discovery-mode "all" to "annotated", breaking
> tons of existing code.
> To prevent any behaviour changes for DeltaSpike users we now explicitly
> define a {{bean-discovery-mode}} ourselfs. And we also leverage the
> {{}} modus of CDI-2.0.
> bean-discovery-mode "all" + has the effect that all classes which are
> CDI candidates get scanned and a {{ProcessAnnotatedType}} event gets fired.
> But with the mode we ONLY create beans for AnnotatedTypes which are
> explicitly defined. This is a good compromise between being able to scan all
> classes via CDI Extensions but still not getting any superfluous CDI beans as
> automatically {{@Dependent}} scoped beans
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1437) DeltaSpike-2.0 umbrella ticket
[ https://issues.apache.org/jira/browse/DELTASPIKE-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721277#comment-17721277 ] ASF subversion and git services commented on DELTASPIKE-1437: - Commit 2e575abc3faae68cb1a266923254c2cc80661592 in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=2e575abc3 ] DELTASPIKE-1437 min java version is now 11 > DeltaSpike-2.0 umbrella ticket > -- > > Key: DELTASPIKE-1437 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1437 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > This is an umbrella ticket for various DeltaSpike 2.0 tasks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1465) print ConfigSource of the values for deltaspike.config.log
[
https://issues.apache.org/jira/browse/DELTASPIKE-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721276#comment-17721276
]
ASF subversion and git services commented on DELTASPIKE-1465:
-
Commit 5fcbc344919e74baf14dad92e931a96b3dd3bd4f in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=5fcbc3449 ]
DELTASPIKE-1465 print effective ConfigSource per value
> print ConfigSource of the values for deltaspike.config.log
> --
>
> Key: DELTASPIKE-1465
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1465
> Project: DeltaSpike
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 2.0
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 2.0
>
>
> When using the configuration {code}deltaspike.config.log=true{code}
> DeltaSpike prints the resolved configuraiton at startup. Right now this
> contains the list of ConfigSources and all configured keys plus their values.
> This could be further enhanced by also printing the ConfigSource from which
> the value finally got picked up.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1435) dsrwid cookie should not be set to sameSite="None" - again
[
https://issues.apache.org/jira/browse/DELTASPIKE-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707193#comment-17707193
]
ASF subversion and git services commented on DELTASPIKE-1435:
-
Commit 124c037c9dad77f0eea0b2deee06ad5331bb1719 in deltaspike's branch
refs/heads/master from Thomas Andraschko
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=124c037c9 ]
Merge pull request #118 from j-be/jbe-DELTASPIKE-1435
DELTASPIKE-1435 Add SameSite=Strict to windowhandler.js
> dsrwid cookie should not be set to sameSite="None" - again
> --
>
> Key: DELTASPIKE-1435
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1435
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
>Affects Versions: 1.9.5
>Reporter: Juri Berlanda
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Very similar to DELTASPIKE-1413, this refers to the missing {{SameSite}}
> attribute in {{windowhandler.js}}
> (https://github.com/apache/deltaspike/blob/deltaspike-1.9.5/deltaspike/modules/jsf/impl/src/main/resources/META-INF/resources/deltaspike/windowhandler.js#L619)
> This means, that the following warning still appears in Firefox (tested on
> 90.0.2):
> {quote}Cookie “dsrwid-326” will be soon rejected because it has the
> “SameSite” attribute set to “None” or an invalid value, without the “secure”
> attribute. To know more about the “SameSite“ attribute, read
> https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite
> windowhandler.js.xhtml:17:364{quote}
> Now, I'd propose to set the cookie to {{SameSite=Strict}} here, too. PR is in
> the works.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1464) Use jfwid over dswid
[ https://issues.apache.org/jira/browse/DELTASPIKE-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707185#comment-17707185 ] ASF subversion and git services commented on DELTASPIKE-1464: - Commit 39b8c68fb4b9f817ce34490f56f6374b55319172 in deltaspike's branch refs/heads/master from Thomas Andraschko [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=39b8c68fb ] DELTASPIKE-1464 > Use jfwid over dswid > > > Key: DELTASPIKE-1464 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1464 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) >Reporter: Thomas Andraschko >Priority: Major > Fix For: 2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1464) Use jfwid over dswid
[ https://issues.apache.org/jira/browse/DELTASPIKE-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707172#comment-17707172 ] ASF subversion and git services commented on DELTASPIKE-1464: - Commit a5a95c9aec28339a688bcb83cf8508425408768c in deltaspike's branch refs/heads/master from Thomas Andraschko [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=a5a95c9ae ] DELTASPIKE-1464 > Use jfwid over dswid > > > Key: DELTASPIKE-1464 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1464 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) >Reporter: Thomas Andraschko >Priority: Major > Fix For: 2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1464) Use jfwid over dswid
[ https://issues.apache.org/jira/browse/DELTASPIKE-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707173#comment-17707173 ] ASF subversion and git services commented on DELTASPIKE-1464: - Commit 6350d02d19cc8e3bd48999c4da69d888cdf68c21 in deltaspike's branch refs/heads/master from Thomas Andraschko [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=6350d02d1 ] DELTASPIKE-1464 > Use jfwid over dswid > > > Key: DELTASPIKE-1464 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1464 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) >Reporter: Thomas Andraschko >Priority: Major > Fix For: 2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1463) Reimplement DS ClientWindow as native Faces ClientWindow
[ https://issues.apache.org/jira/browse/DELTASPIKE-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17706945#comment-17706945 ] ASF subversion and git services commented on DELTASPIKE-1463: - Commit 077ff6957c3ba342c5ab5b447f5c244b7a0733fe in deltaspike's branch refs/heads/master from Thomas Andraschko [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=077ff6957 ] DELTASPIKE-1463 > Reimplement DS ClientWindow as native Faces ClientWindow > > > Key: DELTASPIKE-1463 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1463 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) >Reporter: Thomas Andraschko >Priority: Major > Fix For: 2.0 > > > then we can also remove the ds:disableClientWindow component > JSF components already have a built-it disableClientWindow attr on components -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1437) DeltaSpike-2.0 umbrella ticket
[ https://issues.apache.org/jira/browse/DELTASPIKE-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690446#comment-17690446 ] ASF subversion and git services commented on DELTASPIKE-1437: - Commit cb0d4d07a2ae8604f84eb4acaab89f4bd0504e72 in deltaspike's branch refs/heads/master from Gerhard Petracek [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=cb0d4d07a ] DELTASPIKE-1437 updated plugin version > DeltaSpike-2.0 umbrella ticket > -- > > Key: DELTASPIKE-1437 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1437 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > This is an umbrella ticket for various DeltaSpike 2.0 tasks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1437) DeltaSpike-2.0 umbrella ticket
[ https://issues.apache.org/jira/browse/DELTASPIKE-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690425#comment-17690425 ] ASF subversion and git services commented on DELTASPIKE-1437: - Commit 38ed117dd31ab5de6624a94e13d6a1faa87d2a9a in deltaspike's branch refs/heads/master from Gerhard Petracek [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=38ed117dd ] DELTASPIKE-1437 updated build configuration > DeltaSpike-2.0 umbrella ticket > -- > > Key: DELTASPIKE-1437 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1437 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > This is an umbrella ticket for various DeltaSpike 2.0 tasks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1437) DeltaSpike-2.0 umbrella ticket
[ https://issues.apache.org/jira/browse/DELTASPIKE-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690418#comment-17690418 ] ASF subversion and git services commented on DELTASPIKE-1437: - Commit 289fc67f87f081a83c6384c97c85fffc10770c82 in deltaspike's branch refs/heads/master from Gerhard Petracek [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=289fc67f8 ] DELTASPIKE-1437 changed jdk version > DeltaSpike-2.0 umbrella ticket > -- > > Key: DELTASPIKE-1437 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1437 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > This is an umbrella ticket for various DeltaSpike 2.0 tasks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1460) Move outdated APIs
[ https://issues.apache.org/jira/browse/DELTASPIKE-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690059#comment-17690059 ] ASF subversion and git services commented on DELTASPIKE-1460: - Commit e51845ad6d8f33bee4532539c433a228cda37962 in deltaspike's branch refs/heads/master from Gerhard Petracek [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=e51845ad6 ] DELTASPIKE-1460 updated active modules > Move outdated APIs > -- > > Key: DELTASPIKE-1460 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1460 > Project: DeltaSpike > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek >Priority: Major > > some parts of the api aren't needed with cdi 2.0+ > therefore that parts should be moved until they get removed completely. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1460) Move outdated APIs
[ https://issues.apache.org/jira/browse/DELTASPIKE-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690057#comment-17690057 ] ASF subversion and git services commented on DELTASPIKE-1460: - Commit 9ddb61ff1c9cf4c472fc67caf577969bde132a14 in deltaspike's branch refs/heads/master from Gerhard Petracek [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=9ddb61ff1 ] DELTASPIKE-1460 dropped outdated test-configs > Move outdated APIs > -- > > Key: DELTASPIKE-1460 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1460 > Project: DeltaSpike > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek >Priority: Major > > some parts of the api aren't needed with cdi 2.0+ > therefore that parts should be moved until they get removed completely. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1460) Move outdated APIs
[ https://issues.apache.org/jira/browse/DELTASPIKE-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690058#comment-17690058 ] ASF subversion and git services commented on DELTASPIKE-1460: - Commit a15b16e64d1a47979bd4c03b2f41af122c4a6589 in deltaspike's branch refs/heads/master from Gerhard Petracek [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=a15b16e64 ] DELTASPIKE-1460 dropped outdated dependencies > Move outdated APIs > -- > > Key: DELTASPIKE-1460 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1460 > Project: DeltaSpike > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek >Priority: Major > > some parts of the api aren't needed with cdi 2.0+ > therefore that parts should be moved until they get removed completely. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1460) Move outdated APIs
[ https://issues.apache.org/jira/browse/DELTASPIKE-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690056#comment-17690056 ] ASF subversion and git services commented on DELTASPIKE-1460: - Commit 538a075dd8908949880e02aad240bbed146f0daf in deltaspike's branch refs/heads/master from Gerhard Petracek [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=538a075dd ] DELTASPIKE-1460 moved outdated parts > Move outdated APIs > -- > > Key: DELTASPIKE-1460 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1460 > Project: DeltaSpike > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek >Priority: Major > > some parts of the api aren't needed with cdi 2.0+ > therefore that parts should be moved until they get removed completely. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1437) DeltaSpike-2.0 umbrella ticket
[ https://issues.apache.org/jira/browse/DELTASPIKE-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690027#comment-17690027 ] ASF subversion and git services commented on DELTASPIKE-1437: - Commit 64d9d0af71ecd30ba5454d8e84ce67e2060f5998 in deltaspike's branch refs/heads/master from Gerhard Petracek [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=64d9d0af7 ] DELTASPIKE-1437 updated dependencies > DeltaSpike-2.0 umbrella ticket > -- > > Key: DELTASPIKE-1437 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1437 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > This is an umbrella ticket for various DeltaSpike 2.0 tasks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1437) DeltaSpike-2.0 umbrella ticket
[ https://issues.apache.org/jira/browse/DELTASPIKE-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17689858#comment-17689858 ] ASF subversion and git services commented on DELTASPIKE-1437: - Commit a3f4eeb2ed7369b1fb583599f7f9b535a6dc43ec in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=a3f4eeb2e ] DELTASPIKE-1437 start with our other modules WIP! > DeltaSpike-2.0 umbrella ticket > -- > > Key: DELTASPIKE-1437 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1437 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > This is an umbrella ticket for various DeltaSpike 2.0 tasks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1437) DeltaSpike-2.0 umbrella ticket
[ https://issues.apache.org/jira/browse/DELTASPIKE-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17682261#comment-17682261 ] ASF subversion and git services commented on DELTASPIKE-1437: - Commit 88819124d39374cfcca006089141b592ecd2cd49 in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=88819124d ] DELTASPIKE-1437 re-enable cdictrl basics > DeltaSpike-2.0 umbrella ticket > -- > > Key: DELTASPIKE-1437 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1437 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > This is an umbrella ticket for various DeltaSpike 2.0 tasks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1437) DeltaSpike-2.0 umbrella ticket
[ https://issues.apache.org/jira/browse/DELTASPIKE-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17682249#comment-17682249 ] ASF subversion and git services commented on DELTASPIKE-1437: - Commit 71a68b8d0487a9a4d5315988025f3e3f3e401831 in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=71a68b8d0 ] DELTASPIKE-1437 first steps towards DeltaSpike 2.0 > DeltaSpike-2.0 umbrella ticket > -- > > Key: DELTASPIKE-1437 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1437 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > This is an umbrella ticket for various DeltaSpike 2.0 tasks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1439) Remove Global Alternatives
[ https://issues.apache.org/jira/browse/DELTASPIKE-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17682252#comment-17682252 ] ASF subversion and git services commented on DELTASPIKE-1439: - Commit 851d8e241508b18001b819f2489c129857ebd3e1 in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=851d8e241 ] DELTASPIKE-1439 remove global alternatives > Remove Global Alternatives > -- > > Key: DELTASPIKE-1439 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1439 > Project: DeltaSpike > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: Core >Affects Versions: 2.0 >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > 'Global Alternatives' has been a way to fix a nasty design decision in CDI > 1.0 (see https://issues.redhat.com/browse/CDI-18) in a backward compatible > way. > Nowadays we can ask people to just use`@Priority` and be done. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1437) DeltaSpike-2.0 umbrella ticket
[ https://issues.apache.org/jira/browse/DELTASPIKE-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17682250#comment-17682250 ] ASF subversion and git services commented on DELTASPIKE-1437: - Commit 9c9d279e326e94a5eded1493d179d90c1b3d0aac in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=9c9d279e3 ] DELTASPIKE-1437 remove more unused parts > DeltaSpike-2.0 umbrella ticket > -- > > Key: DELTASPIKE-1437 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1437 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > This is an umbrella ticket for various DeltaSpike 2.0 tasks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1438) Remove EAR support
[ https://issues.apache.org/jira/browse/DELTASPIKE-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17682251#comment-17682251 ] ASF subversion and git services commented on DELTASPIKE-1438: - Commit ec5b4fe9b88f9c1a5c4d5c3182e7fb5bda99baf1 in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=ec5b4fe9b ] DELTASPIKE-1438 remove EAR support most containers do not properly support CDI in EARs anyway. Plus EARs are barely used these times. > Remove EAR support > --- > > Key: DELTASPIKE-1438 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1438 > Project: DeltaSpike > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > CDI iin EARs is broken on most containers alltogether. There is just old > Glassfish EE6, WebSphere 8.0 and 8..5 and TomEE where EAR do work without > leaking classes or creating mem leaks. Thus we can likely also drop our EAR > support as it is a very time intense task to support it. > Plus EARs are rarely used in these times. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1456) Introduce default methods for some functions in ConfigSource
[
https://issues.apache.org/jira/browse/DELTASPIKE-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572870#comment-17572870
]
ASF subversion and git services commented on DELTASPIKE-1456:
-
Commit 63122947001cdece57ad054a9d5a43a84c5aefc9 in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=63122947 ]
DELTASPIKE-1456 add default methods to ConfigSource
* isScannable() is now a default method which returns true
* getOrdinal() is now a default method which checks "deltaspike_ordinal"
or returns 100.
> Introduce default methods for some functions in ConfigSource
>
>
> Key: DELTASPIKE-1456
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1456
> Project: DeltaSpike
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.6
>Reporter: Mark Struberg
>Priority: Major
> Fix For: 1.9.7
>
>
> Right now our {{ConfigSource}} interface is still mostly an old Java6
> interface. We already use a default method for the onChange callback
> registration. We could also provide some other default methods, e.g. for
> {{getOrdinal()}} and {{isScannable().
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta
[ https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564621#comment-17564621 ] ASF subversion and git services commented on DELTASPIKE-1434: - Commit d090c528ea6020bdadcdf6a1380bda049b595bde in deltaspike's branch refs/heads/master from Richard Zowalla [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=d090c528 ] DELTASPIKE-1434 - Adds relocation pattern for javax.el, javax.servlet, javax.decorator, javax.faces > Namespace change javax to jakarta > - > > Key: DELTASPIKE-1434 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1434 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.9.5 >Reporter: John Smith >Assignee: Mark Struberg >Priority: Major > Time Spent: 2h 10m > Remaining Estimate: 0h > > Is there a plan to make the namespace change from javax to jakartaee. Seems > to be required to use deltaspike in the future. > https://jakarta.ee/compatibility/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1455) Allow to pass properties to Weld
[ https://issues.apache.org/jira/browse/DELTASPIKE-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564620#comment-17564620 ] ASF subversion and git services commented on DELTASPIKE-1455: - Commit 651993cd7a515323c40c1aa24df48ae279d65280 in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=651993cd ] DELTASPIKE-1455 only WARN if properties are passed On old Weld Versions there is no setProperties method. If one passes in properties we should just WARN and not fail. Because it might be code which can handle this somehow else. > Allow to pass properties to Weld > > > Key: DELTASPIKE-1455 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1455 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: CdiControl >Affects Versions: 1.9.6 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.9.7 > > > See PR > https://github.com/apache/deltaspike/pull/129 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1455) Allow to pass properties to Weld
[ https://issues.apache.org/jira/browse/DELTASPIKE-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564605#comment-17564605 ] ASF subversion and git services commented on DELTASPIKE-1455: - Commit b7c4f46c1ef893d37f02ca97ef5b5d4bce93e24a in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=b7c4f46c ] DELTASPIKE-1455 call setProperties via reflection Only Weld3 and beyond has a setProperties method. Thus we only support passing properties for those containers and have to use reflection to invoke that method. > Allow to pass properties to Weld > > > Key: DELTASPIKE-1455 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1455 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: CdiControl >Affects Versions: 1.9.6 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.9.7 > > > See PR > https://github.com/apache/deltaspike/pull/129 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta
[ https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544742#comment-17544742 ] ASF subversion and git services commented on DELTASPIKE-1434: - Commit 236dce676af78eb6f8680be71ebdff6b4a84d844 in deltaspike's branch refs/heads/master from Richard Zowalla [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=236dce67 ] DELTASPIKE-1434 - Adds relocation pattern for javax.persistence > Namespace change javax to jakarta > - > > Key: DELTASPIKE-1434 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1434 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.9.5 >Reporter: John Smith >Assignee: Mark Struberg >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > Is there a plan to make the namespace change from javax to jakartaee. Seems > to be required to use deltaspike in the future. > https://jakarta.ee/compatibility/ -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta
[ https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536844#comment-17536844 ] ASF subversion and git services commented on DELTASPIKE-1434: - Commit 4d73324914630f03f03c030738d44a0438818943 in deltaspike's branch refs/heads/master from Richard Zowalla [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=4d733249 ] DELTASPIKE-1434 - Refine relocation patterns for javax -> jakarta + adds service transformer Signed-off-by: Mark Struberg > Namespace change javax to jakarta > - > > Key: DELTASPIKE-1434 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1434 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.9.5 >Reporter: John Smith >Assignee: Mark Struberg >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Is there a plan to make the namespace change from javax to jakartaee. Seems > to be required to use deltaspike in the future. > https://jakarta.ee/compatibility/ -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (DELTASPIKE-1454) Upgrade ASM to 9.3
[ https://issues.apache.org/jira/browse/DELTASPIKE-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519670#comment-17519670 ] ASF subversion and git services commented on DELTASPIKE-1454: - Commit a415104f10f2ae1c8dd07f9c92b780006d4a2ba1 in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=a415104f ] DELTASPIKE-1454 upgrade to ASM 9.3 > Upgrade ASM to 9.3 > -- > > Key: DELTASPIKE-1454 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1454 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Proxy-Module >Affects Versions: 1.9.5 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.9.6 > > > Upgrade ASM to 9.3 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (DELTASPIKE-1433) EntityManagerFactoryProducer should also provide a @Disposes method
[
https://issues.apache.org/jira/browse/DELTASPIKE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519493#comment-17519493
]
ASF subversion and git services commented on DELTASPIKE-1433:
-
Commit 2ed47eda74e984565a6b5f85692c2a5cba54fb46 in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=2ed47eda ]
DELTASPIKE-1433 add disposer for EntityManagerFactory
> EntityManagerFactoryProducer should also provide a @Disposes method
> ---
>
> Key: DELTASPIKE-1433
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1433
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JPA-Module
>Affects Versions: 1.9.5
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.6
>
>
> Right now our {{EntityManagerFactoryProducer}} does only create
> EntityManagerFactories but does not destroy them properly at shutdown.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (DELTASPIKE-1453) injecting config of Class got broken
[ https://issues.apache.org/jira/browse/DELTASPIKE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519454#comment-17519454 ] ASF subversion and git services commented on DELTASPIKE-1453: - Commit f7d918e257c3376594bdfbb19e7958b643522a27 in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=f7d918e2 ] DELTASPIKE-1453 fix injection of configured Class > injecting config of Class got broken > > > Key: DELTASPIKE-1453 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1453 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) > Components: Configuration >Affects Versions: 1.9.5 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.9.6 > > > In release 1.9.5 we broke injection of `@ConfigProperty Class someClass`. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (DELTASPIKE-1452) upgrade to apache-parent 25
[ https://issues.apache.org/jira/browse/DELTASPIKE-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519451#comment-17519451 ] ASF subversion and git services commented on DELTASPIKE-1452: - Commit eecedeecf147dbebc867556337d6360ffeacb8ce in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=eecedeec ] DELTASPIKE-1452 upgrade to apache-parent 25 > upgrade to apache-parent 25 > --- > > Key: DELTASPIKE-1452 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1452 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) > Components: Build >Affects Versions: 1.9.5 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.9.6 > > > upgrade to apache-parent 25 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (DELTASPIKE-1133) Don't override the log level
[ https://issues.apache.org/jira/browse/DELTASPIKE-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17518211#comment-17518211 ] ASF subversion and git services commented on DELTASPIKE-1133: - Commit ecf45785a120b8f6a221363cd317b83fb09ff04f in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=ecf45785 ] DELTASPIKE-1133 remove setting logger level > Don't override the log level > > > Key: DELTASPIKE-1133 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1133 > Project: DeltaSpike > Issue Type: Bug > Components: TestControl >Affects Versions: 1.6.0 >Reporter: John D. Ament >Assignee: John D. Ament >Priority: Major > Attachments: DELTASPIKE-1133-PATCHONE.patch > > > https://github.com/apache/deltaspike/blob/master/deltaspike/modules/test-control/api/src/main/java/org/apache/deltaspike/testcontrol/api/junit/CdiTestSuiteRunner.java#L155 > We override the logger level in place here, and reset it. We shouldn't do > that, as you may want to have no logging output. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (DELTASPIKE-1444) Create POJO and Record based Config
[
https://issues.apache.org/jira/browse/DELTASPIKE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456019#comment-17456019
]
ASF subversion and git services commented on DELTASPIKE-1444:
-
Commit 422a78a3c1c25b8040fa4516dfa080da0baa7ed8 in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=422a78a ]
DELTASPIKE-1444 make BeanConverter a non-static factory
otherwise we might create mem leaks, as rightfully noted by rmannibucau
> Create POJO and Record based Config
> ---
>
> Key: DELTASPIKE-1444
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1444
> Project: DeltaSpike
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.5
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.6
>
>
> Right now we only support Interface based configuration with the
> {{@Configuration}} annotation. We could also support injecting POJOs directly
> and even Java14 Records.
> E.g. a class
> {code}
> public record Endpoint(String host, Integer port, String path){}
> {code}
> or with a parameter ct:
> {code}
> public class Endpoint {
> private final String host;
> ...
> public Endpoint(
> @ConfigProperty(name="host") String host,
> @ConfigProperty(name="port") Integer port,
> @ConfigProperty(name="path") String path){
> this.host = host;
>
> }
> }
> {code}
> Note that the {{@ConfigProperty}} annotation might get omitted if the class
> gets compiled with the {{javac -parameters}} option.
> or with a default ct and field parameters:
> {code}
> public class Endpoint {
> private String host;
> private Integer port;
> private String path;
> ...
> }
> {code}
> Resolving of all the required properties must be performed atomically.
> The solution might either be done via the built-in algorithms as shown above,
> in which case the following call might be used to denote that a bean should
> get resolved which consists of mulitple attributes:
> {code}
> ServerEndpointPojoWithCt someServer =
> ConfigResolver.resolve("myapp.some.server")
> .asBean(ServerEndpointPojoWithCt.class)
> .getValue();
> {code}
> or via an explicit Converter function:
> {code}
> final ServerEndpointPojoWithCt someServer =
> ConfigResolver.resolve("myapp.some.server")
> .asBean(ServerEndpointPojoWithCt.class, (cfg, key) -> new
> ServerEndpointPojoWithCt(
> cfg.resolve(key + ".host").getValue(),
> cfg.resolve(key + ".port").as(Integer.class).getValue(),
> cfg.resolve(key + ".path").getValue());)
> .getValue();
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (DELTASPIKE-1444) Create POJO and Record based Config
[
https://issues.apache.org/jira/browse/DELTASPIKE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456018#comment-17456018
]
ASF subversion and git services commented on DELTASPIKE-1444:
-
Commit facacde41ded50f3f98499354680356283fb3a99 in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=facacde ]
DELTASPIKE-1444 add POJO based Config
> Create POJO and Record based Config
> ---
>
> Key: DELTASPIKE-1444
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1444
> Project: DeltaSpike
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.5
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.6
>
>
> Right now we only support Interface based configuration with the
> {{@Configuration}} annotation. We could also support injecting POJOs directly
> and even Java14 Records.
> E.g. a class
> {code}
> public record Endpoint(String host, Integer port, String path){}
> {code}
> or with a parameter ct:
> {code}
> public class Endpoint {
> private final String host;
> ...
> public Endpoint(
> @ConfigProperty(name="host") String host,
> @ConfigProperty(name="port") Integer port,
> @ConfigProperty(name="path") String path){
> this.host = host;
>
> }
> }
> {code}
> Note that the {{@ConfigProperty}} annotation might get omitted if the class
> gets compiled with the {{javac -parameters}} option.
> or with a default ct and field parameters:
> {code}
> public class Endpoint {
> private String host;
> private Integer port;
> private String path;
> ...
> }
> {code}
> Resolving of all the required properties must be performed atomically.
> The solution might either be done via the built-in algorithms as shown above,
> in which case the following call might be used to denote that a bean should
> get resolved which consists of mulitple attributes:
> {code}
> ServerEndpointPojoWithCt someServer =
> ConfigResolver.resolve("myapp.some.server")
> .asBean(ServerEndpointPojoWithCt.class)
> .getValue();
> {code}
> or via an explicit Converter function:
> {code}
> final ServerEndpointPojoWithCt someServer =
> ConfigResolver.resolve("myapp.some.server")
> .asBean(ServerEndpointPojoWithCt.class, (cfg, key) -> new
> ServerEndpointPojoWithCt(
> cfg.resolve(key + ".host").getValue(),
> cfg.resolve(key + ".port").as(Integer.class).getValue(),
> cfg.resolve(key + ".path").getValue());)
> .getValue();
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (DELTASPIKE-1445) Dynamic Config injection via a Supplier
[
https://issues.apache.org/jira/browse/DELTASPIKE-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456020#comment-17456020
]
ASF subversion and git services commented on DELTASPIKE-1445:
-
Commit 941e3717c18196dc7bcee1de8dcaac86e6f874c4 in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=941e371 ]
DELTASPIKE-1445 implement Supplier support
> Dynamic Config injection via a Supplier
> --
>
> Key: DELTASPIKE-1445
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1445
> Project: DeltaSpike
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.5
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.6
>
>
> We should support injecting Configuration via {{Supplier}}.
> That way we can {{get()}} to access the current value.
> The code to use the feature might look like:
> {code}
> @Inject
> @ConfigProperty(name = "address.header.line", cacheFor = 10, cacheUnit =
> TimeUnit.MINUTES)
> private Supplier addressHeaderLine;
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (DELTASPIKE-1426) DeltaSpikeProxyFactory is slow on start
[ https://issues.apache.org/jira/browse/DELTASPIKE-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17453383#comment-17453383 ] ASF subversion and git services commented on DELTASPIKE-1426: - Commit f49e38635b10bfb8dac16f739eef48a1795a4a12 in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=f49e386 ] DELTASPIKE-1426 fix proxyfactory test > DeltaSpikeProxyFactory is slow on start > --- > > Key: DELTASPIKE-1426 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1426 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) >Reporter: Vladimir Dvorak >Priority: Minor > Fix For: 1.9.6 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Deltaspike ProxyFactory start is slow. YourKit shows that the bottleneck is > in the method "collectAllMethods". It intensively uses Class.getMethod(name, > args), that is known by having poor performance. It seems, that number of > calls could be distinctly decreased by skipping checks of public abstracts > from proxy base class. In my case it improves OWB boot time by 7%. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (DELTASPIKE-1439) Remove Global Alternatives
[ https://issues.apache.org/jira/browse/DELTASPIKE-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17419935#comment-17419935 ] ASF subversion and git services commented on DELTASPIKE-1439: - Commit 851d8e241508b18001b819f2489c129857ebd3e1 in deltaspike's branch refs/heads/main from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=851d8e2 ] DELTASPIKE-1439 remove global alternatives > Remove Global Alternatives > -- > > Key: DELTASPIKE-1439 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1439 > Project: DeltaSpike > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: Core >Affects Versions: 2.0 >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > 'Global Alternatives' has been a way to fix a nasty design decision in CDI > 1.0 (see https://issues.redhat.com/browse/CDI-18) in a backward compatible > way. > Nowadays we can ask people to just use`@Priority` and be done. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1437) DeltaSpike-2.0 umbrella ticket
[ https://issues.apache.org/jira/browse/DELTASPIKE-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17419929#comment-17419929 ] ASF subversion and git services commented on DELTASPIKE-1437: - Commit 71a68b8d0487a9a4d5315988025f3e3f3e401831 in deltaspike's branch refs/heads/main from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=71a68b8 ] DELTASPIKE-1437 first steps towards DeltaSpike 2.0 > DeltaSpike-2.0 umbrella ticket > -- > > Key: DELTASPIKE-1437 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1437 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > This is an umbrella ticket for various DeltaSpike 2.0 tasks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1437) DeltaSpike-2.0 umbrella ticket
[ https://issues.apache.org/jira/browse/DELTASPIKE-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17419930#comment-17419930 ] ASF subversion and git services commented on DELTASPIKE-1437: - Commit 9c9d279e326e94a5eded1493d179d90c1b3d0aac in deltaspike's branch refs/heads/main from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=9c9d279 ] DELTASPIKE-1437 remove more unused parts > DeltaSpike-2.0 umbrella ticket > -- > > Key: DELTASPIKE-1437 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1437 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > This is an umbrella ticket for various DeltaSpike 2.0 tasks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1438) Remove EAR support
[ https://issues.apache.org/jira/browse/DELTASPIKE-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17419931#comment-17419931 ] ASF subversion and git services commented on DELTASPIKE-1438: - Commit ec5b4fe9b88f9c1a5c4d5c3182e7fb5bda99baf1 in deltaspike's branch refs/heads/main from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=ec5b4fe ] DELTASPIKE-1438 remove EAR support most containers do not properly support CDI in EARs anyway. Plus EARs are barely used these times. > Remove EAR support > --- > > Key: DELTASPIKE-1438 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1438 > Project: DeltaSpike > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > CDI iin EARs is broken on most containers alltogether. There is just old > Glassfish EE6, WebSphere 8.0 and 8..5 and TomEE where EAR do work without > leaking classes or creating mem leaks. Thus we can likely also drop our EAR > support as it is a very time intense task to support it. > Plus EARs are rarely used in these times. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1416) deltaspike-core-impl.jar does not contain the Main class to execute in your Manifest.MF to Crypto
[
https://issues.apache.org/jira/browse/DELTASPIKE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417349#comment-17417349
]
ASF subversion and git services commented on DELTASPIKE-1416:
-
Commit d2919f014f5342e47d7fff0ac55ec1a43f3c5dbc in deltaspike's branch
refs/heads/master from Thomas Andraschko
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=d2919f0 ]
Merge pull request #111 from Daniel-Dos/DELTASPIKE-1416
DELTASPIKE-1416: add maven-jar-plugin to to use the MANIFEST.MF
> deltaspike-core-impl.jar does not contain the Main class to execute in your
> Manifest.MF to Crypto
> -
>
> Key: DELTASPIKE-1416
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1416
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Core
>Affects Versions: 1.9.4
>Reporter: Daniel Dias
>Assignee: Mark Struberg
>Priority: Minor
> Fix For: 1.9.5
>
> Attachments: DELTASPIKE-1416.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In [https://deltaspike.apache.org/documentation/encryption.html]
> demo how to run java -jar deltaspike-core-impl.jar encode -masterPassword
> myMasterPassword -masterSalt myMasterSalt
> more in your MANIFEST.MF does not contain the Main-Class that is in META-INF
> of the Core:
> [https://github.com/apache/deltaspike/blob/master/deltaspike/core/impl/src/main/resources/META-INF/MANIFEST.MF]
>
> to resolve, you must include a plugin:
> {code:java}
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
> src/main/resources/META-INF/MANIFEST.MF
>
>
> {code}
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1416) deltaspike-core-impl.jar does not contain the Main class to execute in your Manifest.MF to Crypto
[
https://issues.apache.org/jira/browse/DELTASPIKE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417348#comment-17417348
]
ASF subversion and git services commented on DELTASPIKE-1416:
-
Commit c16f377f937f50ea34c0922f28655b8551ece2e7 in deltaspike's branch
refs/heads/master from Daniel Dias
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=c16f377 ]
DELTASPIKE-1416: add maven-jar-plugin to to use the MANIFEST.MF
> deltaspike-core-impl.jar does not contain the Main class to execute in your
> Manifest.MF to Crypto
> -
>
> Key: DELTASPIKE-1416
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1416
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Core
>Affects Versions: 1.9.4
>Reporter: Daniel Dias
>Assignee: Mark Struberg
>Priority: Minor
> Fix For: 1.9.5
>
> Attachments: DELTASPIKE-1416.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In [https://deltaspike.apache.org/documentation/encryption.html]
> demo how to run java -jar deltaspike-core-impl.jar encode -masterPassword
> myMasterPassword -masterSalt myMasterSalt
> more in your MANIFEST.MF does not contain the Main-Class that is in META-INF
> of the Core:
> [https://github.com/apache/deltaspike/blob/master/deltaspike/core/impl/src/main/resources/META-INF/MANIFEST.MF]
>
> to resolve, you must include a plugin:
> {code:java}
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
> src/main/resources/META-INF/MANIFEST.MF
>
>
> {code}
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1426) DeltaSpikeProxyFactory is slow on start
[ https://issues.apache.org/jira/browse/DELTASPIKE-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417343#comment-17417343 ] ASF subversion and git services commented on DELTASPIKE-1426: - Commit 8f18bfafbe208355a129650faaca6f40d246917e in deltaspike's branch refs/heads/master from Vladimir Dvorak [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=8f18bfa ] DELTASPIKE-1426: Improve ProxyFactory performance on start Class.getMethond(name, args) is expensive operation, that is used intensively on start, when DeltaspikeProxyFactory generates new proxies. It was used even for checks of public abstract methods of proxy's base class, but this methods cannot be overridden. This patch collects all leave methods and skips them in the check. > DeltaSpikeProxyFactory is slow on start > --- > > Key: DELTASPIKE-1426 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1426 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) >Reporter: Vladimir Dvorak >Priority: Minor > Time Spent: 1h > Remaining Estimate: 0h > > Deltaspike ProxyFactory start is slow. YourKit shows that the bottleneck is > in the method "collectAllMethods". It intensively uses Class.getMethod(name, > args), that is known by having poor performance. It seems, that number of > calls could be distinctly decreased by skipping checks of public abstracts > from proxy base class. In my case it improves OWB boot time by 7%. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1426) DeltaSpikeProxyFactory is slow on start
[ https://issues.apache.org/jira/browse/DELTASPIKE-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417346#comment-17417346 ] ASF subversion and git services commented on DELTASPIKE-1426: - Commit c529592001a91518bb0598bd74fd64b087ba0c6c in deltaspike's branch refs/heads/master from Thomas Andraschko [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=c529592 ] Merge pull request #117 from skybber/DELTASPIKE-1426 DELTASPIKE-1426: Improve ProxyFactory performance on start > DeltaSpikeProxyFactory is slow on start > --- > > Key: DELTASPIKE-1426 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1426 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) >Reporter: Vladimir Dvorak >Priority: Minor > Time Spent: 1h > Remaining Estimate: 0h > > Deltaspike ProxyFactory start is slow. YourKit shows that the bottleneck is > in the method "collectAllMethods". It intensively uses Class.getMethod(name, > args), that is known by having poor performance. It seems, that number of > calls could be distinctly decreased by skipping checks of public abstracts > from proxy base class. In my case it improves OWB boot time by 7%. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1426) DeltaSpikeProxyFactory is slow on start
[ https://issues.apache.org/jira/browse/DELTASPIKE-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417345#comment-17417345 ] ASF subversion and git services commented on DELTASPIKE-1426: - Commit 14dd70f0e732229b1c32af2bcf23873558c3026a in deltaspike's branch refs/heads/master from Vladimir Dvorak [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=14dd70f ] DELTASPIKE-1426 add Proxyfactory unit test Check correct output of DeltaspikeProxyFacotry.ignoreMethod > DeltaSpikeProxyFactory is slow on start > --- > > Key: DELTASPIKE-1426 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1426 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) >Reporter: Vladimir Dvorak >Priority: Minor > Time Spent: 1h > Remaining Estimate: 0h > > Deltaspike ProxyFactory start is slow. YourKit shows that the bottleneck is > in the method "collectAllMethods". It intensively uses Class.getMethod(name, > args), that is known by having poor performance. It seems, that number of > calls could be distinctly decreased by skipping checks of public abstracts > from proxy base class. In my case it improves OWB boot time by 7%. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1432) Proxy class definition does not work
[
https://issues.apache.org/jira/browse/DELTASPIKE-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417341#comment-17417341
]
ASF subversion and git services commented on DELTASPIKE-1432:
-
Commit e3f9ce55fe774ffde12802e94a760880c23b3c9b in deltaspike's branch
refs/heads/master from Christian Beikov
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=e3f9ce5 ]
DELTASPIKE-1432 Implement MethodHandles.Lookup based fallback for class
definition on Java 9+
> Proxy class definition does not work
>
>
> Key: DELTASPIKE-1432
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1432
> Project: DeltaSpike
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Proxy-Module
>Affects Versions: 1.9.5
>Reporter: Christian Beikov
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In
> {{org.apache.deltaspike.proxy.impl.AsmDeltaSpikeProxyClassGenerator#loadClass}}
> the current implementation always tries to make the
> {{ClassLoader#defineClass}} method (of module java.base) accessible which is
> disallowed by default since 16. To workaround this, one has to add the
> following command line flags {{\--add-opens java.base/java.lang=ALL-UNNAMED}}
> or {{\--add-opens java.base/java.lang=deltaspike.proxy.module.impl.asm}} if
> running in modular mode. This can be properly implemented though by using the
> new supported API {{java.lang.invoke.MethodHandles.Lookup#defineClass}} like
> Weld 3.1.7 now also did. This would help usability of Deltaspike a lot.
> Here is the exception one sees without the flag:
>
> {code}
> java.lang.reflect.InaccessibleObjectException: Unable to make protected final
> java.lang.Class
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> throws java.lang.ClassFormatError accessible: module java.base does not
> "opens java.lang" to module deltaspike.proxy.module.impl.asm
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:357)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at
> java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
> at
> java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
> at
> deltaspike.proxy.module.impl.asm@1.9.4/org.apache.deltaspike.proxy.impl.AsmDeltaSpikeProxyClassGenerator.loadClass(AsmDeltaSpikeProxyClassGenerator.java:528)
> at
> deltaspike.proxy.module.impl.asm@1.9.4/org.apache.deltaspike.proxy.impl.AsmDeltaSpikeProxyClassGenerator.generateProxyClass(AsmDeltaSpikeProxyClassGenerator.java:73)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1432) Proxy class definition does not work
[
https://issues.apache.org/jira/browse/DELTASPIKE-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417342#comment-17417342
]
ASF subversion and git services commented on DELTASPIKE-1432:
-
Commit 2bf31a3564fc9a4df2f60e5ffb93a963b09cc38b in deltaspike's branch
refs/heads/master from Thomas Andraschko
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=2bf31a3 ]
Merge pull request #119 from beikov/DELTASPIKE-1432
DELTASPIKE-1432 Implement MethodHandles.Lookup based fallback for class
definition on Java 9+
> Proxy class definition does not work
>
>
> Key: DELTASPIKE-1432
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1432
> Project: DeltaSpike
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Proxy-Module
>Affects Versions: 1.9.5
>Reporter: Christian Beikov
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In
> {{org.apache.deltaspike.proxy.impl.AsmDeltaSpikeProxyClassGenerator#loadClass}}
> the current implementation always tries to make the
> {{ClassLoader#defineClass}} method (of module java.base) accessible which is
> disallowed by default since 16. To workaround this, one has to add the
> following command line flags {{\--add-opens java.base/java.lang=ALL-UNNAMED}}
> or {{\--add-opens java.base/java.lang=deltaspike.proxy.module.impl.asm}} if
> running in modular mode. This can be properly implemented though by using the
> new supported API {{java.lang.invoke.MethodHandles.Lookup#defineClass}} like
> Weld 3.1.7 now also did. This would help usability of Deltaspike a lot.
> Here is the exception one sees without the flag:
>
> {code}
> java.lang.reflect.InaccessibleObjectException: Unable to make protected final
> java.lang.Class
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> throws java.lang.ClassFormatError accessible: module java.base does not
> "opens java.lang" to module deltaspike.proxy.module.impl.asm
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:357)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> at
> java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
> at
> java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
> at
> deltaspike.proxy.module.impl.asm@1.9.4/org.apache.deltaspike.proxy.impl.AsmDeltaSpikeProxyClassGenerator.loadClass(AsmDeltaSpikeProxyClassGenerator.java:528)
> at
> deltaspike.proxy.module.impl.asm@1.9.4/org.apache.deltaspike.proxy.impl.AsmDeltaSpikeProxyClassGenerator.generateProxyClass(AsmDeltaSpikeProxyClassGenerator.java:73)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta
[ https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17406030#comment-17406030 ] ASF subversion and git services commented on DELTASPIKE-1434: - Commit 003b3593ee3ad4cf8aa8d3538fe92f71fb12670c in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=003b359 ] DELTASPIKE-1434 add shading for jakarta EE package names This commit adds shading from javax to jakarta namespace as aditional attachted artifacts with qualifier 'jakarta'. > Namespace change javax to jakarta > - > > Key: DELTASPIKE-1434 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1434 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.9.5 >Reporter: John Smith >Assignee: Mark Struberg >Priority: Major > > Is there a plan to make the namespace change from javax to jakartaee. Seems > to be required to use deltaspike in the future. > https://jakarta.ee/compatibility/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1427) JUL Logging with {} as param leeds to NumberFormatException
[
https://issues.apache.org/jira/browse/DELTASPIKE-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306393#comment-17306393
]
ASF subversion and git services commented on DELTASPIKE-1427:
-
Commit 4af09588e9d3dd4890a0a20da1507afdf03c0796 in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=4af0958 ]
DELTASPIKE-1427 fix log format {} -> {0} for JUL
> JUL Logging with {} as param leeds to NumberFormatException
> ---
>
> Key: DELTASPIKE-1427
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1427
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
>Affects Versions: 1.9.5
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.6
>
>
> We sometimes log with {} which results in weird logging errors. Should use
> {0} instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1413) dsrwid cookie should not be set to sameSite="None"
[ https://issues.apache.org/jira/browse/DELTASPIKE-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17295616#comment-17295616 ] ASF subversion and git services commented on DELTASPIKE-1413: - Commit 9d0e3d1af0cb7e62c810ec23f97e12e86ab3cf6f in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=9d0e3d1 ] DELTASPIKE-1413 add SameSite=Strict to dsrwid cookie Sadly had to manually add the SetCookie header as Javas Cookie class does not have a SameSite attribute. > dsrwid cookie should not be set to sameSite="None" > -- > > Key: DELTASPIKE-1413 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1413 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Matthias Walliczek >Assignee: Mark Struberg >Priority: Critical > > Currently the dsrwid cookie set by the lazy window handler is set to > secure=false and sameSite=None. > This combination will not be allowed by Firefox in the future. See > [https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Set-Cookie/SameSite.|https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Set-Cookie/SameSite] > Instead sameSite should be set to "lax", which is default in modern browsers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1416) deltaspike-core-impl.jar does not contain the Main class to execute in your Manifest.MF to Crypto
[
https://issues.apache.org/jira/browse/DELTASPIKE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17295598#comment-17295598
]
ASF subversion and git services commented on DELTASPIKE-1416:
-
Commit 7d11feb46868cf66a0c365e97eba71fa22f8c715 in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=7d11feb ]
DELTASPIKE-1416 fix missing mainclass in Manifest
> deltaspike-core-impl.jar does not contain the Main class to execute in your
> Manifest.MF to Crypto
> -
>
> Key: DELTASPIKE-1416
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1416
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Core
>Affects Versions: 1.9.4
>Reporter: Daniel Dias
>Assignee: Mark Struberg
>Priority: Minor
> Fix For: 1.9.5
>
> Attachments: DELTASPIKE-1416.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In [https://deltaspike.apache.org/documentation/encryption.html]
> demo how to run java -jar deltaspike-core-impl.jar encode -masterPassword
> myMasterPassword -masterSalt myMasterSalt
> more in your MANIFEST.MF does not contain the Main-Class that is in META-INF
> of the Core:
> [https://github.com/apache/deltaspike/blob/master/deltaspike/core/impl/src/main/resources/META-INF/MANIFEST.MF]
>
> to resolve, you must include a plugin:
> {code:java}
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
> src/main/resources/META-INF/MANIFEST.MF
>
>
> {code}
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1420) Update ASM to 9.0
[ https://issues.apache.org/jira/browse/DELTASPIKE-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17295593#comment-17295593 ] ASF subversion and git services commented on DELTASPIKE-1420: - Commit 9282b21ae6c2632d56e0764eec98e8f5a1db0419 in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=9282b21 ] DELTASPIKE-1420 update to ASM-9.1 > Update ASM to 9.0 > - > > Key: DELTASPIKE-1420 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1420 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Proxy-Module >Affects Versions: 1.9.4 >Reporter: Christian Beikov >Assignee: Christian Beikov >Priority: Major > Fix For: 1.9.5 > > Time Spent: 20m > Remaining Estimate: 0h > > We need a new release with ASM 9.0 to be able to test against Java 16. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1423) JSF-2.3 managed() in FacesValidator and FacesConverter break CDI integration
[
https://issues.apache.org/jira/browse/DELTASPIKE-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17295250#comment-17295250
]
ASF subversion and git services commented on DELTASPIKE-1423:
-
Commit 1a37ce7935176b5c51498b911b879e053e22fbd1 in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=1a37ce7 ]
DELTASPIKE-1423 fix weird Spelling error
which also caused not being able to find a component in our test
> JSF-2.3 managed() in FacesValidator and FacesConverter break CDI integration
>
>
> Key: DELTASPIKE-1423
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1423
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JSF-Module
>Affects Versions: 1.9.4
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
>
> JSF-2.3 introduced a new field 'managed' and also changed the way Factory
> Wrappers are invoked. This breaks quite a few things with the CDI integration.
> When people use JSF-2.3 container they now need to set {{managed=true}} in
> the respective annotation.
> Sadly we cannot add unit tests without adding a new module. But I think it's
> not really worth it. We should rather exclude those test for injection in
> FacesConverter and FacesValidator.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1423) JSF-2.3 managed() in FacesValidator and FacesConverter break CDI integration
[
https://issues.apache.org/jira/browse/DELTASPIKE-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17294690#comment-17294690
]
ASF subversion and git services commented on DELTASPIKE-1423:
-
Commit 181490a80e0159606199eb8509448bf468700178 in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=181490a ]
DELTASPIKE-1423 exlude tests which are broken w JSF-2.3
JSF-2.3 introduced some nasty backward incompatibilities.
Discussed with Gerhard - we rather should exclude them for now
if running on a container supporting JSF-2.3.
> JSF-2.3 managed() in FacesValidator and FacesConverter break CDI integration
>
>
> Key: DELTASPIKE-1423
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1423
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JSF-Module
>Affects Versions: 1.9.4
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
>
> JSF-2.3 introduced a new field 'managed' and also changed the way Factory
> Wrappers are invoked. This breaks quite a few things with the CDI integration.
> When people use JSF-2.3 container they now need to set {{managed=true}} in
> the respective annotation.
> Sadly we cannot add unit tests without adding a new module. But I think it's
> not really worth it. We should rather exclude those test for injection in
> FacesConverter and FacesValidator.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1314) ContainerCtrlTckTest fails with tomee7-build-managed
[ https://issues.apache.org/jira/browse/DELTASPIKE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17291951#comment-17291951 ] ASF subversion and git services commented on DELTASPIKE-1314: - Commit 3ca131009825a7ccd98a76ccc19f181e127a4d85 in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=3ca1310 ] DELTASPIKE-1314 fix tomee7-build-managed profile no other magic setting needed anymore to make it work. > ContainerCtrlTckTest fails with tomee7-build-managed > > > Key: DELTASPIKE-1314 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1314 > Project: DeltaSpike > Issue Type: Bug >Reporter: Thomas Andraschko >Assignee: Mark Struberg >Priority: Major > > mvn clean package -Ptomee7-build-managed > [~struberg] Could you check that? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1420) Update ASM to 9.0
[ https://issues.apache.org/jira/browse/DELTASPIKE-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246843#comment-17246843 ] ASF subversion and git services commented on DELTASPIKE-1420: - Commit c2b92702fe21d096a27250e21202f4a29c3580fb in deltaspike's branch refs/heads/master from Christian Beikov [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=c2b9270 ] DELTASPIKE-1420 upgrade to ASM 9.0 > Update ASM to 9.0 > - > > Key: DELTASPIKE-1420 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1420 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Proxy-Module >Affects Versions: 1.9.4 >Reporter: Christian Beikov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > We need a new release with ASM 9.0 to be able to test against Java 16. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1397) Detect the cycled variable references
[
https://issues.apache.org/jira/browse/DELTASPIKE-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17123947#comment-17123947
]
ASF subversion and git services commented on DELTASPIKE-1397:
-
Commit da93fe7882bfaaa816daba7a71401a21823d4e92 in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=da93fe7 ]
DELTASPIKE-1397 log variable in case of recursive definition
> Detect the cycled variable references
> -
>
> Key: DELTASPIKE-1397
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1397
> Project: DeltaSpike
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.1
> Environment: JDK 1.8
>Reporter: Andrew Marinchuk
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.4
>
>
> Due to mistake in config file, we encountered the
> java.lang.StackOverflowError.
> {code:title=properties}fs.docs.path=/opt/docsFolder
> fs.docs.path.IntegrationTest=/mnt/targetDocs
> fs.docs.path.Staging=${fs.docs.path.IntegrationTest}
> fs.docs.path.IntegrationTest=${fs.docs.path.IntegrationTest} <--- here is
> invalid copy-pasted string
> fs.docs.path.Production=${fs.docs.path.IntegrationTest}{code}{code:title=stack
> trace}
> at
> org.apache.deltaspike.core.impl.config.TypedResolverImpl.getValue(TypedResolverImpl.java:253)
>
> at
> org.apache.deltaspike.core.impl.config.TypedResolverImpl.resolveVariables(TypedResolverImpl.java:556)
>
> at
> org.apache.deltaspike.core.impl.config.TypedResolverImpl.getPropertyValue(TypedResolverImpl.java:590)
>
> at
> org.apache.deltaspike.core.impl.config.TypedResolverImpl.resolveStringValue(TypedResolverImpl.java:436)
>
> at
> org.apache.deltaspike.core.impl.config.TypedResolverImpl.getValue(TypedResolverImpl.java:253)
>
> at
> org.apache.deltaspike.core.impl.config.TypedResolverImpl.resolveVariables(TypedResolverImpl.java:556)
>
> at
> org.apache.deltaspike.core.impl.config.TypedResolverImpl.getPropertyValue(TypedResolverImpl.java:590)
>
> at
> org.apache.deltaspike.core.impl.config.TypedResolverImpl.resolveStringValue(TypedResolverImpl.java:436)
>
> at
> org.apache.deltaspike.core.impl.config.TypedResolverImpl.getValue(TypedResolverImpl.java:253)
> {code}
> It's very hard to find the configuration variable with a self-referencing
> problem because StackOverflowError's message does not contain information
> about variable with problem.
> Wrapping each TypedResolver.getValue()'s call into try-catch is not the best
> practice in app code, but it's possible to detect the simplest
> self-referencing issues in
> org.apache.deltaspike.core.impl.config.TypedResolverImpl.resolveVariables(String).
> The better (but much expensive) way is to track the reference chain during
> resolving variables or catching the StackOverflowError in library's code
> (it's not a good practice and will not help to find the core of reference
> loop because try-catch should be done at the first TypedResolver.getValue()'s
> call).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1358) Move shaded ASM classes from proxy-impl into a separate JAR
[ https://issues.apache.org/jira/browse/DELTASPIKE-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17123884#comment-17123884 ] ASF subversion and git services commented on DELTASPIKE-1358: - Commit b6fdf21c46a32c6f8a460f09728ab5ed6274ba95 in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=b6fdf21 ] DELTASPIKE-1358 upgrade to ASM-8.0.1 > Move shaded ASM classes from proxy-impl into a separate JAR > --- > > Key: DELTASPIKE-1358 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1358 > Project: DeltaSpike > Issue Type: Improvement > Components: Proxy-Module >Reporter: Christian Beikov >Assignee: Mark Struberg >Priority: Major > Fix For: 1.9.4 > > > The intention behind this is that this would allow me to have a local Maven > module that shades a new version of ASM. Right now, I'd have to checkout > deltaspike, update the ASM version in the proxy module, and build that > separately. It would be great if switching ASM versions could be made easier > this way. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1404) News links to post and examples.
[ https://issues.apache.org/jira/browse/DELTASPIKE-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17123873#comment-17123873 ] ASF subversion and git services commented on DELTASPIKE-1404: - Commit 4a7f385c99a82afd821603303aa53944fa020e2f in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=4a7f385 ] Merge pull request #106 from Daniel-Dos/DELTASPIKE-1404 DELTASPIKE-1404 - add some links for example and articles. > News links to post and examples. > > > Key: DELTASPIKE-1404 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1404 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) > Components: Documentation >Affects Versions: 1.9.3 >Reporter: Daniel Dias >Assignee: Mark Struberg >Priority: Minor > Fix For: 1.9.4 > > Attachments: DELTASPIKE-1404.patch > > Time Spent: 20m > Remaining Estimate: 0h > > I created some content referring to Deltaspike as a lecture and articles and > I would like to include it on the site. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1404) News links to post and examples.
[ https://issues.apache.org/jira/browse/DELTASPIKE-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17123871#comment-17123871 ] ASF subversion and git services commented on DELTASPIKE-1404: - Commit e46933fc118279d4898fb5454519a8717fd8c4a1 in deltaspike's branch refs/heads/master from Daniel Dias [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=e46933f ] DELTASPIKE-1404 - add some links for example and articles. > News links to post and examples. > > > Key: DELTASPIKE-1404 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1404 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) > Components: Documentation >Affects Versions: 1.9.3 >Reporter: Daniel Dias >Assignee: Mark Struberg >Priority: Minor > Fix For: 1.9.4 > > Attachments: DELTASPIKE-1404.patch > > Time Spent: 20m > Remaining Estimate: 0h > > I created some content referring to Deltaspike as a lecture and articles and > I would like to include it on the site. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1404) News links to post and examples.
[ https://issues.apache.org/jira/browse/DELTASPIKE-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17123872#comment-17123872 ] ASF subversion and git services commented on DELTASPIKE-1404: - Commit 4a7f385c99a82afd821603303aa53944fa020e2f in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=4a7f385 ] Merge pull request #106 from Daniel-Dos/DELTASPIKE-1404 DELTASPIKE-1404 - add some links for example and articles. > News links to post and examples. > > > Key: DELTASPIKE-1404 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1404 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) > Components: Documentation >Affects Versions: 1.9.3 >Reporter: Daniel Dias >Assignee: Mark Struberg >Priority: Minor > Fix For: 1.9.4 > > Attachments: DELTASPIKE-1404.patch > > Time Spent: 20m > Remaining Estimate: 0h > > I created some content referring to Deltaspike as a lecture and articles and > I would like to include it on the site. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1402) ~/.deltaspike/apache-deltaspike.properties doesn't pickup changes during runtime
[
https://issues.apache.org/jira/browse/DELTASPIKE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17123526#comment-17123526
]
ASF subversion and git services commented on DELTASPIKE-1402:
-
Commit 5ffcaf3b8243586e9a479f7a7e554a34c7669844 in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=5ffcaf3 ]
DELTASPIKE-1402 wait a bit longer
sadly a few file systems have a bigger lastModified granularity.
So we better wait a bit longer.
> ~/.deltaspike/apache-deltaspike.properties doesn't pickup changes during
> runtime
>
>
> Key: DELTASPIKE-1402
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1402
> Project: DeltaSpike
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.3
>Reporter: Mark Struberg
>Priority: Major
> Fix For: 1.9.4
>
>
> Right now the {{ConfigSource}} registered via
> {{org.apache.deltaspike.core.impl.config.DefaultConfigSourceProvider#addUserHomeConfigSource}}
> does not reload dynamically if the file got changed.
> That means DeltaSpike Config right now doesn't automatically pick up changes
> in this file.
> The same is true for other
> {{org.apache.deltaspike.core.impl.config.PropertyFileConfigSource}} but most
> of them are in a jar anyway, so it doesn't make any difference.
> Of course for PropertyFileConfigSources representing native files on the disk
> it might also be nice to detect dynamic changes.
> It might be perfectly fine to have changes only picked up based on the
> last-changed timestamp of the file and only checked every minute or so.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1402) ~/.deltaspike/apache-deltaspike.properties doesn't pickup changes during runtime
[
https://issues.apache.org/jira/browse/DELTASPIKE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17123428#comment-17123428
]
ASF subversion and git services commented on DELTASPIKE-1402:
-
Commit 118b9d3e63970fb94038d6f9379f9c261b4e609b in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=118b9d3 ]
DELTASPIKE-1402 add a way to disable dynamic reloading
by using a deltaspike_reload smaller 0 you can disable dynamic reloading.
> ~/.deltaspike/apache-deltaspike.properties doesn't pickup changes during
> runtime
>
>
> Key: DELTASPIKE-1402
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1402
> Project: DeltaSpike
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.3
>Reporter: Mark Struberg
>Priority: Major
> Fix For: 1.9.4
>
>
> Right now the {{ConfigSource}} registered via
> {{org.apache.deltaspike.core.impl.config.DefaultConfigSourceProvider#addUserHomeConfigSource}}
> does not reload dynamically if the file got changed.
> That means DeltaSpike Config right now doesn't automatically pick up changes
> in this file.
> The same is true for other
> {{org.apache.deltaspike.core.impl.config.PropertyFileConfigSource}} but most
> of them are in a jar anyway, so it doesn't make any difference.
> Of course for PropertyFileConfigSources representing native files on the disk
> it might also be nice to detect dynamic changes.
> It might be perfectly fine to have changes only picked up based on the
> last-changed timestamp of the file and only checked every minute or so.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1402) ~/.deltaspike/apache-deltaspike.properties doesn't pickup changes during runtime
[
https://issues.apache.org/jira/browse/DELTASPIKE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17122508#comment-17122508
]
ASF subversion and git services commented on DELTASPIKE-1402:
-
Commit 33c3c2483907c2b0974c0ac3288e6b004c9e438b in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=33c3c24 ]
DELTASPIKE-1402 dynamic reload of PropertyFileConfigSource
DeltaSpike can now dynamically reload configuration of property files in a
file:// location.
The time after which we look for file modification (via lastModified time stamp
of the file)
can be configured with a 'deltaspike_reload=60' property in seconds.
In this case 60 seconds.
If this property is not set we check for changes every 300 seconds or 5 Minutes.
> ~/.deltaspike/apache-deltaspike.properties doesn't pickup changes during
> runtime
>
>
> Key: DELTASPIKE-1402
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1402
> Project: DeltaSpike
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.3
>Reporter: Mark Struberg
>Priority: Major
> Fix For: 1.9.4
>
>
> Right now the {{ConfigSource}} registered via
> {{org.apache.deltaspike.core.impl.config.DefaultConfigSourceProvider#addUserHomeConfigSource}}
> does not reload dynamically if the file got changed.
> That means DeltaSpike Config right now doesn't automatically pick up changes
> in this file.
> The same is true for other
> {{org.apache.deltaspike.core.impl.config.PropertyFileConfigSource}} but most
> of them are in a jar anyway, so it doesn't make any difference.
> Of course for PropertyFileConfigSources representing native files on the disk
> it might also be nice to detect dynamic changes.
> It might be perfectly fine to have changes only picked up based on the
> last-changed timestamp of the file and only checked every minute or so.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-519) ClassLoader leak in ClassDeactivationUtils
[
https://issues.apache.org/jira/browse/DELTASPIKE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17110347#comment-17110347
]
ASF subversion and git services commented on DELTASPIKE-519:
Commit d826c9686ca85a79b4e8f52beda4ab78b38bb680 in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=d826c96 ]
DELTASPIKE-519 fix potential ClassLoader leak
> ClassLoader leak in ClassDeactivationUtils
> --
>
> Key: DELTASPIKE-519
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-519
> Project: DeltaSpike
> Issue Type: Bug
> Components: Core
>Affects Versions: 0.5
>Reporter: Moritz Bechler
>Assignee: Mark Struberg
>Priority: Critical
>
> ClassDeactivationUtils statically holds two maps (classDeactivatorMap,
> activationStatusCache) one having a classloader as key and the other a class.
> These entries are never removed resulting in leaks of the TCCL or the
> classloaders of Deactivatable classes if they do not equal the classloader
> loading deltaspike.
> Suggested fix:
> {code}
> /**
> * This Map holds the ClassLoader as first level to make it possible to
> have different configurations per
> * WebApplication in an EAR or other Multi-ClassLoader scenario.
> *
> * The Map then contains a List of {@link ClassDeactivator}s in order of
> their configured ordinal.
> */
> private static Map>
> classDeactivatorMap
> = Collections.synchronizedMap(new WeakHashMap List>());
> /**
> * Cache for the result. It won't contain many classes but it might be
> accessed frequently.
> * Valid entries are only true or false. If an entry isn't available or
> null, it gets calculated.
> */
> private static Map, Boolean>
> activationStatusCache
> = Collections.synchronizedMap(new WeakHashMap Deactivatable>, Boolean>());
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1409) ProjectStageTestControlTest doesn't work on Weld2
[
https://issues.apache.org/jira/browse/DELTASPIKE-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108589#comment-17108589
]
ASF subversion and git services commented on DELTASPIKE-1409:
-
Commit 70b589387e94fc21d201f10b8b930362cbee07f7 in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=70b5893 ]
DELTASPIKE-1409 disable test-control tests for Weld2
Weld2 has a problem with handling @Alternative classes which got vetoed.
Those tests work perfectly fine on Weld1, Weld3, OWB (any version) and
various EE containers. It's just broken on Weld2.
> ProjectStageTestControlTest doesn't work on Weld2
> -
>
> Key: DELTASPIKE-1409
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1409
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tests
>Affects Versions: 1.9.3
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.4
>
>
> ProjectStageTestControlTest fails in Weld3. It works fine in Weld1 Weld3 and
> also works fine in all other containers.
> The problem is that Weld2 interpreted some wording in the spec quite
> restrictive. If you have an {{}} in a beans.xml and the class is
> {{@Alternative}} BUT is vetoed via an extension, then many Weld 2 versions
> blow up. With some old ones it works though.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1408) Some Weld versions fail on CDI.current() depending on the ClassLoader setup
[
https://issues.apache.org/jira/browse/DELTASPIKE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108218#comment-17108218
]
ASF subversion and git services commented on DELTASPIKE-1408:
-
Commit 19606ca588233676a6db64cb61b81f382014181d in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=19606ca ]
DELTASPIKE-1408 in some situations CDI.current() doesn't work in Weld3
So we try a fallback onto CDI-1.0 tricks to resolve the BeanManager.
> Some Weld versions fail on CDI.current() depending on the ClassLoader setup
> ---
>
> Key: DELTASPIKE-1408
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1408
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Core
>Affects Versions: 1.9.3
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.4
>
>
> Weld 3.1.3.Final and others blow up with an internal Exception when calling
> {{CDI.current()}} in some situations (ClassLoader, boot order, not sure yet).
> What we can rather easily do is to fallback to our classic CDI-1.0 behaviour
> in this case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1405) upgrade to apache-parent 23 and fix distribution
[ https://issues.apache.org/jira/browse/DELTASPIKE-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17081719#comment-17081719 ] ASF subversion and git services commented on DELTASPIKE-1405: - Commit e346e97cb8b76130fe1d6a6902c9846ecddac797 in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=e346e97 ] DELTASPIKE-1405 upgrade to apache parent 23 and fix distribution > upgrade to apache-parent 23 and fix distribution > > > Key: DELTASPIKE-1405 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1405 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Build >Affects Versions: 1.9.3 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.9.4 > > > Right now we use a maven-assembly-plugin which fails for the full > distribution. > We also should upgrade to the latest apache-parent. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1403) Site has no reference to the release of version 1.9.3
[ https://issues.apache.org/jira/browse/DELTASPIKE-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070316#comment-17070316 ] ASF subversion and git services commented on DELTASPIKE-1403: - Commit b178a2d76c504487f87fbe3e129836458f9a02e7 in deltaspike's branch refs/heads/master from Thomas Andraschko [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=b178a2d ] Merge pull request #105 from Daniel-Dos/DELTASPIKE-1403 DELTASPIKE-1403 - fix version to 1.9.3 > Site has no reference to the release of version 1.9.3 > - > > Key: DELTASPIKE-1403 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1403 > Project: DeltaSpike > Issue Type: Bug > Components: Documentation >Affects Versions: 1.9.3 >Reporter: Daniel Dias >Priority: Major > Fix For: 1.9.4 > > Attachments: DELTASPIKE-1403.patch > > Time Spent: 20m > Remaining Estimate: 0h > > 1 - In main page still has 1.8.1 ([https://deltaspike.apache.org/)] > 2 - In Dowload page too ([https://deltaspike.apache.org/download.html)] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1403) Site has no reference to the release of version 1.9.3
[ https://issues.apache.org/jira/browse/DELTASPIKE-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070314#comment-17070314 ] ASF subversion and git services commented on DELTASPIKE-1403: - Commit 4494d7cb174c0ad344ef2ad87852822203190dcd in deltaspike's branch refs/heads/master from Daniel Dias [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=4494d7c ] DELTASPIKE-1403 > Site has no reference to the release of version 1.9.3 > - > > Key: DELTASPIKE-1403 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1403 > Project: DeltaSpike > Issue Type: Bug > Components: Documentation >Affects Versions: 1.9.3 >Reporter: Daniel Dias >Priority: Major > Fix For: 1.9.4 > > Attachments: DELTASPIKE-1403.patch > > Time Spent: 20m > Remaining Estimate: 0h > > 1 - In main page still has 1.8.1 ([https://deltaspike.apache.org/)] > 2 - In Dowload page too ([https://deltaspike.apache.org/download.html)] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1403) Site has no reference to the release of version 1.9.3
[ https://issues.apache.org/jira/browse/DELTASPIKE-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070315#comment-17070315 ] ASF subversion and git services commented on DELTASPIKE-1403: - Commit b178a2d76c504487f87fbe3e129836458f9a02e7 in deltaspike's branch refs/heads/master from Thomas Andraschko [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=b178a2d ] Merge pull request #105 from Daniel-Dos/DELTASPIKE-1403 DELTASPIKE-1403 - fix version to 1.9.3 > Site has no reference to the release of version 1.9.3 > - > > Key: DELTASPIKE-1403 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1403 > Project: DeltaSpike > Issue Type: Bug > Components: Documentation >Affects Versions: 1.9.3 >Reporter: Daniel Dias >Priority: Major > Fix For: 1.9.4 > > Attachments: DELTASPIKE-1403.patch > > Time Spent: 20m > Remaining Estimate: 0h > > 1 - In main page still has 1.8.1 ([https://deltaspike.apache.org/)] > 2 - In Dowload page too ([https://deltaspike.apache.org/download.html)] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1398) Weblogic memory leak
[
https://issues.apache.org/jira/browse/DELTASPIKE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16994602#comment-16994602
]
ASF subversion and git services commented on DELTASPIKE-1398:
-
Commit 02e33e5125b995a184e7678f0938ad107e98cd2e in deltaspike's branch
refs/heads/master from Thomas Andraschko
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=02e33e5 ]
DELTASPIKE-1398 - fixed delegation and change it to more agressive use of
CDI.current. This also fixes the mem leak as our caching isn't used anymore.
> Weblogic memory leak
>
>
> Key: DELTASPIKE-1398
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1398
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Core
>Affects Versions: 1.8.0
>Reporter: THEODOROS CHAIKALIS
>Priority: Blocker
> Fix For: 1.9.2
>
> Attachments: mleak-1.png, mleak-2-leak.png, mleak-2.png,
> mleak-debug1.png, mleak-debug2.png, mleak-debug3.png, server_small.war,
> server_small.zip
>
>
> This extends previously reported issue 1392
> Iam returning back to a previously reported serious memory leak in Weblogic
> 12.2.1-3.
> To be more precise: EJB helpler classes (EJBName_randomChars_NoIntfViewImpl)
> are not being garbage collected after application removal.
>
> Steps to reproduce:
>
> # deploy the attached war (server-small)
> # {{open the webpage at /server-small/views/index.xhtml (mleak2)}}
> # monitor the classes created with a profiler (with starting name
> gr.teohaik...) (mleak1)
> # delete the app
> # check again the profiler. The ejbs are still there! (mleak3)
>
> A suggestion in 1392 was to debug BeanManagerProvider, so we did.
> {{but bpmSingleton.bminfos contains 2 objects. but method }}
> {{cleanupStoredBeanManagerOnShutdown(@Observes BeforeShutdown beforeShutdown)
> }}
> {{is called only once}}
> Attached you can see relevant object contents in the debugger screenshots
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1364) Variable Replacement with @ConfigProperty not project stage aware
[
https://issues.apache.org/jira/browse/DELTASPIKE-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16971205#comment-16971205
]
ASF subversion and git services commented on DELTASPIKE-1364:
-
Commit 63bbcfb75f437c7cee2578c07a4131e18e709ecf in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=63bbcfb ]
DELTASPIKE-1364 Variables in @ConfigProperty
Unit test only.
Seems I already fixed that while reworking the Config to an interface.
> Variable Replacement with @ConfigProperty not project stage aware
> -
>
> Key: DELTASPIKE-1364
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1364
> Project: DeltaSpike
> Issue Type: Bug
> Components: Configuration
>Affects Versions: 1.8.2
>Reporter: Nicolò Chieffo
>Assignee: Mark Struberg
>Priority: Major
>
> reading a property with injection does not correctly use project stage
> properties.
> I have a property file with this content:
>
> {code:java}
> xxx.frontend.prefix=https://dev.xxx.it
> xxx.frontend.prefix.Production=https://prod.xxx.it
> xxx.rsalogin.url=${xxx.frontend.prefix}/#/rsalogin/{rsalogin}
> {code}
>
>
> when reading xxx.rsalogin.url using annontations
> {code:java}
> @Inject
> @ConfigProperty(name = "xxx.rsalogin.url")
> private String url;
> {code}
> In the production environment (noticed that I don't have a
> org.apache.deltaspike.ProjectStage=Production property set because by default
> the stage is Production) it should be evaluated as
> *[https://prod.xxx.it/#/rsalogin/\{rsalogin}|https://prod.xxx.it/#/rsalogin/]*
> but instead I get
> *[https://dev.xxx.it/#/rsalogin/\{rsalogin}|https://dev.xxx.it/#/rsalogin/]*
> When using the declarative API it works correctly
> {code:java}
> ConfigResolver.getProjectStageAwarePropertyValue("xxx.rsalogin.url",
> "");{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1396) Incorrect parameter meaning in AbstractQuartzScheduler.stop of Scheduler Module
[ https://issues.apache.org/jira/browse/DELTASPIKE-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969891#comment-16969891 ] ASF subversion and git services commented on DELTASPIKE-1396: - Commit c7b3a2ea084c40066b533de13f57b28eb21da876 in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=c7b3a2e ] DELTASPIKE-1396 switch default to false for backward compat reasons Since the deltaspike.scheduler.force_stop logic was inverted we now also have to invert the default from TRUE to FALSE as noted by Gary Hodgson. > Incorrect parameter meaning in AbstractQuartzScheduler.stop of Scheduler > Module > --- > > Key: DELTASPIKE-1396 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1396 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Gary Hodgson >Assignee: Mark Struberg >Priority: Major > Fix For: 1.9.2 > > Time Spent: 10m > Remaining Estimate: 0h > > The AbstractQuartzScheduler.stop method calls the shutdown method of the > Quartz scheduler with the base config of "deltaspike.scheduler.force_stop": > > this.scheduler.shutdown(SchedulerBaseConfig.LifecycleIntegration.FORCE_STOP); > > ([https://github.com/apache/deltaspike/blob/master/deltaspike/modules/scheduler/impl/src/main/java/org/apache/deltaspike/scheduler/impl/AbstractQuartzScheduler.java#L161]) > However the parameter is called waitForJobsToComplete > * @param waitForJobsToComplete > * if true the scheduler will not allow this method > * to return until all currently executing jobs have completed. > which means the config actually does the opposite of what it intends, i.e. > deltaspike.scheduler.force_stop=true would actually wait for the executing > jobs to complete rather than stopping immediately. > I presume this would be fixed by negating the parameter: > > this.scheduler.shutdown(!SchedulerBaseConfig.LifecycleIntegration.FORCE_STOP); > > Mailing List Thread: > [https://lists.apache.org/thread.html/366d51433ea5c5deb7e1d83e09891e426bff9cae0eb6bff98990eb40@%3Cusers.deltaspike.apache.org%3E] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1396) Incorrect parameter meaning in AbstractQuartzScheduler.stop of Scheduler Module
[ https://issues.apache.org/jira/browse/DELTASPIKE-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969612#comment-16969612 ] ASF subversion and git services commented on DELTASPIKE-1396: - Commit 4794da1f7cd2e566a4c241c8ea6d74ee523d3c3a in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=4794da1 ] DELTASPIKE-1396 inverted waitForJobsToComplete logic txs to Gary Hodgson for the report and catch! > Incorrect parameter meaning in AbstractQuartzScheduler.stop of Scheduler > Module > --- > > Key: DELTASPIKE-1396 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1396 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Gary Hodgson >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The AbstractQuartzScheduler.stop method calls the shutdown method of the > Quartz scheduler with the base config of "deltaspike.scheduler.force_stop": > > this.scheduler.shutdown(SchedulerBaseConfig.LifecycleIntegration.FORCE_STOP); > > ([https://github.com/apache/deltaspike/blob/master/deltaspike/modules/scheduler/impl/src/main/java/org/apache/deltaspike/scheduler/impl/AbstractQuartzScheduler.java#L161]) > However the parameter is called waitForJobsToComplete > * @param waitForJobsToComplete > * if true the scheduler will not allow this method > * to return until all currently executing jobs have completed. > which means the config actually does the opposite of what it intends, i.e. > deltaspike.scheduler.force_stop=true would actually wait for the executing > jobs to complete rather than stopping immediately. > I presume this would be fixed by negating the parameter: > > this.scheduler.shutdown(!SchedulerBaseConfig.LifecycleIntegration.FORCE_STOP); > > Mailing List Thread: > [https://lists.apache.org/thread.html/366d51433ea5c5deb7e1d83e09891e426bff9cae0eb6bff98990eb40@%3Cusers.deltaspike.apache.org%3E] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1386) Unhandled Exception in DefaultConfigSourceProvider causes deployment failure
[
https://issues.apache.org/jira/browse/DELTASPIKE-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952249#comment-16952249
]
ASF subversion and git services commented on DELTASPIKE-1386:
-
Commit 0eff953a7e5a4df01ab8ded7a1737fd9278178a3 in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=0eff953 ]
DELTASPIKE-1386 check SecurityAccess when accessing user home dir
txs to Thomas Frühbeck for the report!
> Unhandled Exception in DefaultConfigSourceProvider causes deployment failure
>
>
> Key: DELTASPIKE-1386
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1386
> Project: DeltaSpike
> Issue Type: Bug
> Components: Core
>Affects Versions: 1.9.1
>Reporter: Thomas Frühbeck
>Assignee: Mark Struberg
>Priority: Major
>
> For some reason DefaultConfigSourceProvider tries to access the home
> directory of the services user.
> If the access is prohibited by SecurityManager, the AccessControlException is
> not handled and the deployment of the complete application fails.
> 2019-09-15 23:19:21,075 ERROR [org.jboss.msc.service.fail] (MSC service
> thread 1-6) MSC01: Failed to start service
> jboss.deployment.unit."mssms-sec-ear.ear".POST_MODULE:
> org.jboss.msc.service.StartException in service jboss.
> deployment.unit."mssms-sec-ear.ear".POST_MODULE: WFLYSRV0153: Failed to
> process phase POST_MODULE of deployment "mssms-sec-ear.ear"
> at
> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.util.ServiceConfigurationError:
> org.apache.deltaspike.core.spi.config.ConfigSourceProvider: Provider
> org.apache.deltaspike.core.impl.config.DefaultConfigSourceProvider could not
> be instantiated
> at java.util.ServiceLoader.fail(ServiceLoader.java:232)
> at java.util.ServiceLoader.access$100(ServiceLoader.java:185)
> at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:384)
> at java.util.ServiceLoader$LazyIterator.access$700(ServiceLoader.java:323)
> at java.util.ServiceLoader$LazyIterator$2.run(ServiceLoader.java:407)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:409)
> at java.util.ServiceLoader$1.next(ServiceLoader.java:480)
> at
> org.apache.deltaspike.core.util.ServiceUtils.loadServiceImplementations(ServiceUtils.java:81)
> at org.apache.deltaspike.core.impl.config.ConfigImpl.init(ConfigImpl.java:70)
> at
> org.apache.deltaspike.core.impl.config.ConfigProviderImpl.getConfig(ConfigProviderImpl.java:53)
> at
> org.apache.deltaspike.core.impl.config.ConfigProviderImpl.getConfig(ConfigProviderImpl.java:43)
> at
> org.apache.deltaspike.core.api.config.ConfigResolver.resolve(ConfigResolver.java:613)
> at
> org.apache.deltaspike.core.api.config.base.CoreBaseConfig$BeanManagerIntegration.(CoreBaseConfig.java:30)
> at
> org.apache.deltaspike.core.api.provider.BeanManagerProvider.(BeanManagerProvider.java:79)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at
> org.jboss.as.weld.deployment.WeldPortableExtensions.tryRegisterExtension(WeldPortableExtensions.java:53)
> at
> org.jboss.as.weld.deployment.processors.WeldPortableExtensionProcessor.loadAttachments(WeldPortableExtensionProcessor.java:121)
> at
> org.jboss.as.weld.deployment.processors.WeldPortableExtensionProcessor.deploy(WeldPortableExtensionProcessor.java:81)
> at
> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
> ... 5 more
> Caused by: java.security.AccessControlException: WFSM01: Permission check
> failed (permission "("java.io.FilePermission"
> "/home/thomas/.deltaspike/apache-deltaspike.properties" "read")" in code
> source "(vfs:/work/java/mssms/w
> ildfly1011/standalone/deployments/mssms-sec-ear.ear/lib/deltaspike-core-api-1.9.0.jar
> )" of "null")
> at
>
[jira] [Commented] (DELTASPIKE-1390) Client window handler doesn't work with frames
[ https://issues.apache.org/jira/browse/DELTASPIKE-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950283#comment-16950283 ] ASF subversion and git services commented on DELTASPIKE-1390: - Commit f9f0c6aaf997d7a8224d06290048f2e8eae5f1d7 in deltaspike's branch refs/heads/master from Thomas Andraschko [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=f9f0c6a ] Merge pull request #98 from beikov/DELTASPIKE-1390 DELTASPIKE-1390 - Test and fix for CLIENTWINDOW mode with frames > Client window handler doesn't work with frames > -- > > Key: DELTASPIKE-1390 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1390 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) > Components: JSF-Module >Reporter: Christian Beikov >Priority: Major > Fix For: 1.9.2 > > Time Spent: 40m > Remaining Estimate: 0h > > The CLIENTWINDOW handler code loses the window when frames are involved. > Using e.g. a window scoped bean with the Primefaces Dialog Framework will > result in issues. The bean is initialized in window1. A click on a button > opens a dialog, which is opened through an iframe, but the dialog doesn't use > the window id defined in the parent window. If a button in the dialog > requires the original bean, it will find an uninitialized bean, because the > frame gets a new window id window2. > The solution is to use the root window for the window id. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1391) CLIENTWINDOW JS code breaks Primefaces tabview
[
https://issues.apache.org/jira/browse/DELTASPIKE-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950282#comment-16950282
]
ASF subversion and git services commented on DELTASPIKE-1391:
-
Commit 4a05ebf6c8b4c43b5bf1cb2505950589f9beb2de in deltaspike's branch
refs/heads/master from Christian Beikov
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=4a05ebf ]
DELTASPIKE-1391 - Never install tokenized redirect handler for any anchor links
> CLIENTWINDOW JS code breaks Primefaces tabview
> --
>
> Key: DELTASPIKE-1391
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1391
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JSF-Module
>Reporter: Christian Beikov
>Priority: Major
> Fix For: 1.9.2
>
>
> Using a Primefaces tabview is impossible with the CLIENTWINDOW JS code as it
> will do a page redirect for links that have a href like {{#tabview:tabId}}
> which is due to the fact, that all links except ones with just {{#}} in the
> href, get a special onclick handler causing this. The intent of the handler
> is to handle opening new windows, but it should ignore any links with any
> kind of anchor navigation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1390) Client window handler doesn't work with frames
[ https://issues.apache.org/jira/browse/DELTASPIKE-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950281#comment-16950281 ] ASF subversion and git services commented on DELTASPIKE-1390: - Commit cdc155ef3042ec93bce3574eef78e9d78eaecbad in deltaspike's branch refs/heads/master from Christian Beikov [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=cdc155e ] DELTASPIKE-1390 - Fix CLIENTWINDOW mode to work with frames > Client window handler doesn't work with frames > -- > > Key: DELTASPIKE-1390 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1390 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) > Components: JSF-Module >Reporter: Christian Beikov >Priority: Major > Fix For: 1.9.2 > > Time Spent: 40m > Remaining Estimate: 0h > > The CLIENTWINDOW handler code loses the window when frames are involved. > Using e.g. a window scoped bean with the Primefaces Dialog Framework will > result in issues. The bean is initialized in window1. A click on a button > opens a dialog, which is opened through an iframe, but the dialog doesn't use > the window id defined in the parent window. If a button in the dialog > requires the original bean, it will find an uninitialized bean, because the > frame gets a new window id window2. > The solution is to use the root window for the window id. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1390) Client window handler doesn't work with frames
[ https://issues.apache.org/jira/browse/DELTASPIKE-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950284#comment-16950284 ] ASF subversion and git services commented on DELTASPIKE-1390: - Commit f9f0c6aaf997d7a8224d06290048f2e8eae5f1d7 in deltaspike's branch refs/heads/master from Thomas Andraschko [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=f9f0c6a ] Merge pull request #98 from beikov/DELTASPIKE-1390 DELTASPIKE-1390 - Test and fix for CLIENTWINDOW mode with frames > Client window handler doesn't work with frames > -- > > Key: DELTASPIKE-1390 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1390 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) > Components: JSF-Module >Reporter: Christian Beikov >Priority: Major > Fix For: 1.9.2 > > Time Spent: 40m > Remaining Estimate: 0h > > The CLIENTWINDOW handler code loses the window when frames are involved. > Using e.g. a window scoped bean with the Primefaces Dialog Framework will > result in issues. The bean is initialized in window1. A click on a button > opens a dialog, which is opened through an iframe, but the dialog doesn't use > the window id defined in the parent window. If a button in the dialog > requires the original bean, it will find an uninitialized bean, because the > frame gets a new window id window2. > The solution is to use the root window for the window id. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1390) Client window handler doesn't work with frames
[ https://issues.apache.org/jira/browse/DELTASPIKE-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950280#comment-16950280 ] ASF subversion and git services commented on DELTASPIKE-1390: - Commit 3eba0378b4ddd613749ed60a5353f73fff76b89f in deltaspike's branch refs/heads/master from Christian Beikov [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=3eba037 ] DELTASPIKE-1390 - Test that frames don't work with CLIENTWINDOW mode > Client window handler doesn't work with frames > -- > > Key: DELTASPIKE-1390 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1390 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) > Components: JSF-Module >Reporter: Christian Beikov >Priority: Major > Fix For: 1.9.2 > > Time Spent: 40m > Remaining Estimate: 0h > > The CLIENTWINDOW handler code loses the window when frames are involved. > Using e.g. a window scoped bean with the Primefaces Dialog Framework will > result in issues. The bean is initialized in window1. A click on a button > opens a dialog, which is opened through an iframe, but the dialog doesn't use > the window id defined in the parent window. If a button in the dialog > requires the original bean, it will find an uninitialized bean, because the > frame gets a new window id window2. > The solution is to use the root window for the window id. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1388) Can't extend Repository defined as an interface
[
https://issues.apache.org/jira/browse/DELTASPIKE-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16946627#comment-16946627
]
ASF subversion and git services commented on DELTASPIKE-1388:
-
Commit 7cfff5a23812520073286e427583e020cd87c932 in deltaspike's branch
refs/heads/master from Thomas Andraschko
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=7cfff5a ]
Merge pull request #97 from twyszomirski/DELTASPIKE-1388
DELTASPIKE-1388 - Fix initialization issue when using repos extended on
interface
> Can't extend Repository defined as an interface
> ---
>
> Key: DELTASPIKE-1388
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1388
> Project: DeltaSpike
> Issue Type: Bug
> Components: Data-Module
>Affects Versions: 1.9.1
>Reporter: Tomasz Wyszomirski
>Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When I define my repository of interface like this:
> @Repository
> public interface SuperRepository extends FullEntityRepository< MyEntity,
> Long>{}
> and try to extend it like this:
> @Repository
> public interface ExtendedRepository extends SuperRepository {}
>
> I get initialization failure in:
> org.apache.deltaspike.data.impl.metaEntityMetadataInitializer#init(RepositoryMetadata)[39]
> Caused by: java.lang.NullPointerException
> rcs-cps | at
> deployment.rcs-cps-deployable.war//org.apache.deltaspike.data.impl.meta.EntityMetadataInitializer.init(EntityMetadataInitializer.java:39)
> rcs-cps | at
> deployment.rcs-cps-deployable.war//org.apache.deltaspike.data.impl.meta.EntityMetadataInitializer$Proxy$_$$_WeldClientProxy.init(Unknown
> Source)
> rcs-cps | at
> deployment.rcs-cps-deployable.war//org.apache.deltaspike.data.impl.meta.RepositoryMetadataInitializer.init(RepositoryMetadataInitializer.java:83)
> rcs-cps | at
> deployment.rcs-cps-deployable.war//org.apache.deltaspike.data.impl.meta.RepositoryMetadataInitializer$Proxy$_$$_WeldClientProxy.init(Unknown
> Source)
> rcs-cps | at
> deployment.rcs-cps-deployable.war//org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.init(RepositoryMetadataHandler.java:50)
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1388) Can't extend Repository defined as an interface
[
https://issues.apache.org/jira/browse/DELTASPIKE-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16946628#comment-16946628
]
ASF subversion and git services commented on DELTASPIKE-1388:
-
Commit 7cfff5a23812520073286e427583e020cd87c932 in deltaspike's branch
refs/heads/master from Thomas Andraschko
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=7cfff5a ]
Merge pull request #97 from twyszomirski/DELTASPIKE-1388
DELTASPIKE-1388 - Fix initialization issue when using repos extended on
interface
> Can't extend Repository defined as an interface
> ---
>
> Key: DELTASPIKE-1388
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1388
> Project: DeltaSpike
> Issue Type: Bug
> Components: Data-Module
>Affects Versions: 1.9.1
>Reporter: Tomasz Wyszomirski
>Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When I define my repository of interface like this:
> @Repository
> public interface SuperRepository extends FullEntityRepository< MyEntity,
> Long>{}
> and try to extend it like this:
> @Repository
> public interface ExtendedRepository extends SuperRepository {}
>
> I get initialization failure in:
> org.apache.deltaspike.data.impl.metaEntityMetadataInitializer#init(RepositoryMetadata)[39]
> Caused by: java.lang.NullPointerException
> rcs-cps | at
> deployment.rcs-cps-deployable.war//org.apache.deltaspike.data.impl.meta.EntityMetadataInitializer.init(EntityMetadataInitializer.java:39)
> rcs-cps | at
> deployment.rcs-cps-deployable.war//org.apache.deltaspike.data.impl.meta.EntityMetadataInitializer$Proxy$_$$_WeldClientProxy.init(Unknown
> Source)
> rcs-cps | at
> deployment.rcs-cps-deployable.war//org.apache.deltaspike.data.impl.meta.RepositoryMetadataInitializer.init(RepositoryMetadataInitializer.java:83)
> rcs-cps | at
> deployment.rcs-cps-deployable.war//org.apache.deltaspike.data.impl.meta.RepositoryMetadataInitializer$Proxy$_$$_WeldClientProxy.init(Unknown
> Source)
> rcs-cps | at
> deployment.rcs-cps-deployable.war//org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.init(RepositoryMetadataHandler.java:50)
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1388) Can't extend Repository defined as an interface
[
https://issues.apache.org/jira/browse/DELTASPIKE-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16946626#comment-16946626
]
ASF subversion and git services commented on DELTASPIKE-1388:
-
Commit ae9f7523ffee786576ee76429d9632f90f4e8b1b in deltaspike's branch
refs/heads/master from Tomasz Wyszomirski
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=ae9f752 ]
DELTASPIKE-1388 - Fix initialization issue when using repos extended on
interface.
> Can't extend Repository defined as an interface
> ---
>
> Key: DELTASPIKE-1388
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1388
> Project: DeltaSpike
> Issue Type: Bug
> Components: Data-Module
>Affects Versions: 1.9.1
>Reporter: Tomasz Wyszomirski
>Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When I define my repository of interface like this:
> @Repository
> public interface SuperRepository extends FullEntityRepository< MyEntity,
> Long>{}
> and try to extend it like this:
> @Repository
> public interface ExtendedRepository extends SuperRepository {}
>
> I get initialization failure in:
> org.apache.deltaspike.data.impl.metaEntityMetadataInitializer#init(RepositoryMetadata)[39]
> Caused by: java.lang.NullPointerException
> rcs-cps | at
> deployment.rcs-cps-deployable.war//org.apache.deltaspike.data.impl.meta.EntityMetadataInitializer.init(EntityMetadataInitializer.java:39)
> rcs-cps | at
> deployment.rcs-cps-deployable.war//org.apache.deltaspike.data.impl.meta.EntityMetadataInitializer$Proxy$_$$_WeldClientProxy.init(Unknown
> Source)
> rcs-cps | at
> deployment.rcs-cps-deployable.war//org.apache.deltaspike.data.impl.meta.RepositoryMetadataInitializer.init(RepositoryMetadataInitializer.java:83)
> rcs-cps | at
> deployment.rcs-cps-deployable.war//org.apache.deltaspike.data.impl.meta.RepositoryMetadataInitializer$Proxy$_$$_WeldClientProxy.init(Unknown
> Source)
> rcs-cps | at
> deployment.rcs-cps-deployable.war//org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.init(RepositoryMetadataHandler.java:50)
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1387) Update ASM to 7.2
[ https://issues.apache.org/jira/browse/DELTASPIKE-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16944475#comment-16944475 ] ASF subversion and git services commented on DELTASPIKE-1387: - Commit 966d6dd326d742699d65827e7512c60f4f2db5a4 in deltaspike's branch refs/heads/master from Thomas Andraschko [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=966d6dd ] Merge pull request #96 from beikov/patch-1 DELTASPIKE-1387 - Update ASM to 7.2 for Java 13 support > Update ASM to 7.2 > - > > Key: DELTASPIKE-1387 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1387 > Project: DeltaSpike > Issue Type: Improvement > Components: Proxy-Module >Affects Versions: 1.9.1 >Reporter: Christian Beikov >Priority: Major > Fix For: 1.9.2 > > Time Spent: 3h > Remaining Estimate: 0h > > Java 13 was just released and has a new class file version and ASM 7.0 does > not have support for that. ASM 7.2 on the other hand already does. Since it's > a minor update, please get that into 1.9.2 so we can start testing with Java > 13. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1387) Update ASM to 7.2
[ https://issues.apache.org/jira/browse/DELTASPIKE-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16944474#comment-16944474 ] ASF subversion and git services commented on DELTASPIKE-1387: - Commit 2633035598ea0d44db9ea157f8bcadfadcf50ba9 in deltaspike's branch refs/heads/master from Christian Beikov [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=2633035 ] DELTASPIKE-1387 - Update ASM to 7.1 for Java 13 support > Update ASM to 7.2 > - > > Key: DELTASPIKE-1387 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1387 > Project: DeltaSpike > Issue Type: Improvement > Components: Proxy-Module >Affects Versions: 1.9.1 >Reporter: Christian Beikov >Priority: Major > Fix For: 1.9.2 > > Time Spent: 3h > Remaining Estimate: 0h > > Java 13 was just released and has a new class file version and ASM 7.0 does > not have support for that. ASM 7.2 on the other hand already does. Since it's > a minor update, please get that into 1.9.2 so we can start testing with Java > 13. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1385) support init under high load
[ https://issues.apache.org/jira/browse/DELTASPIKE-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905551#comment-16905551 ] ASF subversion and git services commented on DELTASPIKE-1385: - Commit 752a4a57fa79a939dc1713d4c8bbc83b3fc6df5e in deltaspike's branch refs/heads/master from Gerhard Petracek [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=752a4a5 ] DELTASPIKE-1385 added support for init under high load > support init under high load > > > Key: DELTASPIKE-1385 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1385 > Project: DeltaSpike > Issue Type: Improvement > Components: BeanValidation-Module, Core, JSF-Module >Affects Versions: 1.9.0 >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek >Priority: Major > Fix For: 1.9.1 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (DELTASPIKE-1385) support init under high load
[ https://issues.apache.org/jira/browse/DELTASPIKE-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905550#comment-16905550 ] ASF subversion and git services commented on DELTASPIKE-1385: - Commit 8cc79884c6e2d0490eaa3a3c69dc6d0073973783 in deltaspike's branch refs/heads/master from Gerhard Petracek [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=8cc7988 ] DELTASPIKE-1385 added support for init under high load > support init under high load > > > Key: DELTASPIKE-1385 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1385 > Project: DeltaSpike > Issue Type: Improvement > Components: BeanValidation-Module, Core, JSF-Module >Affects Versions: 1.9.0 >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek >Priority: Major > Fix For: 1.9.1 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (DELTASPIKE-1385) support init under high load
[ https://issues.apache.org/jira/browse/DELTASPIKE-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905552#comment-16905552 ] ASF subversion and git services commented on DELTASPIKE-1385: - Commit 8936f921f39d270ecd5cc762d92c0b66f579b61d in deltaspike's branch refs/heads/master from Gerhard Petracek [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=8936f92 ] DELTASPIKE-1385 added support for init under high load > support init under high load > > > Key: DELTASPIKE-1385 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1385 > Project: DeltaSpike > Issue Type: Improvement > Components: BeanValidation-Module, Core, JSF-Module >Affects Versions: 1.9.0 >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek >Priority: Major > Fix For: 1.9.1 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (DELTASPIKE-1377) issue with @Repository + @Query annotation and clustered wildfly
[
https://issues.apache.org/jira/browse/DELTASPIKE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886063#comment-16886063
]
ASF subversion and git services commented on DELTASPIKE-1377:
-
Commit 7909fc405176ab4f718f3901350983e81378ac37 in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=7909fc4 ]
DELTASPIKE-1377 also fix issue with nested arrays
txs to Vladimir Dvorak (skybber) for the report and parts of the patch.
> issue with @Repository + @Query annotation and clustered wildfly
> -
>
> Key: DELTASPIKE-1377
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1377
> Project: DeltaSpike
> Issue Type: Bug
> Components: Data-Module
>Affects Versions: 1.9.0
>Reporter: Andrew Schmidt
>Assignee: Mark Struberg
>Priority: Major
> Attachments: cdri-test.zip, stack.txt
>
>
> Setup: 2 x wildfly 15.0.1.Final (weld-core updated to 3.0.6)
> Clustered standalone-full-ha setup, same machine with a port offset for the
> second machine.
>
> Repo:
> {code:java}
> @Repository
> @ApplicationScoped
> public interface AnimalRepo extends EntityRepository
> {
>@Query( value = "select a from Animal a where ?1 = a.name" )
>Animal findByName(String name);
> }
> {code}
> Session bean:
> {code:java}
> @SessionScoped
> @Named
> public class MyBean implements Serializable
> {
> private static final long serialVersionUID = 1L;
> @Inject
> private AnimalRepo animalRepo;
> public Long getTest()
> {
> return animalRepo.count();
> }
> }
> {code}
> index.xhtml
> {code:java}
>
> #{myBean.test}
>
> {code}
> Visiting the first server yields no error, but upon visiting the second
> server:
> {code:java}
> WELD-001500: Failed to deserialize proxy object with beanId
> org.apache.deltaspike.core.util.bean.ImmutableBeanWrapper:AnimalRepo[@javax.enterprise.context.ApplicationScoped()@org.apache.deltaspike.data.api.Repository(forEntity=class
>
> java.lang.Object,methodPrefix=)]{AnimalRepo.findByName[@org.apache.deltaspike.data.api.Query(hints=[Ljavax.persistence.QueryHint;@774c6737,isNative=false,lock=NONE,max=0,named=,singleResult=JPA,value=select
> a from Animal where ?1 = a.name)](java.lang.String);}
> {code}
> Interestingly, If the @Query annotation is removed from the findByName
> query, there is no issue.
> See attached project.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (DELTASPIKE-1377) issue with @Repository + @Query annotation and clustered wildfly
[
https://issues.apache.org/jira/browse/DELTASPIKE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886039#comment-16886039
]
ASF subversion and git services commented on DELTASPIKE-1377:
-
Commit ab2fa0d1715084a364c666504ad4b4ea74a23cdc in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=ab2fa0d ]
DELTASPIKE-1377 fix array handling for native types
> issue with @Repository + @Query annotation and clustered wildfly
> -
>
> Key: DELTASPIKE-1377
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1377
> Project: DeltaSpike
> Issue Type: Bug
> Components: Data-Module
>Affects Versions: 1.9.0
>Reporter: Andrew Schmidt
>Assignee: Mark Struberg
>Priority: Major
> Attachments: cdri-test.zip, stack.txt
>
>
> Setup: 2 x wildfly 15.0.1.Final (weld-core updated to 3.0.6)
> Clustered standalone-full-ha setup, same machine with a port offset for the
> second machine.
>
> Repo:
> {code:java}
> @Repository
> @ApplicationScoped
> public interface AnimalRepo extends EntityRepository
> {
>@Query( value = "select a from Animal a where ?1 = a.name" )
>Animal findByName(String name);
> }
> {code}
> Session bean:
> {code:java}
> @SessionScoped
> @Named
> public class MyBean implements Serializable
> {
> private static final long serialVersionUID = 1L;
> @Inject
> private AnimalRepo animalRepo;
> public Long getTest()
> {
> return animalRepo.count();
> }
> }
> {code}
> index.xhtml
> {code:java}
>
> #{myBean.test}
>
> {code}
> Visiting the first server yields no error, but upon visiting the second
> server:
> {code:java}
> WELD-001500: Failed to deserialize proxy object with beanId
> org.apache.deltaspike.core.util.bean.ImmutableBeanWrapper:AnimalRepo[@javax.enterprise.context.ApplicationScoped()@org.apache.deltaspike.data.api.Repository(forEntity=class
>
> java.lang.Object,methodPrefix=)]{AnimalRepo.findByName[@org.apache.deltaspike.data.api.Query(hints=[Ljavax.persistence.QueryHint;@774c6737,isNative=false,lock=NONE,max=0,named=,singleResult=JPA,value=select
> a from Animal where ?1 = a.name)](java.lang.String);}
> {code}
> Interestingly, If the @Query annotation is removed from the findByName
> query, there is no issue.
> See attached project.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (DELTASPIKE-1377) issue with @Repository + @Query annotation and clustered wildfly
[
https://issues.apache.org/jira/browse/DELTASPIKE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886038#comment-16886038
]
ASF subversion and git services commented on DELTASPIKE-1377:
-
Commit 6f7de55890adb92fca49985380fe9dfb65e821f8 in deltaspike's branch
refs/heads/master from Vladimir Dvorak
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=6f7de55 ]
DELTASPIKE-1377 fix typeId evaluation
Signed-off-by: Mark Struberg
> issue with @Repository + @Query annotation and clustered wildfly
> -
>
> Key: DELTASPIKE-1377
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1377
> Project: DeltaSpike
> Issue Type: Bug
> Components: Data-Module
>Affects Versions: 1.9.0
>Reporter: Andrew Schmidt
>Assignee: Mark Struberg
>Priority: Major
> Attachments: cdri-test.zip, stack.txt
>
>
> Setup: 2 x wildfly 15.0.1.Final (weld-core updated to 3.0.6)
> Clustered standalone-full-ha setup, same machine with a port offset for the
> second machine.
>
> Repo:
> {code:java}
> @Repository
> @ApplicationScoped
> public interface AnimalRepo extends EntityRepository
> {
>@Query( value = "select a from Animal a where ?1 = a.name" )
>Animal findByName(String name);
> }
> {code}
> Session bean:
> {code:java}
> @SessionScoped
> @Named
> public class MyBean implements Serializable
> {
> private static final long serialVersionUID = 1L;
> @Inject
> private AnimalRepo animalRepo;
> public Long getTest()
> {
> return animalRepo.count();
> }
> }
> {code}
> index.xhtml
> {code:java}
>
> #{myBean.test}
>
> {code}
> Visiting the first server yields no error, but upon visiting the second
> server:
> {code:java}
> WELD-001500: Failed to deserialize proxy object with beanId
> org.apache.deltaspike.core.util.bean.ImmutableBeanWrapper:AnimalRepo[@javax.enterprise.context.ApplicationScoped()@org.apache.deltaspike.data.api.Repository(forEntity=class
>
> java.lang.Object,methodPrefix=)]{AnimalRepo.findByName[@org.apache.deltaspike.data.api.Query(hints=[Ljavax.persistence.QueryHint;@774c6737,isNative=false,lock=NONE,max=0,named=,singleResult=JPA,value=select
> a from Animal where ?1 = a.name)](java.lang.String);}
> {code}
> Interestingly, If the @Query annotation is removed from the findByName
> query, there is no issue.
> See attached project.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (DELTASPIKE-1383) Authorizer is marked initialized before being fully initialed. NullPointerException follows.
[
https://issues.apache.org/jira/browse/DELTASPIKE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874021#comment-16874021
]
ASF subversion and git services commented on DELTASPIKE-1383:
-
Commit 2ae479efbafe7e09b1d43b3ed9ff00ef51985072 in deltaspike's branch
refs/heads/master from Gerhard Petracek
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=2ae479e ]
DELTASPIKE-1383 fixed formatting
> Authorizer is marked initialized before being fully initialed.
> NullPointerException follows.
>
>
> Key: DELTASPIKE-1383
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1383
> Project: DeltaSpike
> Issue Type: Bug
> Components: Security-Module
>Affects Versions: 1.8.0, 1.8.1, 1.8.2, 1.9.0
>Reporter: Hidde Wieringa
>Assignee: Gerhard Petracek
>Priority: Major
> Fix For: 1.9.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Similar to DELTASPIKE-1378!
> Authorizer is marked initialized before being fully initialed. A
> NullPointerException follows.
> This is caused by {{boundAuthorizerBean}} being used for determining if the
> Authorizer is initialized. Futhermore {{boundAuthorizerMethodProxy}} is also
> initialized in that method, and used elsewhere. Another thread can see the
> non-null {{boundAuthorizerBean}} and assume {{boundAuthorizerMethodProxy}} is
> also non-null. This results in a nullpointer exception.
> Stack trace (with some class names removed):
> {noformat}
> 14:17:14.541 [XNIO-1 task-3] ERROR c.n.h.g.h.u.h.DelegateExceptionHandler
> - java.lang.NullPointerException
> org.jboss.resteasy.spi.UnhandledException: java.lang.NullPointerException
> at
> org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:78)
> at
> org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:222)
> at
> org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:175)
> at
> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:418)
> at
> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209)
> at
> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:227)
> at
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
> at
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)
> at
> io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129)
> at
> xxx..xx.xx.XxFilter.doFilter(XxFilter.groovy:106)
> at
> io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
> at
> io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
> at javax.servlet.FilterChain$doFilter.call(Unknown Source)
> at
> xxx..xx.xx.XxFilter.doFilter(XxFilter.groovy:31)
> at
> io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
> at
> io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
> at
> xxx..xx.xx.XxFilter.doFilter(XxFilter.groovy:50)
> at
> xxx..xx.xx.XxFilter$$OwbInterceptProxy0.doFilter(XxFilter.java)
> at
> xxx..xx.xx.XxFilter$$OwbNormalScopeProxy0.doFilter(XxFilter.java)
> at
> io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
> at
> io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
> at
> io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84)
> at
> io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
> at
> io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
> at
> io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
> at
> io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
> at
> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at
>
