I've have similar problem overriding MDB activation config through XML.
It gives me the instance not found exception with JBoss 4.0.4 but seems to work
with JBoss 4.2.0GA.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045411#4045411
Reply to the post :
http
Hmmm...it appears that the resource adapter name is not being set correctly.
Can you tell me what version of EJB3 you are using? Also, I am not sure why are
using annotations and a ejb-jar.xml file. Typically you would only use the XML
configuration if there was something you needed to override.
Issue is still open.
Could somebody close it or fix it :-/ I'm having the same error 2 years later,
think it's a human bug, rather write that down in the bug report so others know
there messing up the same (or not)
Wessel
View the original post :
http://www.jboss.com/index.html?module=bb&op=v
In Jboss 4.0.5GA this problem still occures.. Is it a bug or a human failure.
Can any body post a work around or solution please ?
Wzzl
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4016606#4016606
Reply to the post :
http://www.jboss.com/index.html?module=
I've create JIRA issue for our problem
http://jira.jboss.com/jira/browse/EJBTHREE-671
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963305#3963305
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963305
it seems that if you want to use annotations and ejb-jar.xml (e.g. if you want
to define your MDB with annotations, but specify the destination in
ejb-jar.xml), you must include the tag in
ejb-jar.xml, otherwise you get the "Unable to create activation spec "
exception. Don't know why, bu
slight problem with my previous post. It didn't quite work as well as I had
hoped. It does prevent the exception from occuring, but then it stops picking
up my entries from ejb-jar.xml and jboss.xml. If I change the to
match what I put in the annotation, i get the "Unable to create activatio
I had this same problem. I fixed it by adding the name attribute to the
@MessageDriven annotation
e.g. @MessageDriven(name="testMDB", activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType",
propertyValue = "javax.jms.Queue"),
@ActivationC
I forgot to mention that if I remove message-driven section from ejb-jar.xml,
everything works fine.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959514#3959514
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959514
_
Hi,
I'm having similar problem and I'm not sure if it's jboss bug or not. It
appears whenever I have MDB with activation config properties defined in
annotations and message-driven section for that MDB in ejb-jar.xml.
My MDB:
| @MessageDriven(activationConfig = {
| @ActivationCo
Thanks for your answer.
I have followed your tip and have got a new exception :-(
The new MDB-Code:
| @MessageDriven(activationConfig =
| {
| @ActivationConfigProperty(propertyName="destinationType",
propertyValue="javax.jms.Topic"),
| @ActivationConfigProperty(p
You will want to specfify the JCA/JMS RAR that allows for inflow based
messaging in JBoss. Easiest way to do this is by using the ResourceAdapter
annotation
@ResourceAdapter("jms-ra.rar")
This can be placed after your @MessageDriven annotation. It is a class level
annotation.
View the orig
12 matches
Mail list logo
