[jboss-as7-dev] Binding MDBs to resource adapters by configuration

[Panzer, Robert]

Sorry, I don't know if I got you right now.

The snippet below means to me that you want to extend the schema for the ejb-jar.xml by adding jboss specific tags.
Doesn't this break the parsing of the deployment descriptor on other application servers, that do not know this namespace?

Or was is just an example to point me to another implementation that does something similar for another task?

Kind regards,
Robert

-----Original Message-----
From: jboss-as7-dev-bounces at lists.jboss.org [mailto:jboss-as7-dev-bounces at lists.jboss.org] On Behalf Of Carlo de Wolf
Sent: Thursday, November 17, 2011 3:41 PM
To: jboss-as7-dev at lists.jboss.org
Subject: Re: [jboss-as7-dev] Binding MDBs to resource adapters by configuration

There is no such code yet.

<assembly-descriptor>
<ejb-name>*</ejb-name>
<mdb:resource-adapter>ra-name-of-your-choice</mdb:resource-adapter>
</assembly-descriptor>

That way you can override per MDB.

It requires implementation of an extension xsd and associated parser.
https://github.com/jbossas/jboss-as/blob/master/ejb3/src/main/java/org/jboss/as/ejb3/security/parser/SecurityRoleMetaDataParser.java
https://github.com/jbossas/jboss-as/blob/master/ejb3/src/main/resources/jboss-ejb-security-role_1_0.xsd

Carlo

On 11/17/2011 03:09 PM, Jaikiran Pai wrote:
> Just a FYI - Right now, there's a way to configure the resource-adapter
> used by the MDBs via the standalone.xml/domain.xml. But that then
> applies to all MDBs deployed on that server. You can do it as follows:
>
> <!-- Default MDB configurations -->
> <mdb>
> <resource-adapter-ref resource-adapter-name="ra-name-of-your-choice"/>
> ...
>
> But like you say, there are plans to allow it to be specified at per MDB
> or even a per deployment (applies to all MDBs in that deployment) via
> the jboss-ejb3.xml. Carlo has been working on the jboss-ejb3.xml parts,
> so he'll know if we already have some code to support this. If not, we
> are welcome to contributions.
>
> P.S: We are usually on #jboss-as7 irc.freenode.net IRC channel if you
> want to have a chat about how to proceed on the implementation.
>
> -Jaikiran
> On Thursday 17 November 2011 07:32 PM, Panzer, Robert wrote:
>> Hi,
>>
>> currently binding a message driven bean to another resource adapter
>> than the default resource adapter requires adding a JBoss specific
>> annotation @org.jboss.ejb3.annotation.ResourceAdapter to the MDB.
>>
>> I think there should also be a way to establish this binding using a
>> specific deployment descriptor to allow for deploying portable JEE
>> applications to JBoss 7.
>>
>> Looking at the code I think that this should go into the jboss-ejb3.xml.
>>
>> As far as I can see the parsing code in jboss-metadata-ejb only parses
>> a skeleton document that looks like this:
>>
>> <jboss xmlns="http://www.jboss.com/xml/ns/javaee">
>>
>> <enterprise-beans>
>>
>> <ejb>
>>
>> </ejb>
>>
>> </enterprise-beans>
>>
>> </jboss>
>>
>> So if I have not overseen anything there is no way of establishing
>> this binding.
>>
>> I'd like to contribute to this part but would like to have an opinion
>> how this file should look like in the end.
>>
>> As a resource adapter binding only makes sense for MDBs I would prefer
>> something like this:
>>
>> <jboss xmlns="http://www.jboss.com/xml/ns/javaee">
>>
>> <enterprise-beans>
>>
>> <message-driven>
>>
>> <ejb-name>MyEjbName</ejb-name>
>>
>> <resource-adapter>myConnector.rar</resource-adapter>
>>
>> </message-driven>
>>
>> </enterprise-beans>
>>
>> </jboss>
>>
>> What do you think about this?
>>
>> Kind regards,
>>
>> Robert
>>
>>      *WINCOR NIXDORF International GmbH*
>>      Sitz der Gesellschaft: Paderborn
>>      Registergericht Paderborn HRB 3507
>>      Geschäftsführer: Eckard Heidloff (Vorsitzender), Stefan Auerbach,
>>      Dr. Jürgen Wunram
>>      Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller
>>      Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 -
>>      WEEE-Reg.-Nr. DE44477193
>>
>>      Diese E-Mail enthält vertrauliche Informationen.
>>      Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
>>      irrtümlich erhalten haben,
>>      informieren Sie bitte sofort den Absender und vernichten Sie diese
>>      E-Mail.
>>      Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
>>      E-Mail ist nicht gestattet.
>>
>>      This e-mail may contain confidential information.
>>      If you are not the intended recipient (or have received this
>>      e-mail in error)
>>      please notify the sender immediately and destroy this e-mail.
>>      Any unauthorised copying, disclosure or distribution of the
>>      material in this e-mail is strictly forbidden.
>>
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

WINCOR NIXDORF International GmbH
Sitz der Gesellschaft: Paderborn
Registergericht Paderborn HRB 3507
Geschäftsführer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. Jürgen Wunram
Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller
Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193

Diese E-Mail enthält vertrauliche Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.

This e-mail may contain confidential information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail.
Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.