I think maybe you got some bad advice. If your application was running correctly in development and the only issue is that it will not run correctly in QA then why re-implement the presentation layer to solve the issue? I assume, that in WF, you called a flow service from the html page using the I.S component in WF. This is the correct way to implement your WF task. Sure you can write a DSP that runs the same service, but the UI is not where the problem is. To help better understand and debug why your application does not work in QA it might be helpful to turn on full debugging on the WF Servlet. This is easily accomplished by adding the following two JVM parameters to your runtime. If you are hosting the servlet inside Integration Server or in another environment the procedure is slightly different. However in general, wherever you turn on JVM parameters add the following properties;
The Workflow Servlet will write its diagnostic messages to the standard output. For tomcat this will usually be the catalina.out file or the terminal window if you are running in the foreground. For integration Server, you must run in the foreground by running the server.bat or server.sh startup at the command prompt.
Find the errors that are happening, correct the problem and test the application again.
If DSP/JSP is your goal, then use the Workflow Java Client API and code DSP/JSP to your hearts content. You can use this API as a Java Service inside of Integration Server if you wish, but again, this is not needed in most cases and the API is intended to be used inside an embedded system, such has a pre-existing thick or thin client that needs to become webMethods Workflow enabled.