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

EJB tests dependant on JAX-RPC, have been pruned in Jakarta EE 9 CTS #114

Open
gurunrao opened this issue Jun 25, 2020 · 1 comment
Open

Comments

@gurunrao
Copy link

EJB tests dependant on JAXRPC have been prunned with Jakarta EE 9 CTS.
Source for the tests can be found at https://github.com/eclipse-ee4j/jakartaee-tck/tree/8.0.2/src/com/sun/ts/tests/ejb/ee/webservices/allowedmethodstest

Details of the tests are as follows:
1)testName: wsbmAllowedMethodsTest1
package: com.sun.ts.tests.ejb.ee.webservices.allowedmethodstest.bm
assertion_ids: EJB:SPEC:121; EJB:SPEC:121.1; EJB:SPEC:121.2;EJB:SPEC:121.3; EJB:SPEC:121.4; EJB:SPEC:121.5; EJB:SPEC:121.6;EJB:SPEC:121.7; EJB:SPEC:121.10; EJB:SPEC:121.11; EJB:SPEC:121.12;EJB:SPEC:121.13; EJB:SPEC:121.14;EJB:SPEC:121.15; EJB:SPEC:121.16;EJB:JAVADOC:172; EJB:SPEC:10; EJB:SPEC:7; EJB:SPEC:67

2)testName: wsbmAllowedMethodsTest2
package: com.sun.ts.tests.ejb.ee.webservices.allowedmethodstest.bm
assertion_ids: EJB:SPEC:121.2; EJB:SPEC:823

3)testName: wscmAllowedMethodsTest1
package: com.sun.ts.tests.ejb.ee.webservices.allowedmethodstest.cm
assertion_ids: EJB:SPEC:120; EJB:SPEC:120.1; EJB:SPEC:120.2;EJB:SPEC:120.3; EJB:SPEC:120.4; EJB:SPEC:120.5; EJB:SPEC:120.6;EJB:SPEC:120.7; EJB:SPEC:120.10; EJB:SPEC:120.11; EJB:SPEC:120.12;EJB:SPEC:120.13; EJB:SPEC:120.14; EJB:SPEC:120.15; EJB:SPEC:67;EJB:JAVADOC:172

@gurunrao gurunrao changed the title EJB test dependant on JAX-RPC is pruned with Jakarta EE 9 CTS EJB tests dependant on JAX-RPC is pruned with Jakarta EE 9 CTS Jun 25, 2020
@gurunrao gurunrao changed the title EJB tests dependant on JAX-RPC is pruned with Jakarta EE 9 CTS EJB tests dependant on JAX-RPC, have been pruned in Jakarta EE 9 CTS Jun 25, 2020
@hussainnm
Copy link
Contributor

hussainnm commented Jun 26, 2020

How can we generate these assertion_ids from the current spec document and validate if all these references have actually been removed from spec and javadoc?

I did have a look at https://github.com/eclipse-ee4j/jakartaee-tck-tools and set it up. Is there some guidance on how to use these tools.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants