Re: [jboss-as7-dev] Binding MDB to resource adapter by jboss-ejb3.xml
by Panzer, Robert
I was not aware that it is working like this.
So I am fine with this approach. Thank you for the hint!!!
I would remove my extensions for activation config properties again and prepare a pull request only for the resource-adapter-binding, ok?
<?xml version="1.0" encoding="UTF-8"?>
<jboss xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:jee="http://java.sun.com/xml/ns/javaee"
xmlns:mdb="urn:resource-adapter-binding"
xmlns:security="urn:security">
<jee:enterprise-beans>
<jee:message-driven>
<jee:ejb-name>MyMDB</jee:ejb-name>
<jee:activation-config>
<jee:activation-config-property>
<jee:activation-config-property-name>fooProp</jee:activation-config-property-name>
<jee:activation-config-property-value>fooValue</jee:activation-config-property-value>
</jee:activation-config-property>
</jee:activation-config>
</jee:message-driven>
</jee:enterprise-beans>
<jee:assembly-descriptor>
<mdb:resource-adapter-binding>
<jee:ejb-name>MyMDB</jee:ejb-name>
<mdb:resource-adapter-name>FooConnector.rar</mdb:resource-adapter-name>
</mdb:resource-adapter-binding>
</jee:assembly-descriptor>
</jboss>
Kind regards,
Robert
-----Original Message-----
From: jboss-as7-dev-bounces(a)lists.jboss.org [mailto:jboss-as7-dev-bounces@lists.jboss.org] On Behalf Of Carlo de Wolf
Sent: Friday, November 18, 2011 1:09 PM
To: jboss-as7-dev(a)lists.jboss.org
Subject: Re: [jboss-as7-dev] Binding MDB to resource adapter by jboss-ejb3.xml
I'm not talking about the activation-configType, that is being reused.
Maybe it would make sense to also have it in the assembly, but then it
should be:
<a:additional-activation-config>
<ejb-name>FooBeanMDB</ejb-name>
<activation-config>
</activation-config>
</a:additional-activation-config>
And we would need to specify rules how that element is merged with the
real activation-config element in the message-driven element. The
message-driven element can be used in jboss-ejb3.xml.
<enterprise-beans xmlns="http://java.sun.com/xml/ns/javaee">
<message-driven>
</message-driven>
</enterprise-beans>
In fact it looks like we just want to add additional items to the MDB
container itself, so <mdb:resource-adapter-binding> is wrongly named. It
looks more like a <mdb:template> but that name doesn't look right.
Another alternative which I've yet to implement is extending the
<session>, <entity> and <message-driven> elements themselves.
Carlo
On 11/18/2011 01:02 PM, Panzer, Robert wrote:
> Yes, indeed.
>
> As far as I could see, it does not work adding a message-driven element to the jboss-ejb3.xml right now - correct me from wrong.
> So I think Carlo refers to the message-driven element of the ejb-jar.xml which are the same on every application server.
>
> In my opinion it should be possible to override properties for a specific environment.
>
> WAS for instance resolves this problem by having the activation spec a manageable entity that is not coupled to the application nor the ejb component and there you can define properties. (I hope I did not earn a big Boohhh now... ;-) )
>
> I am preparing branching my fork and will post a message when I have a pull-request ready so that you can review the things I've done.
>
> Kind regards,
> Robert
>
> -----Original Message-----
> From: jboss-as7-dev-bounces(a)lists.jboss.org [mailto:jboss-as7-dev-bounces@lists.jboss.org] On Behalf Of Jaikiran Pai
> Sent: Friday, November 18, 2011 12:55 PM
> To: jboss-as7-dev(a)lists.jboss.org
> Subject: Re: [jboss-as7-dev] Binding MDB to resource adapter by jboss-ejb3.xml
>
> From what I see in that example, Robert isn't duplicating the
> activation-config in the jboss-ejb3.xml. Instead he is reusing the jee
> namespace (that maps to http://java.sun.com/xml/ns/javaee which is used
> as the target namespace by ejb-jar.xml xsd) to specify those
> activation-config properties.
>
> -Jaikiran
> On Friday 18 November 2011 05:12 PM, Carlo de Wolf wrote:
>> activation-config is already an element of message-driven. It would
>> only lead to confusion if you duplicate it.
>>
>> Carlo
>>
>> On 11/18/2011 12:02 PM, Panzer, Robert wrote:
>>> Hi,
>>>
>>> I've got something running now, that binds a message driven bean to a resource adapter using the jboss-ejb3.xml so that it is no longer necessary to define it using a JBoss specific annotation in the source nor to modify the default resource adapter in the server configuration.
>>> It is even possible to redefine activation config properties if they have to have a different value in a JBoss environment.
>>>
>>> An example of the file looks like this:
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <jboss xmlns="http://www.jboss.com/xml/ns/javaee"
>>> xmlns:jee="http://java.sun.com/xml/ns/javaee"
>>> xmlns:mdb="urn:resource-adapter-binding"
>>> xmlns:security="urn:security">
>>>
>>> <jee:assembly-descriptor>
>>> <security:security>
>>> <jee:ejb-name>TestCC</jee:ejb-name>
>>> <security:security-domain>abc</security:security-domain>
>>> </security:security>
>>> <mdb:resource-adapter-binding>
>>> <jee:ejb-name>FooMDB</jee:ejb-name>
>>> <mdb:resource-adapter-name>FooConnector.rar</mdb:resource-adapter-name>
>>> <jee:activation-config>
>>> <jee:activation-config-property>
>>> <jee:activation-config-property-name>fooActivationPropertyName</jee:activation-config-property-name>
>>> <jee:activation-config-property-value>FooValue</jee:activation-config-property-value>
>>> </jee:activation-config-property>
>>> </jee:activation-config>
>>> </mdb:resource-adapter-binding>
>>> </jee:assembly-descriptor>
>>> </jboss>
>>>
>>> What do you think about this structure?
>>>
>>> If there are no objections to this I would propose a pull request.
>>>
>>> The files I have touched are:
>>> # modified: ejb3/src/main/java/org/jboss/as/ejb3/deployment/processors/EjbJarParsingDeploymentUnitProcessor.java
>>> # modified: ejb3/src/main/java/org/jboss/as/ejb3/deployment/processors/merging/ResourceAdaptorMergingProcessor.java
>>> # new file: ejb3/src/main/java/org/jboss/as/ejb3/resourceadapterbinding/metadata/EJBBoundResourceAdapterBindingMetaData.java
>>> # new file: ejb3/src/main/java/org/jboss/as/ejb3/resourceadapterbinding/parser/EJBBoundResourceAdapterBindingMetaDataParser.java
>>> # new file: ejb3/src/main/resources/jboss-ejb-resource-adapter-binding_1_0.xsd
>>>
>>> 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(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)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.
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)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.
12 years, 5 months
Binding MDB to resource adapter by jboss-ejb3.xml
by Panzer, Robert
Hi,
I've got something running now, that binds a message driven bean to a resource adapter using the jboss-ejb3.xml so that it is no longer necessary to define it using a JBoss specific annotation in the source nor to modify the default resource adapter in the server configuration.
It is even possible to redefine activation config properties if they have to have a different value in a JBoss environment.
An example of the file looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<jboss xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:jee="http://java.sun.com/xml/ns/javaee"
xmlns:mdb="urn:resource-adapter-binding"
xmlns:security="urn:security">
<jee:assembly-descriptor>
<security:security>
<jee:ejb-name>TestCC</jee:ejb-name>
<security:security-domain>abc</security:security-domain>
</security:security>
<mdb:resource-adapter-binding>
<jee:ejb-name>FooMDB</jee:ejb-name>
<mdb:resource-adapter-name>FooConnector.rar</mdb:resource-adapter-name>
<jee:activation-config>
<jee:activation-config-property>
<jee:activation-config-property-name>fooActivationPropertyName</jee:activation-config-property-name>
<jee:activation-config-property-value>FooValue</jee:activation-config-property-value>
</jee:activation-config-property>
</jee:activation-config>
</mdb:resource-adapter-binding>
</jee:assembly-descriptor>
</jboss>
What do you think about this structure?
If there are no objections to this I would propose a pull request.
The files I have touched are:
# modified: ejb3/src/main/java/org/jboss/as/ejb3/deployment/processors/EjbJarParsingDeploymentUnitProcessor.java
# modified: ejb3/src/main/java/org/jboss/as/ejb3/deployment/processors/merging/ResourceAdaptorMergingProcessor.java
# new file: ejb3/src/main/java/org/jboss/as/ejb3/resourceadapterbinding/metadata/EJBBoundResourceAdapterBindingMetaData.java
# new file: ejb3/src/main/java/org/jboss/as/ejb3/resourceadapterbinding/parser/EJBBoundResourceAdapterBindingMetaDataParser.java
# new file: ejb3/src/main/resources/jboss-ejb-resource-adapter-binding_1_0.xsd
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.
12 years, 5 months
Recent changes break ejb_vehicle tests
by Thomas Diesler
Folks,
the EJB client jndi binding seems to have changed, which breaks all
(jaxr) ejb_vehicle tests. The log says:
11-18-2011 04:58:00: ERROR: java.lang.RuntimeException:
javax.naming.NameNotFoundException: BusinessLifeCycleManager_ejb_vehicle
-- service jboss.naming.context.java.BusinessLifeCycleManager_ejb_vehicle
at
org.jboss.as.ejb3.deployment.processors.EjbLookupInjectionSource$1.getReference(EjbLookupInjectionSource.java:93)
at
org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:115)
at
org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177)
at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:92)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:213)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.sun.ts.lib.util.TSNamingContext.lookup(TSNamingContext.java:62)
at com.sun.ts.lib.util.TSNamingContext.lookup(TSNamingContext.java:48)
at
com.sun.ts.tests.common.vehicle.ejb.EJBVehicleRunner.run(EJBVehicleRunner.java:52)
at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:102)
at com.sun.ts.lib.harness.EETest.getPropsReady(EETest.java:392)
at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:210)
at com.sun.ts.lib.harness.EETest.run(EETest.java:204)
at
com.sun.ts.tests.common.vehicle.VehicleClient.main(VehicleClient.java:27)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.jboss.as.appclient.service.ApplicationClientStartService$1.run(ApplicationClientStartService.java:123)
at java.lang.Thread.run(Thread.java:662)
Caused by: javax.naming.NameNotFoundException:
BusinessLifeCycleManager_ejb_vehicle -- service
jboss.naming.context.java.BusinessLifeCycleManager_ejb_vehicle
at
org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:88)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177)
at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:82)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:213)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at
org.jboss.as.ejb3.deployment.processors.EjbLookupInjectionSource$1.getReference(EjbLookupInjectionSource.java:79)
I'd guess that the XSLT generated mapping in the jboss descriptors is
not in sync any more.
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
12 years, 5 months
Re: [jboss-as7-dev] Binding MDBs to resource adapters by configuration
by 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(a)lists.jboss.org [mailto:jboss-as7-dev-bounces@lists.jboss.org] On Behalf Of Carlo de Wolf
Sent: Thursday, November 17, 2011 3:41 PM
To: jboss-as7-dev(a)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/jb...
https://github.com/jbossas/jboss-as/blob/master/ejb3/src/main/resources/j...
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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)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.
12 years, 5 months
Binding MDBs to resource adapters by configuration
by Panzer, Robert
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.
12 years, 5 months
How-To: Clustered EJBs
by Carlo de Wolf
I want to see a full user story on clustered EJBs.
- what do I need to configure?
- how do I write a clustered EJB? (with @Clustered?)
- how do I deploy it?
- how do I run and test it? (with Arquillian)
What I don't want to see yet is fine tuning the clustered caches. If
"Hello world" gets replicated and I can see some node affinity in action
I'm a happy nerd.
I'm especially interested into having a clear description of the
relationship between nodes, server groups, clustered nodes and EJB
deployment groups (/ distinct name).
In a next step I want to see rolling upgrade.
This ties into the technical details Scott needs for XPC replication,
but I see it as two different concerns albeit coming to a convergence point.
Carlo
12 years, 5 months
server.logs don't always seem to be created by the testsuite anymore...
by Scott Marlow
To recreate in as7 dev root folder, delete current server.logs ("find
-name server.log -print -ls -delete" will show the current logs and
delete them).
Then do this
./integration-tests.sh install -DallTests./integration-tests.sh clean
install -Dtest=org.jboss.as.test.integration.jpa.hibernate.*TestCase
-Dintegration.module -Dbasic.integration.tests
Then look for server.logs "find -name server.log -print -ls"
12 years, 5 months
XSLT transformation of Sun's descriptors
by Thomas Diesler
Hi Shelly/Ondřej,
would it be possible to raise the priority of JBQA-5449
<https://issues.jboss.org/browse/JBQA-5449> ? This is becomming a
blocker for JAXR TCK progress and I suspect for many other sections too.
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
12 years, 5 months
Term "Site Local Address"
by Heiko Braun
Within the interface config we use the term "site local address". Is this term restricted to IP6 or is used to describe private IP4 address spaces as well?
Ike
12 years, 5 months
