[Users] Queuing in Petals ?

[Christophe DENEUX]

Philip,

The JBI descriptor of an SU of the SE ASE is as following:
<code>
<?xml version="1.0" encoding="UTF-8"?>
<jbi:jbi	xmlns:jbi="http://java.sun.com/xml/ns/jbi" 
	
xmlns:linagora.com="http://petals.ow2.org/components/filetransfer/version-3" 
		xmlns:ase="http://petals.ow2.org/components/ase/version-1"
		xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5"
 		version="1.0">
  <jbi:services binding-component="false">
    	<jbi:provides 
    			interface-name="linagora.com:FileTransferType" 
    			service-name="linagora.com:AsyncTicketWriter"
    			endpoint-name="AsyncTicketWriterEndpoint">
    	
    		        
			<petalsCDK:wsdl>FileTransferService.wsdl</petalsCDK:wsdl>

			
			
    	</jbi:provides>
    	<jbi:consumes 
    			interface-name="linagora.com:FileTransferType"
    			service-name="linagora.com:TicketWriter">
    	
    		
    		<petalsCDK:timeout>30000</petalsCDK:timeout>
      		<petalsCDK:mep>InOnly</petalsCDK:mep>
      		
      		
      		
      		<ase:retry-policy-number>3</ase:retry-policy-number>
      		<ase:retry-policy-base-interval>10</ase:retry-policy-base-interval>
      		<ase:retry-policy-factor>3</ase:retry-policy-factor>
    	</jbi:consumes>
  </jbi:services>
</jbi:jbi>
</code>

The part 'provides' is relative to the service that will be created by SE
ASE. You will invoke it from your consumer.
The part 'consumers' is relative to the real service that is facadized, in
your case, the web-service. In 'interface-name', 'service-name' and
'endpoint-name' you set your service name associated to your web-service.




-----
Christophe DENEUX
Petals ESB Architect
Linagora
Twitter: @ChrisDENEUX
--
View this message in context: http://forum.petalslink.com/Queuing-in-Petals-tp4025640p4025646.html
Sent from the Users (get help, provide help) mailing list archive at Nabble.com.