[jira] [Commented] (AXIS2-5039) Override the SOAPAction from the SOAPMessage MIME header if it is explicitly configured later

[ https://issues.apache.org/jira/browse/AXIS2-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035954#comment-13035954 ] Ivan commented on AXIS2-5039: - Just update a new patch and a case to reproduce this issue. In

[jira] [Updated] (AXIS2-5039) Override the SOAPAction from the SOAPMessage MIME header if it is explicitly configured later

[ https://issues.apache.org/jira/browse/AXIS2-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated AXIS2-5039: Attachment: (was: AXIS2-5039.patch) > Override the SOAPAction from the SOAPMessage MIME header if it is explici

[jira] [Updated] (AXIS2-5039) Override the SOAPAction from the SOAPMessage MIME header if it is explicitly configured later

[ https://issues.apache.org/jira/browse/AXIS2-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated AXIS2-5039: Attachment: AXIS2-5039-Test.patch AXIS2-5039.patch Update a new patch and a case for it. > Overrid

Re: AXIS2 with MTOM issue.

Thanks Andreas. I will pursue that option. Meanwhile, do you see any other leads causing this issue? Does the response has to have a base64Binary element? Is it possible to restrict MTOM to only request and not the response? Appreciate if you can answer these questions. Thanks Anil Atyam Ph:

Re: AXIS2 with MTOM issue.

We don't provide support for commercial products based on Axis2. You should use the correct channels for this, i.e open a PMR with IBM support. Andreas On Wed, May 18, 2011 at 22:29, Anil Atyam wrote: > Thanks Andreas for the response. We are using IBM WebSphere application > server version 7.0

Re: AXIS2 with MTOM issue.

Thanks Andreas for the response. We are using IBM WebSphere application server version 7.0 with latest fix packs. So, I assume IBM using latest and greatest AXIS2 and AXIOM. If not the greatest, they must be using 1.2.8. I have tried my best to locate the information and couldn't find it. I am pas

Re: Missing typeof "duration" in class org.apache.axis2.databinding.types.Union

Yes, this indeed looks like a bug and is still present in the current version of the code. Please open a JIRA report [1] for this issue. Andreas [1] https://issues.apache.org/jira/browse/AXIS2 On Wed, May 18, 2011 at 14:27, Juan Angel Fuentes Dominguez wrote: > Hello, > > I'm new in the list so

Re: AXIS2 with MTOM issue.

On Wed, May 18, 2011 at 19:19, Anil Atyam wrote: > Folks > > I appreciate if you can help with the following issue we are struggling to > resolve. > > We @ National Rail Road Corporation implementing a solution where we send > Itinerary as PDF attachment to the passenger's email. To do so, we are

Re: Bug in JAXWSDeployer.java (Axis2 1.5.4)

This has already been fixed and is scheduled for inclusion in Axis2 1.6.0: https://issues.apache.org/jira/browse/AXIS2-4326 Andreas On Wed, May 18, 2011 at 20:27, Ferdinand Niedermann wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello > > I believe I may have found a bug in Axis

Bug in JAXWSDeployer.java (Axis2 1.5.4)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello I believe I may have found a bug in Axis2. In JAXWSDeployer.java in the method protected ArrayList getListOfClasses(DeploymentFileData deploymentFileData): The line name = name.replaceAll(".class", ""); needs to be replaced with name = name.

AXIS2 with MTOM issue.

Folks I appreciate if you can help with the following issue we are struggling to resolve. We @ National Rail Road Corporation implementing a solution where we send Itinerary as PDF attachment to the passenger's email. To do so, we are using MTOM enabled Web Service which sends to request to a thi

Re: RESTful webservice and session management

>> Please go and have a look if REST supports WS Addressing! Well according to axis2 developers it does, there is even an example in the axis2 distribution under \axis2-1.5.4\samples\userguide\src\userguide\clients\RESTClient.java with the following lines of code: options.setTransportIn

[jira] [Created] (AXIS2-5047) For provider-based endpoints with WSDLs using xsd:import, schemaLocation of imported xsd does not resolve correctly

For provider-based endpoints with WSDLs using xsd:import, schemaLocation of imported xsd does not resolve correctly --- Key: AXIS2-5047 URL: https://is

Trouble with sts client and usernametoken

I am trying to get the rampart sts policy sample 05 to use a usernametoken and I have added the following in my sts_policy.xml file http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";> http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient"; />

AW: RESTful webservice and session management

Please go and have a look if REST supports WS Addressing! I think REST was developed with the idea of a pritty small SOAP XML Protocoll and hence every thing adding to it is against REST. Josef -sombody more known-to-the-subject to comment please. -Ursprüngliche Nachricht- Von: Denise Wu

Missing typeof "duration" in class org.apache.axis2.databinding.types.Union

Hello, I'm new in the list so I'll try to do my best. I'm using axis2 1.5.4, but I also tried this with the last snapshot of version 1.5.5. I think there' s a missing typeof in class org.apache.axis2.databinding.types.Union I'm trying to use this type in my webservice:

Stub generated using Axis2 is unable to Maintain session between RESTful service and Client

Hi, I created a webservice and enabled session management on both server and client. It works FINE until I enable REST on the client by adding the 3rd line of code in the serviceStub.java. The session management stops working. // add session management _serviceClient.getOptions().setManageSession