Some of the handlers could be easily made a part of axis, but the MBean that actually checks the email is fairly jboss specific, and it depends on the JBoss' mail service. also the authentication (xml digital signature) is somewhat JBossSX bound.
I certainly need to have this functionality in the client portion as well, but I took the more familiar (to me) route to get a server working.
Hopefully as I gain a more complete understanding of how all the parts work together I will be able to decouple some of the JBoss specific stuff.
It would certainly be nice to have an email transport as an integral part of axis, If you or anyone else can make suggestions on how to convert the jboss bound parts I will gladly write some code.
-jason
On Monday, November 18, 2002, at 11:43 AM, Steve Loughran wrote:
----- Original Message ----- From: "Jason Essington" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 18, 2002 7:07 AM Subject: Re: SOAP over SMTPHi ArulJason,
I am trying to build an email transport into jboss.net (the axis in
JBoss). There is already some code in cvs
(http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/contrib/
jboss.net/src/main/org/jboss/net/axis/mail/) the code that is there is
rather rough so far. I have to have message verification and
authentication via xml digital signatures working soon as well.
There are certainly huge gaps in this implementation as of yet. For
instance there isn't a way to send SOAP messages via email.
I could use comments / code from people who are interested in an email
transport or xml security (digital signatures and encryption) for SOAP.
why are you adding this to jboss rather than Axis itself? It would be a lot
better in Axis as then the clients would all support it too...
