Re: [Axis2] SimpleMailListener denys SOAP11 content-ype
This[1] may also help you. Regarding Axis2 1.5 release, there was a discussion but not much progress. But definitely it will shift with the new transports. Thanks, Amila. [1] http://amilachinthaka.blogspot.com/2008/09/using-ws-commons-mail-transport-with.html On Fri, Nov 21, 2008 at 1:28 AM, [EMAIL PROTECTED] wrote: Hello, we would like to use the mail transport implementation as included with Apache Synapse in combination with Axis2 1.4.1 (see message below). Now I have learned that recent changes to this implementation have been moved to a new ws_commons project for transports. Therefore, my questions are: - Will the mail transport implementation from ws_commons be available with Axis2 1.5? - If yes, when is version 1.5 of Axis2 due to be released? - Will mail transport still be restricted to SOAP 1.2 as with the current implementation in Axis2 1.4.1? Thanks for your help! Kind regards, Matthias -- *Von:* Asankha C. Perera [mailto:[EMAIL PROTECTED] *Gesendet:* Donnerstag, 29. Mai 2008 08:40 *An:* [EMAIL PROTECTED] *Betreff:* Re: [Axis2 1.3] SimpleMailListener denys SOAP11 content-ype Christopher You can try the Mail transport implementation we have developed for Apache Synapse. This can be made to replace the Axis2 Mail transport, but dropping the JAR file [1] into your lib directory, and updating your axis2.xml as follows: [1] http://repo1.maven.org/maven2/org/apache/synapse/synapse-transports/1.1.2/synapse-transports-1.1.2.jar transportReceiver name=mailto class=org.apache.synapse.transport.mail.MailTransportListener !-- configure any optional POP3/IMAP properties check com.sun.mail.pop3 and com.sun.mail.imap package documentation for more details-- /transportReceiver !-- Uncomment and configure the SMTP server information check com.sun.mail.smtp package documentation for descriptions of properties transportSender name=mailto class=org.apache.synapse.transport.mail.MailTransportSender parameter name=mail.smtp.hostsmtp.gmail.com/parameter parameter name=mail.smtp.port587/parameter parameter name=mail.smtp.starttls.enabletrue/parameter parameter name=mail.smtp.authtrue/parameter parameter name=mail.smtp.usersynapse.demo.0/parameter parameter name=mail.smtp.passwordmailpassword/parameter parameter name=mail.smtp.from[EMAIL PROTECTED] /parameter /transportSender-- Now for each of your services, you can configure the mail properties on the services.xml using the following properties: e.g. parameter name=transport.mail.Address[EMAIL PROTECTED]/parameter parameter name=transport.mail.Protocolpop3/parameter parameter name=transport.PollInterval5/parameter parameter name=mail.pop3.hostpop.gmail.com/parameter parameter name=mail.pop3.port995/parameter parameter name=mail.pop3.usersynapse.demo.1/parameter parameter name=mail.pop3.passwordmailpassword/parameter parameter name=mail.pop3.socketFactory.classjavax.net.ssl.SSLSocketFactory/parameter parameter name=mail.pop3.socketFactory.fallbackfalse/parameter parameter name=mail.pop3.socketFactory.port995/parameter With the new mail transport, you can have multiple services listening on different email accounts with their own separate polling schedules etc.. and message can be within the body, an attachment etc, and the subject can be changed, or copies CC, BCC'ed etc.. This documentation is still not in a good format, but you can refer to the codehttp://svn.apache.org/viewvc/synapse/trunk/java/modules/transports/src/main/java/org/apache/synapse/transport/mail/and the Synapse samples http://synapse.apache.org for a better understanding. asankha [EMAIL PROTECTED] wrote: Hi Team, I have to send my SOAP-messages with SOAP11. But the server does not accept mails with the content-type text/xml: [ERROR] According to the mail sepec, mail transport should support only application/soap+xml [ERROR] Error in SimpleMailListener - processing mail org.apache.axis2.AxisFault: According to the mail sepec, mail transport should support only application/soap+xml at org.apache.axis2.transport.mail.SimpleMailListener.buildSOAPEnvelope(SimpleMailListener.java:470) ... Unfortunately this check is hardcoded into the SimpleMailListener: if (contentType.indexOf(SOAP12Constants.SOAP_12_CONTENT_TYPE) -1) { TransportUtils .processContentTypeForAction(contentType, msgContext); } else {... Is there any way around or did I simply miss some property to be set? Thanks for helping, Christopher - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL
Re: [Axis2] SimpleMailListener denys SOAP11 content-ype
Hello, we would like to use the mail transport implementation as included with Apache Synapse in combination with Axis2 1.4.1 (see message below). Now I have learned that recent changes to this implementation have been moved to a new ws_commons project for transports. Therefore, my questions are: * Will the mail transport implementation from ws_commons be available with Axis2 1.5? * If yes, when is version 1.5 of Axis2 due to be released? * Will mail transport still be restricted to SOAP 1.2 as with the current implementation in Axis2 1.4.1? Thanks for your help! Kind regards, Matthias Von: Asankha C. Perera [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 29. Mai 2008 08:40 An: [EMAIL PROTECTED] Betreff: Re: [Axis2 1.3] SimpleMailListener denys SOAP11 content-ype Christopher You can try the Mail transport implementation we have developed for Apache Synapse. This can be made to replace the Axis2 Mail transport, but dropping the JAR file [1] into your lib directory, and updating your axis2.xml as follows: [1] http://repo1.maven.org/maven2/org/apache/synapse/synapse-transports/1.1.2/synapse-transports-1.1.2.jar transportReceiver name=mailto class=org.apache.synapse.transport.mail.MailTransportListener !-- configure any optional POP3/IMAP properties check com.sun.mail.pop3 and com.sun.mail.imap package documentation for more details-- /transportReceiver !-- Uncomment and configure the SMTP server information check com.sun.mail.smtp package documentation for descriptions of properties transportSender name=mailto class=org.apache.synapse.transport.mail.MailTransportSender parameter name=mail.smtp.hostsmtp.gmail.com/parameter parameter name=mail.smtp.port587/parameter parameter name=mail.smtp.starttls.enabletrue/parameter parameter name=mail.smtp.authtrue/parameter parameter name=mail.smtp.usersynapse.demo.0/parameter parameter name=mail.smtp.passwordmailpassword/parameter parameter name=mail.smtp.from[EMAIL PROTECTED]/parameter /transportSender-- Now for each of your services, you can configure the mail properties on the services.xml using the following properties: e.g. parameter name=transport.mail.Address[EMAIL PROTECTED]/parameter parameter name=transport.mail.Protocolpop3/parameter parameter name=transport.PollInterval5/parameter parameter name=mail.pop3.hostpop.gmail.com/parameter parameter name=mail.pop3.port995/parameter parameter name=mail.pop3.usersynapse.demo.1/parameter parameter name=mail.pop3.passwordmailpassword/parameter parameter name=mail.pop3.socketFactory.classjavax.net.ssl.SSLSocketFactory/parameter parameter name=mail.pop3.socketFactory.fallbackfalse/parameter parameter name=mail.pop3.socketFactory.port995/parameter With the new mail transport, you can have multiple services listening on different email accounts with their own separate polling schedules etc.. and message can be within the body, an attachment etc, and the subject can be changed, or copies CC, BCC'ed etc.. This documentation is still not in a good format, but you can refer to the code http://svn.apache.org/viewvc/synapse/trunk/java/modules/transports/src/main/java/org/apache/synapse/transport/mail/ and the Synapse samples http://synapse.apache.org for a better understanding. asankha [EMAIL PROTECTED] wrote: Hi Team, I have to send my SOAP-messages with SOAP11. But the server does not accept mails with the content-type text/xml: [ERROR] According to the mail sepec, mail transport should support only application/soap+xml [ERROR] Error in SimpleMailListener - processing mail org.apache.axis2.AxisFault: According to the mail sepec, mail transport should support only application/soap+xml at org.apache.axis2.transport.mail.SimpleMailListener.buildSOAPEnvelope(SimpleMailListener.java:470) ... Unfortunately this check is hardcoded into the SimpleMailListener: if (contentType.indexOf(SOAP12Constants.SOAP_12_CONTENT_TYPE) -1) { TransportUtils .processContentTypeForAction(contentType, msgContext); } else {... Is there any way around or did I simply miss some property to be set? Thanks for helping, Christopher - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] SimpleMailListener denys SOAP11 content-ype
Matthias, It is expected that Axis2 1.5 will be bundled with a release of the transports from WS-Commons. The current code no longer has a restriction on the content type and is tested with SOAP 1.1. Andreas On Thu, Nov 20, 2008 at 20:58, [EMAIL PROTECTED] wrote: Hello, we would like to use the mail transport implementation as included with Apache Synapse in combination with Axis2 1.4.1 (see message below). Now I have learned that recent changes to this implementation have been moved to a new ws_commons project for transports. Therefore, my questions are: Will the mail transport implementation from ws_commons be available with Axis2 1.5? If yes, when is version 1.5 of Axis2 due to be released? Will mail transport still be restricted to SOAP 1.2 as with the current implementation in Axis2 1.4.1? Thanks for your help! Kind regards, Matthias Von: Asankha C. Perera [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 29. Mai 2008 08:40 An: [EMAIL PROTECTED] Betreff: Re: [Axis2 1.3] SimpleMailListener denys SOAP11 content-ype Christopher You can try the Mail transport implementation we have developed for Apache Synapse. This can be made to replace the Axis2 Mail transport, but dropping the JAR file [1] into your lib directory, and updating your axis2.xml as follows: [1] http://repo1.maven.org/maven2/org/apache/synapse/synapse-transports/1.1.2/synapse-transports-1.1.2.jar transportReceiver name=mailto class=org.apache.synapse.transport.mail.MailTransportListener !-- configure any optional POP3/IMAP properties check com.sun.mail.pop3 and com.sun.mail.imap package documentation for more details-- /transportReceiver !-- Uncomment and configure the SMTP server information check com.sun.mail.smtp package documentation for descriptions of properties transportSender name=mailto class=org.apache.synapse.transport.mail.MailTransportSender parameter name=mail.smtp.hostsmtp.gmail.com/parameter parameter name=mail.smtp.port587/parameter parameter name=mail.smtp.starttls.enabletrue/parameter parameter name=mail.smtp.authtrue/parameter parameter name=mail.smtp.usersynapse.demo.0/parameter parameter name=mail.smtp.passwordmailpassword/parameter parameter name=mail.smtp.from[EMAIL PROTECTED]/parameter /transportSender-- Now for each of your services, you can configure the mail properties on the services.xml using the following properties: e.g. parameter name=transport.mail.Address[EMAIL PROTECTED]/parameter parameter name=transport.mail.Protocolpop3/parameter parameter name=transport.PollInterval5/parameter parameter name=mail.pop3.hostpop.gmail.com/parameter parameter name=mail.pop3.port995/parameter parameter name=mail.pop3.usersynapse.demo.1/parameter parameter name=mail.pop3.passwordmailpassword/parameter parameter name=mail.pop3.socketFactory.classjavax.net.ssl.SSLSocketFactory/parameter parameter name=mail.pop3.socketFactory.fallbackfalse/parameter parameter name=mail.pop3.socketFactory.port995/parameter With the new mail transport, you can have multiple services listening on different email accounts with their own separate polling schedules etc.. and message can be within the body, an attachment etc, and the subject can be changed, or copies CC, BCC'ed etc.. This documentation is still not in a good format, but you can refer to the code and the Synapse samples for a better understanding. asankha [EMAIL PROTECTED] wrote: Hi Team, I have to send my SOAP-messages with SOAP11. But the server does not accept mails with the content-type text/xml: [ERROR] According to the mail sepec, mail transport should support only application/soap+xml [ERROR] Error in SimpleMailListener - processing mail org.apache.axis2.AxisFault: According to the mail sepec, mail transport should support only application/soap+xml at org.apache.axis2.transport.mail.SimpleMailListener.buildSOAPEnvelope(SimpleMailListener.java:470) ... Unfortunately this check is hardcoded into the SimpleMailListener: if (contentType.indexOf(SOAP12Constants.SOAP_12_CONTENT_TYPE) -1) { TransportUtils .processContentTypeForAction(contentType, msgContext); } else {... Is there any way around or did I simply miss some property to be set? Thanks for helping, Christopher - 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]