Re: [jboss-dev] EJB3 DevForum: Resource adapter file name hard coded into ejb3/MessagingContainer

This would need to be fixed before AS 5.1. Since without this fix, we can't use JBM 2.0 properly in AS 5.1. JBM 2.0 is on the roadmap for EAP 5.1, and EAP 5.1 will consume AS 5.1. So.. you guys got a couple of days to sort it out before code freeze. :) Jesper Pedersen wrote: > On Thursday 23 April 2009 09:11:28 Clebert Suconic wrote: > >> > From what i see in the code >> >> (org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.createActivationSpec >> >> ()) the only reason why the rar-name is being used is to get hold of >> the >> resource adapter MBean for creating the activation spec. >> >> Isn' t there a better way of doing this? >> >> It sounds like a hack to me. the rar-name is already specified on the >> tx-connection-factory, and the MDB has a reference to the factory being >> used, so IMO you shouldn' t need any other reference to the rar. JCA >> should provide you some decent way of getting what you needed without >> adding the hard link. >> >> Jesper: What do you think? >> > > There are plans to include a JBoss JCA SPI in the new container > implementation such that these integration issues can be easier fix. > > MDBs is of course one of the use-cases. > > Best regards, > Jesper > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development >