On Jul 21, 2008, at 12:27 PM, David Blevins wrote:
On Jul 21, 2008, at 6:08 AM, Jacek Laskowski wrote:
On Mon, Jul 21, 2008 at 5:33 AM, David Blevins (JIRA) <[EMAIL PROTECTED]
> wrote:
Usage of Quartz quarts-ra.rar
-----------------------------
What is this for? I believe it's for Timer stuff, but am not quite
sure.
See this user list thread:
http://www.nabble.com/Re%3A-need-help-getting-quartz-ra.rar-file-to-deploy-p18561656.html
Been looking into this one for a couple days now and I'm discovering
some issues with out MDB code. Seems that our MDB activation config
and how that relates to matching the bean up with a container is not
right. Essentially, the code will only work if your ActivationSpec
supports the properties "destinationType" and "destinationName".
These are used in JMS. The TCK uses an ActivationSpec identical to
JMS so it never uncovered this issue. If your connector's
ActivationSpec does not support these two parameters we forcefully add
them to the MDBs ActivationConfig anyway. In short, in several places
whether you want it or not, we will hammer JMS-like config onto your
bean in few different places.
We need to do some major work on this code so that the auto-magic JMS-
related stuff is nicely contained and only executed when appropriate.
We really should also add some code to aggressively check the
ActivationSpec (allowed parameters) against the supplied
ActivationConfig (parameter values) and report clearly any and all
parameters not supported by the Connector. Going to have to add a
fake Connector impl of our own that has nothing in common with JMS so
that we can verify with more certainty that it will work for any
connector.
-David
