08 May 2007 - 1.7.1 home user-guide eclipse jbossws intellij netbeans maven 1.X/2.X PDF files forums bugs sourceforge






Vote for soapUI at the WSJ Readers' Choice awards in the

'Best Web Services Utility' and

'Best Web Services Testing Tool'

categories

Getting Started with the JBossWS Plugin

JBossWS-related functionality is made available as a JBossWS-Nature which can be enabled for any type of java-project. This allows you to easily publish, consume and implement webservice from most kinds of projects (web, ejb, jar, etc.). Enabling the nature adds a "JBossWS Web Services" node to the project which corresponds to a soapUI-project.xml file in the file system. In the Eclipse Project Explorer, this node will contain all WebS ervices handled by the project:

  • Published Web Services - generated from existing EJB / Pojos as described under Publishing Web Services.
  • Imported Web Services - imported from external Web Services either for consuming or implementing from in the project.

Internally, this node corresponds to a soapUI project-node (with some limitations), specific actions available for this node are:

  • Save - saves changes specific to this node
  • Add WSDL from URL - imports an external Web Service definition (for example for implementing or for consuming)
  • Add WSDL from File - imports an existing WebS ervice definition (for example for implementing)
  • Online Help - shows online help

More information on this node and its functionality is availble in the Eclipse User-Guide.

Enabling JBossWS Support

Enable the nature for a project by selecting "JBossWS / Add JBossWS Nature" from the project menu:

This will prompt with the following dialog:

The prompted options control the basic behaviour of a JBossWS project:

  • Output Source Directory - the directory into which source code is to be generated when implementing a Web Service
  • JBossWS WSTools - the path to the installed WSTools script included in the JBossWS distribution. This option defaults to the global setting (as described above), but can be changed on a project basis (for evaluating new versions).
  • Output Classes Directory - the binary directory for java classes that are to be published as web services.
  • Add JBossWS JAR - adds the bundled jbossws-client.jar to the projects classpath. Select this option if you intend to use any Web Service specific API's/class (annotations, jax-rpc, etc).

Once the JBossWS Nature has been enabled, these settings are available for later modification from the projects properties:

Once the JBossWS Nature has been enabled, you are now ready to:

  • Publish an existing POJO/EJB as a Web Service
  • Consume an external Web Service from within your code
  • Implement an existing Web Service definition
  • Annotate an existing POJO/EJB3 to be published as a JAX-WS Web Service


Next: Publishing Web Services with JBossWS