Java Reference
In-Depth Information
AS_ADMIN_PASSWORD=adminadmin
deploy.cp=${sun.app.ant.jar}${path.separator}${gf.root}/lib/
admin-cli.jar${path.separator}${gf.root}/lib/
appserv-rt.jar${path.separator}${gf.root}/lib/appserv-admin.jar
server.location=http://${gf.server.address}:${gf.port}
#2.1
sun.app.ant.jar=${lib.dir}/sun-appserv-ant.jar
sun.ws.tools.jar=${lib.dir}/webservices-tools.jar
sun.ws.rt.jar=${lib.dir}/webservices-rt.jar
#TASKS
junit.task.path=${lib.dir}/ant-junit.jar
xjc.task.path=${sun.app.ant.jar}${path.separator}${sun.ws.tools.jar}
${path.separator}${sun.ws.rt.jar}
Run the “all” target on the Ant build and you should be up and running.
Don't forget that you may want clients to use your original schema; the JAXB types generated
from them will lose all type restriction information. There are ways of validating Java objects
against a service schema, which we examine in other recipes. If you have only Java clients,
you can bundle the generated classes and the original schema in a client JAR for them to in-
voke.
See Also
Validating Against a Schema During Marshaling and Unmarshaling
for further discussion on
schema validation options and
Validating Your Payload Against a Schema on the Client
to see
how to validate client data using this schema, WSDL, and service as an example.
