[jira] [Commented] (AXIS2-5067) content-type header is not generated with SAAJ API

[ https://issues.apache.org/jira/browse/AXIS2-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047031#comment-13047031 ] Ivan commented on AXIS2-5067: - A bit explanation for the patch a. From the JavaDoc of saveChan

[jira] [Updated] (AXIS2-5067) content-type header is not generated with SAAJ API

[ https://issues.apache.org/jira/browse/AXIS2-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated AXIS2-5067: Attachment: AXIS2-5067.patch Attach a patch for it, please help to review, thanks. > content-type header is not ge

[jira] [Commented] (AXIS2-4170) WSDL2JAVA for WSDL2.0 has CodeGenerationException/NullPointerException

[ https://issues.apache.org/jira/browse/AXIS2-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047017#comment-13047017 ] Ping Liu commented on AXIS2-4170: - This is a post comment to my previous comment on June 2

Re: [Axis2] wsdl to Java to wsdl to change style/use in initial WSDL?

Please help. On Thu, Jun 9, 2011 at 3:42 PM, fire fox wrote: > Hi all, > > -> I've created Java files using -ss -sd options using Axis2. > > -> I've used the skeleton class to create the WSDL from it. > > -> Apparently I've achieved what I've wanted, the binding style in the > wsdl changed from r

Re: Filtering MTOM attachments based on disposition file name and content type

I understand your point. All we are trying to do is satisfy some security audit black list, white list requirement. We just want accept the configured file extensions not everything. So,If can't get the file name through part content disposition then what would you recommend? Because, SOAP request

[jira] [Updated] (AXIS2-4517) AxisServlet error. NullPointerException and StackOverflowError

[ https://issues.apache.org/jira/browse/AXIS2-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4517: --- Fix Version/s: 1.6.0 > AxisServlet error. NullPointerException and StackOverflowError > -

Re: Filtering MTOM attachments based on disposition file name and content type

There is indeed no API to get access to the Content-Disposition header. There is a reason for this: MTOM actually defines an equivalency between plain SOAP messages and MIME messages, but the specification doesn't attach any meaning to the Content-Disposition MIME header. That means that when const

[jira] [Updated] (AXIS2-5068) Enable engaging addressing module to service level.

[ https://issues.apache.org/jira/browse/AXIS2-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shivendra tripathi updated AXIS2-5068: -- Issue Type: Bug (was: Improvement) > Enable engaging addressing module to service leve

Re: [VOTE][RAMPART] Release Rampart-1.6.0 - 2nd call

This vote has been active for more than 72 hours and there are six +1 binding votes and no -1 , 0 votes. I will continue with this release. Thanks ! On Thu, Jun 9, 2011 at 11:52 AM, Isuru Suriarachchi wrote: > +1 > Thanks, > ~Isuru > On Thu, Jun 9, 2011 at 10:03 AM, Thilina Mahesh Buddhika > wr

[jira] [Created] (AXIS2-5069) Configuration guide should clearly state the root elements and locations for axis2.xml services.xml and module.xml

Configuration guide should clearly state the root elements and locations for axis2.xml services.xml and module.xml -- Key: AXIS2-5069 URL: https://issu

[jira] [Created] (AXIS2-5068) Enable engaging addressing module to service level.

Enable engaging addressing module to service level. --- Key: AXIS2-5068 URL: https://issues.apache.org/jira/browse/AXIS2-5068 Project: Axis2 Issue Type: Improvement Components: Addres

Re: Filtering MTOM attachments based on disposition file name and content type

Swapna, Sure, I can write the module but when you say axis api what exactly you are referring to? We are on Aixs 2 (1.4) version and our org.apache.axiom.attachments.Attachments version doesn't even look into the "Content-Disposition: attachment; name=", at least I don't see anywhere. *Are you refe

[jira] [Created] (AXIS2-5067) content-type header is not generated with SAAJ API

content-type header is not generated with SAAJ API -- Key: AXIS2-5067 URL: https://issues.apache.org/jira/browse/AXIS2-5067 Project: Axis2 Issue Type: Bug Components: saaj Affects

[Axis2] wsdl to Java to wsdl to change style/use in initial WSDL?

Hi all, -> I've created Java files using -ss -sd options using Axis2. -> I've used the skeleton class to create the WSDL from it. -> Apparently I've achieved what I've wanted, the binding style in the wsdl changed from rpc/encoded [axis2 does not support] to doc/literal. But, I'm suspicious ab