...
| Info |
|---|
| title | Configuration |
|---|
| borderStyle | solidbgColor='lighblue' |
|---|
|
Name | Type | Description | Default |
|---|
printStackTraceInFaults | boolean | print the full stack trace in faults when an exception occurs | false |
of total simulatenous connections | 256 | |
XBean deployment
Deployment
You can deploy Service Units containing a file named xbean.xml for activating consumer and provider endpoints.
...
Any numbers of endpoints can be specified in the xbean.xml file.
As the main purpose is to expose a POJO, you will have to include the needed class files / jars in the service unit and reference them using the following tags in your xbean.xml configuration file:
| Code Block |
|---|
|
<classpath>
<location>.</location>
</classpath>
|
This will add the content of the location tags (relative to the unzipped service unit) to the classpath. The previous configuration will just add the class files contained in the service unit, as if it is a plain jar.
If you want to embed jars, just use something like
| Code Block |
|---|
|
<classpath>
<location>lib/foo.jar</location>
</classpath>
|
Endpoint
| Info |
|---|
| title | Endpoint attributes |
|---|
| borderStyle | solidbgColor='lighblue' |
|---|
|
Name | Type | Description | Required |
|---|
annotations | String | The annotations used to configure the service. Can be "none", "java5", "jsr181", "commons". If not specified, the annotations type will be discovered by looking at the class. | no | pojo | Object | the instanciated POJO to service requests | one of pojo or pojoClass | pojoClass | String | the class name of the POJO to service requests | one of pojo or pojoClass | serviceInterface | String | the class name of the interface to expose as a service | no | typeMapping | String | Can be "default", "xmlbeans", "jaxb2". Defaults to "default" (Aegis) if no annotations used, else defaults to "jaxb2" | no |
|
