|
| Exported build.xml doesn't build Service Control correctly |
 |
Thu, 10 Apr 2008 13:48:53 -070 |
We created a few components that build properly in Workshop...but not in the
build.xml that Workshop generates. We are using Workshop 9.2.
Here is what we did...
1) Coded a Web Service that uses the ALDSP 3.0 dynamic mediator API (to access
a data service)
2) Generated a WSDL from that service
3) Created a Service Control (that uses the WSDL from #2)
When we do a build via Project -> Clean (with Build Automatically enabled),
this gets built just fine.
When we run the Ant task with the targets "clean, build", it fails
when it tries to compile the SEI file (the file that gets generated for #3
above).
During the build process (from the Workshop-exported build.xml file), the
com.bea.control.servicecontrol.impl.ServiceControlAssembler appears to generate
the MyServiceControlSEI.java file that does not compile.
Although the compile error probably has to do with the naming conventions in our
XML schema, we at least want to get the build.xml build process to act the same
way as the regular Project -> Clean process (in which case our project builds
just fine...even with our XML schema issues).
My question is...does the Project -> Clean process use a different set of
APTs or tasks to generate the SEI file than the build.xml process? If so, how
can we configure the exported build.xml file to use the same tasks/tools as the
Project -> Clean process?
Thank you,
|
| Post Reply
|
|
|
|
|
|
|
|
|
|