3.2 was changed to allow multple invokers
per ejb: e.g. you can access via RMI or RMI/IIOP
or RMI/HTTP, etc.
allow this doesn't make much sense for mdbs :-)
The configuration is now done using
invoker proxy bindings.
You should define your own invoker proxy binding
Then reference it on the bean
Of course, you could just use the name
"message-driven-bean" which would replace
the definition in standardjboss.xml for
thank you very much for you answer. Now I realized that the dtd of RC4 is finally reflecting these changes, which the dtd of RC3 didn't.
Pretty easy in theory but not in code of practice *G*:
the dtd doesn't allow all the tags under proxy-factory-config (JMSProviderAdapterJNDI, ServerSessionPoolFactoryJNDI, ... , MDBConfig).
Is the dtd up to date? Can't I deploy a complete invoker-proxy-binding for my MDB?
Yes, I do.
I checked out JBoss 3.2.0 yesterday and there were changes on this dtd since RC4 or compared to teh binary release at sourceforge (but I didn't check the differences).
Looking at my most acutal jboss_3_2.dtd shows me this line:
<!ELEMENT proxy-factory-config (client-interceptors)>. No JMSProviderAdapterJNDI and the other elements allowed here.
I've updated the dtd to include the mdb
config and iiop was missing as well.
To use it, you should replace it in jboss.jar
Thanks a lot! I will do some tests on it soon.
Can <invoker-proxy-binding> be extended? (Like <container-configuration>)