Asynchronous Method Naming Conflicts
When building an asynchronous client, be aware of possible naming collisions between your service operation names and the generated asynchronous service operation methods. Asynchronous methods are generated with a suffix Start and End. For example, for the service operation getDayofWeek, HydraExpress will generate two asynchronous service operation methods getDayOfWeekStart() and getDayOfWeekEnd(). If your service operation name already ends with “Start” or “End”, a naming conflict will exist.
HydraExpress tries to prevent naming collisions by adding a “_1” to service operation methods of the same name, but you may want to avoid this renaming by not using “start” and “end” in your service operations in the same portType.