Issue with handling MTOM

Hi, We are receiving two elements from the SOAP response. The first element is MTOM that contains the base64Binary data. The second element is a simple String. I am using maven axis2-wsdl2code-maven-plugin to generate the java code from wsdl. The maven generate the below code snippet **

RE: Custom exceptions in axis2

Hi, You can catch a custom Exception in your service and from there throw you custom exception. Thanks, Swapna Soni. -Original Message- From: Denise Wu [mailto:wadie...@gmail.com] Sent: Thursday, May 26, 2011 9:56 PM To: java-dev@axis.apache.org; java-u...@axis.apache.org Subject: Cus

[jira] [Created] (AXIS2-5056) AxisFault exception(Server does not have an epr for the wsdl epr) is thrown when the protocal defined for EPR in original wsdl differs from the protocol defined in httpFr

AxisFault exception(Server does not have an epr for the wsdl epr) is thrown when the protocal defined for EPR in original wsdl differs from the protocol defined in httpFrontendHostUrl parameter in axis2.xml --

[jira] [Created] (AXIS2-5055) POJO Web Services using Apache Axis2 (Spring Sample Error)

POJO Web Services using Apache Axis2 (Spring Sample Error) -- Key: AXIS2-5055 URL: https://issues.apache.org/jira/browse/AXIS2-5055 Project: Axis2 Issue Type: Bug Components:

[jira] [Commented] (AXIS2-5043) Add a TransportListener to the Axis2 Local transport

[ https://issues.apache.org/jira/browse/AXIS2-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039913#comment-13039913 ] Andreas Veithen commented on AXIS2-5043: Doesn't the hardcoded "/services/" in the

Re: MIME Headers - Parsing Issues- AXIS2

Strict interpretation of the specs would actually suggest that a semicolon at the end of the content type is not valid. I think that RFC 2045 applies here, which defines the syntax of the Content-Type header as follows (see section 5.1): content := "Content-Type" ":" type "/" subtype

[jira] [Updated] (AXIS2-5049) Axis2 Services / ServiceGroups Not Updating Properly When doing Hot-Update with Transport Session

[ https://issues.apache.org/jira/browse/AXIS2-5049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anjana Fernando updated AXIS2-5049: --- Attachment: AXIS2-5049-Patch-2.txt Hi, There's a small issue in the previous patch (AXIS2-50

Custom exceptions in axis2

Hi, I created a custom exception on my server side but my client is always getting an AxisFault exception. Is there a way for the server to send instead the custom exception? Thanks for your help! - To unsubscribe, e-mail: java-

MIME Headers - Parsing Issues- AXIS2

AXIS2 Committors- It appears that there* may be* a bug in parsing MIME body parts. I have downloaded the source code and included additional logging. Please see the below details. Brief History: The first MIME header (Not Working) comes from ESB server which in turn invoked a web service on IIS

[jira] [Commented] (RAMPART-332) InvalidSecurity for first requests

[ https://issues.apache.org/jira/browse/RAMPART-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039712#comment-13039712 ] Oliver Rohr commented on RAMPART-332: - We have included a rampart-core patch in our s

[jira] [Issue Comment Edited] (RAMPART-332) InvalidSecurity for first requests

[ https://issues.apache.org/jira/browse/RAMPART-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039712#comment-13039712 ] Oliver Rohr edited comment on RAMPART-332 at 5/26/11 2:01 PM: -

Re: [Axis2] Axis2 1.1 and JDK 1.6

hi, AFAIK axis2 used to ship xml libs since default jdk shipped ones are not preferred. But with JDK 1.6 releases contains those libs by default. Cant figure out the exact error though. --Pradeep - To unsubscribe, e-mail: java-