Interface Configuration


  • public interface Configuration
    The configuration of the TCK. The TCK may be configured using system properties or placed in a properties file called META-INF/cdi-tck.properties. Porting package property names are the FQCN of the SPI class. Other property names (one for each non-porting package SPI configuration option) are specified here. The TCK may also be configured programatically through this interface.
    Author:
    Pete Muir, Martin Kouba
    • Method Detail

      • setCdiLiteMode

        void setCdiLiteMode​(Boolean cdiLiteMode)
      • getBeans

        Beans getBeans()
        The implementation of Beans in use.
      • getContexts

        <T extends jakarta.enterprise.context.spi.Context> Contexts<T> getContexts()
        The implementation of Contexts in use.
      • getEl

        EL getEl()
        The implementation of EL in use.
      • setBeans

        void setBeans​(Beans beans)
      • setContexts

        <T extends jakarta.enterprise.context.spi.Context> void setContexts​(Contexts<T> contexts)
      • setContextuals

        void setContextuals​(Contextuals contextuals)
      • setCreationalContexts

        void setCreationalContexts​(CreationalContexts creationalContexts)
      • setEl

        void setEl​(EL el)
      • getLibraryDirectory

        String getLibraryDirectory()
        The TCK allows additional libraries to be put in the deployed test artifacts (for example the porting package for the implementation). Any jars in this directory will be added to the deployed artifact. By default no directory is used.
        Returns:
        path to additional libraries
      • setLibraryDirectory

        void setLibraryDirectory​(String libraryDir)
      • getTestDataSource

        String getTestDataSource()
        Few TCK tests need to work with Java EE services related to persistence (JPA, JTA) - test datasource must be provided. These tests belong to testng group persistence.
        Returns:
        the JNDI name of the test datasource
      • setTestDataSource

        void setTestDataSource​(String testDatasource)
        Parameters:
        testDatasource -
      • getTestJmsConnectionFactory

        String getTestJmsConnectionFactory()
        Returns:
        the JNDI name of the test JMS connection factory
      • setTestJmsConnectionFactory

        void setTestJmsConnectionFactory​(String testJmsConnectionFactory)
        Parameters:
        testJmsConnectionFactory -
      • getTestJmsQueue

        String getTestJmsQueue()
        Returns:
        the JNDI name of the test JMS queue
      • setTestJmsQueue

        void setTestJmsQueue​(String testJmsQueue)
        Parameters:
        testJmsQueue -
      • getTestJmsTopic

        String getTestJmsTopic()
        Returns:
        the JNDI name of the test JMS topic
      • setTestJmsTopic

        void setTestJmsTopic​(String testJmsTopic)
        Parameters:
        testJmsTopic -
      • getTestTimeoutFactor

        int getTestTimeoutFactor()
        All tests using some timeout technique (e.g. wait for async processing) should use this value to adjust the final timeout so that it's possible to configure timeouts according to the testing runtime performance and throughput.
        Returns:
        the test timeout factor (in percent)
      • setTestTimeoutFactor

        void setTestTimeoutFactor​(int timeoutFactor)
        Parameters:
        timeoutFactor -