[Axis2] Axis2, WebSphere 7 and Java2 security issues

Hi, I have to use WebSphere 7 and axis2 based application . However, this particular production environment has important security restrictions (I.e. not permitted* "createClassLoader"* and *"setContextClassLoader"*): I can't use own classloader (in this case axis2 classloader). Logically, I've g

[jira] [Commented] (AXIS-1753) All xs:choice members are non-nillable

[ https://issues.apache.org/jira/browse/AXIS-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013885#comment-13013885 ] Nebojsa Simic commented on AXIS-1753: - Great !! Change the name of the project and all

[jira] [Created] (AXIS2-4994) JSON formatter removes leading zeros if content of element is convertable to number

JSON formatter removes leading zeros if content of element is convertable to number --- Key: AXIS2-4994 URL: https://issues.apache.org/jira/browse/AXIS2-4994 Project: Axi

[jira] [Commented] (AXIS-1753) All xs:choice members are non-nillable

[ https://issues.apache.org/jira/browse/AXIS-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013913#comment-13013913 ] Andreas Veithen commented on AXIS-1753: --- Axis and Axis2 are two completely different

[jira] [Updated] (AXIS2-4994) JSON formatter removes leading zeros if content of element is convertable to number

[ https://issues.apache.org/jira/browse/AXIS2-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miyuru Wanninayaka updated AXIS2-4994: -- Attachment: AXIS2-4994.diff Patch for Axis2 trunk > JSON formatter removes leading zer

[jira] [Commented] (AXIS-1510) WSDL creates class that extends Object array

[ https://issues.apache.org/jira/browse/AXIS-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013941#comment-13013941 ] Frederic Giltay commented on AXIS-1510: --- Hello, I have a wsdl that generates the same

[jira] [Issue Comment Edited] (AXIS-1510) WSDL creates class that extends Object array

[ https://issues.apache.org/jira/browse/AXIS-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013941#comment-13013941 ] Frederic Giltay edited comment on AXIS-1510 at 3/31/11 12:15 PM:

[jira] [Commented] (AXIS-1510) WSDL creates class that extends Object array

[ https://issues.apache.org/jira/browse/AXIS-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013945#comment-13013945 ] Frederic Giltay commented on AXIS-1510: --- @Dominik Kacprzak : I found a difference bet

[jira] [Issue Comment Edited] (AXIS-1510) WSDL creates class that extends Object array

[ https://issues.apache.org/jira/browse/AXIS-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013941#comment-13013941 ] Frederic Giltay edited comment on AXIS-1510 at 3/31/11 12:23 PM:

[jira] [Commented] (AXIS2-4599) can not find type {http://schemas.xmlsoap.org/soap/encoding/}Array from the parent schema

[ https://issues.apache.org/jira/browse/AXIS2-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013963#comment-13013963 ] Frederic Giltay commented on AXIS2-4599: Too bad, I need that as well > can not

[jira] [Commented] (AXIS2-4992) Incorrect default requrest wrapper class name is used

[ https://issues.apache.org/jira/browse/AXIS2-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013998#comment-13013998 ] Jarek Gawor commented on AXIS2-4992: So if the purpose of this latest patch is to esse

[jira] [Commented] (AXIS2-4244) NullPointerException in generated Stub.

[ https://issues.apache.org/jira/browse/AXIS2-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014215#comment-13014215 ] Anish Pyne commented on AXIS2-4244: --- Which version of Axis2 has the fix? Or there is a w

[jira] [Resolved] (AXIS2-4992) Incorrect default requrest wrapper class name is used

[ https://issues.apache.org/jira/browse/AXIS2-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved AXIS2-4992. - Resolution: Invalid Thanks, Jarek, I found that my case is caused by other reasons, the codes here should be cor

[jira] [Commented] (AXIS2-4993) Throw JAXBException if the built JAXBContext from classes are not valid

[ https://issues.apache.org/jira/browse/AXIS2-4993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014383#comment-13014383 ] Ivan commented on AXIS2-4993: - I tried to read more Axis2 codes, and find that it might be req

[jira] [Updated] (AXIS2-4993) Throw JAXBException if the built JAXBContext from classes are not valid

[ https://issues.apache.org/jira/browse/AXIS2-4993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated AXIS2-4993: Attachment: AXIS-4993-01.patch > Throw JAXBException if the built JAXBContext from classes are not valid >

Re: SHA2 support

Hi Leos, SHA256 is not supported right now. I just checked the rampart code to verify this and seems like we are not using the digest value from the AlgorithmSuite available in the policy. Also asymmetricSignature in AlgorithmSuite is hard coded to http://www.w3.org/2000/09/xmldsig#rsa-sha1 This

Re: SHA2 support

2011/4/1 Ruchith Fernando : > Hi Leos, > > SHA256 is not supported right now. > > I just checked the rampart code to verify this and seems like we are > not using the digest value from the AlgorithmSuite available in the > policy. > > Also asymmetricSignature in AlgorithmSuite is hard coded to > ht

Re: SHA2 support

Hi Leoš, Here's a quick patch (on current trunk) to fix the issue for the most common case IMHO. There are several other cases to check where signature is constructed but feel free to use this if you need this immediately. I will do a through check and commit a more comprehensive fix if I find som

Re: SHA2 support

This is fixed on Rampart trunk now! Thanks, Ruchith 2011/4/1 Ruchith Fernando : > Hi Leoš, > > Here's a quick patch (on current trunk) to fix the issue for the most > common case IMHO. There are several other cases to check where > signature is constructed but feel free to use this if you need th