The problem is not transferring SOME "VALUE" once it is decided, but
agreeing on what "VALUE" to use. I mean a URI or a mail address [which
is a bit problematic as I mentioned earlier.] or some thing else. Please
note that I am only speaking with respect to the mail transport since
the URI option seems to be working ok in the HTTP case.
Best Regards,
Chamil Thanthrimudalige.
Chathura Herath wrote:
Well a simpler solution would be to use the Subject to transfer the
SOAPAction :-)
Chathura
-----Original Message-----
From: Eran Chinthaka [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 17, 2005 3:30 PM
To: axis-dev@ws.apache.org
Subject: RE: [Axis2] REQUEST_URI in mail transport
Hi Chamil,
hi all,
Well let me start by telling how I have setup the mail transport code
for the time being. [Currently working on a maillet that can work with
James.]
There is a poling thread that listens to a specified mail address and
when a mail comes to that address it will be fetched; broken down; MC
made and this MC will be used to call the engine.receive(MC) method.
My problem is that since it is required to set a REQUEST_URI (which will
be used to find out the service that should be called) before calling
engine.receive(MC), what can I use to set this?
IMO, Service identification must be done through the SOAPAction found in
the
mime header, at the transport level. This is the same done even in Axis
1.x.
mimeMessage.getHeader("SOAPAction") will give you that. Get the SOAPAction
from that and use that to set the SOAPAction in
MessageInformationHeaderCollection of the message context.
Regards,
Eran Chinthaka
Using the email address might cause a problem because then for different
services the mail listener will have to listen to many email address.
Before the current change I set the service using a value stored on the
mail header.
Best Regards,
Chamil Thanthrimudalige.
