Agree with Rob, here. The “normal” pattern is for Flow services to invoke Java services when a specific task can be accomplished more elegantly in Java.
While there are times when you need larger Java services, a very big portion of most integration projects can be completed almost entirely using Flow with occasional calls to a custom library of very small, fine-grained java services specific to your needs.
There are times when you need to invoke a Flow using a Java service, but this should be the exception rather than the rule and should not be viewed as a way to keep from learning/leveraging the strengths of Flow. Doing this is working against the tool not with the tool and will lead to higher maintenance costs and less ROI from your company’s WM investment.
One case in which I’ve used a java service to invoke a flow is the service I always have in my toolbox that will invoke either a Flow or java service on its own thread.
HTH,
Mark
#Integration-Server-and-ESB#Flow-and-Java-services#webMethods