Scott and others,
Moving the jax-rpc
tck to a separate repo is fine for "safe keeping", but I would
not expect any updates to this since jax-rpc has very little use and it's
being pruned from Jakarta EE. The Spec and API for JAX-RPC are in
the Stable
API Project,
so I'd either re-use the jax-rpc
repo or
create a new one.
If there are vendors
who are still looking to support JAX-RPC, then that would have to be done
at the Jakarta EE 8 level and that TCK would need to be used. We
are not defining any integration of Jakarta EE 9 features with the pruned
Jakarta EE 8 features.
I'm not really sure if there are any vendors that would be interested, as no one stepped forward yet to express interest. Mostly, I wanted to pause and take a moment to collect input, to make sure that others have a chance to speak up. Very interesting about the Stable API Project, thanks for pointing that out!
Thanks for pointing out that we are not defining any integration of Jakarta EE 9 features with pruned Jakarta EE 8 features. That makes sense and I think aligns well with the big bang approach that we are taking. I/we should stick to the guidelines that we are following, otherwise, it could take longer to achieve our goals.
If a Jakarta EE 9 implementation still supports JAXRPC, I'm not really sure of how they would test that at the Jakarta EE 8 level, unless they are able to fully test with an EE 8 implementation (which isn't really testing JAXRPC with EE 9). Just pointing out this distinction, in case it helps those vendors in the future, to follow this discussion.
Scott
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From:
Scott
Marlow <smarlow@xxxxxxxxxx>
To:
jakartaee-tck
developer discussions <jakartaee-tck-dev@xxxxxxxxxxx>
Date:
05/13/2020
09:49
Subject:
[EXTERNAL]
Re: [jakartaee-tck-dev] Please give feedback on removal of webservices
as part of pruning javax.xml.rpc classes
Sent
by: jakartaee-tck-dev-bounces@xxxxxxxxxxx
On Wed, May 13, 2020 at 8:52 AM Lance
Andersen <lance.andersen@xxxxxxxxxx>
wrote:
Hi Scott,
One more thought is to pull the webservices
test into their own TCK if there are vendors who continue to provide
JAXRPC support within their platform
That might be useful, as some of the
webservices tests will require use of other Jakarta EE 9 technologies (e.g. jakarta.ejb.SessionBean
instead of javax.ejb.SessionBean).
For the jaxrpc test folder, I think
there will also be some jakarta.servlet changes, so in both cases, your
idea would be useful, as the Jakarta EE 8 Platform would not likely work.
Does anyone else think that they would
use a standalone JAXRPC TCK that contains the current jaxrpc tests +
the webservices tests that depend on JAXRPC?
Would JAXRPC not being part of Jakarta
EE 9, mean the tests would need to be moved to a separate repo, so the
JAXRPC standalone TCK could be released and maintained independently
of the Jakarta EE Platform TCK 9.0.0?
Best
Lance
On May 12, 2020, at 3:40 PM, Lance Andersen
<lance.andersen@xxxxxxxxxx>
wrote:
On May 12, 2020,
at 2:45 PM, Scott Marlow <smarlow@xxxxxxxxxx>
wrote:
On Tue, May 12,
2020 at 12:10 PM Lance Andersen <lance.andersen@xxxxxxxxxx>
wrote:
Hi Scott,
I would consider
making the tests configurable similar to how JAXRPC is and remove when
JAXRPC is finally removed
We are supposed
to remove the JAXRPC tests now (as per EE 9 release plan [1]). Soon,
we will no longer be able to reference javax.xml.rpc classes in the Jakarta
EE 9 TCK source. I think that the general concern was about
removing any tests from the src/com/sun/ts/tests/webservices folder, in
case they are expected to cover testing non-JAXRPC technologies.
I keep forgetting
JAXRPC is finally being removed
From the keyword.properties
[2], it looks like the answer is that the webservices source tree,
only contains JAXRPC tests. Sound right?
I believe these
tests all reply on JAXRPC and based on a quick scan appears to be the case.
Scott
[1] https://eclipse-ee4j.github.io/jakartaee-platform/jakartaee9/JakartaEE9ReleasePlan
[2] https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/lib/harness/keyword.properties#L288
On May 12, 2020,
at 11:58 AM, Scott Marlow <smarlow@xxxxxxxxxx>
wrote:
Hi,
Do you have feedback
to share about removing webservices tests that reference (Jakarta
XML RPC) javax.xml.rpc classes?
Please see discussion +
concerns raised on https://github.com/eclipse-ee4j/jakartaee-tck/issues/210.
In summary we are
questioning whether to remove the webservices tests that reference
javax.xml.rpc classes, versus ignoring them in EE 9, so that they might
be refactored to do testing of something else in the future.
Your feedback is
appreciated!
Scott
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
<oracle_sig_logo.gif>
Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037
Oracle Java
Engineering
1 Network Drive
Burlington, MA 01803
Lance.Andersen@xxxxxxxxxx
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
<oracle_sig_logo.gif>
Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037
Oracle Java
Engineering
1 Network Drive
Burlington, MA 01803
Lance.Andersen@xxxxxxxxxx

Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037
Oracle Java
Engineering
1 Network Drive
Burlington, MA 01803
Lance.Andersen@xxxxxxxxxx
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev