[jira] Commented: (AXIS2-4086) WSDL11ToAxisServiceBuilder: The HTTP verb is read from an AxisBindingOperation object but it should be read from the AxisBinding object instead

2010-09-29 Thread Dennis Kieselhorst (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916121#action_12916121 ] Dennis Kieselhorst commented on AXIS2-4086: --- The issue still exists in 1.5.2. Ple

Hudson build is back to normal : Axis2-trunk-java-1.6 #171

2010-09-29 Thread Apache Hudson Server
See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Re: svn commit: r991441 - /axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/description/java2wsdl/Java2WSDLConstants.java

2010-09-29 Thread Isuru Suriarachchi
Hi Andreas, I applied your solution into codegen engine. It solves the original problem and WSDL11ActionHelper#getWSAWActionExtensionAttribute method returns the correct action (http://../..). But unfortunately this fix creates a separate issue. WSDL11ToAxisServiceBuilder#findPort method finds a

[jira] Created: (AXIS2-4834) Allow calls to HTTP endpoint using same address as the SOAP endpoint

2010-09-29 Thread Dennis Kieselhorst (JIRA)
Allow calls to HTTP endpoint using same address as the SOAP endpoint Key: AXIS2-4834 URL: https://issues.apache.org/jira/browse/AXIS2-4834 Project: Axis2 Issue Type: Improv

[jira] Updated: (AXIS2-4834) Allow calls to HTTP endpoint using same address as the SOAP endpoint

2010-09-29 Thread Dennis Kieselhorst (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst updated AXIS2-4834: -- Attachment: RequestURIBasedServiceDispatcher.patch > Allow calls to HTTP endpoint using

[jira] Created: (AXIS2-4835) Wrong order in http location table using WSDL 1.1

2010-09-29 Thread Dennis Kieselhorst (JIRA)
Wrong order in http location table using WSDL 1.1 - Key: AXIS2-4835 URL: https://issues.apache.org/jira/browse/AXIS2-4835 Project: Axis2 Issue Type: Bug Components: kernel Affects

[jira] Updated: (AXIS2-4835) Wrong order in http location table using WSDL 1.1

2010-09-29 Thread Dennis Kieselhorst (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst updated AXIS2-4835: -- Attachment: HttpLocationTableOrder.patch > Wrong order in http location table using WSD

[jira] Created: (AXIS2-4836) REST: operation dispatch fails due to inconsistent http locations

2010-09-29 Thread Dennis Kieselhorst (JIRA)
REST: operation dispatch fails due to inconsistent http locations - Key: AXIS2-4836 URL: https://issues.apache.org/jira/browse/AXIS2-4836 Project: Axis2 Issue Type: Bug Affe

[jira] Updated: (AXIS2-4836) REST: operation dispatch fails due to inconsistent http locations

2010-09-29 Thread Dennis Kieselhorst (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst updated AXIS2-4836: -- Attachment: HTTPLocationBasedDispatcher.patch I attached a patch working for my case, b

Hudson build became unstable: Axis2 #396

2010-09-29 Thread Apache Hudson Server
See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

multiple soap Headers in axis2/axiom

2010-09-29 Thread Raymond Zhou
Hi All,   I am moving from axis/java to axis2/java. I am encountering a few issues. One of them has to do with soap headers in soap envelope.   In axis/java, I used to do like this:      Vector headers = soapenvelope.getHeaders();   This is to get all the soap headers (soap:header) from a soap en

Hudson build is back to stable : Axis2 » Apache Axis2 - JAXWS #397

2010-09-29 Thread Apache Hudson Server
See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Hudson build is back to stable : Axis2 #397

2010-09-29 Thread Apache Hudson Server
See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]