wsimport(1) [mojave man page]
wsimport(1) General Commands Manual wsimport(1) NAME
wsimport - JAX-WS 2.0 SYNOPSIS
wsimport [options] wsdl DESCRIPTION
The wsimport tool generates JAX-WS portable artifacts, such as: o Service Endpoint Interface (SEI) o Service o Exception class mapped from wsdl:fault (if any) o Async Reponse Bean derived from response wsdl:message (if any) o JAXB generated value types (mapped java classes from schema types) These artifacts can be packaged in a WAR file with the WSDL and schema documents along with the endpoint implementation to be deployed. The generated Service class can be used to invoke the Web Service endpoint. OPTIONS
-d directory Specify where to place generated output files. -b path Specify external JAX-WS or JAXB binding files (Each file must have its own -b). -catalog Specify catalog file to resolve external entity references, it supports TR9401, XCatalog, and OASIS XML Catalog format. Please read the XML Entity and URI Resolvers document or see wsimport_catalog sample. -extension Allow vendor extensions (functionality not specified by the specification). Use of extensions may result in applications that are not portable or may not interoperate with other implementations. -help Display help. -httpproxy:host:port Specify an HTTP proxy server (port defaults to 8080). -keep Keep generated files. -p Specifying a target package via this command-line option, overrides any wsdl and schema binding customization for package name and the default package name algorithm defined in the specification. -s directory Specify where to place generated source files. -verbose Output messages about what the compiler is doing. -version Print version information. -wsdllocation location @WebService.wsdlLocation and @WebServiceClient.wsdlLocation value Multiple JAX-WS and JAXB binding files can be specified using -b option and they can be used to customize various things like package names, bean names, etc. More information on JAX-WS and JAXB binding files can be found in the customization documentation. Examples wsimport -d generated http://example.org/stock?wsdl This command generates JAX-WS portable artifacts for http://example.org/stock?wsdl in to the generated directory. wsimport stock.wsdl -b stock.xml -b stock.xjb The above example generates JAX-WS artifacts for stock.wsdl and uses the customization files stock.xml (jax-ws customization file) and stock.xjb (jaxb customization file) in the process. 07 Aug 2006 wsimport(1)
Check Out this Related Man Page
schemagen(1) General Commands Manual schemagen(1) NAME
schemagen - Java(TM) Architecture for XML Binding Schema Generator Specification Version: 2.0 Reference Implementation (RI) Version: 2.0 ea3 Launching schemagen The schema generator can be launched using the appropriate schemagen shell script in the bin directory for your platform. The current schema generator can process either Java source files or class files. We also provide an Ant task to run the schema generator - see the instructions for using schemagen with Ant. For Solaris/Linux % path/to/jaxb/bin/schemagen.sh Foo.java Bar.java ... Note: Writing schema1.xsd For WindowsNT/2000/XP > path ojaxbinschemagen.bat Foo.java Bar.java ... Note: Writing schema1.xsd If your java sources/classes reference other classes, they must be accessable on your system CLASSPATH environment variable, or they need to be given to the tool by using the -classpath/-cp options. Otherwise you will see errors when generating your schema. Command Line Options Usage: schemagen [-options ...] <java files> Options: -d <path> : Specify where to place processor and javac generated class files -cp <path> : Specify where to find user specified files -classpath <path> : Specify where to find user specified files -help : Display this usage message Generated Resource Files The current schema generator simply creates a schema file for each namespace referenced in your Java classes. There is no way to control the name of the generated schema files at this time. For that purpose, use the schema generator ant task. See Also o JAXB 2.0: * Release Notes @ http://java.sun.com/webservices/docs/2.0/jaxb/ReleaseNotes.html * XJC @ http://java.sun.com/webservices/docs/2.0/jaxb/xjc.html * XJCTask @ http://java.sun.com/webservices/docs/2.0/jaxb/xjcTask.html * SchemaGen @ http://java.sun.com/webservices/docs/2.0/jaxb/schemagen.html * schemagenTask @ http://java.sun.com/webservices/docs/2.0/jaxb/schemagenTask.html * Sample Apps @ http://java.sun.com/webservices/docs/2.0/jaxb/samples.html * Changelog @ http://java.sun.com/webservices/docs/2.0/jaxb/changelog2.html o JAXB 1.0.x: * Release Notes @ http://java.sun.com/webservices/docs/2.0/jaxb/jaxb-1_0.html * Changelog @ http://java.sun.com/webservices/docs/2.0/jaxb/changelog.html o JAXB RI Extensions: * Runtime Properties @ http://java.sun.com/webservices/docs/2.0/jaxb/vendorProperties.html * XJC Customizations @ http://java.sun.com/webservices/docs/2.0/jaxb/vendorCustomizations.html * Develop Plugins @ http://java.sun.com/webservices/docs/2.0/jaxb/developPlugins.html o JAXB RI Schema Languages: * W3C XML Schema @ http://java.sun.com/webservices/docs/2.0/jaxb/vendorSchemaLangs.html#xschema * RELAX NG @ http://java.sun.com/webservices/docs/2.0/jaxb/vendorSchemaLangs.html#relaxng * DTD @ http://java.sun.com/webservices/docs/2.0/jaxb/vendorSchemaLangs.html#dtd o JAXB Community: * Java.net Homepage @ http://jaxb.dev.java.net * Developer interest list @ https://jaxb.dev.java.net/servlets/ProjectMailingListList * FAQ @ https://jaxb.dev.java.net/faq/index.html 07 Aug 2006 schemagen(1)