We already have the wrapper :-) Just add a new map. (Its up to you I was just
suggesting -- this is primarily a do-ocracy with excessive feedback from the troll
because he hasn't gotten to do much coding this week and is jealous :-) )
BTW I addded your mail account. Have fun.
View the
This one has been taking a long time for me to understand! :-)
Is what you mean that rather than having a wrapper around the Mail class with the
extra info, you would prefer to have this info contained in a separate transient
header class pointed to by the mail object itself?
I'll wait
lets not add a second wrapper, lets add something like transient header or something
to the existing objects.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3834795#3834795
Reply to the post :
I've made a few changes for retry. I went with the alternative implementation I
suggested since I got stuck with the JMS/DLQ stuff (Still not sure if it is possible).
If a mail fails for remote/local delivery the MDB puts it in a wrapper object and
calls JMSMailListener again.
The wrapper
He doesn't say, and not sure I dare ask :-) I'll look into it a bit more soon though.
If we have a container-transaction configured it works.
I'm more concerned about the delaying retries/keeping track of who the message has
been successfuly sent to.
View the original post :
So what exception does he think you're supposed to throw?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3833080#3833080
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3833080
Custom DLQ not a problem. I got that set that up.
The thing that brought me onto the EJBException/RuntimeException is that the message
was not retried until I added the container-tranaction bits to the MDB ejb-jar.xml.
According to Adrian/JMS spec, throwing RuntimeExceptions from onMessage is
Also, doesn't seem like throwing any exceptions is allowed from onMessage()
http://www.jboss.org/index.html?module=bbop=viewtopict=49010
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3832554#3832554
Reply to the post :
H,
I've got the basic framework down. If RemoteDeliveryMDB can't send to some of the
recipients it throws an EJBException causing it to retry. After the max number of
retries it gets placed on an alternative DLQ with another MDB at the end of it, which
is all well and good.
The problem
