I have been unable to get into JIRA this afternoon to log this, maybe
someone can confirm if this would be considered a bug:

I made it past the first setup problems and got my WebSphere application
successfully retrieving the QueueConnectionFactory from JNDI, for a
SOAP/JMS implementation.  However, I then ran into a problem when I
discovered that the org.apache.axis.transport.jms.JMSConnector class is
calling the setExceptionListener method on a Connector.

As documented in the links below, this is not J2EE compliant, and WebSphere
does not allow calls to this method; this brings my attempt to place a
message on a queue to a halt.

http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tmj_desap.html

http://www.devwebsphere.com/devwebsphere/2003/11/why_are_jms_api.html

Apparently, no one had recently tried to run this in WebSphere...

Fortunately for me, Apache distributes the source code, so I'm able to
identify the problem and can modify the code to get past this for my own
application.  It would be nice if future releases of Axis could possibly
cease using this method?  Or at least, catch the IllegalStateException that
is thrown by WebSphere and continue without completely failing...

Thanks,

Meghan

_________________________________
Meghan Pietila
Java Middleware Architect
Sales & Service Management Program
US Bank
Gold 4
(651) 205-0904
(651) 271-2815 cell
[EMAIL PROTECTED]


------------------------------------------------------------------------------
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==============================================================================

Reply via email to