jakartaee / jws-api Goto Github PK

JWS API (Eclipse Project for JAX-WS)

License: BSD 3-Clause "New" or "Revised" License

Java 59.31% Groovy 15.00% Shell 25.69%

jws-api's Introduction

Jakarta Web Services Metadata project

Jakarta Web Services Metadata defines a programming model for Web Services in Java, use of metadata, a non-normative processing model for metadata annotated web service source files, runtime requirements for a container, and annotations used for WSDL, binding, and configuration.

This project is part of Jakarta XML Web Services project.

License

Most of the Jakarta Web Services Metadata project source code is licensed under the Eclipse Distribution License (EDL) v1.0.; see the license information at the top of each source file.
The source code for the Jakarta Web Services Metadata Specification project is licensed under the Eclipse Public License (EPL) v2.0 and GNU General Public License (GPL) v2 with Classpath Exception; again, the license is in each source file.
The binary jar files published to the Maven repository are licensed under the same licenses as the corresponding source code; see the file META-INF/LICENSE.txt in each jar file.

You’ll find the text of the licenses in the workspace in various LICENSE.txt or LICENSE.md files. Don’t let the presence of these license files in the workspace confuse you into thinking that they apply to all files in the workspace.

You should always read the license file included with every download, and read the license text included in every source file.

Contributing

We use contribution policy, which means we can only accept contributions under the terms of Eclipse Contributor Agreement.

jws-api's People

Contributors

Stargazers

Watchers

Forkers

cousjava lukasj jakarta-ee tomas-kraus jbescos lilian-benoit senivam janwesterkamp-ijug seanpm2001

jws-api's Issues

Compatibility certification request for EI of JXWS 3.0.0-M5

javax -> jakarta package rename

Compatibility certification request for Eclipse Metro 3.0.0-M3

Release to OSSRH staging repository

Uptake new Eclipse versions of dependencies (if any). Use GlassFish 5.1 Release Tracker wiki to find components versions to use.
Release to OSSRH staging repository
Update GlassFish 5.1 Release Tracker with released version number.

Update Eclipse GlassFish

Update Eclipse GlassFish to use the new version of your API (and implementation, if applicable) by submitting a PR to GlassFish.

Although a new version of GlassFish will not be released for Jakarta EE 8, we hope to release an update sometime later.

Compatibility certification request for Eclipse Metro 2.4.4

Release CI/CD pipeline

We need to create a release CI/CD pipeline for this project.

Use these documents as a reference:

Jakarta EE 8 TCK job

To test Jakarta EE 8 compatibility we need to create a Jenkins job on project's Cloud Jenkins instance formally testing the API against the relevant TCK and as needed, relevant CTS subset tests.

For projects that do not already have automated testing, there is provided parameterized Jenkins job that can be invoked to perform these tests. User provides a link to an Eclipse GlassFish test build and sets the test sub-set parameters:

For CTS -- https://ci.eclipse.org/jakartaee-tck/job/jakartaeetck-certification/
For Stand-alone TCKs -- https://ci.eclipse.org/jakartaee-tck/job/standalonetck-certification/

Additional instructions and guidance for using and directly running TCKs is available on this wiki. Also in the jakartaee-tck project repository.

Update EFSL for Specifications and Javadoc

Per the discussions on the Spec Committee and Platform Dev mailing lists, it's been discovered that many of the Javadoc and Spec references to the EFSL need updating. Please reference the following required updates and keep them in mind as your Spec Project is updating the files for Jakarta EE 9.

Note: Some Spec Projects have already started or even completed these updates. If so, just kindly return/close this Issue. Thanks!

Required EFSL updates for Javadoc

For javadoc, the EFSL.html located in src/main/javadoc/doc-files should be modified as follows:

the <<url to this license>> needs to be replaced with efsl.php link[1]
the [title and URI of the Eclipse Foundation specification document] needs to be replaced with the Specification Name and URL (Reference [2] for an example.)
The javadoc footer copyright year needs to be updated to 2018, 2020 as defined in the pom.xml

Required EFSL updates for Specifications

For specification, the license-efsl.adoc located in src/main/asciidoc should be modified as follows:

Update copyright year to 2018, 2020 from 2019. Add link to EFSL.
the <<url to this license>> needs to be replaced with efsl.php link[1]
the [title and URI of the Eclipse Foundation specification document] needs to be replaced with the Specification Name and URL (Reference [2] for an example.)

[1] https://www.eclipse.org/legal/efsl.php
[2] https://jakarta.ee/specifications/enterprise-beans/4.0/

Deliver jws-api (Web Services Metadata) Specification Version update for Jakarta EE 9

Is your feature request related to a problem? Please describe.
Jakarta EE 9 is the next major release, with the main focus of moving from the javax namespace to the jakarta namespace.

Describe the solution you'd like
This issue will be used to track the progress of this work effort via the Jakarta EE 9 Project board.

Additional context
Jakarta EE Specification Process
Eclipse Project Handbook
Eclipse Release Record for Jakarta EE 9

ToDo

Please verify that spec api artifacts for 2.1.0 are available on maven central...

Is the Jenkins job that handled the 2.1.0 spec api release pushing to Maven central?

Maven repo only seems to have 1.1.1

CC @lukasj + @Tomas-Kraus

Compatibility certification request for Eclipse Metro 3.0.0

Tags? Is this jsr181/jsr181-api or javax.jws

I need this as a dependency of spring-web I cannot tell if this is jsr181/jsr181-api or javax.jws.

I see a 1.1 snapshot, so that would match versioning of jsr181. I do not see the javax.jws-api artifact id per the pom.xml in maven central repo.

I can grab a snapshot tag for my needs, but just curious in general if this is the proper home. If tags can be added, etc. thanks!

bundle symbolic name should match artifactId

Update CONTRIBUTING.md for Specification Project's repositories

Create/Update CONTRIBUTING files

Per input from the Eclipse EMO, each Specification Project needs to ensure that a CONTRIBUTING.md or CONTRIBUTING.adoc file exists in each specification-related repository maintained by Specification Projects.
In addition, the CONTRIBUTING.md or CONTRIBUTING.adoc file needs to include the following text:

## Eclipse Development Process

This Eclipse Foundation open project is governed by the Eclipse Foundation
Development Process and operates under the terms of the Eclipse IP Policy.

The Jakarta EE Specification Committee has adopted the Jakarta EE Specification
Process (JESP) in accordance with the Eclipse Foundation Specification Process
v1.2 (EFSP) to ensure that the specification process is complied with by all
Jakarta EE specification projects.

* https://eclipse.org/projects/dev_process
* https://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf
* https://jakarta.ee/about/jesp/
* https://www.eclipse.org/legal/efsp_non_assert.php

Please do this at your earliest convenience.
Thank you!

-- EE4J PMC ([email protected])

Public Release

Last CTS runs indicate no failures in this component. It's time to make a public release. Before the release make sure that Eclipse Release Review is passed and all dependencies have been released.

Build CI/CD pipeline

This task is for creating a basic build CI/CD pipeline for this project on Eclipse infrastructure. More information is here: https://ci.eclipse.org/.

Prepare Jakarta Web Services Metadata for the Jakarta EE 8 Release

Instructions

Update text files
Generate "boilerplate" specification project
Make a staging release
Generate Stand-alone TCK test results
Submit tests for ballot
Release to Maven Central

See here for detailed instructions.

Compatibility certification request for EI of JXWS 3.0.0

Completion Steps for Jakarta Web Services Metadata 3.0

Specification Committee Mentor

creates an issue in the specification project that includes the following checklist for the specification project team
Specification Project Team
promotes api staging release promotes the specification api jars to maven central. An example release job script can be found here https://wiki.eclipse.org/MavenReleaseScript.
go through the merged jakarta.ee specification website page to verify all the links are valid.
approve the compatibility request.
The compatible implementation project/vendor MUST send an email to [email protected] for approval of the compatible implementation for trademark usage.
merge any final release branch as appropriate for the branch management for the project.

jakartaee_web_services_metadata_handler_3_0.xsd includes jakartaee_9.xsds which does not exist

jws-api/api/src/main/resources/jakarta/jws/jakartaee_web_services_metadata_handler_3_0.xsd

Line 52 in 16f648d

<xsd:include schemaLocation="jakartaee_9.xsds"/>

Compare with

jws-api/api/src/main/resources/jakarta/jws/javaee_web_services_metadata_handler_2_0.xsd

Line 28 in 16f648d

<xsd:include schemaLocation="javaee_5.xsd"/>

Originally posted in jakartaee/jakarta.ee#1519

Change Maven coordinates

All current API libraries shipped must be distributed to Maven Central under a sub-package of the jakarta groupId. Before the first release Maven coordinates of this project must be changed as it's described here.

Change name of xsd file

On the Platform call today, it was pointed out that the XSD for JWS-API still had the "javaee" name. This needs to change to use the "jakartaee" name... Just creating this Issue so that we don't forget...

https://github.com/eclipse-ee4j/jws-api/blob/master/api/src/main/resources/jakarta/jws/javaee_web_services_metadata_handler_2_0.xsd

-->

https://github.com/eclipse-ee4j/jws-api/blob/master/api/src/main/resources/jakarta/jws/jakartaee_web_services_metadata_handler_2_0.xsd