Hi David, Mark
I think for right now this would work fine - if Mark can validate that
the fixes does work as expected, and not break anything else. However in
the longer run, and to ensure that we could support MQ as well as
ActiveMQ and any other JMS implementation the best we can, it would make
sense for me and any others to get that copy installed. Hopefully, I
will not need Websphere, DB2 etc..etc.. to just get MQ running ;-)
thanks
asankha
David Illsley wrote:
Mark, Asankha,
I believe that developerworks does provide a free 90 day trial version
of WebSphere MQ [1]. Does that satisfy your needs?
Cheers,
David
[1]
http://www.ibm.com/developerworks/downloads/ws/wmq/?S_TACT=105AGX10&S_CMP=LP
On 18/06/07, Mark Badorrek <[EMAIL PROTECTED]> wrote:
Hi asankha,
As far as I know, IBM does not offer a free version of WebsphereMQ.
It's their flagship messaging product and they always collect on it.
Having said that, it is obviously in Axis2's interest to support
WebsphereMQ as it is one of two dominant messaging products in the
world today. More importantly, it is in IBM's interest to have Axis2
supporting WebsphereMQ.
I'm an IBM business partner so I obviously can't just send over a
copy, but I do note that there are quite a few Axis2 committers that
work for IBM - can they source a copy? If we can get a copy sent to
you I can certainly write up a quick one-page run-sheet outling how
to setup QueueManagers, Queues, Authorities etc to conduct a test.
Alternatively, in the meantime, if the changes are made, I can
confirm whether they succeeded or not. Is this sufficient or do you
wish to have this become a part of the standard regression test suite?
Unfortunately I'm having no end of trouble getting maven to behave
properly with our proxy so I can't build locally at the moment. :-(
Mark B
________________________________
From: Asankha C. Perera [mailto:[EMAIL PROTECTED]
Sent: Mon 6/18/2007 10:01 PM
To: axis-dev@ws.apache.org
Subject: Re: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ
doesn't support 'CLIENT' connections
Mark
Does WebSphere have a community edition (i.e. that does not require
the purchase of a license) that could be used to test this fix?
asankha
Mark Badorrek (JIRA) wrote:
[
https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Badorrek updated AXIS2-2816:
---------------------------------
Attachment: Axis2-websphereMQ-fix.zip
Can't test as I can't build Axis2 under maven at the moment.
If this is included in the nightly build I can run it through
a websphereMQ test.
Current functionality remains unchanged; there is no logical
or API modification.
The new functionality is only activated if the new parameters
are present in the JNDI tree.
JMS over WebsphereMQ doesn't support 'CLIENT'
connections
---------------------------------------------------------
Key: AXIS2-2816
URL:
https://issues.apache.org/jira/browse/AXIS2-2816
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.2
Environment: Tomcat 6, WindowsXP, WebsphereMQ
6.0
Reporter: Mark Badorrek
Attachments: Axis2-websphereMQ-fix.zip
Currently Axis2 can only connect withthe
factory.createConnection() method from the JMS API.
This is insufficient for WebspherMQ CLIENT
connections, where the administrator must nominate a particular
userID and password per connectionfactory, resulting in the following
call which is unsupported in the Axis2 JMS code:
factory.createConnection(userID, password)
The attached Axis2 JMS files contain the fix to allow
the deployer to specify a nominated userID and password through the
standard Axis2 JNDI lookup mechanism.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For
additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
