[jira] Resolved: (AXIS2C-1284) Savan/C build fails when --enable-filtering=no

[ https://issues.apache.org/jira/browse/AXIS2C-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage resolved AXIS2C-1284. -- Resolution: Fixed This is fixed now Savan/C build fails when --enable-filtering=no

[jira] Commented: (AXIS2C-1286) Improve the logging facilities to let the client specify their own logging mechanism

[ https://issues.apache.org/jira/browse/AXIS2C-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12646518#action_12646518 ] Damitha Kumarage commented on AXIS2C-1286: -- However my small change to your patch

[jira] Created: (AXIS2C-1288) new version 1.5.0 is not ready to create a .so file

new version 1.5.0 is not ready to create a .so file -- Key: AXIS2C-1288 URL: https://issues.apache.org/jira/browse/AXIS2C-1288 Project: Axis2-C Issue Type: Task Components:

[jira] Resolved: (AXIS2C-1286) Improve the logging facilities to let the client specify their own logging mechanism

[ https://issues.apache.org/jira/browse/AXIS2C-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage resolved AXIS2C-1286. -- Resolution: Fixed Patch applied. Thanks Dmitry for the patch. I have done only small

[jira] Created: (AXIS2C-1287) new version 1.5.0 is not ready to create a .so file

new version 1.5.0 is not ready to create a .so file --- Key: AXIS2C-1287 URL: https://issues.apache.org/jira/browse/AXIS2C-1287 Project: Axis2-C Issue Type: Bug Environment:

[jira] Resolved: (AXIS2-4126) Remove SOAP Version Restriction from JAX-WS Provider Endpoint

[ https://issues.apache.org/jira/browse/AXIS2-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker resolved AXIS2-4126. -- Resolution: Fixed revision 713055 Remove SOAP Version Restriction from JAX-WS Provider

[jira] Created: (AXIS2-4127) JSR 181 annotations web services giving errors

JSR 181 annotations web services giving errors -- Key: AXIS2-4127 URL: https://issues.apache.org/jira/browse/AXIS2-4127 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.4.1

Configuration option to disable the legacy endpoint in Axis2

Hi guys, According to Nandana's article in WSO2 Security Vulnerabilities in Apache Axis2 1.4 / Rampart 1.4 and Avoiding Them http://wso2.org/library/3787Axis2 users should not attach security policy on the binding or port (as it should be according the ws security policy spec) but should instead

Is automatic module engagement supported?

Hi guys, Does Axis2 currently support automatic module enagement? By examining the code I found out that the AxisDescription's engageModulesForPolicy method is called only in applyPolicy(..) which is not explicitly called anywhere (or at least I could not find it). Does this mean that to support

[jira] Created: (AXIS2-4128) Java2WSDL does not generate enum fields

Java2WSDL does not generate enum fields --- Key: AXIS2-4128 URL: https://issues.apache.org/jira/browse/AXIS2-4128 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.4.1

[jira] Commented: (AXIS2-4128) Java2WSDL does not generate enum fields

[ https://issues.apache.org/jira/browse/AXIS2-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12646669#action_12646669 ] Jesse Rosalia commented on AXIS2-4128: -- After some investigation, it appears that the

[jira] Issue Comment Edited: (AXIS2-4128) Java2WSDL does not generate enum fields

[ https://issues.apache.org/jira/browse/AXIS2-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12646669#action_12646669 ] thejenix edited comment on AXIS2-4128 at 11/11/08 1:35 PM:

[jira] Commented: (AXIS2-4128) Java2WSDL does not generate enum fields

[ https://issues.apache.org/jira/browse/AXIS2-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12646673#action_12646673 ] Jesse Rosalia commented on AXIS2-4128: -- Just modified my maven pom file to use version

[jira] Reopened: (AXIS2-4126) Remove SOAP Version Restriction from JAX-WS Provider Endpoint

[ https://issues.apache.org/jira/browse/AXIS2-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker reopened AXIS2-4126: -- The new StringProviderTests failed due to incorrect port associated in the endpoint URL. I will

Re: Is automatic module engagement supported?

Hi Detelin, applyPolicy(..) method is used in code generated stubs. If you look at the constructor you can see _service.applyPolicy() which recursively calls the child descriptions. So automatic module engagement works in the client side as mentioned here [1]. But doesn't see this being

[jira] Closed: (AXIS2-4126) Remove SOAP Version Restriction from JAX-WS Provider Endpoint

[ https://issues.apache.org/jira/browse/AXIS2-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker closed AXIS2-4126. Remove SOAP Version Restriction from JAX-WS Provider Endpoint