Same handler inserted in two places
---
Key: AXIS2C-1294
URL: https://issues.apache.org/jira/browse/AXIS2C-1294
Project: Axis2-C
Issue Type: Bug
Components: core/phaseresolver
Environment:
In oder to support JTA transactions in synapse, I'm working on changing axis2
configuration (axis2.xml) to support following new transaction manager
definition.
transactionManager
parameter name=stringtext/parameter*
/transactionManager
Example,
transactionManager
parameter
[
https://issues.apache.org/jira/browse/AXIS2-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-4134.
-
Resolution: Fixed
fixed in svn revision 718571.
thanks Lizet.
-- dims
JAXWS has
[
https://issues.apache.org/jira/browse/AXIS2-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frank Bitzer closed AXIS2-4076.
---
Resolution: Fixed
Content-Type not parsed correctly in MTOM SOAP 1.2 messages
[
https://issues.apache.org/jira/browse/AXIS2-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12648730#action_12648730
]
Frank Bitzer commented on AXIS2-4076:
-
Well, after a lot of testing and debugging I
Asankha,
Please check in ONLY if the new MIME4J dependent code is in another
maven module.
thanks,
dims
On Tue, Nov 18, 2008 at 9:46 PM, Asankha C. Perera [EMAIL PROTECTED] wrote:
Hi all
Last night I noticed that the patch contributed by Oleg for better MIME
parsing [1] has not yet been