[JBoss-user] [Messaging, JMS JBossMQ] - Re: MDB extends base class: Verification of Enterprise Beans
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 setMessageDrivenContext(MessageDrivenContext context)
throws EJBException
| {
| this.context = context;
| }
|
| public void ejbRemove() throws EJBException
| {
| }
|
| public void ejbCreate() throws EJBException
| {
| }
|
| }
|
My subclass implements the BaseMessageBean and onMessage(Message m) correctly
| public class ReportSchedulerBean extends BaseMessageBean
| implements MessageDrivenBean, MessageListener
| {
| public void onMessage(Message message)
| {
|// stuff happens here
| }
|
| }
|
But I still get the spec violation stack.
14:56:07,578 WARN [verifier] EJB spec violation:
Bean : ReportSchedulerListener
Section: 15.7.4
Warning: The message driven bean must declare one onMessage() method.
I'm running
Jboss 4.0.3SP1,
Java 1.5.0_06-b05
This worked on 4.0.1sp1
Thoughts?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3931439#3931439
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3931439
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS JBossMQ] - Re: MDB extends base class: Verification of Enterprise Beans
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 EARs they communicated with. Our only isolated EARs today in 4.0.2 are those that don't contain MDBs and don't communicate via RMI to ears containing them, or any other unisolated ear. The suspicion I have, but haven't had the time to prove, yet, is that unless the container itself is configured for J2EE compliance the ears containing MDBs can have this problem. It is possibly related to a classpath issue, because during deploy I noticed that the classpath can be different than at runtime. This isn't the only issue where deployment errors were related to classpath issues that wouldn't have arisen if the EAR was isolated, or because the deployment classpath was different than the runtime classpath. I know this is a vague explanation, and could be proven wrong, but it has explained our behavior and guided our decisions about which ears to isolate until we have the time to convert all our applications into a J2EE compliant state. Ask yourself these questions: 1. Is our container configured for J2EE compliance? I forgot the exact settings, but one is jboss-service.xml/...NamingService/CallByValue. 2. Is your application containing the MDB isolated if your container is not? This setting is in jboss-app.xml for EARs and jboss-web.xml for WARs. In our configuration, we did not get the error when both 1 and 2 were false. In the end, 1 isn't an option for us without code changes due to reliance on a hibernate2 sar, and that change isn't on the project plan yet, so we put off isolating most of our EARs for this release. I suspect that if 1 and 2 are true, you may not get the error either. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3931469#3931469 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3931469 --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS JBossMQ] - Re: MDB extends base class: Verification of Enterprise Beans
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 Logger logger =
Logger.getLogger(SubscriberTxBean.class.getName());
| private static final String subscriberName = local/SubscriberTxBean;
|
| String getSubscriberName()
| {
| return subscriberName;
| }
|
| public void setMessageDrivenContext(
| MessageDrivenContext messageDrivenContext) throws EJBException {
}
|
| public void ejbRemove() {}
|
| public void onMessage(Message message) {
| logger.info(Processing message!);
| }
|
| public void ejbCreate() {}
|
| String getBinding()
| {
| return singleton-message-driven-bean;
| }
|
anonymous wrote : 12:19:19,486 WARN [verifier] EJB spec violation:
| Bean : SubscriberTxBean
| Section: 15.7.4
| Warning: The message driven bean must declare one onMessage() method.
|
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3892267#3892267
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3892267
---
SF.Net email is Sponsored by the Better Software Conference EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile Plan-Driven Development * Managing Projects Teams * Testing QA
Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS JBossMQ] - Re: MDB extends base class: Verification of Enterprise Beans
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=bbop=viewtopicp=3892098#3892098 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3892098 --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS JBossMQ] - Re: MDB extends base class: Verification of Enterprise Beans
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=bbop=viewtopicp=3892179#3892179 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3892179 --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS JBossMQ] - Re: MDB extends base class: Verification of Enterprise Beans
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=bbop=viewtopicp=3891890#3891890 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3891890 --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS JBossMQ] - Re: MDB extends base class: Verification of Enterprise Beans
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 super:
public void onMessage(Message message) {
| super.onMessage(message);
| }
I'm really confused why this doesn't work. I can understand a bug that can't
find the method signature via the parent class; but not one that's clearly
defined in the concrete classes as well.
Is there a fix? Is there a way I can work around this until we can upgrade?
We just spent a month upgrading to 4.0.2 from 3.2.7, so 4.0.3 probably won't be
an option this year.
Erik
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3891878#3891878
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3891878
---
SF.Net email is Sponsored by the Better Software Conference EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile Plan-Driven Development * Managing Projects Teams * Testing QA
Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS JBossMQ] - Re: MDB extends base class: Verification of Enterprise Beans
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;
|}
|
|public void onMessage(Message msg){
| handleMessage(new myMessageWrapper(msg));
|}
|
|protected abstract void handleMessage(myMessageWrapper msg);
|
| }
|
So now you bean code dont have to import any of the javax.jms.* stuff when it
extends the base class as long as your myMessageWrapper class can provide all
the appropriate gettor/settor methods for processing. Cheers.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3868172#3868172
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3868172
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS JBossMQ] - Re: MDB extends base class: Verification of Enterprise Beans
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 message to the
ConcreteMDB class via an abstract call. See code below:
public abstract class AbstractMDB implements MessageListener, MessageDrivenBean
{
public abstract onMessage(custom.Message message);
public void onMessage(Message message)
{
if( message instanceof ObjectMessage )
{
// convert to message
ObjectMessage om = (ObjectMessage) message;
// pull out our custom message
custom.Message m = (custom.Message)om.getObject();
// pass this message to the concrete class
this.onMessage(m);
}
}
public void setMessageDrivenContext(MessageDrivenContext ctx)
{
}
public void ejbCreate()
{
}
public void ejbRemove()
{
}
}
public class ConcreteMDB extends AbstractMDB
{
public void onMessage(custom.Message m)
{
System.out.println(ConcreteMDB: + m);
}
}
when i deploy the ConcreteMDB, I get The message driven bean must declare one
onMessage() method.. But from a code perspective, I do not want to let the
concrete bean know it is an mdb and do not want javax.jms.* in it at all. I
want that decision to be a deployment decision.
Ideas?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3868102#3868102
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3868102
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS JBossMQ] - Re: MDB extends base class: Verification of Enterprise Beans
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 onMessage to process, it deploys fine.
Changing it to onMessage2 still did not work. So what is the deal? Why
should the name of the method matter when the parameter is different?
This works:
public class ConcreteMDB extends AbstractMDB
{
public void process(custom.Message m)
{
System.out.println(ConcreteMDB: + m);
}
}
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3868106#3868106
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3868106
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS JBossMQ] - Re: MDB extends base class: Verification of Enterprise Beans
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=bbop=viewtopicp=3868111#3868111 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3868111 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS JBossMQ] - Re: MDB extends base class: Verification of Enterprise Beans
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 signature validation across inheritence hiearchy
| *
| * @author [EMAIL PROTECTED]
| * @version $Revision:$
| */
| public abstract class AbstractMDB implements MessageListener,
MessageDrivenBean
| {
|public void onMessage(Message message)
|{
| if( message instanceof TextMessage )
| {
| TextMessage tm = (TextMessage) message;
| onTextMessage(tm);
| }
|}
|
|public void setMessageDrivenContext(MessageDrivenContext ctx)
|{
|}
|
|public void ejbCreate()
|{
|}
|
|public void ejbRemove()
|{
|}
|
|public abstract void onTextMessage(TextMessage tm);
| }
|
| package org.jboss.test.cts.ejb;
|
| import javax.jms.TextMessage;
|
| /**
| * @author [EMAIL PROTECTED]
| * @version $Revision:$
| */
| public class ConcreteMDB extends AbstractMDB
| {
|public void onTextMessage(TextMessage tm)
|{
| System.out.println(ConcreteMDB: +tm);
|}
| }
|
Submit a bug report with an example that is failing to:
http://jira.jboss.com/jira/browse/JBAS
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3859853#3859853
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859853
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
