[jira] Resolved: (AXIS2C-444) Add a fault handling sample to show how to deal with SOAP faults
[ https://issues.apache.org/jira/browse/AXIS2C-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-444. -- Resolution: Fixed Google sample now has some fault handling logic that can serve this purpose Add a fault handling sample to show how to deal with SOAP faults Key: AXIS2C-444 URL: https://issues.apache.org/jira/browse/AXIS2C-444 Project: Axis2-C Issue Type: Improvement Components: samples Affects Versions: 0.95 Reporter: Samisa Abeysinghe Assigned To: Samisa Abeysinghe Fix For: 1.0.0 We should add a sample to show how to deal with SOAP faults. We do not have any such sample as of now. Something similar to faulthandling in Axis2/Java samples -- 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-444) Add a fault handling sample to show how to deal with SOAP faults
[ https://issues.apache.org/jira/browse/AXIS2C-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-444: Assignee: Samisa Abeysinghe (was: Sanjaya Ratnaweera) Add a fault handling sample to show how to deal with SOAP faults Key: AXIS2C-444 URL: https://issues.apache.org/jira/browse/AXIS2C-444 Project: Axis2-C Issue Type: Improvement Components: samples Affects Versions: 0.95 Reporter: Samisa Abeysinghe Assigned To: Samisa Abeysinghe Fix For: 1.0.0 We should add a sample to show how to deal with SOAP faults. We do not have any such sample as of now. Something similar to faulthandling in Axis2/Java samples -- 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: next release / open jiras
Thanks Nadir! Franz Nadir Amra schrieb: Franz, Still trying to learn about the release process. Unless someone with experience volunteers to be release manager, I have to figure this out and it will take some time - and I am very busy with other work so I guess I cannot commit to anything right now except to say I am trying to see what it would take to produce a candidate release. Then I will go through the process. I do not think AxisCPP will be dead after 1.6 is released. We will still be supporting it. So you will still see releases assuming significant fixes are put in. I think the big ticket item is support for SOAP 1.2, which I plan on doing. I hope to fix/investigate the following for 1.6: AXISCPP-543 Have some comments in generated code explaining what is going on AXISCPP-623 Support for the WSDL construct all AXISCPP-888 Deserializer does give any indication of error when tags not in the WSDL are encountered. AXISCPP-989 Memory leak in Clients after arrays are serialized AXISCPP-1014 incorrect handling of xsd:decimal due to missing code I also hoped to revamp tracing support, but that is probably wishful thinking at this point for release 1.6. Nadir K. Amra Franz Fehringer [EMAIL PROTECTED] wrote on 03/20/2007 07:11:45 AM: Hello Nadir, What are your current 1.6 release prospects? Do you have a tentative timeline first for a release candidate and then a real release? Will AXISCPP (given the advent of AXISC) be dead after 1.6 or can we expect 1.6.1 or even (gasp) 1.7? Which JIRAs do you plan to work on before 1.6? What about AXISCPP-1014 for example? Cheers and thanks for your good work Franz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Franz Fehringer (Dipl. Math.) Projektleiter Touristik-Systeme ISO Software Systeme GmbH Eichendorffstrasse 29 90491 Nürnberg Germany Tel.: +49/(911) - 99594-0 mailto:[EMAIL PROTECTED] http://www.isogmbh.de Amtsgericht Nürnberg HRB 18299 Geschäftsführer: Dipl.-Inform., Dipl.-Kaufm. Harald Goeb Sitz: Nürnberg begin:vcard fn:Dr. Franz Fehringer n:Fehringer;Franz org:ISO Software Systeme adr;quoted-printable:;;Eichendorffstrasse 29;N=C3=BCrnberg;;90491;Deutschland email;internet:mailto:[EMAIL PROTECTED] tel;work:+49/(911) - 99594-0 tel;fax:+49/(911) - 99594-580 x-mozilla-html:TRUE url:http://www.isogmbh.de/ version:2.1 end:vcard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2C-292) Inconsistent use of prefixes in util subproject
[ https://issues.apache.org/jira/browse/AXIS2C-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484081 ] Sanjaya Ratnaweera commented on AXIS2C-292: --- I think axutil is a better prefix for util subproject. Any comment? Inconsistent use of prefixes in util subproject --- Key: AXIS2C-292 URL: https://issues.apache.org/jira/browse/AXIS2C-292 Project: Axis2-C Issue Type: Improvement Components: util Affects Versions: 0.94 Reporter: James Clark Assigned To: Sanjaya Ratnaweera Priority: Minor Fix For: 1.0.0 It seems inconsitent that the util subproject should have use the same prefix for its include files and for its symbols as the main axis2 modules. We have the main axis2 stuff (which uses an axis2 prefix) which depends on axiom (which uses an axiom prefix) which depends on util (which uses a ... axis2 prefix). The util directory ought to use its own prefix (axutil or wsutil or something like that). -- 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: (AXIS2C-292) Inconsistent use of prefixes in util subproject
[ https://issues.apache.org/jira/browse/AXIS2C-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484091 ] Nandika Jayawardana commented on AXIS2C-292: In addition to changing the prefix, AXIS2_CALL , AXIS2_EXTERN, AXIS2_IMPORT etc should be changed to corresponding project's prefix. This is required not only for consistancy, but also when exporting and importing functions from dlls on windows , this is necessary. Inconsistent use of prefixes in util subproject --- Key: AXIS2C-292 URL: https://issues.apache.org/jira/browse/AXIS2C-292 Project: Axis2-C Issue Type: Improvement Components: util Affects Versions: 0.94 Reporter: James Clark Assigned To: Sanjaya Ratnaweera Priority: Minor Fix For: 1.0.0 It seems inconsitent that the util subproject should have use the same prefix for its include files and for its symbols as the main axis2 modules. We have the main axis2 stuff (which uses an axis2 prefix) which depends on axiom (which uses an axiom prefix) which depends on util (which uses a ... axis2 prefix). The util directory ought to use its own prefix (axutil or wsutil or something like that). -- 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-498) Axiom OM structure built is inconsistent with the original xml document in certain cases where the default namespace is set to the empty namespace
[ https://issues.apache.org/jira/browse/AXIS2C-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-498. -- Resolution: Fixed Someone has applied the given patch Axiom OM structure built is inconsistent with the original xml document in certain cases where the default namespace is set to the empty namespace -- Key: AXIS2C-498 URL: https://issues.apache.org/jira/browse/AXIS2C-498 Project: Axis2-C Issue Type: Bug Components: xml/om Affects Versions: Current (Nightly) Reporter: Dumindu Pallewela Fix For: 1.0.0 Attachments: patch-498 When the default namespace is is set to the empty namespace as follows (in element c) it is ignored while building the OM structure. Therefore in the following case the built OM structure says element c's namespace is the same as element b's namespace. a xmlns= b xmlns=urn:def c xmlns= /c /b /a I.e., the built OM structure represents the following, which is different to the original XML document: a b xmlns=urn:def c /c /b /a However, it should be noted that in the following case where we do not specifically mention that element a's namespace as the empty namespace; the built OM structure properly represents element c as an unqualified element with the empty namespace. a b xmlns=urn:def c xmlns= /c /b /a -- 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-564) Issues in the Axis2-C Installation Guide - Installing and Running on Microsoft Windows (win32)
Issues in the Axis2-C Installation Guide - Installing and Running on Microsoft Windows (win32) -- Key: AXIS2C-564 URL: https://issues.apache.org/jira/browse/AXIS2C-564 Project: Axis2-C Issue Type: Bug Components: documentation Environment: Windows XP Reporter: Evanthika Amarasiri The following issues were found in the Installation Guide under the heading Installing and Running on Microsoft Windows (win32) === 1. In the Axis2-C Installation Guide, under the heading 2. Installing and Running on Microsoft Windows (win32) it asks the user to download libxml but it does not say which version to download. When you go to the relevant site, you can see several versions of libxml. E.g. - LATEST_LIBXML2, LATEST_LIBXML2_IS_2.6.27, LATEST_LIBXSLT, LATEST_LIBXSLT_IS_1.1.20. Therefore, it should clearly state which version to download 2. In the Axis2-C Installation Guide under the heading Using Binary Release it says that you can download Microsoft VSExpress2005 edition from the Microsoft Web site. It's better if you can give the site here. (It's true that you can google it and find out but it's good if you can specify the correct link to download Microsoft VSExpress2005. E.g.:- Specify the correct download page) 3. In the Axis2-C Installation Guide, no paths are specified as to where you can download the latest source and binary distributions. Appropriate links should be given in the relevant places E.g.:- Specify the axis2 download page - http://ws.apache.org/axis2/c/download.cgi 4. The path where the configure.in is located is not given (2. 2. Using The Source Release 2.2.3. Editing configure.in File). When you search for the particular file, it gives 4 instances. Therefore, the document should clearly specify, which file the user should refer. 5. Under the heading 2.2.4. Compiling The Source it asks the user to run the vcvars32.bat file but no such file exists in the source distribution (Assuming that it is in the source distribution). But the problem is I cannot find the vcvars32.bat file. Then I realised that this file resides in the VS installation folder. E.g.:- C:\Program Files\Microsoft Visual Studio 8\VC\bin. This is confusing to the user. The correct path of the vcvars32.bat have to be specified clearly. 6. The document states build the system and create a directory named deploy under build directory: What I understand by this is that you have to build the source first and then have to create a folder called deploy. What it should mean is that when you build the source, a folder named deploy will be created. Please rephrase this. 7. Under the heading 2. 2. Using The Source Release, first is asks the user to edit the configure.in file which is inside the source distribution and then as the next step it asks the user to extract the source distribution to a folder of choice, etc. How can you edit the file which is inside the source distribution without extracting it first? Therefore first it should ask the user to extract the source and then only it should ask the user to edit the particular file. Please rephrase. 8. Minor Issue - Under the heading 2.2.3. Editing configure.in File, it says that the default location for libxml2 is C:\libxml2 but when you check the file you will see that the path specified in the file is E:\libxml2-2.6.23.win32. This might be a bit confusing to the user. Therefore, the document should be replaced with the correct path. 9. Under the heading 2.2.3. Editing configure.in File it should also state that the paths for iconv and zlib1 should also be replaced with the correct paths. -- 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-503) Provide Makefile and vc projects for samples in win32-bin
[ https://issues.apache.org/jira/browse/AXIS2C-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dushshantha Chandradasa closed AXIS2C-503. -- Resolution: Fixed I have added vc projects and nmake files for the saples we are shipping with win32 binary distribution. Provide Makefile and vc projects for samples in win32-bin - Key: AXIS2C-503 URL: https://issues.apache.org/jira/browse/AXIS2C-503 Project: Axis2-C Issue Type: Task Components: build system (Windows) Affects Versions: 0.96 Environment: Windows Reporter: Nabeel Yoosuf Assigned To: Dushshantha Chandradasa Priority: Minor Fix For: 1.0.0 At present, the win32-bin distribution does not provide any assistance on building samples. It'd be helpful to provide the Makefile and vc projects for samples. -- 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-506) proxy doesn't work with REST client
[ https://issues.apache.org/jira/browse/AXIS2C-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-506. Resolution: Fixed After refactoring transport, this issue is fixed. Now proxy work for both SOAP and REST. Tested with googele client and yahoo search client through a proxy. proxy doesn't work with REST client --- Key: AXIS2C-506 URL: https://issues.apache.org/jira/browse/AXIS2C-506 Project: Axis2-C Issue Type: Bug Components: core/transport, transport/http Affects Versions: 0.96 Reporter: Dinesh Premalal Assigned To: Dinesh Premalal Fix For: 1.0.0 Tried bothe google sample and yahoo search sample through a proxy server. First edit proxy host and port in axis2.xml and then execute google and yahoo samples. Google client invocation successful where as yahoo client failed. -- 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-497) Wrong content type doesn't give proper fault
[ https://issues.apache.org/jira/browse/AXIS2C-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal reassigned AXIS2C-497: -- Assignee: Dinesh Premalal Wrong content type doesn't give proper fault Key: AXIS2C-497 URL: https://issues.apache.org/jira/browse/AXIS2C-497 Project: Axis2-C Issue Type: Bug Components: core/transport Affects Versions: 0.96 Reporter: Dinesh Premalal Assigned To: Dinesh Premalal Fix For: 1.0.0 for request with wrong content type , simple axis server doesn't give proper soap fault. request POST /axis2/services/echo HTTP/1.1 User-Agent: Axis2/C Content-Length: 108 Content-Type: application/TEST123 Host: 127.0.0.1:9090 ns1:echoString xmlns:ns1=http://ws.apache.org/axis2/c/samples; textHello World !/text/ns1:echoString response -- HTTP/1.1 500 Internal Server Error Content-Type: application/soap+xml;charset=UTF-8 Content-Length: 194 ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header/soapenv:Header soapenv:Body/soapenv:Body /soapenv:Envelope -- 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: (AXIS2C-497) Wrong content type doesn't give proper fault
[ https://issues.apache.org/jira/browse/AXIS2C-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484180 ] Dinesh Premalal commented on AXIS2C-497: Do we need to send SOAPFault for this occasion, Since this is a transport level error we can choose default Content-Type and go ahead or we can send transport level (HTTP) error message. What would be the correct approach ? Wrong content type doesn't give proper fault Key: AXIS2C-497 URL: https://issues.apache.org/jira/browse/AXIS2C-497 Project: Axis2-C Issue Type: Bug Components: core/transport Affects Versions: 0.96 Reporter: Dinesh Premalal Assigned To: Dinesh Premalal Fix For: 1.0.0 for request with wrong content type , simple axis server doesn't give proper soap fault. request POST /axis2/services/echo HTTP/1.1 User-Agent: Axis2/C Content-Length: 108 Content-Type: application/TEST123 Host: 127.0.0.1:9090 ns1:echoString xmlns:ns1=http://ws.apache.org/axis2/c/samples; textHello World !/text/ns1:echoString response -- HTTP/1.1 500 Internal Server Error Content-Type: application/soap+xml;charset=UTF-8 Content-Length: 194 ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header/soapenv:Header soapenv:Body/soapenv:Body /soapenv:Envelope -- 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: (AXIS2C-521) in desc_builder_process_params parent param is null checked.
[ https://issues.apache.org/jira/browse/AXIS2C-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484182 ] Dinesh Premalal commented on AXIS2C-521: Damitha, If you could provide bit clarification on this issue, That will be helpful and much appreciated. in desc_builder_process_params parent param is null checked. Key: AXIS2C-521 URL: https://issues.apache.org/jira/browse/AXIS2C-521 Project: Axis2-C Issue Type: Bug Reporter: Damitha Kumarage Assigned To: Damitha Kumarage in desc_builder_process_params parent parameter is AXIS2_PARAM_CHECKed. But this is fault since parent parameter can be NULL and inside the code it is NULL check where it is necessary. -- 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: (AXIS2C-497) Wrong content type doesn't give proper fault
[ https://issues.apache.org/jira/browse/AXIS2C-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484263 ] Samisa Abeysinghe commented on AXIS2C-497: -- I think choosing default Content-Type and going ahead would be fine Wrong content type doesn't give proper fault Key: AXIS2C-497 URL: https://issues.apache.org/jira/browse/AXIS2C-497 Project: Axis2-C Issue Type: Bug Components: core/transport Affects Versions: 0.96 Reporter: Dinesh Premalal Assigned To: Dinesh Premalal Fix For: 1.0.0 for request with wrong content type , simple axis server doesn't give proper soap fault. request POST /axis2/services/echo HTTP/1.1 User-Agent: Axis2/C Content-Length: 108 Content-Type: application/TEST123 Host: 127.0.0.1:9090 ns1:echoString xmlns:ns1=http://ws.apache.org/axis2/c/samples; textHello World !/text/ns1:echoString response -- HTTP/1.1 500 Internal Server Error Content-Type: application/soap+xml;charset=UTF-8 Content-Length: 194 ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header/soapenv:Header soapenv:Body/soapenv:Body /soapenv:Envelope -- 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-170) Compact the if blocks into one if block in create_dll method so that the lib is loaded into a void object.
[ https://issues.apache.org/jira/browse/AXIS2C-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-170: Assignee: Samisa Abeysinghe (was: Damitha Kumarage) Compact the if blocks into one if block in create_dll method so that the lib is loaded into a void object. -- Key: AXIS2C-170 URL: https://issues.apache.org/jira/browse/AXIS2C-170 Project: Axis2-C Issue Type: Improvement Components: util Affects Versions: 0.92 Environment: all platforms Reporter: Damitha Kumarage Assigned To: Samisa Abeysinghe Priority: Minor Fix For: 1.0.0 Compact the if blocks into one if block in create_dll method so that the lib is loaded into a void object. Currently the only difference between different if blocks is in the difference in error code. Try to set the error code in dll_desc and get the error code from there in a single if block -- 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-170) Compact the if blocks into one if block in create_dll method so that the lib is loaded into a void object.
[ https://issues.apache.org/jira/browse/AXIS2C-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-170. -- Resolution: Fixed Removed unwanted if blocks Compact the if blocks into one if block in create_dll method so that the lib is loaded into a void object. -- Key: AXIS2C-170 URL: https://issues.apache.org/jira/browse/AXIS2C-170 Project: Axis2-C Issue Type: Improvement Components: util Affects Versions: 0.92 Environment: all platforms Reporter: Damitha Kumarage Assigned To: Samisa Abeysinghe Priority: Minor Fix For: 1.0.0 Compact the if blocks into one if block in create_dll method so that the lib is loaded into a void object. Currently the only difference between different if blocks is in the difference in error code. Try to set the error code in dll_desc and get the error code from there in a single if block -- 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-565) Issues in the Axis2-C Installation Guide - Installing Apache2 Web Server Integration Module (mod_axis2)
Issues in the Axis2-C Installation Guide - Installing Apache2 Web Server Integration Module (mod_axis2) --- Key: AXIS2C-565 URL: https://issues.apache.org/jira/browse/AXIS2C-565 Project: Axis2-C Issue Type: Bug Components: documentation Environment: Windows XP Reporter: Evanthika Amarasiri The following issues were found in the Installation Guide under the heading Installing Apache2 Web Server Integration Module (mod_axis2) 1. Under the heading 3.1.2 On Win32 Platform it says Provide the apache2 location in configure.in file in APACHE_INSTALL_DIR. Since there were no such tag in the configure.in file, I added a variable called APACHE_INSTALL_DIR and it gave an error. What it actually expects is to replace the path given for APACHE_BIN_DIR with the correct Apache2 location 2. The guide states After compiling the sources (As described in Section 2) build the mod_axis2.dll by issuing the command nmake axis2_apache_module. From which folder should you build this from? The location should be specified clearly 3. The guide does not mention that the user should install Apache2. Better if the guide can provide a link to the download page of Apache2. 4. Everytime a new console window opens the vcvars32.bat file should be executed before executing the command nmake axis2_apache_module, but this is not mentioned anywhere in the guide 5. In Windows when you installl Apache2 into a folder with spaces and when trying to build the mod_axis2.dll using the command nmake axis2_apache_module you get an error. This is solved when Apache2 is installed to a folder without spaces. Please mention about this in the guide 6. As per Buddhika you need super user priviledges to install Apache2 on Linux but this is not mentioned under 3.1. Building mod_axis2 From Source Tree. So please add this as well Under 3.2. Deploying in Apache2 Web Server it says that the user has to have super user priviledges. What does it mean by Super user previledges here? In windows that the user has to have Administrative rights? Or does this apply only for Linux? A brief explanation is needed here. 7. Cannot start the Apache2 server. An error is given saying that there is a syntax error in the httpd.conf file. I have added all the things that the Installation guide has given. When I start the Apache2 server I get the following error. *** The Apache service named reported the following error: httpd.exe: Syntax error on line 115 of C:/Apache2.2/conf/httpd.conf: LoadModule takes two arguments, a module name and the name of a shared object file to load it from. *** What is given in the Installation Guide LoadModule axis2_module apache2 modules directory/mod_axis2.so Axis2RepoPath axis2 repository path Axis2LogFile axis2 log file path Axis2LogLevel LOG_LEVEL Location /axis2 SetHandler axis2_module /Location What I have specified in the httpd.conf file LoadModule C:/Apache2.2/modules/mod_axis2.so Axis2RepoPath C:/WSO2/WSO2-Releases/Axis2_C Axis2LogFile C:/WSO2/WSO2-Releases/Axis2_C/build/deploy/logs Axis2LogLevel AXIS2_LOG_LEVEL_DEBUG Location /axis2 SetHandler axis2_module /Location 8. Under 3.2. Deploying in Apache2 Web Server it says that the Apache2 user should have read permission to the repository and write permission to the log file. I think this applies only for Linux. Please specify clearly -- 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-566) The link here is directed to a location which does not exist.Axis2/C Installation Guide
The link here is directed to a location which does not exist.Axis2/C Installation Guide - Key: AXIS2C-566 URL: https://issues.apache.org/jira/browse/AXIS2C-566 Project: Axis2-C Issue Type: Bug Reporter: Evanthika Amarasiri -- 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-567) The link here of the Axis2/C Installation Guide is directed to a file which does not exist.
The link here of the Axis2/C Installation Guide is directed to a file which does not exist. --- Key: AXIS2C-567 URL: https://issues.apache.org/jira/browse/AXIS2C-567 Project: Axis2-C Issue Type: Bug Components: documentation Environment: Windows XP Reporter: Evanthika Amarasiri In the Axis2/C Installation Guide the link here given in the sentence To subscribe to developer mailing list see here is directed to a file which does not exist ** File not found Firefox can't find the file at /C:/WSO2/WSO2-Releases/Axis2_C/xdocs/mail-lists.html. ** Please specify the correct link location here -- 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-257) free methods should return void not axis2_status_t
[ https://issues.apache.org/jira/browse/AXIS2C-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-257: Assignee: Samisa Abeysinghe (was: Sanjaya Ratnaweera) free methods should return void not axis2_status_t -- Key: AXIS2C-257 URL: https://issues.apache.org/jira/browse/AXIS2C-257 Project: Axis2-C Issue Type: Improvement Affects Versions: Current (Nightly) Reporter: Samisa Abeysinghe Assigned To: Samisa Abeysinghe Fix For: 1.0.0 Although the allocator free method returns void, you've made the free methods of objects return an axis2_status_t. However, your code almost always seems to ignore the returned status. Either a) free methods should return a status and all callers should always check it and deal with, or b) free methods should return void I would suggest (b). There's nothing useful you can do with an error from a free method, and there's no need for the user supplied free function to return an error. The situation where free might need to generate an error are the case where memory has got corrupted through programmer error, but a return code isn't the right way to deal wit this situation. (based on comments by James) -- 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: (AXIS2C-557) WSDL2C: generated adb code does not allow any elements to be omitted - too inflexible
[
https://issues.apache.org/jira/browse/AXIS2C-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484318
]
Milinda Lakmal Pathirage commented on AXIS2C-557:
-
Thanks for the explanation. I'll look into this issue.
WSDL2C: generated adb code does not allow any elements to be omitted - too
inflexible
-
Key: AXIS2C-557
URL: https://issues.apache.org/jira/browse/AXIS2C-557
Project: Axis2-C
Issue Type: Bug
Components: code generation
Affects Versions: Current (Nightly)
Environment: Windows XP
Reporter: Dave Meier
Attachments: test2.wsdl
I am using WSDL2C with adb data binding.
The code that is generated requires all elements specified in the WSDL for a
given web service call to be present. It should instead check the name of
each node and allow some data elements to be omitted.
Instead it generates code like the following, where it assumes the next node
is the node it expects. It should check the name of the node and skip to the
next expected node if the name does not match:
/**
* because elements are ordered this
works fine
*/
if( current_node != NULL)
{
current_node =
AXIOM_NODE_GET_NEXT_SIBLING( current_node, env);
}
if ( current_node != NULL)
{
current_element = AXIOM_NODE_GET_DATA_ELEMENT(
current_node, env);
text_value =
AXIOM_ELEMENT_GET_TEXT(current_element, env, current_node );
Here it blindly gets the text_value and sets it into the field that it
expects the value to be for. This means that all the nodes must be present
or it will set the wrong values in the fields. So if new arguments are
added to an object passed in the call, it will no longer be backwards
compatible with clients that are using the older version of the WSDL.
--
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-568) Issues in the Axis2/C Manual - Quick Start Guide
Issues in the Axis2/C Manual - Quick Start Guide Key: AXIS2C-568 URL: https://issues.apache.org/jira/browse/AXIS2C-568 Project: Axis2-C Issue Type: Bug Components: documentation Environment: Windows XP Reporter: Evanthika Amarasiri The following issues were found in the Installation Guide under the heading Installing Apache2 Web Server Integration Module (mod_axis2) 1. Minor Issue - Under the heading 1. Quick Start Guide, the sentence First download the latest binary release form Apache Axis2/C download page. is broken into two and the download page part is displayed as a seperate paragraph. Make this a single sentence. 2. After compiling the service class, it seems that you have to link it using the command link.exe /nologo /LIBPATH:. in order to created the .dll file but steps to generate the .dll file is not mentioned in the document. Please add this. 3. Before compiling the service class, if you do not run the vcvars32.bat file, you will get an error. Therefore, the guide should mention that you should run this bat file before you compile the service class. 4. The command given to compile the service class is wrong. As per Dushyantha it should be corrected as, cl.exe /D WIN32 /D _WINDOWS /D _MBCS/DAXIS2_DECLARE_EXPORT /D AXIS2_SVR_MULTI_THREADED /w /nologo /I $(AXIS2_INCLUDE_PATH) /I $(APACHE_INCLUDE_PATH) hello.c (/I should be added before $(AXIS2_INCLUDE_PATH) and $(APACHE_INCLUDE_PATH) and /I given before hello.c should be removed) Please update the guide with the correct command -- 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]
