If a service interface uses raw generic types (generic classes without type parameters, such as List, Map, or custom generics), Enterprise Distributed Application Service (EDAS) cannot parse the interface. The service does not appear in the service list.
Identify the problem
Check your service interface definitions for raw generic types:
// Raw generic types - EDAS cannot parse these
public interface OrderService {
List getOrders(String userId); // Missing type parameter
Map getOrderDetails(String orderId); // Missing type parameters
CompletableFuture processOrder(Order order); // Missing type parameter
ResponseWrapper getStatus(String orderId); // Missing type parameter on custom generic
}Fix the code
Add the type parameter to every generic type in your service interface:
// Parameterized generic types - EDAS parses these correctly
public interface OrderService {
List<Order> getOrders(String userId);
Map<String, Object> getOrderDetails(String orderId);
CompletableFuture<String> processOrder(Order order);
ResponseWrapper<OrderStatus> getStatus(String orderId);
}After you update the interface definitions, rebuild and redeploy the application to EDAS.
Verify the fix
Open the EDAS console and go to the service list for your application.
Confirm that the previously missing service now appears.
Test the service by initiating an invocation from the console or a consumer application.