...
| Info |
|---|
| title | Consumer endpoint attributes |
|---|
| borderStyle | solidbgColor='lighblue' |
|---|
|
Name | Type | Description | Required |
|---|
service | QName | the service name of the proxied endpoint | yes | endpoint | String | the endpoint name of the proxied endpoint | yes | interfaceName | QName | the interface name of the proxied endpoint | | targetService | QName | the service name of the target endpoint | no (defaults to the service attribute) | targetEndpoint | String | the endpoint name of the target endpoint | no (defaults to the endpoint attribute) | targetInterfaceName | QName | the interface name of the target endpoint | | role | String | must be 'consumer' | yes | defaultMEP | URI | the default MEP uri to use | no | defaultOperation | QName | the default operation name to set on the JBI exchange. if not set, it defaults to the QName of the root xml element | no | soap | boolean | if set, the component will parse the soap requests and send the content into the NMR | no (defaults to false) | soapVersion | string | can be set to '1.1' to force the use of SOAP 1.1 messages | no | wsdlResource | Spring resource | if set, the wsdl will be retrieved from the given Spring resource | no | initialContextFactory | String | | yes (unless a default one is provided on the jms component configuration) | jndiProviderURL | String | | yes (unless a default one is provided on the jms component configuration) | destinationStyle | String | | yes (unless a default one is provided on the jms component configuration) | jndiConnectionFactoryName | String | | yes (unless a default one is provided on the jms component configuration) | jndiDestinationName | String | | yes (one of jndiDestinationName or jmsProviderDestinationName) | jmsProviderDestinationName | String | | yes (one of jndiDestinationName or jmsProviderDestinationName) | connectionFactory | javax.jms.ConnectionFactory | the connectionFactory to use. This optional property can be used instead of using JNDI configuration | no |
|
The targetService, targetEndpoint and targetInterfaceName attributes can be used to specify the routing method to use (routing by interface, service or endpoint) and is also useful to allow several proxy endpoints to be created for the same JBI endpoint. For example to create an JMS only endpoint and an JMS+SOAP endpoint, both jms endpoints will have the same targetEndpoint and targetService, but they must have different endpoint names.
...
| Info |
|---|
| title | Provider endpoint attributes |
|---|
| borderStyle | solidbgColor='lighblue' |
|---|
|
Name | Type | Description | Required |
|---|
service | QName | the service name of the exposed jbi endpoint | yes | endpoint | String | the endpoint name of the exposed jbi endpoint | yes | interfaceName | QName | the interface name of the exposed jbi endpoint | no | role | String | must be 'provider' | yes | locationURI | URI | the http url of the target service | yes | soap | boolean | if set, the component will parse the soap requests and send the content into the NMR | no (defaults to false) | wsdlResource | Spring resource | if set, the wsdl will be retrieved from the given Spring resource | no | initialContextFactory | String | | yes (unless a default one is provided on the jms component configuration) | jndiProviderURL | String | | yes (unless a default one is provided on the jms component configuration) | destinationStyle | String | | yes (unless a default one is provided on the jms component configuration) | jndiConnectionFactoryName | String | | yes (unless a default one is provided on the jms component configuration) | jndiDestinationName | String | | yes (one of jndiDestinationName or jmsProviderDestinationName) | jmsProviderDestinationName | String | | yes (one of jndiDestinationName or jmsProviderDestinationName) | connectionFactory | javax.jms.ConnectionFactory | the connectionFactory to use. This optional property can be used instead of using JNDI configuration | no |
|
WSDL Deployment
In addition to xbean based deployment, the component accepts WSDL-based deployment.
The service unit may contain any number of WSDL files, each one being parsed and activating the specified endpoints.
To retrieve the necessary informations from the wsdl, the component can recognize a jms extension to provide JNDI informations and a jbi extension which specifies the role of the component and the default MEP to use for JBI exchanges.
...
