OSB: how a MDB Proxy Service is implemented

today I have created a Proxy Service, reading messages from a Topic, durable subscriber, and I have called it badmdb/consumefromtopic
(badmdb is the project name)

If you look in WL deployments, you find:
C:\bea103b\user_projects\domains\osb_domain\sbgen\ProxyService_badmdb_consumefromto641026.ear

this contains a ejb.jar, which contains only a ejb-jar.xml and a weblogic-ejb-jar.xml
These DD specify:

ejb-class=com.bea.wli.sb.transports.jms.JmsInboundMDB
activation-config-property: subscriptionDurability=Durable

destination-jndi-name=the_topic_jndi
provider-url=t3://localhost:7011
connection-factory-jndi-name=weblogic.jms.XAConnectionFactory
generate-unique-jms-client-id=true
durable-subscription-deletion=true


My guess is that the JmsInboundMDB will internally dispatch the JMSMessage to the OSB Kernel for Message Flow processing