[jira] Resolved: (AXIS2C-744) wsdl2c tool generated call to non-existent AXIS2_QNAME_TO_STRING
[ https://issues.apache.org/jira/browse/AXIS2C-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-744. --- Resolution: Fixed wsdl2c tool generated call to non-existent AXIS2_QNAME_TO_STRING Key: AXIS2C-744 URL: https://issues.apache.org/jira/browse/AXIS2C-744 Project: Axis2-C Issue Type: Bug Components: code generation Affects Versions: 1.1.0 Environment: I'm running Windows XP SP2, but this looks like it is not platform specific. Reporter: Michael Mole Assignee: Sanjaya Ratnaweera Priority: Minor Fix For: 1.2.0 The WSDL2C code generation tool released with Axis2/Java 1.3 is generating calls to a non-existent AXIS2_QNAME_TO_STRING. This is causing linker errors. I did a search through the Axis2/C 1.1 source and couldn't find this function. There is, however, a function called axutil_qname_to_string located in axutil_qname.c. It appears that somewhere along the line, the code generation tool, and the Axis2/C source got out of sync. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-738) Unreachable code found in http_reciever.c
[ https://issues.apache.org/jira/browse/AXIS2C-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-738. --- Resolution: Fixed Fixed in current svn Unreachable code found in http_reciever.c - Key: AXIS2C-738 URL: https://issues.apache.org/jira/browse/AXIS2C-738 Project: Axis2-C Issue Type: Bug Components: transport/http Environment: Ubuntu 7.10 (Gutsy Gibbon) Reporter: Senaka Fernando Assignee: Sanjaya Ratnaweera Priority: Minor Fix For: 1.2.0 Attachments: diff.txt Line 296 in /axis2/c/src/core/transport/http/receiver/http_reciever.c, is never reached. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2C-702) No documents/guides available on how to run the tcp server
[ https://issues.apache.org/jira/browse/AXIS2C-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-702: - Fix Version/s: 1.2.0 No documents/guides available on how to run the tcp server -- Key: AXIS2C-702 URL: https://issues.apache.org/jira/browse/AXIS2C-702 Project: Axis2-C Issue Type: Bug Components: documentation Affects Versions: 1.1.0 Environment: Windows XP Reporter: Evanthika Amarasiri Assignee: Dinesh Premalal Priority: Minor Fix For: 1.2.0 There are no documents/guides provided to test the TCP transport server -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-704) readme files in codegen sample directories contain wrong information.
[ https://issues.apache.org/jira/browse/AXIS2C-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dushshantha Chandradasa resolved AXIS2C-704. Resolution: Fixed modified the readme files. readme files in codegen sample directories contain wrong information. - Key: AXIS2C-704 URL: https://issues.apache.org/jira/browse/AXIS2C-704 Project: Axis2-C Issue Type: Bug Components: documentation Environment: all Reporter: Dushshantha Chandradasa Assignee: Dushshantha Chandradasa Priority: Trivial Fix For: 1.2.0 readme files in codegen sample directories contain wrong information. It says the command to execute is WSDL2Code. This sould be WSDL2C. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2C-704) readme files in codegen sample directories contain wrong information.
[ https://issues.apache.org/jira/browse/AXIS2C-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dushshantha Chandradasa closed AXIS2C-704. -- readme files in codegen sample directories contain wrong information. - Key: AXIS2C-704 URL: https://issues.apache.org/jira/browse/AXIS2C-704 Project: Axis2-C Issue Type: Bug Components: documentation Environment: all Reporter: Dushshantha Chandradasa Assignee: Dushshantha Chandradasa Priority: Trivial Fix For: 1.2.0 readme files in codegen sample directories contain wrong information. It says the command to execute is WSDL2Code. This sould be WSDL2C. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-742) Improper placement of code in data_handler.c leads to increased time overhead and memory leaks.
[
https://issues.apache.org/jira/browse/AXIS2C-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjaya Ratnaweera resolved AXIS2C-742.
---
Resolution: Fixed
Fixed in current SVN
Improper placement of code in data_handler.c leads to increased time overhead
and memory leaks.
---
Key: AXIS2C-742
URL: https://issues.apache.org/jira/browse/AXIS2C-742
Project: Axis2-C
Issue Type: Bug
Components: xml/om
Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Sanjaya Ratnaweera
Fix For: 1.2.0
Attachments: diff.txt
The code portion
struct stat stat_p;
if (-1 == stat(data_handler-file_name, stat_p))
{
return AXIS2_FAILURE;
}
else if (stat_p.st_size == 0)
{
*output_stream = NULL;
*output_stream_size = 0;
return AXIS2_SUCCESS;
}
in axis2/c/axiom/src/attachments/data_handler.c (line 175) is repeatedly
executed and thus leads to increased time overhead.
Nevertheless, if the function is to return, resources occupied by byte_stream
is not freed, and thus leads to a memory leak.
I propose to move this portion of code out of the do-while loop.
Reasons:
* Evaluation of stat() just one time is enough as any other error that could
occur during reading the file is returned by the fread() and ferror()
combination.
* Therefore, repeated evaluation of a parameter that is technically not
supposed to change, is not worth it.
* Even it does change, that particular change may occur just after stat()
was evaluated, and thus makes the above argument base-less.
Thus, it seems to be the best option.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-743) some return paths in axiom_data_handler_read_from() does not call fclose() on the open file stream, in data_handler.c
[ https://issues.apache.org/jira/browse/AXIS2C-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-743. --- Resolution: Fixed Fixed in current SVN some return paths in axiom_data_handler_read_from() does not call fclose() on the open file stream, in data_handler.c - Key: AXIS2C-743 URL: https://issues.apache.org/jira/browse/AXIS2C-743 Project: Axis2-C Issue Type: Bug Components: xml/om Environment: Ubuntu 7.10 (Gutsy Gibbon) Reporter: Senaka Fernando Assignee: Sanjaya Ratnaweera Priority: Minor Fix For: 1.2.0 in axis2/c/axiom/src/attachments/data_handler.c axiom_data_handler_read_from() some return paths do not close the open file stream. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2C-704) readme files in codegen sample directories contain wrong information.
[ https://issues.apache.org/jira/browse/AXIS2C-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-704: - Component/s: documentation Fix Version/s: 1.2.0 Assignee: Dushshantha Chandradasa readme files in codegen sample directories contain wrong information. - Key: AXIS2C-704 URL: https://issues.apache.org/jira/browse/AXIS2C-704 Project: Axis2-C Issue Type: Bug Components: documentation Environment: all Reporter: Dushshantha Chandradasa Assignee: Dushshantha Chandradasa Priority: Trivial Fix For: 1.2.0 readme files in codegen sample directories contain wrong information. It says the command to execute is WSDL2Code. This sould be WSDL2C. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] [Axis2] Damitha as Release Manager for Apache Axis2/C 1.2.0 Release
+1 -Dumindu. Samisa Abeysinghe wrote: Hi All, I would like to propose Damitha as the release manager for Apache Axis2/C 1.2.0 release. Damitha, a WS PMC as well as an active committer for Apache Axis2/C, has expressed his willingness to be the release manager for Apache Axis2/C 1.2.0 and I would like to welcome him for this role. Here is my +1. Thanks, Samisa... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform signature.asc Description: OpenPGP digital signature
[jira] Commented: (AXIS2C-719) v2.0.x apache module compilation error
[ https://issues.apache.org/jira/browse/AXIS2C-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542739 ] Dushshantha Chandradasa commented on AXIS2C-719: I tested with apache 2.0.59 and it works fine. I tried few samples as well. v2.0.x apache module compilation error -- Key: AXIS2C-719 URL: https://issues.apache.org/jira/browse/AXIS2C-719 Project: Axis2-C Issue Type: Bug Components: build system (Windows) Affects Versions: 1.1.0 Environment: Visual Studio 2005 apache v2.0.59 apache v2.0.61 DEBUG=1 APACHE_VERSION_2_0_X = 1 Reporter: David Klassen Assignee: Dushshantha Chandradasa Fix For: 1.2.0 I read how to install the apache module, and naturally decided to use 2.2.x. Everything installed fine. However after finding the apache httpd.exe memory size was growing fast for 25 concurrent users (AXIS2C-717), I decided to install an older version of apache to make sure this was not related to some apache 2.2.x features interfering with axis2c. Looking on-line I remembered seeing that special configuration changes were needed to work with 2.0.x version of apache: http://ws.apache.org/axis2/c/docs/axis2c_manual.html#mod_axis2 I set the configuration setting: APACHE_VERSION_2_0_59 = 1 However a compilation error still occurrs: C:\SOAP\axis2c-src-1.1.0\axis2c-src-1.1.0\build\win32nmake axis2_apache_module Microsoft (R) Program Maintenance Utility Version 8.00.50727.42 Copyright (C) Microsoft Corporation. All rights reserved. Creating library ..\deploy\lib\mod_axis2.lib and object ..\deploy\lib\mod_axis2.exp mod_axis2.obj : error LNK2019: unresolved external symbol __imp__ap_real_exit_code referenced in function _axis2_module_init ..\deploy\lib\mod_axis2.dll : fatal error LNK1120: 1 unresolved externals NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 8\VC\BIN\link.exe' : return code '0x460' Stop. Unfortunately I am not sure of the best remedy yet. Perhaps axis2c does not support apache 2.0.x ? If so the on-line documentation should be updated. However I would like to make sure the memory leak is not constrained to 2.2.x alone... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-725) Parsing WS response with an item without namespace
[ https://issues.apache.org/jira/browse/AXIS2C-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-725. --- Resolution: Fixed Fixed in current svn Parsing WS response with an item without namespace -- Key: AXIS2C-725 URL: https://issues.apache.org/jira/browse/AXIS2C-725 Project: Axis2-C Issue Type: Bug Components: code generation Affects Versions: 1.1.0 Environment: Linux Reporter: Antonio Chiurla Assignee: Sanjaya Ratnaweera Fix For: 1.2.0 Attachments: pack.tar.gz I created stub using wsdl2c (distributed with 1.3 version) with -d adb option. The deserialize function failed parsing if Response contains an item without namespace contained in an array. I have fixed generated code substituting third parameter in axutil_qname_create with NULL value to the place of an empty string. cheers Antonio -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2C-719) v2.0.x apache module compilation error
[ https://issues.apache.org/jira/browse/AXIS2C-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dushshantha Chandradasa closed AXIS2C-719. -- Resolution: Fixed This problem is no longer exists. Hence close the issue v2.0.x apache module compilation error -- Key: AXIS2C-719 URL: https://issues.apache.org/jira/browse/AXIS2C-719 Project: Axis2-C Issue Type: Bug Components: build system (Windows) Affects Versions: 1.1.0 Environment: Visual Studio 2005 apache v2.0.59 apache v2.0.61 DEBUG=1 APACHE_VERSION_2_0_X = 1 Reporter: David Klassen Assignee: Dushshantha Chandradasa Fix For: 1.2.0 I read how to install the apache module, and naturally decided to use 2.2.x. Everything installed fine. However after finding the apache httpd.exe memory size was growing fast for 25 concurrent users (AXIS2C-717), I decided to install an older version of apache to make sure this was not related to some apache 2.2.x features interfering with axis2c. Looking on-line I remembered seeing that special configuration changes were needed to work with 2.0.x version of apache: http://ws.apache.org/axis2/c/docs/axis2c_manual.html#mod_axis2 I set the configuration setting: APACHE_VERSION_2_0_59 = 1 However a compilation error still occurrs: C:\SOAP\axis2c-src-1.1.0\axis2c-src-1.1.0\build\win32nmake axis2_apache_module Microsoft (R) Program Maintenance Utility Version 8.00.50727.42 Copyright (C) Microsoft Corporation. All rights reserved. Creating library ..\deploy\lib\mod_axis2.lib and object ..\deploy\lib\mod_axis2.exp mod_axis2.obj : error LNK2019: unresolved external symbol __imp__ap_real_exit_code referenced in function _axis2_module_init ..\deploy\lib\mod_axis2.dll : fatal error LNK1120: 1 unresolved externals NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 8\VC\BIN\link.exe' : return code '0x460' Stop. Unfortunately I am not sure of the best remedy yet. Perhaps axis2c does not support apache 2.0.x ? If so the on-line documentation should be updated. However I would like to make sure the memory leak is not constrained to 2.2.x alone... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] [Axis2] Damitha as Release Manager for Apache Axis2/C 1.2.0 Release
+1 Thanks -sahan On 11/15/07, Dumindu Pallewela [EMAIL PROTECTED] wrote: +1 -Dumindu. Samisa Abeysinghe wrote: Hi All, I would like to propose Damitha as the release manager for Apache Axis2/C 1.2.0 release. Damitha, a WS PMC as well as an active committer for Apache Axis2/C, has expressed his willingness to be the release manager for Apache Axis2/C 1.2.0 and I would like to welcome him for this role. Here is my +1. Thanks, Samisa... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2C-767) http Basic authentication fails when server requests http BASIC authentication
http Basic authentication fails when server requests http BASIC authentication -- Key: AXIS2C-767 URL: https://issues.apache.org/jira/browse/AXIS2C-767 Project: Axis2-C Issue Type: Bug Components: core/transport, transport/http Affects Versions: 1.1.0 Environment: Any Reporter: Ryan Ahearn When trying to connect to a webservice using the Axis2/C 1.1 client library, authentication is failing because http_sender.c is using a case sensitive compare between the server returned authentication required and the types of authentication that the client knows how to handle. Here is a diff of http_sender.c with the changes I made to enable BASIC authentication interoperable with Basic authentication. 1293c1293 if (axutil_strcmp(auth_type, AXIS2_HTTP_AUTH_TYPE_BASIC) == 0) --- if (axutil_strcasecmp(auth_type, AXIS2_HTTP_AUTH_TYPE_BASIC) == 0) 1296c1296 else if (axutil_strcmp(auth_type, AXIS2_HTTP_AUTH_TYPE_DIGEST) == 0) --- else if (axutil_strcasecmp(auth_type, AXIS2_HTTP_AUTH_TYPE_DIGEST) == 0) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] [Axis2] Damitha as Release Manager for Apache Axis2/C 1.2.0 Release
+1. On Nov 15, 2007 11:05 AM, Sahan Gamage [EMAIL PROTECTED] wrote: +1 Thanks -sahan On 11/15/07, Dumindu Pallewela [EMAIL PROTECTED] wrote: +1 -Dumindu. Samisa Abeysinghe wrote: Hi All, I would like to propose Damitha as the release manager for Apache Axis2/C 1.2.0 release. Damitha, a WS PMC as well as an active committer for Apache Axis2/C, has expressed his willingness to be the release manager for Apache Axis2/C 1.2.0 and I would like to welcome him for this role. Here is my +1. Thanks, Samisa... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Eran Chinthaka The whole of science is nothing more than a refinement of everyday thinking - Albert Einstein, Physics and Reality.
[jira] Created: (AXIS2C-768) Null pointer exception in WSDL2C compiling schema when generating ADB
Null pointer exception in WSDL2C compiling schema when generating ADB - Key: AXIS2C-768 URL: https://issues.apache.org/jira/browse/AXIS2C-768 Project: Axis2-C Issue Type: Bug Components: wsdl2c tool Affects Versions: Current (Nightly) Environment: Windows XP Reporter: Bill Mitchell When I attempt to generate C bindings for the WSDL file below, the WSDL2C utility fails with a null pointer exception without generating any stub code whatsoever. The exception trace is: java org.apache.axis2.wsdl.WSDL2C -or -d adb -wv 1.1 -u -uri service.wsdl Retrieving document at 'service.wsdl'. Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:278) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2C.main(WSDL2C.java:31) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:53) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:231) ... 2 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:50) ... 3 more Caused by: org.apache.axis2.schema.SchemaCompilationException: java.lang.NullPointerException at org.apache.axis2.schema.writer.CStructWriter.write(CStructWriter.java:197) at org.apache.axis2.schema.SchemaCompiler.writeComplexType(SchemaCompiler.java:939) at org.apache.axis2.schema.SchemaCompiler.processNamedComplexSchemaType(SchemaCompiler.java:925) at org.apache.axis2.schema.SchemaCompiler.processComplexContent(SchemaCompiler.java:1087) at org.apache.axis2.schema.SchemaCompiler.processContentModel(SchemaCompiler.java:1054) at org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:998) at org.apache.axis2.schema.SchemaCompiler.processNamedComplexSchemaType(SchemaCompiler.java:919) at org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:833) at org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:531) at org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:491) at org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:1904) at org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:1791) at org.apache.axis2.schema.SchemaCompiler.processComplexContent(SchemaCompiler.java:1170) at org.apache.axis2.schema.SchemaCompiler.processContentModel(SchemaCompiler.java:1054) at org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:998) at org.apache.axis2.schema.SchemaCompiler.processNamedComplexSchemaType(SchemaCompiler.java:919) at org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:833) at org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:531) at org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:502) at org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:309) at org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:219) at org.apache.axis2.schema.ExtensionUtility.invoke(ExtensionUtility.java:80) ... 8 more Caused by: java.lang.NullPointerException at org.apache.axis2.schema.writer.CStructWriter.addPropertyEntries(CStructWriter.java:635) at org.apache.axis2.schema.writer.CStructWriter.populateInfo(CStructWriter.java:516) at org.apache.axis2.schema.writer.CStructWriter.getBeanElement(CStructWriter.java:439) at org.apache.axis2.schema.writer.CStructWriter.process(CStructWriter.java:320) at org.apache.axis2.schema.writer.CStructWriter.write(CStructWriter.java:192) ... 29 more I receive this failure both with the WSDL2C released in Axis2-1.3 and in the current nightly build I downloaded yesterday. Of course, it is a little difficult to isolate what in the WSDL is causing the failure, as no stub code is generated that might hint at the problem area. The same WSDL is accepted by the Axis2 WSDL2Java utility, so the issue is specific to C code generation. As the
[jira] Created: (AXIS2C-769) Program crashes if optional attributes are not provided
Program crashes if optional attributes are not provided
---
Key: AXIS2C-769
URL: https://issues.apache.org/jira/browse/AXIS2C-769
Project: Axis2-C
Issue Type: Bug
Components: code generation
Affects Versions: Current (Nightly)
Environment: Windows + UNIX
Reporter: Michael Mole
Priority: Critical
This is similar to AXIS2C-753.
The generated serialize method of this complex type assumes that attributes
will be provided even if the WSDL specifies them as Optional. If the WSDL
specifies an attribute as required, there should be some error checking that
provides a useful error message if it is not supplied. Currently, the program
will just crash.
I have a complex type defined as follows:
complexType name=Foo
sequence
element name=my_element type=anyType minOccurs=0
/element
/sequence
attribute name=property use=required type=QName
/attribute
attribute name=length type=unsignedInt use=optional
/attribute
/complexType
The generated code around both attributes looks like this:
text_value = (axis2_char_t*) AXIS2_MALLOC (env- allocator, sizeof
(axis2_char_t) * (64 + strlen(length)));
sprintf(text_value, ns2:length=\%d\, _Foo-property_length);
axutil_stream_write(stream, env, text_value, axutil_strlen(text_value));
AXIS2_FREE(env- allocator, text_value);
For the length attribute, this should check and only try to write to the stream
if the length was provided:
Ex.
if ( _Foo-property_length != NULL ) {
...write to stream...
}
For the property attribute, this should check if the attribute was provided and
return an error if it was not.
Ex.
if ( _Foo-property_property == NULL ) {
return Error;
}
else {
... write to stream ...
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2C-770) Incorrect memory is allocated for attributes
Incorrect memory is allocated for attributes Key: AXIS2C-770 URL: https://issues.apache.org/jira/browse/AXIS2C-770 Project: Axis2-C Issue Type: Bug Components: code generation Affects Versions: Current (Nightly) Reporter: Michael Mole I noticed in CADBBeanTemplateSource.xsl that some of the attributes have incorrect use of parenthesis which leads to incorrect memory allocation. For example (Note this code was taken somewhere in the range of line 2509): If you look at lines 4 and 5, we are trying to add 3 numbers: 64, and the values returned from each strlen. The 1st strlen does not close off it's parenthesis before trying to add the value returned by the 2nd strlen. 1xsl:when test=$nativePropertyType='axutil_base64_binary_t*' 2 text_value = axutil_base64_binary_get_encoded_binary(xsl:value-of select=$propertyInstanceName/, env); 3 string_to_stream = (axis2_char_t*) AXIS2_MALLOC (env- allocator, sizeof (axis2_char_t) * 4(64 + strlen(xsl:value-of select=$propertyName/ + 5 strlen(text_value; 6 sprintf(string_to_stream, xsl:value-of select=$namespacePrefix/xsl:value-of select=$propertyName/=\%s\, text_value); 7 axutil_stream_write(stream, env, string_to_stream, axutil_strlen(string_to_stream)); 8 AXIS2_FREE(env- allocator, string_to_stream); Lines 4 and 5 should look something more like this: I've added a ) right before the + on line 4 and removed a ) right before the ; on line 5. 4(64 + strlen(xsl:value-of select=$propertyName/) + 5 strlen(text_value))); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2C-771) Program crashes if attribute is of type axutil_qname_t*
Program crashes if attribute is of type axutil_qname_t*
---
Key: AXIS2C-771
URL: https://issues.apache.org/jira/browse/AXIS2C-771
Project: Axis2-C
Issue Type: Bug
Components: code generation
Affects Versions: Current (Nightly)
Environment: Win + UNIX
Reporter: Michael Mole
Priority: Critical
If I have a complex type with an attribute of type axutil_qname_t*, my program
crashes when serializing because the generated code is trying to write to
unallocated memory.
For example, my complex type looks like this:
complexType name=Foo
sequence
element name=content type=anyType minOccurs=0
/element
/sequence
attribute name=property use=required type=QName
/attribute
/complexType
The generated code in the serialize method looks like this:
if(!parent_tag_closed)
{
sprintf(text_value, %s:%s,
axutil_qname_get_prefix(_Foo-property_property, env),
axutil_qname_get_localpart(_Foo-property_property, env));
string_to_stream = (axis2_char_t*) AXIS2_MALLOC
(env- allocator, sizeof (axis2_char_t) *
(64 +
strlen(property +
strlen(text_value;
sprintf(string_to_stream, ns2:property=\%s\,
text_value);
axutil_stream_write(stream, env, string_to_stream,
axutil_strlen(string_to_stream));
AXIS2_FREE(env- allocator, string_to_stream);
AXIS2_FREE(env-allocator, text_value);
...
This crashes when trying to get the strlen(text_value) when assigning
string_to_stream. This is because text_value had never been allocated memory.
I found that adding this line above the first sprintf allowed the code to
proceed:
text_value = (axis2_char_t*) AXIS2_MALLOC ( env- allocator, sizeof
(axis2_char_t) *
( 64 +
strlen(axutil_qname_get_prefix(_Fooproperty_property, env)) +
strlen(axutil_qname_get_localpart(_Fooproperty_property, env)) ) );
This should be added in CADBBeanTemplateSource.xsl at approximately line 2475
when the axutil_qname_t attribute code is generated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-739) Function Definition does not match declaration in soap_builder.c
[ https://issues.apache.org/jira/browse/AXIS2C-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-739. --- Resolution: Fixed Function Definition does not match declaration in soap_builder.c Key: AXIS2C-739 URL: https://issues.apache.org/jira/browse/AXIS2C-739 Project: Axis2-C Issue Type: Bug Components: xml/om Environment: Ubuntu 7.10 (Gutsy Gibbon) Reporter: Senaka Fernando Assignee: Sanjaya Ratnaweera Fix For: 1.2.0 Attachments: diff.txt Function Definition does not match declaration in soap_builder.c, in Line 726. The type should in fact be axis2_bool_t, but is stated as int, which violates the convention, and thus leading to potential bugs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2C-772) Guththila Parser write extra namespace
[ https://issues.apache.org/jira/browse/AXIS2C-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake updated AXIS2C-772: -- Attachment: patch_file I've change the code of guththila_xml_writer.c now it doesn't add aditional namespace to response xml. Guththila Parser write extra namespace -- Key: AXIS2C-772 URL: https://issues.apache.org/jira/browse/AXIS2C-772 Project: Axis2-C Issue Type: Bug Components: build system (Unix/Linux) Affects Versions: Current (Nightly) Environment: Ubuntu Reporter: Lahiru Gunathilake Fix For: Current (Nightly) Attachments: patch_file I did some performance testings using apache benchmark by using Libxml2 and Guththila Parser with the the math sample which ships with apache Axis2c.Response of the math service with Guththila parser is slightly different to the response with Libxml2.With Guththila parser it add Namespace http://www.w3.org/2003/05/soap-envelope; in to soap header and soap body as well. Then the document size is different when using two XML parsers.Here are the two soap response soap messages got with two XML parsers. -- with Guththila Parser --- soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soapenv:Header/soapenv:Headersoapenv:Body xmlns:soapenv = http://www.w3.org/2003/05/soap-envelope;ns1:result xmlns:ns1 = http://axis2/test/namespace1;18/ns1:result/soapenv:Body/soapenv:Envelope --- --with Libxml2 Parser-- soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soapenv:Header/soapenv:Bodyns1:result xmlns:ns1=http://axis2/test/namespace1;18/ns1:result/soapenv:Body/soapenv:Envelope - This is probably cause to reduce the speed of Guththila parser since it send nearly 78 more bytes of data in the response message with a simple service like math.But with more data still the Guththila Parser is much faster than with Libxml2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2C-772) Guththila Parser write extra namespace
Guththila Parser write extra namespace -- Key: AXIS2C-772 URL: https://issues.apache.org/jira/browse/AXIS2C-772 Project: Axis2-C Issue Type: Bug Components: build system (Unix/Linux) Affects Versions: Current (Nightly) Environment: Ubuntu Reporter: Lahiru Gunathilake Fix For: Current (Nightly) I did some performance testings using apache benchmark by using Libxml2 and Guththila Parser with the the math sample which ships with apache Axis2c.Response of the math service with Guththila parser is slightly different to the response with Libxml2.With Guththila parser it add Namespace http://www.w3.org/2003/05/soap-envelope; in to soap header and soap body as well. Then the document size is different when using two XML parsers.Here are the two soap response soap messages got with two XML parsers. -- with Guththila Parser --- soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soapenv:Header/soapenv:Headersoapenv:Body xmlns:soapenv = http://www.w3.org/2003/05/soap-envelope;ns1:result xmlns:ns1 = http://axis2/test/namespace1;18/ns1:result/soapenv:Body/soapenv:Envelope --- --with Libxml2 Parser-- soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soapenv:Header/soapenv:Bodyns1:result xmlns:ns1=http://axis2/test/namespace1;18/ns1:result/soapenv:Body/soapenv:Envelope - This is probably cause to reduce the speed of Guththila parser since it send nearly 78 more bytes of data in the response message with a simple service like math.But with more data still the Guththila Parser is much faster than with Libxml2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-772) Guththila Parser write extra namespace
[ https://issues.apache.org/jira/browse/AXIS2C-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-772. --- Resolution: Fixed Fix Version/s: (was: Current (Nightly)) 1.2.0 Fixed in current SVN. Thanks Lahiru for the patch Guththila Parser write extra namespace -- Key: AXIS2C-772 URL: https://issues.apache.org/jira/browse/AXIS2C-772 Project: Axis2-C Issue Type: Bug Components: build system (Unix/Linux) Affects Versions: Current (Nightly) Environment: Ubuntu Reporter: Lahiru Gunathilake Assignee: Sanjaya Ratnaweera Fix For: 1.2.0 Attachments: patch_file I did some performance testings using apache benchmark by using Libxml2 and Guththila Parser with the the math sample which ships with apache Axis2c.Response of the math service with Guththila parser is slightly different to the response with Libxml2.With Guththila parser it add Namespace http://www.w3.org/2003/05/soap-envelope; in to soap header and soap body as well. Then the document size is different when using two XML parsers.Here are the two soap response soap messages got with two XML parsers. -- with Guththila Parser --- soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soapenv:Header/soapenv:Headersoapenv:Body xmlns:soapenv = http://www.w3.org/2003/05/soap-envelope;ns1:result xmlns:ns1 = http://axis2/test/namespace1;18/ns1:result/soapenv:Body/soapenv:Envelope --- --with Libxml2 Parser-- soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soapenv:Header/soapenv:Bodyns1:result xmlns:ns1=http://axis2/test/namespace1;18/ns1:result/soapenv:Body/soapenv:Envelope - This is probably cause to reduce the speed of Guththila parser since it send nearly 78 more bytes of data in the response message with a simple service like math.But with more data still the Guththila Parser is much faster than with Libxml2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2C-772) Guththila Parser write extra namespace
[ https://issues.apache.org/jira/browse/AXIS2C-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake closed AXIS2C-772. - Now guththila doesn't write additional namespaces. Guththila Parser write extra namespace -- Key: AXIS2C-772 URL: https://issues.apache.org/jira/browse/AXIS2C-772 Project: Axis2-C Issue Type: Bug Components: build system (Unix/Linux) Affects Versions: Current (Nightly) Environment: Ubuntu Reporter: Lahiru Gunathilake Assignee: Sanjaya Ratnaweera Fix For: 1.2.0 Attachments: patch_file I did some performance testings using apache benchmark by using Libxml2 and Guththila Parser with the the math sample which ships with apache Axis2c.Response of the math service with Guththila parser is slightly different to the response with Libxml2.With Guththila parser it add Namespace http://www.w3.org/2003/05/soap-envelope; in to soap header and soap body as well. Then the document size is different when using two XML parsers.Here are the two soap response soap messages got with two XML parsers. -- with Guththila Parser --- soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soapenv:Header/soapenv:Headersoapenv:Body xmlns:soapenv = http://www.w3.org/2003/05/soap-envelope;ns1:result xmlns:ns1 = http://axis2/test/namespace1;18/ns1:result/soapenv:Body/soapenv:Envelope --- --with Libxml2 Parser-- soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soapenv:Header/soapenv:Bodyns1:result xmlns:ns1=http://axis2/test/namespace1;18/ns1:result/soapenv:Body/soapenv:Envelope - This is probably cause to reduce the speed of Guththila parser since it send nearly 78 more bytes of data in the response message with a simple service like math.But with more data still the Guththila Parser is much faster than with Libxml2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2C-772) Guththila Parser write extra namespace
[ https://issues.apache.org/jira/browse/AXIS2C-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera reassigned AXIS2C-772: - Assignee: Sanjaya Ratnaweera Guththila Parser write extra namespace -- Key: AXIS2C-772 URL: https://issues.apache.org/jira/browse/AXIS2C-772 Project: Axis2-C Issue Type: Bug Components: build system (Unix/Linux) Affects Versions: Current (Nightly) Environment: Ubuntu Reporter: Lahiru Gunathilake Assignee: Sanjaya Ratnaweera Fix For: Current (Nightly) Attachments: patch_file I did some performance testings using apache benchmark by using Libxml2 and Guththila Parser with the the math sample which ships with apache Axis2c.Response of the math service with Guththila parser is slightly different to the response with Libxml2.With Guththila parser it add Namespace http://www.w3.org/2003/05/soap-envelope; in to soap header and soap body as well. Then the document size is different when using two XML parsers.Here are the two soap response soap messages got with two XML parsers. -- with Guththila Parser --- soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soapenv:Header/soapenv:Headersoapenv:Body xmlns:soapenv = http://www.w3.org/2003/05/soap-envelope;ns1:result xmlns:ns1 = http://axis2/test/namespace1;18/ns1:result/soapenv:Body/soapenv:Envelope --- --with Libxml2 Parser-- soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soapenv:Header/soapenv:Bodyns1:result xmlns:ns1=http://axis2/test/namespace1;18/ns1:result/soapenv:Body/soapenv:Envelope - This is probably cause to reduce the speed of Guththila parser since it send nearly 78 more bytes of data in the response message with a simple service like math.But with more data still the Guththila Parser is much faster than with Libxml2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Sanjaya Karunasena as an Axis2 commiter
+1 Thanks Sandakith On Nov 13, 2007 12:00 AM, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi all, Sanjaya Karunasena has done enough work to become as a commiter , he has implemented fastinforset [FI] support in Axis2. And giving he commiter access will encourage him to contribute some more to the project and will make our job easier [no need to commit the patches]. Here my +1 for Sanjaya as an Axis2 commiter. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [VOTE] Bjorn Townsend for committer
+1 Thanks Sandkaith On Nov 14, 2007 10:02 PM, Glen Daniels [EMAIL PROTECTED] wrote: Hi folks! As mentioned I'd like us to invite Bjorn Townsend, who's been helping out on the fringes of Axis for a while now, to become a committer so he can help us out with the Axis1 1.5 release. He's kindly volunteered to help pull together the release, and toward that end, we need him to be able to fix bugs and commit patches. Here's my +1. Thanks, --Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[jira] Created: (AXIS2-3343) JAX-WS Dispatch(Source) returns a StAXSource if JDK 6.0. StAXSource is not acceptable in many scenarios.
JAX-WS Dispatch(Source) returns a StAXSource if JDK 6.0. StAXSource is not acceptable in many scenarios. - Key: AXIS2-3343 URL: https://issues.apache.org/jira/browse/AXIS2-3343 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Rich Scheuerle Assignee: Rich Scheuerle History: The JAX-WS Dispatch(Source) implementation detects if StAXSource is available. StAXSource is not part of JDK 4.2 or JDK 5.0. However, StAXSource wraps a XMLStreamReader, so it seemed to be a performant alternative to StreamSource. Problem: JAXB, the main consumer of a Source in JAX-WS scenarios, does not support StAXSource. Other users have reported quality concerns with StAXSource. Solution: Quick change to the code to return the same Source (non-StAXSource) for all of the JDK versions. This promotes consistency. Kudos to Samuel Isokpunwu who collaborated with this solution. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3344) Performance: Synchronization of AbstractContext.addPropertyDifference degrades performance
Performance: Synchronization of AbstractContext.addPropertyDifference degrades
performance
--
Key: AXIS2-3344
URL: https://issues.apache.org/jira/browse/AXIS2-3344
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Rich Scheuerle
Assignee: Rich Scheuerle
Problem:
David Strite, a member of the IBM performance analysis team, discovered that
the synchronization of AbstractContext.addPropertDifference has a performance
impact due to the high volume of callers of AbstractContext.getProperty and
AbstractContext.setProperty.
Solution:
The synchronization is changed so that it is limited to the case where a
ClusterManager is available.
private void addPropertyDifference(String key) {
ConfigurationContext cc = getRootContext();
if (cc == null) {
return;
}
// Add the property differences only if Context replication is enabled,
// and there are members in the cluster
ClusterManager clusterManager =
cc.getAxisConfiguration().getClusterManager();
if (clusterManager == null ||
clusterManager.getContextManager() == null) {
return;
}
// Narrowed the synchronization so that we only wait
// if a property difference is added.
synchronized(this) {
propertyDifferences.put(key, new PropertyDifference(key, false));
}
}
Long Term Solution:
We might want to consider using a ConcurrentHashMap (only available in JDK 5+)
or narrow the synchronization for the other methods.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-3344) Performance: Synchronization of AbstractContext.addPropertyDifference degrades performance
[
https://issues.apache.org/jira/browse/AXIS2-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-3344.
---
Resolution: Fixed
Committed Revision 595293
Performance: Synchronization of AbstractContext.addPropertyDifference
degrades performance
--
Key: AXIS2-3344
URL: https://issues.apache.org/jira/browse/AXIS2-3344
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Rich Scheuerle
Assignee: Rich Scheuerle
Problem:
David Strite, a member of the IBM performance analysis team, discovered that
the synchronization of AbstractContext.addPropertDifference has a performance
impact due to the high volume of callers of AbstractContext.getProperty and
AbstractContext.setProperty.
Solution:
The synchronization is changed so that it is limited to the case where a
ClusterManager is available.
private void addPropertyDifference(String key) {
ConfigurationContext cc = getRootContext();
if (cc == null) {
return;
}
// Add the property differences only if Context replication is
enabled,
// and there are members in the cluster
ClusterManager clusterManager =
cc.getAxisConfiguration().getClusterManager();
if (clusterManager == null ||
clusterManager.getContextManager() == null) {
return;
}
// Narrowed the synchronization so that we only wait
// if a property difference is added.
synchronized(this) {
propertyDifferences.put(key, new PropertyDifference(key, false));
}
}
Long Term Solution:
We might want to consider using a ConcurrentHashMap (only available in JDK
5+) or narrow the synchronization for the other methods.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Preparing to get Axis 1.5 on track
+1 for a 1.5 release. Some time back I was talking about helping with running TCK compliance tests. But I'm not sure if the current TCK stuff that we have in axis-tck project are still valid for Axis 1.5. Dims, what are your thoughts on running the TCK again for Axis 1.x? Please let me know if you need my help in actual execution of these test chain and reporting results. - venkat On Nov 14, 2007 10:01 PM, Tom Jordahl [EMAIL PROTECTED] wrote: Awesome! +1 to getting a 1.5 release rolling. P.S. Yes, I am awake. -- Tom Jordahl Adobe -Original Message- From: Glen Daniels [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 14, 2007 11:29 AM To: Axis-Dev Subject: Preparing to get Axis 1.5 on track Axis-dev'ers: Greetings from ApacheCon! Bjorn Townsend and I just sat down and took a look at [1], with an eye towards getting started on a bugfix release for Axis 1. I would expect that 1.5 will be the final Axis1 release. I just created a 1.5 target in JIRA, and our next step is to target the JIRAs that Bjorn references to that. Then we get started on the actual work! :) Toward that end, I'm going to initiate a VOTE on a separate thread to grant Bjorn commit karma, since he's willing and able to get this train moving forward. So, please vote, please scan through JIRA and add to the list if you have things that aren't already represented, and please consider reviewing and committing some patches (hey Tom, you awake out there?)... Thanks, --Glen [1] http://wiki.apache.org/ws/FrontPage/Axis/Axis1%2e5ReleasePlan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Created: (AXIS2-3344) Performance: Synchronization of AbstractContext.addPropertyDifference degrades performance
Rich,
If ConcurrentHashMap is a better solution, you can use the backport
version which works on Java 1.4 and Java5. See
org.apache.axis2.util.CallbackReceiver for an example.
Cheers,
David
On 15/11/2007, Rich Scheuerle (JIRA) [EMAIL PROTECTED] wrote:
Performance: Synchronization of AbstractContext.addPropertyDifference
degrades performance
--
Key: AXIS2-3344
URL: https://issues.apache.org/jira/browse/AXIS2-3344
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Rich Scheuerle
Assignee: Rich Scheuerle
Problem:
David Strite, a member of the IBM performance analysis team, discovered that
the synchronization of AbstractContext.addPropertDifference has a performance
impact due to the high volume of callers of AbstractContext.getProperty and
AbstractContext.setProperty.
Solution:
The synchronization is changed so that it is limited to the case where a
ClusterManager is available.
private void addPropertyDifference(String key) {
ConfigurationContext cc = getRootContext();
if (cc == null) {
return;
}
// Add the property differences only if Context replication is
enabled,
// and there are members in the cluster
ClusterManager clusterManager =
cc.getAxisConfiguration().getClusterManager();
if (clusterManager == null ||
clusterManager.getContextManager() == null) {
return;
}
// Narrowed the synchronization so that we only wait
// if a property difference is added.
synchronized(this) {
propertyDifferences.put(key, new PropertyDifference(key, false));
}
}
Long Term Solution:
We might want to consider using a ConcurrentHashMap (only available in JDK
5+) or narrow the synchronization for the other methods.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
David Illsley - IBM Web Services Development
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3341) Marshaling arrays and lists seems to be wrong
[ https://issues.apache.org/jira/browse/AXIS2-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542785 ] Boris Georgiev commented on AXIS2-3341: --- I inspected the Axis2 1.3 source code, and I found that this is a strictly JAX-WS problem. All the jax-ws method marshallers (the one to inherit from MethodMarshaller) make the assumption that the webservice will return a single object (method marshalResponse). All of them create a single Element object from the return result (returnObject parameter of the method). The Element contains an array (or list) and that how it gets passed to the method MethodMarshallerUtils.toMessage. It retrieves a single JAXBElement, containing the array, which ultimately returns all the array element listed in a single XML elements. I will try to become a contributor and find what is the best way to fix the issue. Marshaling arrays and lists seems to be wrong - Key: AXIS2-3341 URL: https://issues.apache.org/jira/browse/AXIS2-3341 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.3, 1.2 Environment: JDK 1.5 and Geronimo 1.1 , also Websphere 6.1 Reporter: Boris Georgiev Attachments: jaxws-axis2.zip, return_messages.txt The problem seems to be about incorrect marshaling of arrays and lists. Looks like, for each element in the array is called the method toString(), then all of the array elements are separated by spaces and finally all the result is placed in a single xml element. As I see, according to the schema in the WSDL, every element of the array needs to be in its own element. Then, calling toString() may work for a simple type, it is completely meaningless for a complex types, as it is usually the string representation of the object's handle. I get the same result with or without response wrapper objects. I observe it for the return types, I have not tested it for arrays in the input paparameters. Can I use some other databinding mechanism, in order to avoid this and how? To demonstarate it, I have created a simple web service project. The service name is GenericService there are four methods, returning: array of string, array of a complex type, list of string and a list of a complex type. The attached file return_messages.txt contains the messages: as they are observed and as they need to be for arrays. For lists, the messages are the same. Te attached file jaxw-axis2.zip contains the sample geronimo/eclipse project, without the axis2 libraries. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Created: (AXIS2-3258) Extend Spring support to accept proxies
From where I can get those axis2-rmi-*.jar?I didn't find them in the latest nightly build iksrazal wrote: rmi is new, comming in after the 1.3 release. Try looking for axis2-rmi-*.jar and adding it to WEB-INF/lib . HTH, Robert On Nov 12, 2007 8:25 AM, BJuma [EMAIL PROTECTED] wrote: I downloaded the latest nightly build along with what I posted below and it works fine. However I am having an exception when the server is starting up which is: [exec] 17:25:51,287 ERROR org.apache.axis2.deployment.AxisConfigBuilder:319 - org.apache.axis2.rmi.deploy.RMIServiceDeployer [exec] java.lang.ClassNotFoundException: org.apache.axis2.rmi.deploy.RMIServiceDeployer [exec] at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318) [exec] at java.lang.ClassLoader.loadClass(ClassLoader.java:289) [exec] at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143) [exec] at java.lang.ClassLoader.loadClass(ClassLoader.java:235) [exec] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) [exec] at java.lang.Class.forName0(Native Method) [exec] at java.lang.Class.forName(Class.java:141) [exec] at org.apache.axis2.util.Loader.loadClass(Loader.java:261) [exec] at org.apache.axis2.deployment.AxisConfigBuilder.processDeployers(AxisConfigBuilder.java:316) [exec] at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:233) [exec] at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:628) [exec] at org.apache.axis2.deployment.WarBasedAxisConfigurator.init(WarBasedAxisConfigurator.java:146) [exec] at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:501) [exec] at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:421) [exec] at com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:2354) [exec] at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4795) [exec] at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4889) [exec] at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:1015) [exec] at com.evermind.server.http.HttpApplication.init(HttpApplication.java:549) [exec] at com.evermind.server.Application.getHttpApplication(Application.java:890) [exec] at com.evermind.server.http.HttpServer.getHttpApplication(HttpServer.java:707) [exec] at com.evermind.server.http.HttpSite.initApplications(HttpSite.java:625) [exec] at com.evermind.server.http.HttpSite.setConfig(HttpSite.java:278) [exec] at com.evermind.server.http.HttpServer.setSites(HttpServer.java:278) [exec] at com.evermind.server.http.HttpServer.setConfig(HttpServer.java:179) [exec] at com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2394) [exec] at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1551) [exec] at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:92) Any idea? iksrazal wrote: Hmm, the Service needs to be a concrete class, ie, have an implementation and not be just an interface. Any bean dependencies, such as for beans that have methods you invoke, have been known to work in some cases as interfaces by avoiding them be spring proxies. This particular problem is that there is no proxy class that This issue has come up several times before and have had solutions, please search the forums. HTH, Robert On Nov 12, 2007 5:47 AM, BJuma [EMAIL PROTECTED] wrote: Hi, I am facing this problem now. My understanding to fix it is by having an interface for the current webservice and defining it in the services.xml as a ServiceClass, like this: service name=SpringAwareService description simple spring example /description parameter name=ServiceClassspring.SpringAwareServiceInterface/parameter parameter name=ServiceObjectSupplierorg.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier/parameter parameter name=SpringBeanNamespringAwareService/parameter operation name=getValue messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation /service Is this sufficient? I tried it but not worked. Did I miss any thing or should I try certain fix build. Thanks, JIRA [EMAIL PROTECTED] wrote: Extend Spring support to accept proxies --- Key: AXIS2-3258 URL: https://issues.apache.org/jira/browse/AXIS2-3258 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: deployment, wsdl Affects Versions: 1.3
[jira] Resolved: (AXIS2-3343) JAX-WS Dispatch(Source) returns a StAXSource if JDK 6.0. StAXSource is not acceptable in many scenarios.
[ https://issues.apache.org/jira/browse/AXIS2-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle resolved AXIS2-3343. --- Resolution: Fixed Committed Revision 595329 JAX-WS Dispatch(Source) returns a StAXSource if JDK 6.0. StAXSource is not acceptable in many scenarios. - Key: AXIS2-3343 URL: https://issues.apache.org/jira/browse/AXIS2-3343 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Rich Scheuerle Assignee: Rich Scheuerle History: The JAX-WS Dispatch(Source) implementation detects if StAXSource is available. StAXSource is not part of JDK 4.2 or JDK 5.0. However, StAXSource wraps a XMLStreamReader, so it seemed to be a performant alternative to StreamSource. Problem: JAXB, the main consumer of a Source in JAX-WS scenarios, does not support StAXSource. Other users have reported quality concerns with StAXSource. Solution: Quick change to the code to return the same Source (non-StAXSource) for all of the JDK versions. This promotes consistency. Kudos to Samuel Isokpunwu who collaborated with this solution. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Help with AXIS2-3155, please.
Hello everyone, I have a very long outstanding bug in AXIOM, which I submitted as AXIS2-3155 almost 3 months ago. It is still unsassigned. Can someone please take a look at it? The link is here: https://issues.apache.org/jira/browse/AXIS2-3155 This is really causing problems on our end. I appreciate any help! -- View this message in context: http://www.nabble.com/Help-with-AXIS2-3155%2C-please.-tf4815269.html#a13775605 Sent from the Axis - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2931) CLONE -Web Service request loop causes many TIME_WAIT Connections BindException: Address already in use: connect
[
https://issues.apache.org/jira/browse/AXIS2-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542809
]
Tobias Jordan commented on AXIS2-2931:
--
I am sorry, but the issue still exists in 1.3. I tried to set the
AUTO_RELEASE_CONNECTION option in a blocking operations client (together with
REUSE_HTTP_CLIENT). This results in 'Attempted read on closed stream'
exceptions.
CLONE -Web Service request loop causes many TIME_WAIT Connections
BindException: Address already in use: connect
Key: AXIS2-2931
URL: https://issues.apache.org/jira/browse/AXIS2-2931
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.1.1, nightly
Environment: Windows XP, Tomcat, Axis2 nightly build (also
encountered in 1.1.1), JiBX 1.1.3, Microsoft Windows XP [Version 5.1.2600],
126 GB free disk space, 1GB RAM.
Reporter: Gerry Holly
Priority: Critical
I am performing the following:
- Executing a tight loop calling a singel web service
- Using the same Stub over and over
- Creating the Stub with a custom ConfigurationContext (see below)
- Sending cleanup() to Stub after each message sent (although problem existed
even before cleanup() was added)
After approximately 4000 messages have been sent, an AxisFault is generated
caused by the following exception (see below for full stack trace):
java.net.BindException: Address already in use: connect
It appears that connections from the client to Axis on Tomcat sometimes (but
not always) remain in the TIME_WAIT state for several minutes. There are
1200-1500 TIME_WAIT connections open when the AxisFault is generated.
If I step through the web service messages in a debugger, the problem does
not appear to occur, as the system eventually releases the connections after
a minute or two.
Also, if I insert a System.gc() in the client code each time it sends a
message to the web service (the commented out line of code below), the
AxisFault does not occur. I have executed the loop over 60,000 times with
the garbage collection included without generating an AxisFault. There were
only 400-700 connections in the TIME_WAIT state at a given time, but
performance slowed down to a crawl.
Here is the code I am using to create the Stub:
HttpConnectionManagerParams connectionManagerParams = new
HttpConnectionManagerParams();
connectionManagerParams.setTcpNoDelay(true);
connectionManagerParams.setStaleCheckingEnabled(true);
MultiThreadedHttpConnectionManager connectionManager = new
MultiThreadedHttpConnectionManager();
connectionManager.setParams(connectionManagerParams);
HttpClient httpClient = new HttpClient(connectionManager);
ConfigurationContext configurationContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(null,
null);
configurationContext.setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.TRUE);
configurationContext.setProperty(HTTPConstants.CACHED_HTTP_CLIENT,
httpClient);
stub = new MyServiceStub(configurationContext, target);
boolean success = true;
while(success) {
success = stub.performService(records);
stub.cleanup();
// System.gc();
}
Here is the complete stack trace:
Exception in thread main org.apache.axis2.AxisFault: Address already
in use: connect
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:377)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:179)
at
org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:73)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:310)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:202)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:446)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
at
com.ws.service.MyServiceStub.performService(MyServiceStub.java:300)
at com.ws.client.MyClient.main(MyClient.java:88)
Caused by: java.net.BindException: Address already in use: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at
[jira] Updated: (AXIS2-3345) Getting [ERROR] More than one part for message
[ https://issues.apache.org/jira/browse/AXIS2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Victor Ceban updated AXIS2-3345: Affects Version/s: 1.3 Getting [ERROR] More than one part for message -- Key: AXIS2-3345 URL: https://issues.apache.org/jira/browse/AXIS2-3345 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.3 Environment: axis 2-1.3 Reporter: Victor Ceban Attachments: RecruitmentOneStop.wsdl Can not generate java classes with attached wsdl file -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AXIS2 : problem in Logging in DEBUG mode
HI all, I want to enable logging in my server as well as client side. and i need to log it in a file so as per the instructions i did following changes in my 1. commons-logging.properties file # Uncomment the next line to enable log4j based logging org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger 2. And in log4j.properties file (both of this files atre present in webapps\WEB-INF\classes folder) # Set root category priority to INFO and its only appender to CONSOLE. #log4j.rootCategory=INFO, CONSOLE log4j.rootCategory=DEBUG, CONSOLE, LOGFILE #log4j.rootCategory=DEBUG, LOGFILE # Set the enterprise logger priority to FATAL log4j.logger.org.apache.axis2.enterprise=FATAL log4j.logger.de.hunsicker.jalopy.io=FATAL log4j.logger.httpclient.wire.header=FATAL log4j.logger.org.apache.commons.httpclient=FATAL # CONSOLE is set to be a ConsoleAppender using a PatternLayout. log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout log4j.appender.CONSOLE.layout.ConversionPattern=[%p] %m%n # LOGFILE is set to be a File appender using a PatternLayout. log4j.appender.LOGFILE=org.apache.log4j.FileAppender log4j.appender.LOGFILE.File=C:\axis2.log log4j.appender.LOGFILE.Append=true log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout log4j.appender.LOGFILE.layout.ConversionPattern=%d [%t] %-5p %c %x - %m%n the problem the logfile s never created at the location C:\axis2.log can sombody suggest me or give me a link to enable logging in AXIS2 1.3version on both client and server side. regards, Sushil
[jira] Updated: (AXIS2-3345) Getting [ERROR] More than one part for message
[ https://issues.apache.org/jira/browse/AXIS2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Victor Ceban updated AXIS2-3345: Attachment: RecruitmentOneStop.wsdl Getting [ERROR] More than one part for message -- Key: AXIS2-3345 URL: https://issues.apache.org/jira/browse/AXIS2-3345 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.3 Environment: axis 2-1.3 Reporter: Victor Ceban Attachments: RecruitmentOneStop.wsdl Can not generate java classes with attached wsdl file -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3346) problem in axis2 version service + internal server error prevents access to services/admin pages
problem in axis2 version service + internal server error prevents access to services/admin pages Key: AXIS2-3346 URL: https://issues.apache.org/jira/browse/AXIS2-3346 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: axis2-1.3 installed under geronimo (geronimo-tomcat6-jee5-2.0.2) web server on a linux rhe4 server. Reporter: Gurol Akman i copied the axis2-1.3.war file under the deploy directory of geronimo and this resulted in auto-deployment of the axis2 aplc. installation seemed to go well and i can access the axis2 happiness page through my browser. when i click on the validation link on the axis2 happiness page, all looks ok except i see the following complaints under 'examining version service' section on the page: there was a problem in axis2 version service, maybe the service not available or some thing has gone wrng. but that does not mean system is not working! try to upload some other service and check to see whether it is working. first of all, i don't know what i can do to alleviate this complaint. second, and more importantly, when i click on the 'services' or 'administration' links on the happiness page, i get an internal server error. hence, i cannot do much. how can i go about debugging and fixing the root cause of this problem? also, do you think these 2 problems (e.g., version related complaint and internal server error) are somewhat related? thanks for your help in advance -- ga -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3345) Getting [ERROR] More than one part for message
Getting [ERROR] More than one part for message -- Key: AXIS2-3345 URL: https://issues.apache.org/jira/browse/AXIS2-3345 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Environment: axis 2-1.3 Reporter: Victor Ceban Can not generate java classes with attached wsdl file -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
axis 1.4 and Basic Profile
Hi all, Does anyone know if Axis1.4 is Basic Profile 1.1 compliant? Thanks, --kumar
Re: axis 1.4 and Basic Profile
Hi Kumar, By basic profile I'm assuming you mean the WS-I basic profile. I don't think you can label a runtime as WS-I compliant as there are many things that you can do with Web services that are not recommended by the WS-I - that's why there is a WS-I - such as rpc encoded services and importing schemas in a WSDL document with the wsdl:import element. The real question when it comes to WS-I compliance is is service X WS-I compliant? If the service description and implementation follows the WS-I recommendations than it is compliant. Note that even if service X is compliant, service Y, which is deployed to the same runtime (Axis or otherwise), can be non-compliant. Lawrence Iyengar, Kumar [EMAIL PROTECTED] 11/15/2007 08:45 PM Please respond to axis-dev@ws.apache.org To axis-dev@ws.apache.org cc Subject axis 1.4 and Basic Profile Hi all, Does anyone know if Axis1.4 is Basic Profile 1.1 compliant? Thanks, --kumar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3345) Getting [ERROR] More than one part for message
[ https://issues.apache.org/jira/browse/AXIS2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542945 ] Amila Chinthaka Suriarachchi commented on AXIS2-3345: - for soap:body the attribute name is parts not part soapbind:body message=tns:JAFolderIn part=body use=literal/ it should be soapbind:body message=tns:JAFolderIn parts=body use=literal/ Getting [ERROR] More than one part for message -- Key: AXIS2-3345 URL: https://issues.apache.org/jira/browse/AXIS2-3345 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.3 Environment: axis 2-1.3 Reporter: Victor Ceban Attachments: RecruitmentOneStop.wsdl Can not generate java classes with attached wsdl file -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3345) Getting [ERROR] More than one part for message
[ https://issues.apache.org/jira/browse/AXIS2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Victor Ceban updated AXIS2-3345: Attachment: RecruitmentOneStop.wsdl Fixed the parts. Now getting this [ERROR] message part null not found in the WSDL org.apache.axis2.AxisFault: message part null not found in the WSDL any ideas ? Getting [ERROR] More than one part for message -- Key: AXIS2-3345 URL: https://issues.apache.org/jira/browse/AXIS2-3345 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.3 Environment: axis 2-1.3 Reporter: Victor Ceban Attachments: RecruitmentOneStop.wsdl, RecruitmentOneStop.wsdl Can not generate java classes with attached wsdl file -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3345) Getting [ERROR] More than one part for message
[ https://issues.apache.org/jira/browse/AXIS2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542968 ] Amila Chinthaka Suriarachchi commented on AXIS2-3345: - can you attach the whole stack trace and the other files ? Getting [ERROR] More than one part for message -- Key: AXIS2-3345 URL: https://issues.apache.org/jira/browse/AXIS2-3345 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.3 Environment: axis 2-1.3 Reporter: Victor Ceban Attachments: RecruitmentOneStop.wsdl, RecruitmentOneStop.wsdl Can not generate java classes with attached wsdl file -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Sanjaya Karunasena as an Axis2 commiter
+1 Saminda On Nov 15, 2007 3:17 PM, Lahiru Sandakith [EMAIL PROTECTED] wrote: +1 Thanks Sandakith On Nov 13, 2007 12:00 AM, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi all, Sanjaya Karunasena has done enough work to become as a commiter , he has implemented fastinforset [FI] support in Axis2. And giving he commiter access will encourage him to contribute some more to the project and will make our job easier [no need to commit the patches]. Here my +1 for Sanjaya as an Axis2 commiter. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F -- Saminda Abeyruwan Senior Software Engineer WSO2 Inc. - www.wso2.org
