Steps to re-create the problem :
--------------------------------
Please extract the contents of the ws-sandbox.zip file and then do the following.  All references are from the root of the expanded zip archive.  These steps assume a Windows platform:

Copy the file junit.jar from C:\ws-sandbox\lib (my test case package) to C:\Sun\AppServer\lib\ant\lib so Ant can find the JUnit task.

1. Start the application server and login into the admin console.
2. Through the admin console, deploy the following war files.  ON THE 'Deploy Web Module' Page, MAKE SURE THAT YOU SET THE CONTEXT ROOT TO '/apps/<APPLICATION_NAME>
   * build\SimpleManagerService.war
   * build\WsdlGeneratedManagerService.war
3. In the application server, allow for DEBUG level logging on the following packages:
   * us.co.douglas.webservice
   * us.co.douglas.webservice.alt
4. Open a Windows command proompt.  Change to the root directory of the expanded arechive and run the test cases:
   * C:\> cd \temp\ws-sandbox
   * C:\temp\ws-sandbox>
   * C:\temp\ws-sandbox>C:\<ANT_1.6.3_INSTALL_DIR>\bin\ant.bat -f runTestCases.xml

------------

* SimpleManagerService
  o WSDL generated from a Java interface
  o Server specifies the use of an attachment handler to add attachments
  o Client has a message handler to read attachements
  o Works as expected
  o Classes are in package 'us.co.douglas.webservice'

* WsdlGeneratedManagerService
  o Java interfaces are generated from a pre-defined WSDL file
  o Server specifies the use of an attachment handler to add attachments
  o Client explicitly interrogates the SOAPMessage for attachments
  o Does not work as expected. If you notice in the attached output1.txt control never goes to handleResponse() in case of WsdlGeneratedManagerService. It looks as though the EJBC step does not create an implementation using the specified handler class.
  o Classes are in package 'us.co.douglas.webservice.alt'