[jira] Created: (AXIS2-4976) Axis2 wsdl2code code generation bug caused by "localName"

Axis2 wsdl2code code generation bug caused by "localName" - Key: AXIS2-4976 URL: https://issues.apache.org/jira/browse/AXIS2-4976 Project: Axis2 Issue Type: Bug Components: co

[jira] Commented: (AXIS2-3337) Problem with soap:address location in the WSDL (IP Address is not a public IP that is accessible from Internet).

[ https://issues.apache.org/jira/browse/AXIS2-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005580#comment-13005580 ] Denis Nelubin commented on AXIS2-3337: -- The parameter "hostname" defines the IP addre

Build failed in Jenkins: Axis2 #673

See Changes: [azeez] 1. Enabled channel heartbeat 2. Synchronizing channel send since otherwise it causes failures at Tribes level -- Started by an SCM change Building remotely on ubuntu2 Updating ht

[jira] Commented: (RAMPART-216) Wrong SignatureMethod and DigestMethod generated in request in case of algoritm suite having SHA256 hashing algorithm (example: Basic256Sha256)

[ https://issues.apache.org/jira/browse/RAMPART-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005626#comment-13005626 ] Leos Literak commented on RAMPART-216: -- Could you please resolve this issue? A gover

SHA2 support

Hello, I wonder whether Rampart supports SHA2 digest algorithm. It has been some time since SHA2 started to be preferred over SHA1 and it has been pushed by legislative process in European union. So I assume that many people must use it regularly. Though we face same issue as described in RAMPA

RE: SHA2 support

the currently supported (Rampart) Digest Algorithms are: contents of org.apache.ws.secpolicy.SPConstants: public final static String SHA1 = "http://www.w3.org/2000/09/xmldsig#sha1";; public final static String SHA256 = "http://www.w3.org/2001/04/xmlenc#sha256";; public final static

[jira] Created: (RAMPART-329) Interoperability with WSIT problem: RampartException: Error in adding token into store

Interoperability with WSIT problem: RampartException: Error in adding token into store -- Key: RAMPART-329 URL: https://issues.apache.org/jira/browse/RAMPART-329 Proj

RE: SHA2 support

Martin, Thank you for your quick reply. Can you help us, how to setup axis to use SHA256? Leoš Od: Martin Gainty [mailto:[email protected]] Odesláno: 11. března 2011 15:06 Komu: [email protected] Předmět: RE: SHA2 support the currently supported (Rampart) Digest Algorithms

[jira] Updated: (RAMPART-329) Interoperability with WSIT problem: RampartException: Error in adding token into store

[ https://issues.apache.org/jira/browse/RAMPART-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rustam Abdullaev updated RAMPART-329: - Description: The combination: Axis2(Rampart) Service + Metro(WSIT) Client doesn't work w

[jira] Updated: (RAMPART-329) Interoperability with WSIT problem: RampartException: Error in adding token into store

[ https://issues.apache.org/jira/browse/RAMPART-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rustam Abdullaev updated RAMPART-329: - Affects Version/s: 1.4 > Interoperability with WSIT problem: RampartException: Error in

RE: SHA2 support

As mentioned in https://issues.apache.org/jira/browse/RAMPART-216 we used as well (and few others) with no luck. Od: Leos Literak [mailto:[email protected]] Odesláno: 11. března 2011 15:36 Komu: '[email protected]' Předmět: RE: SHA2 support Martin, Thank you for your qu

Axis2: how to send multiple datahandler?

Hi, I have a web service in axis2 that I can send a file to, from a WS client. The file is read as byte[] and then from these bytes a javax.activation.DataHandler is constructed. This DataHandler is send to the web service as a member of an object. No problem so far. The DataHandler is create

Jenkins build is back to normal : Axis2-trunk-java-1.6 #346

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Fwd: Neethi 3 release....

FYI. -- Forwarded message -- From: Daniel Kulp Date: Sat, Mar 12, 2011 at 2:22 AM Subject: Neethi 3 release To: [email protected] It looks like we're going to try and release the next version of CXF fairly shortly.Thus, I'd like to start the release process for Neethi