Hi,
We have been working on the initial design for the Inbound Endpoint support
for ESB.
- Inbound endpoint is a dynamically configured message source for ESB.
- The current axis2 based transports other than HTTP/S doesn't work in
multitenant mode. The main idea is to supporting all transport (not only
HTTP) in multi-tenant mode with the introduction of inbound endpoints.
- The inbound endpoints will have multiple behavior based on
implementation: polling, busy wait or listening.
- In W/M separated setups, the coordination requirements for polling
behavior is handled by taks which is based on ntasks.
This is the initial syntax we came up with:
<inboundEndpoint name="MyJMSListenerEP"
protocol="jms"
interval="1000" suspend="false">
<parameters>
<parameter
name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
<parameter
name="java.naming.provider.url">tcp://localhost:61616</parameter>
<parameter
name="jms.ConnectionFactoryJNDIName">QueueConnectionFactory</parameter>
<parameter name="jms.ConnectionFactoryType">queue</parameter>
<parameter name="jms.Destination">ordersQueue</parameter>
</parameters>
<sequence key="requestHandlerSeq" onError="inFault"/>
</inboundEndpoint>
The inbound endpoint will be a new construct in ESB which goes at the top
level as with proxy services, APIs etc.
I have completed the initial work related to inbound EP and implemented a
basic JMS inbound EP. Also I've verified the functionality in super tenant
and tenant mode as well.
Ravi is working on getting the end to end scenario working for JMS Inbound
EP.
Please review the design and share your thoughts.
Thanks,
Kasun
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
