Re: [jakartaee-tck-dev] com/sun/ts/tests/signaturetest/javaee/JavaEESigT

[Joakim Erdfelt <joakim.erdfelt@xxxxxxxxx>]

If the Jakarta EE 8 release is supposed to be bytecode compatible with Java EE 7, then yeah, I agree the @Deprecated shouldn't be there for the Jakarta EE 8 release.

Linking to ApiDocs for Java EE 7 for ServletContext.getRealPath(String) ...

https://docs.oracle.com/javaee/7/api/javax/servlet/ServletContext.html#getRealPath-java.lang.String-

Besides, I don't think we are allowed to change the TCK behavior for Jakarta EE 8.

Is this a correct assumption?

On Tue, Aug 20, 2019 at 10:34 AM Scott Marlow <smarlow@xxxxxxxxxx> wrote:

Hi,

Servlet 2.1 deprecated ServletRequest#getRealPath(String path) however,
the current Jakarta platform TCK signature test doesn't allow
@Deprecated annotation to be added to ServletRequest#getRealPath [1], so
we are seeing Jakarta TCK signature failure [2].

Should the @Deprecated annotation be removed from [1] to resolve the tck
[2] failure?

Scott

[1]
https://github.com/eclipse-ee4j/servlet-api/blob/master/api/src/main/java/javax/servlet/ServletRequest.java#L362

[2] Added Annotations
[javatest.batch] -----------------
[javatest.batch]
[javatest.batch] javax.servlet.ServletRequest:
getRealPath(java.lang.String):anno 0 java.lang.Deprecated()
[javatest.batch]
[javatest.batch]
[javatest.batch]
[javatest.batch] 08-19-2019 22:31:36:  SVR: ********** Package
'javax.servlet' - FAILED (STATIC MODE) **********
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev