Cucumber-picocontainer fails to provide default constructors for String.

When picocontainer tries to resolve the constructor for the class String it detects that there are multiple satisfiable constructors.

I am using picocontainer to resolve dependencies for Steps and Hooks. One of my Steps has constructor which takes a String as parameter.

This problem also happens with other classes like Integer, Double, Float, Boolean, etc.

Version: 1.2.5-SNAPSHOT Module: cucumber-picocontainer Command: Running tests Output: 3 satisfiable constructors is too many for ‘class java.lang.String’. Constructor List:[<init>(<init>Buffer), <init>(<init>Builder), <init>()] Pull Request: #1045 Steps to reproduce: Add the following test in PicoFactoryTest and run it.

@Test
    public void shouldGetStringInstance() {
        // Given
        ObjectFactory factory = new PicoFactory();
        factory.addClass(String.class);

        // When
        factory.start();
        String str = factory.getInstance(String.class);

        // Then
        assertNotNull(str);
    }
'''

[mlvandijk]

From the discussion on gitter (edited for brevity; you can find the full discussion on gitter: https://gitter.im/cucumber/cucumber-jvm) -

Aslak Hellesøy @aslakhellesoy Aug 13 2016 00:00 that’s PicoContainer saying "I don’t know what string to pass in here - let me see if I can construct one myself from the other components I know about. And then it blows up because it has too many choices. Did you consider where that string constructor argument would come from? [edited] Aslak Hellesøy @aslakhellesoy Aug 13 2016 09:10 I don’t think pico should make up primitive values to satisfy your constructors. Provide empty constructors instead, delegating to your string constructor. [edited] Alonso A. Ortega @alayor Aug 14 2016 02:10 [edited] I understand the this is not a common problem for many people, so for the time being I’ll use a default constructor.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.