skuzzle

package test;

import java.util.Optional;

public class Test {
    
    interface GenericInterface<T> {

        Optional<String> methodReturningOptionalOfString();
    }

skuzzle

import java.io.UnsupportedEncodingException;
import java.nio.ByteBuffer;
import java.nio.CharBuffer;
import java.nio.charset.CharacterCodingException;
import java.nio.charset.CharsetDecoder;
import java.nio.charset.StandardCharsets;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.http.HttpStatus;

skuzzle

@SpringBootTest
@WithWiremock(injectHostInto = "your.application.property.serviceUrl")
public class ExampleTest {
    @Autowired
    private WiremockServcer wiremock;
    @Value("${your.application.property.serviceUrl}")
    private String serviceUrl;
    
    @Test
    void testWiremock() {

skuzzle

API designers might know the struggle: you have a package defining the public API as interfaces and then you have another package containing the implementation. How do you make the implementation accessible to the outside but also restrict unwanted instantiations?

Forbidding unwanted usage of your API actually makes it easier to use because it is harder to be used the wrong way.

Let's look at this simple example and start with a public service interface: