as you specified type, specufy the provider:

provider="com.example:myProvId"

- Romain


2012/6/27 Bjorn Danielsson <[email protected]>

> Yes, I did. I think loading-by-provider may be broken, because I
> peeked at the TomEE source and found that if the provider is null
> it will find by type. So I made it work by removing the provider
> attribute in tomee.xml, and giving the full classname as the type:
>
> <Resource id="My Other JMS Resource Adapter"
> type="com.sun.genericra.GenericJMSRA">
> </Resource>
>
> And I made the corresponding name change in service-jar.xml:
>
>    types="com.sun.genericra.GenericJMSRA"
>
> instead of
>
>    types="GenericJMSRA"
>
> Without this it wouldn't find the class. Maybe there is some
> other way to make the short type-name work, but these changes
> were enough to get the resource created.
>
> Then I deployed my webapp and got some new errors, but I haven't
> really started configuring the adapter yet, so I'll get back
> here again when I have tried that.
>
> --
> Björn Danielsson
> Cuspy Code AB
>
>
> Romain Manni-Bucau <[email protected]> wrote:
> > did you put it in tomee/lib?
> >
> > - Romain
> >
> >
> > 2012/6/27 Bjorn Danielsson <[email protected]>
> >
> >> Thanks!
> >>
> >> Here is my first question (and stumbling block). I tried the second
> >> method on the wiki page, using the Generic JMS Resource Adapter to
> >> integrate an Apache Qpid client. But TomEE complained that it didn't
> >> find the provider:
> >>
> >> Jun 27, 2012 2:05:58 PM org.apache.openejb.config.ConfigurationFactory
> >> configureService
> >> SEVERE: Failed Configuring Service(id=My Other JMS Resource Adapter)
> >> org.apache.openejb.config.NoSuchProviderException: Cannot find the
> >> ServiceProvider id com.example in the service-jar.xml at com.example.
> Check
> >> that your OpenEJB configuration file is point to the right
> ServiceProvider
> >> id."
> >>        at
> >>
> org.apache.openejb.config.ServiceUtils.getServiceProvider(ServiceUtils.java:114)
> >>        at
> >>
> org.apache.openejb.config.ConfigurationFactory.resolveServiceProvider(ConfigurationFactory.java:1025)
> >>        at
> >>
> org.apache.openejb.config.ConfigurationFactory.configureService(ConfigurationFactory.java:887)
> >>        at
> >>
> org.apache.openejb.config.ConfigurationFactory.getOpenEjbConfiguration(ConfigurationFactory.java:403)
> >> [...]
> >>
> >> This is my resource declaration in tomee.xml:
> >>
> >> <Resource id="My Other JMS Resource Adapter" type="GenericJMSRA"
> >> provider="com.example">
> >> </Resource>
> >>
> >> And this is the jar I put in $CATALINA_HOME/lib to package
> service-jar.xml:
> >>
> >> # jar tvf tomee-qpid.jar
> >>     0 Wed Jun 27 14:02:02 CEST 2012 META-INF/
> >>    71 Wed Jun 27 14:02:02 CEST 2012 META-INF/MANIFEST.MF
> >>     0 Wed Jun 27 12:29:38 CEST 2012 META-INF/com.example/
> >>  2395 Wed Jun 27 12:29:38 CEST 2012 META-INF/com.example/service-jar.xml
> >>
> >> Why didn't it work?
> >>
> >> Version info:
> >>
> >> apache-tomee-1.1.0-20120627.041358-42-plus
> >> genericjmsra/v2.1a
> >>
> >> No webapps deployed, just a fresh install, easy to replicate.
> >>
> >> --
> >> Björn Danielsson
> >> Cuspy Code AB
> >>
> >>
> >> David Blevins <[email protected]> wrote:
> >> > On Jun 26, 2012, at 12:46 AM, Bjorn Danielsson wrote:
> >> >
> >> >> Does anyone have a recipe for using Apache Qpid or JORAM
> >> >> with TomEE-plus (i.e. replacing the bundled ActiveMQ)?
> >> >> The configuration I have in mind is a container-managed
> >> >> MDB that receives messages from an external broker.
> >> >
> >> > Created this doc for you:
> >> >
> >> >   http://openejb.apache.org/changing-jms-implementations.html
> >> >
> >> > It's just an hour old, so may not fully answer the question. :)
> >> >
> >> > Between the two of us I'm sure we can perfect it.  You can use the
> >> little blue pencil icon in the upper right to edit.  Feel free to tweak
> it
> >> as much as you like and feel free to keep asking questions.
> >> >
> >> > One of the areas we really need to document better.  The last time
> this
> >> came up it didn't go beyond the mailing list, so hopefully this time we
> can
> >> capture the steps more permanently :)
> >> >
> >> > Thanks for the question!
> >> >
> >> >
> >> > -David
> >>
>

Reply via email to