Enterprise Distributed Application Service:Error code: HSF-0014

Error message

java.lang.IllegalArgumentException: The interface class [com.taobao.hsf.jar.test.HelloWorldService1] specified in ProviderBean does not exist.

Cause

The serviceInterface attribute in ProviderBean references an interface class that does not exist on the classpath. This is a configuration error. Retrying or restarting the application does not resolve it.

Common reasons:

• Typo in the class name. The fully qualified class name in serviceInterface is misspelled or uses incorrect capitalization.

• Missing dependency. The JAR or module that contains the interface class is not included in the project dependencies.

• Incorrect package path. The package structure in serviceInterface does not match the actual location of the interface class.

Solution

1. Open the ProviderBean configuration and locate the serviceInterface attribute.

   XML example:

   <bean id="myServiceProvider" class="...">
       <!-- Verify this value matches an existing interface class -->
       <property name="serviceInterface" value="com.taobao.hsf.jar.test.HelloWorldService1" />
   </bean>

2. Verify that the interface class exists in your project.

   From the project root, run:

   find . -name "HelloWorldService1.java" -o -name "HelloWorldService1.class"

   If no results are returned, the class is missing. You can also search for the class name in your IDE to confirm it exists in the source tree or dependencies.

3. Fix the configuration based on the results:

   Issue	Fix
   Class name is misspelled	Correct the serviceInterface value to match the exact fully qualified class name.
   JAR dependency is missing	Add the dependency that contains the interface to your pom.xml or build.gradle.
   Package path is wrong	Update the package path in serviceInterface to match the actual class location.

4. Rebuild and redeploy the application.

Verify the fix

After redeployment, confirm that:

• The application starts without the HSF-0014 error in the logs.

• The HSF service is published and registered in the EDAS console.