I barely remember this, so bare with me if I'm not correct, but I do believe
that at that time we were trying to isolate the EAR and progress towards J2EE
compliance. We avoided this problem by, for the time being, giving up on
isolating any EAR that contained MDBs, and consequently, any other
I have a similar issue where my abstract base class doesn't have the
onMessage(Message m) declaration.
| public abstract class BaseMessageBean implements MessageDrivenBean,
MessageListener
| {
| private MessageDrivenContext context = null;
|
| public void setMessageDrivenCont
Right now I'd settle for understanding what's wrong and hearing either
confirmation that there is a bug in 4.0.2 or an example of a workaround for it.
Even this doesn't work:
| public class SubscriberTxBean
| implements MessageDrivenBean, MessageListener
| {
| private static
erik777 - it seems simple enough to create a delegate class. Basically, create
an MDB class that wraps another (does not subclass).
anonymous wrote : if a patch becomes available
I suggest you write your own.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=38
That's an option we'll consider if a patch becomes available. Until then, does
anyone have any suspicion as to the cause or possible way around it?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3892098#3892098
Reply to the post :
http://www.jboss.org/ind
erik - when JBoss has a bug in it, it's fairly easy to come up with your
own patched .jar file and build a custom installation.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3891890#3891890
Reply to the post :
http://www.jboss.org/index.html?module=bb&o
I'm getting this in 4.0.2, only I can't find a workaround. In my case, two
conrete MDBs subclass an abstract one that contains the onMessage(), declared
public void onMessage(javax.jms.Message message)
To try to get around the validation error, I subclassed and had the conrete
classes call su
I believe this is what you want
|
| public abstract class myBeanBase implements MessageDriverBean,
MessageListener {
|
|public void ejbCreate() {}
|public void ejbRemove(){}
|public void setMessageDrivenContext(MessageDrivenContext ctx) {
| this.ctx = ctx;
Bug report raised, since the poster seems incapable of following basic
instructions
and I don't want my mail filling up with guess work:
http://jira.jboss.com/jira/browse/JBAS-1532
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3868111#3868111
Reply to the pos
Very interesting. I have found that the deployment problem has something to do
with the name of the abstract method I call on the concrete class from the
abstract class. In my example above, I use the onMessage(custom.Message
message) signature. That fails.
When I change the method name from
I too am having a similar problem. In the code example above, the ConcreteMDB
class contains an onMessage method that takes a javax.jms.TextMessage object.
In my case, I want the AbstractMDB to handle a javax.jms.ObjectMessage that
contains a non-JMS system message and pass that non-jms messag
The following testcase works fine for me:
| package org.jboss.test.cts.ejb;
|
| import javax.ejb.MessageDrivenBean;
| import javax.ejb.MessageDrivenContext;
| import javax.jms.MessageListener;
| import javax.jms.Message;
| import javax.jms.TextMessage;
|
| /** Test of signatur
12 matches
Mail list logo
