I had some time to investigate this further, and I identified at least two issues that (may) explain the problems you describe: WSCOMMONS-467 and WSCOMMONS-468.
Andreas On Tue, Apr 14, 2009 at 00:00, Keith Bohnenberger <[email protected]> wrote: > At this point I'm a little lost on this thread but .... > > > >>>>> Why do you have >>>>> ..transport.jms.ConnectionFactory=cn=outgoingQueueFactory... ? i.e. why >>>>> =cn=..? > > The"cn=" was a typo and should not be there. I did try this with the > factory name that was in my axis2.xml file. > >>>>> >>>> >>>> I'm trying to use the connectionfactory that is set in the axis2.xml file >>>> in >>>> the "JMSSender" section. Similar to how the jms proxy uses the connection >>>> factory in the JMSListener for listening to the queue. >>>> >>> >>> To do this, define one or more connection factories in the sender as >>> follows.. the names does not really matter, as you *must* continue to >>> provide the full address URL when sending to a destination. Internally the >>> sender will check if a CF is defined, and if so use it as appropriate >> >> That is actually not true: you can refer to a connection factory >> definition in axis2.xml explicitly using the >> transport.jms.ConnectionFactory parameter. >> > > In the SNAPSHOT that I have, it is true that you can refer to a connection > factory definition in axi2.xml explicitly. However, if you don't set the > other parameters as well you get an error when you bring up Synapse and your > mediator doesn't deploy. I can't remember if you have to set all of the > params shown in sample 251 but having only the following set does not work: > <address uri="jms:/myDest?transport.jms.ConnectionFactory=myConnFact"/> > Even though I had the "myConnFact" in the axis2.xml file, this alone would > not deploy because it complained that I needed the other params set at well. > > With both the connection factory explicitly set and the other params I had > to set to get passed the deployment error, I ran into the same JNDI > connection problems that I was running into with the > connectionfactoryjndiname set as a param. > > > > > > > This communication, along with any attachments, is covered by federal and > state law governing electronic communications and may contain company > proprietary and legally privileged information. > If the reader of this message is not the intended recipient, you are hereby > notified that any dissemination, distribution, use or copying of this message > is strictly prohibited. > If you have received this in error, please reply immediately to the sender > and delete this message. Thank you. > >
