Container configuration for my MDB doesn't work as expected

[frito]

Hi,

I am providing my own container configuration in jboss.xml deployed with my MDB. But it seems, that the container-invoker-conf doesn't work. I am using JBoss 3.2RC4 and the jboss.xml is valid against jboss_3_2.dtd .

This is a snippit of the jboss.xml:
[pre]
<container-configuration>
<container-name>My Message Driven Bean</container-name>
<call-logging>false</call-logging>
<container-interceptors>
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor
org.jboss.ejb.plugins.LogInterceptor
org.jboss.ejb.plugins.RunAsSecurityInterceptor
<!-- CMT -->
org.jboss.ejb.plugins.TxInterceptorCMT
org.jboss.ejb.plugins.MetricsInterceptor
org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor
<!-- BMT -->
org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor
org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT
org.jboss.ejb.plugins.MetricsInterceptor
org.jboss.resource.connectionmanager.CachedConnectionInterceptor
</container-interceptors>
<instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool</instance-pool>
<instance-cache></instance-cache>
<persistence-manager></persistence-manager>
<transaction-manager>org.jboss.tm.TxManager</transaction-manager>
<container-invoker-conf>

20

queue/myDLQ
1
60


</container-invoker-conf>
<container-pool-conf>
100
</container-pool-conf>
</container-configuration>
[/pre]

The configuration used instead is defined in my standardjboss.xml (invoker-proxy-binding).

What do I have to do to get my own configuration working (differend configurations for different beans deployed in my .jar)?

Greetings,

Frito

[adrian.brock]

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

<invoker-proxy-bindings>
<invoker-proxy-binding>
my-message-driven-bean
<invoker-mbean>default</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
<proxy-factory-config>
DefaultJMSProvider
StdJMSPool
15
1
True

10

queue/DLQ
10
0


</proxy-factory-config>
</invoker-proxy-binding>
</invoker-proxy-bindings>

Then reference it on the bean

<enterprise-beans>
<message-driven>
<ejb-name>Whatever</ejb-name>
<invoker-bindings>

<invoker-proxy-binding-name>my-message-driven-bean</invoker-proxy-binding-name>

</invoker-bindings>
</message-driven>
</enterprise-beans>

Of course, you could just use the name
"message-driven-bean" which would replace
the definition in standardjboss.xml for
this jboss.xml

Regards,
Adrian

[frito]

Hi Adrian,

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.

Greetings,

Frito

[frito]

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?

Greetings,

Frito

[adrian.brock]

You are using the following dtd?

<!DOCTYPE jboss PUBLIC
"-//JBoss//DTD JBOSS 3.2//EN"
"http://www.jboss.org/j2ee/dtd/jboss_3_2.dtd">

Regards,
Adrian

[frito]

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.

Greetings,
Frito

[adrian.brock]

I've updated the dtd to include the mdb
config and iiop was missing as well.

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/jboss/src/resources/org/jboss/metadata/jboss_3_2.dtd?annotate=1.1.2.7

To use it, you should replace it in jboss.jar

Regards,
Adrian

[frito]

Thanks a lot! I will do some tests on it soon.

Greetings,

Frito

[seven]

Can <invoker-proxy-binding> be extended? (Like <container-configuration>)

Horia