[GitHub] [cxf] jimma merged pull request #924: Various fixes for jakarta support

2022-03-28 Thread GitBox


jimma merged pull request #924:
URL: https://github.com/apache/cxf/pull/924


   


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [cxf] reta opened a new pull request #928: Update SwaggerUI to 4.9.1

2022-03-28 Thread GitBox


reta opened a new pull request #928:
URL: https://github.com/apache/cxf/pull/928


   Update SwaggerUI to 4.9.1


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [cxf] reta commented on pull request #927: Merge Opensaml4 to Jakarta EE branch

2022-03-28 Thread GitBox


reta commented on pull request #927:
URL: https://github.com/apache/cxf/pull/927#issuecomment-1080570595


   > @reta When I download this patch and apply it to the CXF-8371 branch I see 
a lot of compilation errors, e.g. in rt-transports-jms and transports-http. Am 
I doing something incorrectly? When I run the tests in cxf-rt-ws-security I see 
errors like:
   
   Yeah, we are slowly progressing but the branch is not fully buildable just 
yet (the jms was fixed by https://github.com/apache/cxf/pull/919 but we 
reverted that), excluding problematic modules would be a way to go for now (as 
@jimma suggested here [1]). I will share the command line today in the 
description for [2] how to build with modules excluded, sorry for that.
   
   [1] https://github.com/apache/cxf/pull/927#issuecomment-1080423204
   [2] https://github.com/apache/cxf/pull/912
   


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




JDK 18 General Availability, and oracle-actions/setup-java

2022-03-28 Thread David Delabassee

Greetings!

JDK 18 has been released (General Availability) on March 22nd as 
planned, the release cadence is working like clockwork! As a small token 
of gratitude, some of you have been specifically acknowledged in the 
"The Arrival of Java 18" announcement [1]. On behalf of the entire team, 
let me extend our thanks to all of you.


With JDK 18 released, the focus should now be on making sure your 
project(s) compile and work on JDK 19. As always, if you face any issue 
with early-access builds of JDK 19 please let us know. To help you in 
this task, we have just released a GitHub action to install the OpenJDK 
Early-Access builds. For more information, please check the heads-up below.


I'll conclude with a short teaser, i.e. JavaOne is Back! [2] Stay tuned 
for more details.


[1] https://inside.java/2022/03/22/the-arrival-of-java18/
[2] https://www.oracle.com/cloudworld/javaone/


## Heads-Up: oracle-actions/setup-java

To help you test your project(s), we have released a GitHub Action [3] 
to download and install various JDK builds produced by Oracle. In 
addition to the latest OpenJDK GA builds (GPL v2 W/CPE) and the Oracle 
JDK builds (NFTC license), this action can also download and install 
OpenJDK early-access builds, and early-access builds of OpenJDK projects 
(ex. Project Loom, Project Valhalla, etc.).


When doing tests using EA builds, it is key to always use the upstream 
EA builds from jdk.java.net as issues should be logged against those 
upstream builds, and ideally against a specific build version. This 
GitHub action is actively following the OpenJDK EA builds releases. 
Please make sure to check the announcement [4] for more details, and 
short FAQ.


To help you isolate regression between different EA builds, we are 
working to add support for archived builds. If you have feedback, please 
either issue the Issue tracker [5] or just send me a mail.


[3] 
https://github.com/marketplace/actions/setup-java-development-kits-built-by-oracle

[4] https://inside.java/2022/03/11/setup-java/
[5] https://github.com/oracle-actions/setup-java/issues


## General Availability of Java 18 / JDK 18

JDK 18 is now Generally Available [6]. The OpenJDK builds which are 
provided under the GNU General Public License v2, with the Classpath 
Exception are available [7], the JDK 18 Release Notes are also available 
[8].


[6] https://mail.openjdk.java.net/pipermail/jdk-dev/2022-March/006458.html
[7] https://jdk.java.net/18/
[8] https://jdk.java.net/18/release-notes

Along with hundreds of smaller enhancements and over a thousand bug 
fixes, JDK 18 includes following JEPs:

- JEP 400: UTF-8 by Default
- JEP 408: Simple Web Server
- JEP 413: Code Snippets in Java API Documentation
- JEP 416: Reimplement Core Reflection with Method Handles
- JEP 417: Vector API (Third Incubator)
- JEP 418: Internet-Address Resolution SPI
- JEP 419: Foreign Function & Memory API (Second Incubator)
- JEP 420: Pattern Matching for switch (Second Preview)
- JEP 421: Deprecate Finalization for Removal

Thanks to everyone who contributed to JDK 18, whether by designing and 
implementing features or enhancements, by fixing bugs, or by downloading 
and testing the early-access builds.



## JDK 19 Early-Access builds

JDK 19 Early-Access builds 15 are now available [9], and are provided 
under the GNU General Public License v2, with the Classpath Exception. 
The Release Notes are also available [10].


[9] https://jdk.java.net/19/
[10] https://jdk.java.net/19/release-notes

### JEPs targeted to JDK 19, so far:
- JEP 422: Linux/RISC-V Port https://openjdk.java.net/jeps/422

### Recent changes that maybe of interest:
- JDK-8283415: Update java.lang.ref to use sealed classes
- JDK-8280494: (D)TLS signature schemes
- JDK-8282081: java.time.DateTimeFormatter: wrong definition of symbol F
- JDK-8281181: Do not use CPU Shares to compute active processor count
- JDK-7192189: Support endpoint identification algorithm in RFC 6125
- JDK-8277474: jarsigner does not check if algorithm parameters are disabled
- JDK-8280357: If the users home directory is invalid, system property 
user.home is set to $HOME

- JDK-8277204: Implement PAC-RET branch protection on Linux/AArch64
- JDK-8282411: Add useful predicates to ElementKind
- JDK-8282131: java.time.ZoneId should be a sealed abstract class
- JDK-8281375: Accelerate bitCount operation for AVX2 and AVX512 target


## Topics of Interest:

- “Java 18 is Here!” - Inside Java Podcast
https://inside.java/2022/03/22/podcast-023/

- “The Simple Web Server” - Inside Java Podcast
https://inside.java/2022/03/04/podcast-022/

- “Finalization Deprecation” - Inside Java Podcast
https://inside.java/2022/01/12/podcast-021/

- All About JDK 18 - Inside Java Newscast
https://inside.java/2022/03/10/insidejava-newscast-021/

- JDK 18 - Security Enhancements
https://seanjmullan.org/blog/2022/03/23/jdk18

- JDK 18 - Programmer's Guide to Snippets
https://docs.oracle.com/en/java/javase/18/code-snippet/index.html

- 

[GitHub] [cxf] jimma edited a comment on pull request #927: Merge Opensaml4 to Jakarta EE branch

2022-03-28 Thread GitBox


jimma edited a comment on pull request #927:
URL: https://github.com/apache/cxf/pull/927#issuecomment-1080423204


   @coheigea  These compilation failures are caused by the jakarta dependencies 
are missing. I locally excluded these modules and code/test in pom file like : 
https://github.com/jimma/cxf/commit/751f91e2c5ba53537720c1a282493010f14000ae


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [cxf] jimma commented on pull request #927: Merge Opensaml4 to Jakarta EE branch

2022-03-28 Thread GitBox


jimma commented on pull request #927:
URL: https://github.com/apache/cxf/pull/927#issuecomment-1080423204


   @coheigea  These compilation failures are caused by the jakarta dependencies 
are missing. I simply excluded these modules and code/test in pom file like : 
https://github.com/jimma/cxf/commit/751f91e2c5ba53537720c1a282493010f14000ae


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [cxf] coheigea commented on pull request #927: Merge Opensaml4 to Jakarta EE branch

2022-03-28 Thread GitBox


coheigea commented on pull request #927:
URL: https://github.com/apache/cxf/pull/927#issuecomment-1080352632


   @reta When I download this patch and apply it to the CXF-8371 branch I see a 
lot of compilation errors, e.g. in rt-transports-jms and transports-http. Am I 
doing something incorrectly? When I run the tests in cxf-rt-ws-security I see 
errors like:
   
   java.lang.NoClassDefFoundError: javax/xml/ws/WebServiceException
at 
org.apache.cxf.ws.security.wss4j.saml.StaxToDOMSamlTest.createService(StaxToDOMSamlTest.java:619)


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




Re: Systest failures with wss4j-3.0.0-SNAPSHOT

2022-03-28 Thread Jim Ma
Thanks for the merge, Andriy.
I just checked this test with this merge, I still get the same failure.


On Sat, Mar 26, 2022 at 11:46 PM Andriy Redko  wrote:

> Hey Jim, Colm,
>
> I have created this pull request [1] to merge changes from OpenSaml4 to
> Jakarta
> branch, looks like everything is in, @Colm could you please take a look?
> Thank you!
>
> [1] https://github.com/apache/cxf/pull/927/files
>
> JM> Hi Colm,
> JM> You are right. My working branch missed several commits.
> JM> This is a good idea to merge these missed things to jakarta branch.
> I'll
> JM> have a test again
> JM> after @Andriy Redko  merge these changes.
>
> JM> Thanks,
> JM> Jim
>
> JM> On Thu, Mar 24, 2022 at 4:31 PM Colm O hEigeartaigh <
> cohei...@apache.org>
> JM> wrote:
>
> >> Hi Jim,
>
> >> Your branch is behind CXF master with regards several commits. I think
> >> it would be better if we just worked off one official branch at CXF.
> >> @Andriy Redko maybe we should just incorporate
> >> https://github.com/apache/cxf/tree/opensaml4 into your Jakarta branch
> >> so that I can look at what's failing with WSS4J 3.0.0?
>
> >> Colm.
>
> >> On Wed, Mar 23, 2022 at 12:42 PM Jim Ma  wrote:
> >> >
> >> > Thanks for the quick fix, Colm.
> >> >
> >> > It seems there is another failure under
> services/sts/systests/advanced:
> >> >
> >> > [INFO] Running org.apache.cxf.systest.sts.renew.SAMLRenewTest
> >> > [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed:
> >> 10.297 s <<< FAILURE! - in
> org.apache.cxf.systest.sts.renew.SAMLRenewTest
> >> > [ERROR]
> >> org.apache.cxf.systest.sts.renew.SAMLRenewTest.testRenewExpiredTokens
> Time
> >> elapsed: 9.671 s  <<< ERROR!
> >> > jakarta.xml.ws.soap.SOAPFaultException: A security error was
> encountered
> >> when verifying the message
> >> > at
> >>
> org.apache.cxf.systest.sts.renew.SAMLRenewTest.doubleIt(SAMLRenewTest.java:145)
> >> > at
> >>
> org.apache.cxf.systest.sts.renew.SAMLRenewTest.testRenewExpiredTokens(SAMLRenewTest.java:116)
> >> > Caused by: org.apache.cxf.binding.soap.SoapFault: A security error was
> >> encountered when verifying the message
> >> > at
> >>
> org.apache.cxf.systest.sts.renew.SAMLRenewTest.doubleIt(SAMLRenewTest.java:145)
> >> > at
> >>
> org.apache.cxf.systest.sts.renew.SAMLRenewTest.testRenewExpiredTokens(SAMLRenewTest.java:116)
> >> >
> >> > I checked these spring configuration files and other places, and
> didn't
> >> find the place we need to change to the jakarta namespace.
> >> > Is there anything else we need to check ?
> >> >
> >> >
> >> >
> >> > On Wed, Mar 23, 2022 at 7:15 PM Colm O hEigeartaigh <
> cohei...@apache.org>
> >> wrote:
> >> >>
> >> >> The SAML failures were caused by a hard-coded String in SAMLUtils, I
> >> >> fixed it in CXF master here:
> >> >>
> >>
> https://github.com/apache/cxf/commit/1e90f53f720b76c2dbac910e58ef0b291f98c032
> >> >>
> >> >> Colm.
> >> >>
> >> >> On Tue, Mar 22, 2022 at 12:48 PM Jim Ma 
> wrote:
> >> >> >
> >> >> > Hi Colm,
> >> >> >
> >> >> > Please checkout my working branch :
> >> https://github.com/jimma/cxf/tree/wss4j-30-jakarta
> >> >> > Build all cxf artifacts first with: mvn clean install -Pfastinstall
> >> >> > then go to systests/ws-security, run these tests and you'll get
> these
> >> test failures.
> >> >> > Please let me know if you have other issues when trying this out.
> >> >> >
> >> >> > Thanks,
> >> >> > Jim
> >> >> >
> >> >> > On Tue, Mar 22, 2022 at 5:18 PM Colm O hEigeartaigh <
> >> cohei...@apache.org> wrote:
> >> >> >>
> >> >> >> Hi Jim,
> >> >> >>
> >> >> >> Which branch are you testing this on in CXF?
> >> >> >>
> >> >> >> Colm.
> >> >> >>
> >> >> >> On Mon, Mar 21, 2022 at 7:26 AM Jim Ma 
> wrote:
> >> >> >> >
> >> >> >> > Hi Colm,
> >> >> >> > After I upgraded wss4j version to 3.0.0-SNAPSHOT(jakarta
> version)
> >> in CXF,
> >> >> >> > I got the following ws-security systests failures.
> >> >> >> > Could you please help look at if there is still something we
> need
> >> to fix in
> >> >> >> > wss4j ? Or we need to fix it in CXF ?
> >> >> >> >
> >> >> >> > Thanks,
> >> >> >> > Jim
> >> >> >> >
> >> >> >> > 
> >> >> >> > [ERROR]
> >> >> >> > org.apache.cxf.systest.ws
> >> .saml.SamlTokenTest.testAudienceRestrictionServiceName[14036:dom]
> >> >> >> >  Time elapsed: 0.076 s  <<< ERROR!
> >> >> >> > jakarta.xml.ws.soap.SOAPFaultException: A security error was
> >> encountered
> >> >> >> > when verifying the message
> >> >> >> > at
> >> >> >> > org.apache.cxf.systest.ws
> >>
> .saml.SamlTokenTest.testAudienceRestrictionServiceName(SamlTokenTest.java:1194)
> >> >> >> > Caused by: org.apache.cxf.binding.soap.SoapFault: A security
> error
> >> was
> >> >> >> > encountered when verifying the message
> >> >> >> > at
> >> >> >> > org.apache.cxf.systest.ws
> >>
> .saml.SamlTokenTest.testAudienceRestrictionServiceName(SamlTokenTest.java:1194)
> >> >> >> >
> >> >> >> > [ERROR]
> >> >> >> > org.apache.cxf.systest.ws
> >>