[Axis2] Difference between mex-xxx.jar file and mex-xxx.mar file.

hi, It seems like both mex-xxx.jar and mex-xxx.mar files have the same content. Since mex-xxx.jar file contains a module.xml file it tries to deploy as a module when the server starts up. I think we need to remove module.xml part from the jar file. thanks, Amila. -- Amila Suriarachchi WSO2 Inc

[jira] Commented: (AXIS2-3970) Upgrade to Axis2 1.4 problem, WstxParsingException for null value properties,plz help me as soon as possible!! Thanks

[ https://issues.apache.org/jira/browse/AXIS2-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717425#action_12717425 ] Brandon Richins commented on AXIS2-3970: Experienced the same issue. I created a w

Axis2 and .NET client (ans webservice in SOAPSession)

Hi All, we have some webservices which can be consumed without problem by a .NET client. We have only a problems with a webservice which is defined a session=SOAPSession. Appareantly when a servicegroupid is generated and send back it is not picked-up by the .NET client. I thought Axis2 webser

Re: Axis2 and sticky sessions

Hi Deepal, thanks for the feedback. We do use clustering with Axis2 (which is working fine) but we can't get the LB correctly. So do you say that Axis2 and Apache LB do not work together and clustering is needed to 'correct' this problem (meaning to be sure that the session related data is copi

[jira] Updated: (AXIS2-4367) Parameter of type object is always passed as javax.activation.DataHandler

[ https://issues.apache.org/jira/browse/AXIS2-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pétur Runólfsson updated AXIS2-4367: Attachment: Server.wsdl Attached WSDL file generated by Axis2 when service is deployed. >

[jira] Created: (AXIS2-4367) Parameter of type object is always passed as javax.activation.DataHandler

Parameter of type object is always passed as javax.activation.DataHandler - Key: AXIS2-4367 URL: https://issues.apache.org/jira/browse/AXIS2-4367 Project: Axis 2.0 (Axis2)

[jira] Updated: (AXIS2-4367) Parameter of type object is always passed as javax.activation.DataHandler

[ https://issues.apache.org/jira/browse/AXIS2-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pétur Runólfsson updated AXIS2-4367: Attachment: Value.java Attached value type (maps to xsd:Value in the wsdl) > Parameter of

[jira] Updated: (AXIS2-4367) Parameter of type object is always passed as javax.activation.DataHandler

[ https://issues.apache.org/jira/browse/AXIS2-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pétur Runólfsson updated AXIS2-4367: Attachment: services.xml Attached services.xml used to deploy web service. > Parameter of

[jira] Updated: (AXIS2-4367) Parameter of type object is always passed as javax.activation.DataHandler

[ https://issues.apache.org/jira/browse/AXIS2-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pétur Runólfsson updated AXIS2-4367: Attachment: Server.java Attached web service used to trigger problem. > Parameter of type

[jira] Commented: (AXIS2-4362) If WSDL has multiple services, DeploymentEngine uses incorrect one

[ https://issues.apache.org/jira/browse/AXIS2-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717229#action_12717229 ] Ben Reif commented on AXIS2-4362: - They do match. That's what I mean, it's not looking at t

[jira] Updated: (AXIS2-4328) Please make RPCMessageReceiver and related classes more flexible

[ https://issues.apache.org/jira/browse/AXIS2-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pétur Runólfsson updated AXIS2-4328: Attachment: AXIS2-4328-1.patch OK, here's a starter. This converts all methods in RPCUtil f

[jira] Resolved: (AXIS2-4359) org.apache.axis2.AxisFault: Connection refused: connect

[ https://issues.apache.org/jira/browse/AXIS2-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-4359. Resolution: Invalid Resolving this issue because it is clearly a configuration issue and th

[jira] Closed: (AXIS2-4288) Support HttpState object association with a client and use it when invoking httpClient.executeMethod(...)

[ https://issues.apache.org/jira/browse/AXIS2-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov closed AXIS2-4288. > Support HttpState object association with a client and use it when invoking > httpClient.executeMeth

[jira] Resolved: (AXIS2-4288) Support HttpState object association with a client and use it when invoking httpClient.executeMethod(...)

[ https://issues.apache.org/jira/browse/AXIS2-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov resolved AXIS2-4288. -- Resolution: Fixed All patches and the documentation have been committed. > Support HttpState o