E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (14)
View Page History
...
{section} If you want more details about jsr181, you can consult this the specification on the Java Community Process portal : [http://jcp.org/en/jsr/detail?id=181|http://jcp.org/en/jsr/detail?id=181]
{column}
{column:width=350px}
{column:width=350px}
... xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-4.0"
xmlns:jsr181="http://petals.ow2.org/components/jsr181/version-1.0>
xmlns:jsr181="http://petals.ow2.org/components/jsr181/version-1.0>
<jbi:component type="service-engine" bootstrap-class-loader-delegation="parent-first">
<jbi:identification>
<jbi:identification>
... <jbi:bootstrap-class-name>org.ow2.petals.se.jsr181.Bootstrap</jbi:bootstrap-class-name>
<jbi:bootstrap-class-path>...</jbi:bootstrap-class-path>
<jbi:bootstrap-class-path>...</jbi:bootstrap-class-path>
<!-- Component Development Kit Parameters -->
<petalsCDK:acceptor-pool-size>5</petalsCDK:acceptor-pool-size>
<petalsCDK:acceptor-pool-size>5</petalsCDK:acceptor-pool-size>
...\\
{note:title=Note}Actually, nothing is configurable in this JBI descriptor, so leave it as it is.{note}
{note:title=Note}Actually, nothing is configurable in this JBI descriptor, so leave it as it is.{note}
{note:title=Node}The class name values in italic should not be modified by the user.{note}
{note}
{include:0 CDK Component Configuration Table}
\\
{include:0 CDK Interceptor configuration for SU}
{include:0 CDK Interceptor configuration for SU}
h1. Service Configuration
{loremipsum:2}
PROVIDE SERVICE : Expose an Java Class as Service in the JBI environment.
The petals-se-jsr181 component can expose a Java Class as JBI ServiceEndpoint. This is done by deploying a Service Unit on it.
When a message is received on a JSR181 linked endpoint from the JBI environment, it is mapped to an Axis2 message and sent to the Axis2 runtime. The linked Java Class is called and the response is processed and returned to the JBI environment.
The petals-se-jsr181 component can expose a Java Class as JBI ServiceEndpoint. This is done by deploying a Service Unit on it.
When a message is received on a JSR181 linked endpoint from the JBI environment, it is mapped to an Axis2 message and sent to the Axis2 runtime. The linked Java Class is called and the response is processed and returned to the JBI environment.
h3. Service Unit descriptor
{loremipsum:1}
The Service Unit descriptor file ( jbi.xml ) looks like this :
\\
\\
{code:lang=xml}
<?xml version="1.0" encoding="UTF-8"?>
<jbi:jbi version="1.0"
<?xml version="1.0" encoding="UTF-8"?>
<jbi:jbi version="1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:jbi="http://java.sun.com/xml/ns/jbi"
xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-4.0"
xmlns:helloworld="http://petals.ow2.org/helloworld"
xmlns:jsr181="http://petals.ow2.org/components/jsr181/version-1.0">
<jbi:services binding-component="false">
<jbi:provides interface-name="helloworld:Helloworld" service-name="helloworld:HelloworldService"
endpoint-name="HelloworldEndpoint">
<petalsCDK:wsdl>Service.wsdl</petalsCDK:wsdl>
<jsr181:class>org.ow2.petals.usecase.jsr181.TestService</jsr181:class>
xmlns:jbi="http://java.sun.com/xml/ns/jbi"
xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-4.0"
xmlns:helloworld="http://petals.ow2.org/helloworld"
xmlns:jsr181="http://petals.ow2.org/components/jsr181/version-1.0">
<jbi:services binding-component="false">
<jbi:provides interface-name="helloworld:Helloworld" service-name="helloworld:HelloworldService"
endpoint-name="HelloworldEndpoint">
<petalsCDK:wsdl>Service.wsdl</petalsCDK:wsdl>
<jsr181:class>org.ow2.petals.usecase.jsr181.TestService</jsr181:class>
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" </jbi:provides>
xmlns:jbi="http://java.sun.com/xml/ns/jbi">
</jbi:services>
</jbi:jbi>
</jbi:jbi>
{code}