Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JAX-WS: IllegalArgumentException fix when special characters are used for namespace with combination of monitor-1.0 feature #30837

Merged
merged 5 commits into from
Feb 26, 2025

Conversation

BerksanAtes
Copy link
Member

@BerksanAtes BerksanAtes added in:Web Services team:Bobcats JAX-WS Web Services Team labels Feb 20, 2025
@BerksanAtes BerksanAtes self-assigned this Feb 20, 2025
@BerksanAtes
Copy link
Member Author

BerksanAtes commented Feb 20, 2025

#build (view Open Liberty Personal Build - ❌ completed with errors/failures.)

Note: Target locations of links might be accessible only to IBM employees.

@LibbyBot
Copy link

Code analysis and actions

DO NOT DELETE THIS COMMENT.
  • 1 infrastructure code files were changed.

  • 2 product code files were changed.

  • Please describe in a separate comment how you tested your changes.

@LibbyBot
Copy link

Your personal build request is at https://wasrtc.hursley.ibm.com:9443/jazz/resource/itemOid/com.ibm.team.build.BuildResult/_UamNAPBUEe-iabY-3Iflhw

Target locations of links might be accessible only to IBM employees.

@BerksanAtes
Copy link
Member Author

BerksanAtes commented Feb 21, 2025

#build (view Open Liberty Personal Build - ❌ completed with errors/failures.)

Note: Target locations of links might be accessible only to IBM employees.

@LibbyBot
Copy link

Code analysis and actions

DO NOT DELETE THIS COMMENT.
  • 1 infrastructure code files were changed.

  • 2 product code files were changed.

  • Please describe in a separate comment how you tested your changes.

@LibbyBot
Copy link

Your personal build request is at https://wasrtc.hursley.ibm.com:9443/jazz/resource/itemOid/com.ibm.team.build.BuildResult/_uXjAgPD_Ee-iabY-3Iflhw

Target locations of links might be accessible only to IBM employees.

@BerksanAtes
Copy link
Member Author

BerksanAtes commented Feb 24, 2025

#build (view Open Liberty Personal Build - ❌ completed with errors/failures.)

Note: Target locations of links might be accessible only to IBM employees.

@LibbyBot
Copy link

Code analysis and actions

DO NOT DELETE THIS COMMENT.
  • 16 FAT files were changed, added, or removed.

  • Check that the build did not break the affected FAT suite(s).

  • 1 infrastructure code files were changed.

  • 2 product code files were changed.

  • Please describe in a separate comment how you tested your changes.

@LibbyBot
Copy link

Your personal build request is at https://wasrtc.hursley.ibm.com:9443/jazz/resource/itemOid/com.ibm.team.build.BuildResult/_NRE14PMjEe-5mo24eL2W6g

Target locations of links might be accessible only to IBM employees.

@BerksanAtes
Copy link
Member Author

BerksanAtes commented Feb 25, 2025

#build (view Open Liberty Personal Build - ❌ completed with errors/failures.)

Note: Target locations of links might be accessible only to IBM employees.

@LibbyBot
Copy link

Code analysis and actions

DO NOT DELETE THIS COMMENT.
  • 16 FAT files were changed, added, or removed.

  • Check that the build did not break the affected FAT suite(s).

  • 1 infrastructure code files were changed.

  • 2 product code files were changed.

  • Please describe in a separate comment how you tested your changes.

@LibbyBot
Copy link

Your personal build request is at https://wasrtc.hursley.ibm.com:9443/jazz/resource/itemOid/com.ibm.team.build.BuildResult/_z3t3sPQkEe-5mo24eL2W6g

Target locations of links might be accessible only to IBM employees.

Copy link
Member

@neuwerk neuwerk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@BerksanAtes BerksanAtes merged commit e0e747b into OpenLiberty:integration Feb 26, 2025
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants