[jira] [Created] (AXIS2-5409) Generated SOAP12 fault codes are not following the specification

2012-08-31 Thread Kristina Petkova (JIRA)
Kristina Petkova created AXIS2-5409: --- Summary: Generated SOAP12 fault codes are not following the specification Key: AXIS2-5409 URL: https://issues.apache.org/jira/browse/AXIS2-5409 Project: Axis2

[jira] [Commented] (AXIS2-5346) SOAP Fault, Prefix cannot be "null" when creating a QName with LR.

2012-08-31 Thread Rohit (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445769#comment-13445769 ] Rohit commented on AXIS2-5346: -- Axis Implementation Issue. Resolved. > SOAP

[jira] [Resolved] (AXIS2-5346) SOAP Fault, Prefix cannot be "null" when creating a QName with LR.

2012-08-31 Thread Rohit (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit resolved AXIS2-5346. -- Resolution: Cannot Reproduce > SOAP Fault, Prefix cannot be "null" when creating a QName with LR. > ---

[jira] [Created] (AXIS2-5410) Error While Starting webservice Application.

2012-08-31 Thread Rohit (JIRA)
Rohit created AXIS2-5410: Summary: Error While Starting webservice Application. Key: AXIS2-5410 URL: https://issues.apache.org/jira/browse/AXIS2-5410 Project: Axis2 Issue Type: Bug Report

[jira] [Closed] (AXIS2-5346) SOAP Fault, Prefix cannot be "null" when creating a QName with LR.

2012-08-31 Thread Rohit (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit closed AXIS2-5346. > SOAP Fault, Prefix cannot be "null" when creating a QName with LR. >

[jira] [Updated] (AXIS2-5410) org.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: addressing

2012-08-31 Thread Rohit (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit updated AXIS2-5410: - Description: I am getting error while starting web service application. 1) Weblogic 10.3.50 2) Axis1.6.2 - attac

[jira] [Commented] (AXIS2-5410) org.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: addressing

2012-08-31 Thread Rohit (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445773#comment-13445773 ] Rohit commented on AXIS2-5410: -- org.apache.axis2.AxisFault: The system is attempting to engag

[jira] [Updated] (AXIS2-5410) org.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: addressing

2012-08-31 Thread Rohit (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit updated AXIS2-5410: - Attachment: AppxServices.war Attaching example application. > org.apache.axis2.AxisFault: The sy

[jira] [Commented] (AXIS2-5070) Enumeration type fromValue() function update breaks stub compilation

2012-08-31 Thread Vilnis Termanis (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445825#comment-13445825 ] Vilnis Termanis commented on AXIS2-5070: Looks like you're right, since there are

Re: Using rampart as an STS

2012-08-31 Thread Hasini Gunasinghe
Hi, Sample 08 shipped with Rampart distribution demonstrates how to obtain a SAML token from Secure Token Service backed by rampart-trust module. You can find this sample at http://svn.apache.org/repos/asf/axis/axis2/java/rampart/trunk/modules/rampart-samples/policy/sample08/ Also, WSO2 Identity

Re: Axis2 limit incoming response.

2012-08-31 Thread fyrachek
Hi, it looks like I found workaround for this : define custom Message Builder, and check input stream in it. But as for me it's only workaround fyrachek wrote: > > I'm calling external web service with axis2. > And I want to discard response message if its size(content of the incoming > Input

Re: Axis2 limit incoming response.

2012-08-31 Thread Hiranya Jayathilaka
If your response message is guaranteed to have a Content-Length header, then you can access its value through MessageContext. It would be something like: Map headers = (Map) messageContext.getProperty(MessageContext.TRANSPORT_HEADERS); String contentLength = headers.get("Content-Length"); Hope th

[jira] [Reopened] (AXIS2-5070) Enumeration type fromValue() function update breaks stub compilation

2012-08-31 Thread Vilnis Termanis (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vilnis Termanis reopened AXIS2-5070: As per A. Gourley's comment, shouldn't it be java.lang.String instead of string?

[jira] [Commented] (AXIS2-5266) Axis2 phase ordering insufficiently expressive

2012-08-31 Thread James Grahn (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446441#comment-13446441 ] James Grahn commented on AXIS2-5266: This issue seems to be dependent upon #AXIS2-5267

[jira] [Commented] (AXIS2-5267) Valid phase order configurations may result in invalid phase execution orders

2012-08-31 Thread James Grahn (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446464#comment-13446464 ] James Grahn commented on AXIS2-5267: I am developing a patch for this issue using a li