As JAX-RPC development is not supported by OEPE (WLS supports JAX-RPC though), we want to writeOnce you have implemented your ant build script and wired it up into project build in the builders property page, just use the deployment assembly to add a rule that maps your builder's output directory into the war. Make sure that you've configured project refresh when configuring your ant builder or Eclipse will not see your new files. Then test using ear/war export wizards. If you are getting the expected results, the deployment to WLS will work as well. Both export and deployment are driven by the same deployment assembly rules. You do not need to be concerned with the content the .beabuild.txt file.
a custom ant builder to process the jws files and generate the output in certain folder hierarchy that
the publish plugin will pick them up automatically. This is something we need until we get a chance to
upgrade to JAX-WS.
This is where we need a better understanding of what output folders are automatically linked in .beabuild.txt