[jira] Commented: (AXIS2C-745) Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException

[ https://issues.apache.org/jira/browse/AXIS2C-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539021 ] Dimuthu Gamage commented on AXIS2C-745: --- It seems you are using an older version of axis2/java. You better

[jira] Commented: (AXIS2C-731) /util/src/base64.c incorrect calculation of length in 'axutil_base64_decode_len'

[ https://issues.apache.org/jira/browse/AXIS2C-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539057 ] Malinda Kaushalye Kapuruge commented on AXIS2C-731: --- I've tested the code. It worked fine for *

[jira] Created: (AXIS2C-746) axis2.pc broken in version 1.1

axis2.pc broken in version 1.1 -- Key: AXIS2C-746 URL: https://issues.apache.org/jira/browse/AXIS2C-746 Project: Axis2-C Issue Type: Bug Components: build system (Unix/Linux) Affects Versions: 1.1.1

[jira] Commented: (AXIS2C-734) Enabling Service Level Custom Logs

[ https://issues.apache.org/jira/browse/AXIS2C-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539260 ] Damitha Kumarage commented on AXIS2C-734: - I have tested this OK Enabling Service Level Custom Logs

[jira] Commented: (AXIS2C-732) Log file size increasing with no upper limit

[ https://issues.apache.org/jira/browse/AXIS2C-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539261 ] Damitha Kumarage commented on AXIS2C-732: - I don't think it is neccessary to implement 1. 2 is handled by

[jira] Created: (AXIS2C-748) Memory leak in dep_engine.c

Memory leak in dep_engine.c --- Key: AXIS2C-748 URL: https://issues.apache.org/jira/browse/AXIS2C-748 Project: Axis2-C Issue Type: Bug Components: core/deployment Environment: Ubuntu 7.04 (Feisty

[jira] Updated: (AXIS2C-748) Memory leak in dep_engine.c

[ https://issues.apache.org/jira/browse/AXIS2C-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando updated AXIS2C-748: --- Attachment: diff.txt Memory leak in dep_engine.c ---

[Fwd: svn commit: r590625 - /webservices/axis2/trunk/c/util/src/base64.c]

Kaushalye, Please let the users know that you have done this change. I think there was a mail on the user list on if this change would be done or now as well as how to use this function. Thanks, Samisa... Original Message Subject: svn commit: r590625 -

[Fwd: svn commit: r590865 - in /webservices/axis2/trunk/c: src/core/transport/http/server/simple_axis2_server/http_server_main.c util/include/axutil_file_handler.h util/include/axutil_log.h util/src/f

Hi Damitha, Looks like you are doing some changes on the log file size. Could you please explain what your are planing to do here? Also, I see that the change is incorporated to the simple axis server. What about the tcp server and the httpd module? Please explain. Thanks, Samisa...

[Fwd: svn commit: r589983 - in /webservices/axis2/trunk/c/util: include/axutil_utils.h src/utils.c]

Hi Nandika, Looks like you have improved the URL encoding functions. Could you please explain where in the engine these are used. Thanks, Samisa... Original Message Subject: svn commit: r589983 - in /webservices/axis2/trunk/c/util: include/axutil_utils.h src/utils.c

Re: [Fwd: svn commit: r590625 - /webservices/axis2/trunk/c/util/src/base64.c]

Samisa Abeysinghe wrote: Kaushalye, Please let the users know that you have done this change. I comment on the JIRA issue[1]. Anyways will drop a mail too. I think there was a mail on the user list on if this change would be done or now as well as how to use this function. No diversion

Re: Rampart 1.2 with Axis2 1.3 final release

Have you tried with Rampart 1.3? Sanjiva. Andrew Puzankov wrote: Hi, Is there a version of Rampart that works with Axis2 1.3 final release? I saw posts in the forum that Rampart 1.2 has issues with Axis1.3 RC1 but does that issue also exist with Axis 1.3 final release? I am trying

[jira] Commented: (AXIS2-3293) NPE in AxisEngine when trying to use TCP transport

[ https://issues.apache.org/jira/browse/AXIS2-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539023 ] Adrian Lang commented on AXIS2-3293: I got the same problem: import org.apache.axis2.Constants; import

Re: [AXIS2] WS-policy support

Hi, Once you generated the stub, you need to do the followings 1) Creating a stub instance providing a ConfigurationContext. The ConfigurationContext should point to a axis2 repository where it contains the Rampart module. It is necessary since Rampart module is responsible for interpreting

[Axis2] Services.xml is wrong but when the WSDL queried is corrected somewhere?

Hi everybody, I am using Axis2 1.3 and rampart2 1.2. I observed something interesting. I am using a custom tool to generate a services.xml. This tool is under development so it did not works perfect at the moment. I am testing the symmetric binding and have the following services.xml generated:

[jira] Assigned: (AXIS2-3315) Compile error in generated JUnit

[ https://issues.apache.org/jira/browse/AXIS2-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith reassigned AXIS2-3315: --- Assignee: Amila Chinthaka Suriarachchi Amila , can you please look in to this,

having the list of a remote axis2 services programmatically

Hi everyone, I have been trying to use the axis2 API to have the list of a remote axis2 services , but I can't find a way to do it. In a more specific description, I need to write a java function that takes as argument the axis2 url (or its repository or something like that) and returns the list

[Axis2] WS-policy client support

Hello friends, I am wondering whether Axis2 support WS-policy client? My WSDL server is Weblogic and the WSDL has following WS-policy. I am not sure whether Axis2 will be able to handle WS-policy in such case. If it does, could anybody let me know how to implement the client side support for

[jira] Created: (AXIS2-3318) Java2WSDL -p2n command line issue

Java2WSDL -p2n command line issue - Key: AXIS2-3318 URL: https://issues.apache.org/jira/browse/AXIS2-3318 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.3

ExceptionInInitializerError when trying to create a new ServiceClient

Hi all, Has anyone seen this? It was working for me till I tried removing some of the jar files that are part of axis2. After that I added the removed ones back in and still get this error. I am using Axis2 1.3 and it is generating this error when trying to create a ServiceClient.

Re: [Axis2] Proposal to chage the method signature of set/get documentation

+1 that we'd be making the keep-the-simple-case-simple rule by losing the String method. Keith, what's the harm in having two methods? That is, do both. Sanjiva. Tom Jordahl wrote: Removing String as an argument type seems like a bad idea to me for two reasons: 1. Breaking API

Re: having the list of a remote axis2 services programmatically

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 If your remote Axis2 server is deployed using Axis2 war, then try accessing http://ip:port/axis2/services/listServices. You will be returned an html which has the list of services together with their endpoints. EL ALAMI wrote: Hi everyone, I

RE: having the list of a remote axis2 services programmatically

Thank you for your replay But I still woder if there is any better way to do this? Do you now how to use the getConfigurationContextFromURI to get the ConfigurationContext from a remote axis using just its URL. I can get this, then I can get the AxisConfiguration, and then use the getServices

Re: having the list of a remote axis2 services programmatically

You need some beans that expose the admin functionality as services so that you can control it remotely. If you look at the source for WSO2 WSAS you can see how we do it - you can either use WSAS' directly for it or just copy the bits that you care about. See:

Re: [Axis2] Proposal to chage the method signature of set/get documentation

We can have the setter method for both but not the getter. So we can have public void setDocumentation(String documentation); but we cant have public String getDocumentation(); cause we would already have public OMNode getDocumentation(); Thanks, Keith. On 11/1/07, Sanjiva Weerawarana [EMAIL

Re: [Axis2] WS-policy client support

That's a proprietary policy assertion language. It's supported only by BEA products. Talk to BEA and convince them to add support for the standard OASIS WS-SecurityPolicy. Anne On 10/31/07, Feng Lu [EMAIL PROTECTED] wrote: Hello friends, I am wondering whether Axis2 support WS-policy client?

[jira] Created: (AXIS2-3319) engageModule for ContextMessage has wrong parameters

engageModule for ContextMessage has wrong parameters Key: AXIS2-3319 URL: https://issues.apache.org/jira/browse/AXIS2-3319 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions:

Re: [Axis2] Axis2 Release Restructuring

So shall we first conclue what should be included into the minimal distribution? I would like to discribe the minimal distribution as follows, It inclues the minimal set of jars which some one needs to creates a webservice using either 1. Contract first approach here we going to provide

Re: [Axis2] Axis2 Release Restructuring

Hi Amila, Thanks for summarizing the conversation. I take it your summary is for the Axis2 server bundle that's been discussed. Two issues: 1. Will the 5 Axis2 jars be rolled up into a single Axis2-server jar as has been requested and discussed? 2. You listed

Re: [Axis2] WS-policy client support

Hi, One work around would be to use the ServiceClient instead of using a generated stub and attach the equivalent standard policy of that proprietary policy expreesion. You may also have to set username and password in options. e.g. Options options = serviceClient.getOptions();