You must set certain properties for your property server to define a JAX-WS web service on JBoss.
Parameter | Description |
---|---|
WEBSERVICES_BUILDS | Required. Can take a comma separated list that can include YIFWebService and SIXBeanXapiJaxWS. |
XBEAN_PACKAGE | Optional. By default, the xbean package names
and namespace generated for JAX-WS web services include the word documentation.
Use this parameter to replace the word documentation with
another string. This value can be any string which would form a valid
java package name. Important: Regardless of how it is
entered, Sterling Warehouse Management System will
always convert this string to all lowercase characters to comply with Java™ standards.
|
JAXB_LOCAL_SCOPING | Required. Valid values are true/false. Set to true. This flag affects the way that JAXB generates beans. Everything becomes toplevel so all classes will exist in the default package rather than existing in a hierarchy. Typically, for Sterling Warehouse Management System APIs, not using top-level scoping will result in generated file names that are too long for the file system. |
JAXB_ALWAYS_ANNOTATE_CLASSNAMES | Required. The classes that are generated by
JAXB are given 1-up numbers at the end of their names to
prevent having multiple classes with the same name when top level
scoping is used. By default, this flag is included and set to true (yes, annotate all classes). If you prefer to minimize the use of one-up numbers, specify the AnnotateClassNames attribute in the webservicebeans.xml file for selected APIs, as shown in the following example.
|
SUPPRESS_JAXWS_HANDLERS | By default, Sterling Warehouse Management System applies handlers to JAX-WS based web services as part of security enablement. If you do not want the handlers applied, set this sandbox.cfg variable to true. For more information about web services security, see the Planning for secure deployment of the PA-DSS and SSDCPlanning for secure deployment of the PA-DSS and SSDC topic on the corresponding version of the Sterling Selling and Fulfillment Suite information center. |
jaxws.compiler.jvm.args=-J-XX:MaxPermSize=512m -J-Xmx768m
webservicebeans.xml attributes | Description |
---|---|
Bean attributes Note: Do not put the same API into two beans.
|
|
BeanName | Required. Enter a descriptive name for the web service. The
first letter of the BeanName must be an uppercase letter. This name is used by the WSDL generator and reflected in the client code. Required. For example, a company named Dave's BBQ might use the following:
|
BeanPackage | Required. Required. Enter a descriptive name for the package.
Each bean must have a unique package name. This name is used by the
WSDL generator and reflected in the client code. For example, a company named Dave's BBQ might use the following:
|
API element attributes | |
Api Name | The name of the API that you configured using the Service Builder. |
ExposedName | The name that is used in the Web Services Description Language
(WSDL) file. This is the name that is used to call the web service
programmatically. When specifying a service name for ExposedName,
choose a literal that does not match any of the standard application
API names. The exposed name must start with a lower case letter. |
AnnotateClassNames | Specify the AnnotateClassNames attribute on the webservicebeans.xml to indicate which APIs need to have annotations. This flag provides a more granular way of indicating that 1-up annotations are required for specific APIs as compared to the sandbox variable ALWAYS_ANNOTATE_CLASS_NAMES. |
Service element attributes | |
Service Name | The name of the service that you configured using the Service Builder. |
ExposedName | The name that is used in the Web Services Description Language
(WSDL) file. This is the name that is used to call the web service
programmatically. When specifying a service name for ExposedName,
choose a literal that does not match any of the standard application
service names. The exposed name must start with a lower case letter. |
AnnotateClassName | Specify the AnnotateClassNames attribute on the webservicebeans.xml to indicate which APIs need to have annotations. |
To expose an SDF service as a web service, you must also complete the procedure in Exposing an SDF service as a Web service on JBoss. |