[Rampart] Unable to access Rampart Jira

Hi All, I am unable to access Rampart-Jira (https://issues.apache.org/jira/browse/Rampart). When i try to access, i get following error. "502 Proxy Error". Please let me know how to resolve this. Thanks AmilaJ - To unsubscribe,

AXIOM-28 Issue

Hi, There is an issue about Axiom, AXIOM-28, that is assigned for Andreas Veithen. I saw that this bug will be fixed just on Axiom 1.2.12. Is that correct? I’m experiencing some problems when I try to use the method, “AXIOMUtil.stringToOM(SomeString)”, to convert a XML content to a OMElement,

Re: AXIOM-28 Issue

Fernando, The right mailing list for purely Axiom related questions is [email protected]. Andreas On Fri, Feb 4, 2011 at 13:08, Fernando Cesar Silva wrote: > Hi, > > > > There is an issue about Axiom, AXIOM-28, that is assigned for Andreas > Veithen. > > I saw that this bug will be fixed just

Re: [Rampart] Unable to access Rampart Jira

Hi Amila, It looks a bit slow initially getting loaded initially, but it's accessible... Regards, --Vijitha. On Fri, Feb 4, 2011 at 2:16 PM, Amila Jayasekara wrote: > Hi All, > I am unable to access Rampart-Jira > (https://issues.apache.org/jira/browse/Rampart). When i try to access, > i get f

[jira] Commented: (AXIS2-4191) Axis2 Generated Client: UnExpected SubElement error while processing Response.

[ https://issues.apache.org/jira/browse/AXIS2-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990624#comment-12990624 ] Malleswara Sarma commented on AXIS2-4191: - I think it is fixed in1.5 Regards Sa

[jira] Created: (AXIS2-4948) JAX-WS 2.2 CTS - Wrong wsdlLocation in EPR returned by BindingProvider.getEndpointReference

JAX-WS 2.2 CTS - Wrong wsdlLocation in EPR returned by BindingProvider.getEndpointReference --- Key: AXIS2-4948 URL: https://issues.apache.org/jira/browse/AXIS2-4948

[jira] Commented: (AXIS2-4077) Wrong wsa:Action returned in fault message when an operation declares multiple faults

[ https://issues.apache.org/jira/browse/AXIS2-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990631#comment-12990631 ] Katherine Sanders commented on AXIS2-4077: -- This issue has been fixed under AXIS2

Re: Axis2 1.6 release plan

When I run TCK for last time around half of test cases were failed. I didn't make any configuration change or had no time to investigate about failing test cases , with some modifications we may improve the pass rate. But I also believe it will take much more time to pass complete TCK. BTW rece

Lifecycle interface: AXIS2-633

All - I have a service in place the returns a set of attachments using SwA. These attachments are generated on the server and placed in a tmp directory before they are returned. I've implemented the Lifecycle interface so I can cleanup the tmp files after the service returns in the destroy metho

[AXIS2] Redirecting a response from axis2 handler to client

Hi, I have a custom module deployed on axis2 server side. While the client  request goes to that handler in an inflow, i want it should create one error response in that handler and send back to client without doing any further processing or forwarding the client request to the Web Service. Ho

[jira] Commented: (AXIS2-2477) Unusual service name/epr is presented when a pojo annotation class is deployed

[ https://issues.apache.org/jira/browse/AXIS2-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990924#comment-12990924 ] Isuru Eranga Suriarachchi commented on AXIS2-2477: -- The issue was when de

[jira] Resolved: (AXIS2-2477) Unusual service name/epr is presented when a pojo annotation class is deployed

[ https://issues.apache.org/jira/browse/AXIS2-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Eranga Suriarachchi resolved AXIS2-2477. -- Resolution: Fixed Fixed in revision 1067399. Thanks, ~Isuru > Unusual