[jira] [Commented] (CXF-7996) Jakarta EE TCKs and compatibility
[
https://issues.apache.org/jira/browse/CXF-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008461#comment-17008461
]
Andy McCright commented on CXF-7996:
I recognize some of those failures. I'll plan to open up separate pull
requests for them unless you'd prefer a single PR with multiple commits for the
different classes of failures.
I have one ready to go that should fix ~4 FormParam-related failures. I also
have one that should fix at least one SSE-related failure (possibly more), but
that ends up causing some of the unit tests to fail - I'll need to investigate
those more before submitting them.
> Jakarta EE TCKs and compatibility
> -
>
> Key: CXF-7996
> URL: https://issues.apache.org/jira/browse/CXF-7996
> Project: CXF
> Issue Type: Task
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Attachments: JTreport-26-December-2019.zip, JTwork-
> 26-December-2019.zip
>
>
> Mail thread:
> [https://mail-archives.apache.org/mod_mbox/cxf-dev/201901.mbox/%3C6edd1da6-d651-]
> e2a3-8092-59bdc7a54...@apache.org%3E
> Jakarta EE TCK:
> [https://projects.eclipse.org/proposals/eclipse-jakarta-ee-tck]
> Github Repo: [https://github.com/eclipse-ee4j/jakartaee-tck]
> Latest updates from [jakarta.ee-spec] TCK information, June 2019, the
> excerpts:
> * {color:#00}We have summed up some information about how the TCK can be
> built (or {color}
> {color:#00}grabbed pre-built), configured, and run [1].{color}
> * {color:#00}This is assumed to be run against a Glassfish with the
> latest API {color}
> {color:#00}integrated (replacing the original API in the
> Glassfish).{color}
> * {color:#00}We have created a recording of a presentation of the
> Jenkins jobs that {color}
> {color:#00}manage all that [2].{color}
> * {color:#00}We have created 3 Jenkins files for pipeline job (as an
> example for {color}
> {color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
> b) to grab {color}
> {color:#00}the API artifact built by a Jenkins build job and integrate
> it to a {color}
> {color:#00}Glassfish and c) to grab the pre-built TCK bundle from
> Eclipse Download, {color}
> {color:#00}grab the configured ts.jte file, grab the Glassfish with new
> API {color}
> {color:#00}integrated, and run the TCK [3].{color}
> {color:#00}For the complete information, please allow me to mention the
> list of the {color}
> {color:#00}TCK tasks needed to be done before the Jakarta EE release can
> be {color}
> {color:#00}finished [4].{color}
> {color:#00}The [5] is the example how to run Jakarta EE TCKs with
> Tomcat.{color}
> {color:#00}{color:#00}The{color} [6] is the official list of the
> instructions.{color}
>
> {color:#00}[1]
> {color}+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
> {color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
> {color:#00}[3] {color}
>
> +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
> {color:#00}[4] {color}+[https://github.com/orgs/eclipse-ee4j/projects/14]+
> [5] [https://cwiki.apache.org/confluence/display/TOMCAT/Jakarta+EE+TCKs]
> [6]
> +[https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Instructions-for-building-and-running-JakartaEE-TCK-bundle]+
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (CXF-7996) Jakarta EE TCKs and compatibility
[
https://issues.apache.org/jira/browse/CXF-7996?focusedWorklogId=366445&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-366445
]
ASF GitHub Bot logged work on CXF-7996:
---
Author: ASF GitHub Bot
Created on: 06/Jan/20 00:10
Start Date: 06/Jan/20 00:10
Worklog Time Spent: 10m
Work Description: andymc12 commented on pull request #620: CXF-7996: TCK:
Resolves FormParam-related failures
URL: https://github.com/apache/cxf/pull/620
Should fix:
allParamsInParamTest_from_standalone
allParamsOnFieldTest_from_standalone
formParamInParamTest_from_standalone
formParamOnFieldTest_from_standalone
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 366445)
Remaining Estimate: 0h
Time Spent: 10m
> Jakarta EE TCKs and compatibility
> -
>
> Key: CXF-7996
> URL: https://issues.apache.org/jira/browse/CXF-7996
> Project: CXF
> Issue Type: Task
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Attachments: JTreport-26-December-2019.zip, JTwork-
> 26-December-2019.zip
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Mail thread:
> [https://mail-archives.apache.org/mod_mbox/cxf-dev/201901.mbox/%3C6edd1da6-d651-]
> e2a3-8092-59bdc7a54...@apache.org%3E
> Jakarta EE TCK:
> [https://projects.eclipse.org/proposals/eclipse-jakarta-ee-tck]
> Github Repo: [https://github.com/eclipse-ee4j/jakartaee-tck]
> Latest updates from [jakarta.ee-spec] TCK information, June 2019, the
> excerpts:
> * {color:#00}We have summed up some information about how the TCK can be
> built (or {color}
> {color:#00}grabbed pre-built), configured, and run [1].{color}
> * {color:#00}This is assumed to be run against a Glassfish with the
> latest API {color}
> {color:#00}integrated (replacing the original API in the
> Glassfish).{color}
> * {color:#00}We have created a recording of a presentation of the
> Jenkins jobs that {color}
> {color:#00}manage all that [2].{color}
> * {color:#00}We have created 3 Jenkins files for pipeline job (as an
> example for {color}
> {color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
> b) to grab {color}
> {color:#00}the API artifact built by a Jenkins build job and integrate
> it to a {color}
> {color:#00}Glassfish and c) to grab the pre-built TCK bundle from
> Eclipse Download, {color}
> {color:#00}grab the configured ts.jte file, grab the Glassfish with new
> API {color}
> {color:#00}integrated, and run the TCK [3].{color}
> {color:#00}For the complete information, please allow me to mention the
> list of the {color}
> {color:#00}TCK tasks needed to be done before the Jakarta EE release can
> be {color}
> {color:#00}finished [4].{color}
> {color:#00}The [5] is the example how to run Jakarta EE TCKs with
> Tomcat.{color}
> {color:#00}{color:#00}The{color} [6] is the official list of the
> instructions.{color}
>
> {color:#00}[1]
> {color}+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
> {color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
> {color:#00}[3] {color}
>
> +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
> {color:#00}[4] {color}+[https://github.com/orgs/eclipse-ee4j/projects/14]+
> [5] [https://cwiki.apache.org/confluence/display/TOMCAT/Jakarta+EE+TCKs]
> [6]
> +[https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Instructions-for-building-and-running-JakartaEE-TCK-bundle]+
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (CXF-7996) Jakarta EE TCKs and compatibility
[
https://issues.apache.org/jira/browse/CXF-7996?focusedWorklogId=366451&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-366451
]
ASF GitHub Bot logged work on CXF-7996:
---
Author: ASF GitHub Bot
Created on: 06/Jan/20 01:08
Start Date: 06/Jan/20 01:08
Worklog Time Spent: 10m
Work Description: andymc12 commented on pull request #621: CXF-7996: TCK
Fixes for SSE reconnect state tests
URL: https://github.com/apache/cxf/pull/621
This should resolve at least one of the failing SSE tests (specifically,
defaultWaiting1s_from_standalone). The TCK is very picky about the `isOpen`
method - and the behavior of the `SseEventSource` is not terribly intuitive.
While the "state" of the SseEventSource might be CLOSED or CONNECTING, the TCK
still expects that the `isOpen` method will return true until it has been
explicitly closed (via the `close` method). I adjusted the unit tests to
expect this distinction - but also to continue testing for the proper state of
the SseEventSource.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 366451)
Time Spent: 20m (was: 10m)
> Jakarta EE TCKs and compatibility
> -
>
> Key: CXF-7996
> URL: https://issues.apache.org/jira/browse/CXF-7996
> Project: CXF
> Issue Type: Task
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Attachments: JTreport-26-December-2019.zip, JTwork-
> 26-December-2019.zip
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Mail thread:
> [https://mail-archives.apache.org/mod_mbox/cxf-dev/201901.mbox/%3C6edd1da6-d651-]
> e2a3-8092-59bdc7a54...@apache.org%3E
> Jakarta EE TCK:
> [https://projects.eclipse.org/proposals/eclipse-jakarta-ee-tck]
> Github Repo: [https://github.com/eclipse-ee4j/jakartaee-tck]
> Latest updates from [jakarta.ee-spec] TCK information, June 2019, the
> excerpts:
> * {color:#00}We have summed up some information about how the TCK can be
> built (or {color}
> {color:#00}grabbed pre-built), configured, and run [1].{color}
> * {color:#00}This is assumed to be run against a Glassfish with the
> latest API {color}
> {color:#00}integrated (replacing the original API in the
> Glassfish).{color}
> * {color:#00}We have created a recording of a presentation of the
> Jenkins jobs that {color}
> {color:#00}manage all that [2].{color}
> * {color:#00}We have created 3 Jenkins files for pipeline job (as an
> example for {color}
> {color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
> b) to grab {color}
> {color:#00}the API artifact built by a Jenkins build job and integrate
> it to a {color}
> {color:#00}Glassfish and c) to grab the pre-built TCK bundle from
> Eclipse Download, {color}
> {color:#00}grab the configured ts.jte file, grab the Glassfish with new
> API {color}
> {color:#00}integrated, and run the TCK [3].{color}
> {color:#00}For the complete information, please allow me to mention the
> list of the {color}
> {color:#00}TCK tasks needed to be done before the Jakarta EE release can
> be {color}
> {color:#00}finished [4].{color}
> {color:#00}The [5] is the example how to run Jakarta EE TCKs with
> Tomcat.{color}
> {color:#00}{color:#00}The{color} [6] is the official list of the
> instructions.{color}
>
> {color:#00}[1]
> {color}+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
> {color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
> {color:#00}[3] {color}
>
> +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
> {color:#00}[4] {color}+[https://github.com/orgs/eclipse-ee4j/projects/14]+
> [5] [https://cwiki.apache.org/confluence/display/TOMCAT/Jakarta+EE+TCKs]
> [6]
> +[https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Instructions-for-building-and-running-JakartaEE-TCK-bundle]+
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CXF-8088) ensure jaxrs endpoint can work correctly when using a shared bus exposed from another bundle
[
https://issues.apache.org/jira/browse/CXF-8088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008594#comment-17008594
]
Xilai Dai commented on CXF-8088:
Hi [~ffang],
The changes seems introduce a regression in case of operate the
JAXRSServerFactoryBean dynamically using blueprint configuration.
In blueprint.xml:
{code}
{code}
Adding some providers to the jaxrs:server dynamically in Java class:
{code}
public class ServiceSecurityProvider {
private JAXRSServerFactoryBean serviceEndpoint;
public void setServiceEndpoint(JAXRSServerFactoryBean serviceEndpoint) {
this.serviceEndpoint = serviceEndpoint;
}
public void init() {
Server oldServer = serviceEndpoint.getServer();
if (oldServer.isStarted()) {
oldServer.stop();
oldServer.destroy();
}
List providers = (List) serviceEndpoint.getProviders();
//add some security providers dynamically depends on the configuration
changes
providers.add(xxx);
Server newServer = serviceEndpoint.create();
newServer.start();
}
}
{code}
Then the new Server couldn't be created properly with the expected providers in
CXF 3.3.4.
But it worked well in CXF 3.3.1.
> ensure jaxrs endpoint can work correctly when using a shared bus exposed from
> another bundle
>
>
> Key: CXF-8088
> URL: https://issues.apache.org/jira/browse/CXF-8088
> Project: CXF
> Issue Type: Bug
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Major
> Fix For: 3.2.10, 3.3.3
>
>
> major 2 issues
> 1. not unregister the jaxrs endpoint correctly when stop the jaxrs endpoint
> bundle.
> 2. jaxrs binding should be added as bus extension so that the bus used by
> jaxrs binding factory is always valid
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
