[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| 
Re: [jakarta.ee-spec] Question about removing of TCK tests like security manager tests...
 | 
  
  
    Hi Emily,
    On 10/5/21 3:10 PM, Emily Jiang via
      jakarta.ee-spec wrote:
    
    
      
      
        Hi Scott,
        Thanks for reaching out to me! My concern is that we need
          to understand the SecurityManager tests. I might be wrong but
          I assume these tests use SecurityManager apis to test other
          functionalities. If we delete them, would the functionalities
          live without accompanied tests?
       
    
    First, I apologize for raising this on this mailing list, I
      corrected my address book entry for you (I intended to just follow
      up with you privately to better understand your point).
    
    If for example, we removed the
https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/tests/servlet/ee/spec/security/permissiondd/TestServlet.java
      + likely
https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/tests/servlet/ee/spec/security/permissiondd/Client.java,
      that would remove dedicated testing of the combination of
      SecurityManager with Servlet.  But the answer to your question
      really varies depending on how the test is written.  
    
    Some other tests combine testing of multiple Java SE technologies
      within the same test source that also tests multiple Jakarta EE
      technologies (typically targeting a base Jakarta EE technology but
      also involving other Jakarta EE technologies).  
    
    
      
        Would Java 17 make SecurityManger completely obsolete? 
       
    
    No, Java SE 17 does not make the SecurityManager obsolete, it
      only marks it as deprecated (for removal in a future Java SE
      release).
    
    
    
    
      
        Basically removing the security manager apis does not make
          any differences.
       
    
    The SecurityManager apis are not removed in Java SE 17.
    
    Thanks,
      Scott
    
    
      
      
      
        
        
          
            Or is it more that you just don't want to lose any
              security related tests?  
            
            Scott
            
            On 10/5/21 12:22 PM, Scott Marlow wrote:
            
            
              Hi Emily,
              I would like to better understand why you said that we
                cannot remove Java Security Manager tests from the TCK
                without adding replacement tests?  
              
              I am thinking that if we remove Java Security Manager
                TCK tests for Jakarta EE 10 and there is a new way in
                later Java SE versions that standardizes how equivalent
                security testing could be done in a TCK, that someone
                could contribute changes to then add new security TCK
                tests but that is not likely to happen for the EE 10
                release.  
              
              Scott
              
            
           
          _______________________________________________
          jakarta.ee-spec mailing list
          jakarta.ee-spec@xxxxxxxxxxx
          To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec
        
       
      
      
      -- 
      
      
      
      _______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec