Axis2/C subversion repository disappeared?
Hi, I can't access the SVN repositort of Axis2/C since yesterday. $ LANG=C svn checkout http://svn.apache.org/repos/asf/webservices/axis2/trunk/c axis2c.svn svn: URL 'http://svn.apache.org/repos/asf/webservices/axis2/trunk/c' doesn't exist It looks like the whole axis2/trunk directory disappeared from the server: see http://svn.apache.org/repos/asf/webservices/axis2/trunk/ Olivier Mengué.
Re: Axis2/C subversion repository disappeared?
Yeah, I can't access it either!! Regards Søren 2010/2/19 Olivier Mengué omen...@oxymel.com Hi, I can't access the SVN repositort of Axis2/C since yesterday. $ LANG=C svn checkout http://svn.apache.org/repos/asf/webservices/axis2/trunk/c axis2c.svn svn: URL 'http://svn.apache.org/repos/asf/webservices/axis2/trunk/c'http://svn.apache.org/repos/asf/webservices/axis2/trunk/c%27doesn't exist It looks like the whole axis2/trunk directory disappeared from the server: see http://svn.apache.org/repos/asf/webservices/axis2/trunk/ Olivier Mengué. -- Med venlig hilsen/Best regards Søren H. Berggreen
[jira] Created: (AXIS2C-1452) Memory leak in axis2_engine_send
Memory leak in axis2_engine_send Key: AXIS2C-1452 URL: https://issues.apache.org/jira/browse/AXIS2C-1452 Project: Axis2-C Issue Type: Bug Components: core/engine Affects Versions: 1.6.0 Environment: Windows XP, Visual Studio 2008 Reporter: Kalin Rashev Hi guys, I found a memory leak, which is pretty annoyng to me. It is small, but my applications runs really long time, and it sends frequent requests. I'm developing under windows and I'm using a nice memory leak tool, called Visual Leak Detector. Here is the Visual Leak Detector stacktrace report: d:\workspaces\toptapi\cti-build-setups\axis2c-src-1.6.0\util\src\allocator.c (75): axutil_allocator_malloc_impl d:\workspaces\toptapi\cti-build-setups\axis2c-src-1.6.0\util\src\stream.c (86): axutil_stream_create_internal d:\workspaces\toptapi\cti-build-setups\axis2c-src-1.6.0\util\src\stream.c (510): axutil_stream_create_socket 0x01021760 (File and line number not available): (Function name unavailable) 0x01024D65 (File and line number not available): (Function name unavailable) 0x0102B66A (File and line number not available): (Function name unavailable) 0x0102A9A5 (File and line number not available): (Function name unavailable) d:\workspaces\toptapi\cti-build-setups\axis2c-src-1.6.0\src\core\engine\engine.c (176): axis2_engine_send d:\workspaces\toptapi\cti-build-setups\axis2c-src-1.6.0\src\core\clientapi\op_client.c (1171): axis2_op_client_two_way_send d:\workspaces\toptapi\cti-build-setups\axis2c-src-1.6.0\src\core\clientapi\op_client.c (508): axis2_op_client_execute d:\workspaces\toptapi\cti-build-setups\axis2c-src-1.6.0\src\core\clientapi\svc_client.c (733): axis2_svc_client_send_receive_with_op_qname The (Function name unavailable) is actually a macro, that's why it can't find the stacktrace. It is in line 176: status = AXIS2_TRANSPORT_SENDER_INVOKE(transport_sender, env, msg_ctx); This macro actually allocates memory for an axutil_stream_t *stream in axis2c-src-1.6.0\util\src\stream.c (510): axutil_stream_create_socket function. This stream is never freed. Could you add the call to axutil_stream_free(...) where appropriate? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE : Axis2/C subversion repository disappeared?
The new reository seems to be there:
http://svn.apache.org/repos/asf/axis/axis2/c/core/trunk
Could someone update the web site?
http://ws.apache.org/axis2/c/lists_issues.html
When will the mailing list address change?
Olivier Mengué
Message d'origine
De: Olivier Mengué [mailto:omen...@oxymel.com]
Date: ven. 19/02/2010 11 h 08
À: Apache AXIS C Developers List; axis-c-dev@ws.apache.org
Objet : RE : Axis2/C subversion repository disappeared?
I did more investigation:
$ svn log '-r{2010-02-13}:HEAD'
http://svn.apache.org/repos/asf/webservices/axis2/trunk/
r909680 | gmcdonald | 2010-02-13 02:30:58 +0100 (Sat, 13 Feb 2010) | 1 line
Moving axis svn, part of TLP move INFRA-2441
r909681 | gmcdonald | 2010-02-13 02:32:03 +0100 (Sat, 13 Feb 2010) | 1 line
Moving axis svn, part of TLP move INFRA-2441
According to the issue https://issues.apache.org/jira/browse/INFRA-2441
it looks like that was a planned move.
Isn't the axis-c-dev mailing list the right place for such announcements?
Olivier Mengué
Message d'origine
De: Olivier Mengué [mailto:omen...@oxymel.com]
Date: ven. 19/02/2010 10 h 53
À: axis-c-dev@ws.apache.org
Objet : Axis2/C subversion repository disappeared?
Hi,
I can't access the SVN repositort of Axis2/C since yesterday.
$ LANG=C svn checkout http://svn.apache.org/repos/asf/webservices/axis2/trunk/c
axis2c.svn
svn: URL 'http://svn.apache.org/repos/asf/webservices/axis2/trunk/c' doesn't
exist
It looks like the whole axis2/trunk directory disappeared from the server: see
http://svn.apache.org/repos/asf/webservices/axis2/trunk/
Olivier Mengué.
winmail.dat
Re: RE : Axis2/C subversion repository disappeared?
The repository can now be found at:
http://svn.apache.org/repos/asf/axis/axis2/c/core/trunk/
Regards
Søren
On Fri, Feb 19, 2010 at 11:08 AM, Olivier Mengué omen...@oxymel.com wrote:
I did more investigation:
$ svn log '-r{2010-02-13}:HEAD'
http://svn.apache.org/repos/asf/webservices/axis2/trunk/
r909680 | gmcdonald | 2010-02-13 02:30:58 +0100 (Sat, 13 Feb 2010) | 1 line
Moving axis svn, part of TLP move INFRA-2441
r909681 | gmcdonald | 2010-02-13 02:32:03 +0100 (Sat, 13 Feb 2010) | 1 line
Moving axis svn, part of TLP move INFRA-2441
According to the issue https://issues.apache.org/jira/browse/INFRA-2441
it looks like that was a planned move.
Isn't the axis-c-dev mailing list the right place for such announcements?
Olivier Mengué
Message d'origine
De: Olivier Mengué [mailto:omen...@oxymel.com omen...@oxymel.com]
Date: ven. 19/02/2010 10 h 53
À: axis-c-dev@ws.apache.org
Objet : Axis2/C subversion repository disappeared?
Hi,
I can't access the SVN repositort of Axis2/C since yesterday.
$ LANG=C svn checkout
http://svn.apache.org/repos/asf/webservices/axis2/trunk/c axis2c.svn
svn: URL
'http://svn.apache.org/repos/asf/webservices/axis2/trunk/c'http://svn.apache.org/repos/asf/webservices/axis2/trunk/c%27doesn't
exist
It looks like the whole axis2/trunk directory disappeared from the server:
see http://svn.apache.org/repos/asf/webservices/axis2/trunk/
Olivier Mengué.
--
Med venlig hilsen/Best regards
Søren H. Berggreen
Re: Linker error
Hi Problem solved. The libraries used were VC++ compiled and therefore could not be used with MinGW/Dev-C++. I solved the problem by using a tool to create definition files from the existing dll's. I then edited the stdcall functions in the definition files. All the stdcall functions in the file were in the form _n...@ordinal. I simply changed it to be just name. This would have worked also: name = _n...@ordinal I then used dlltool to create .a files from the dll's and the definition files, .def. After this, the linking went OK. Regards Søren On Fri, Feb 19, 2010 at 6:13 AM, Selvaratnam Uthaiyashankar uthaiyashan...@gmail.com wrote: Hi, I think you are using Axis2/C binary release and you compile your program using MinGW? Is that correct? Axis2/C binary was compiled using microsoft compilers (visual studio). So, I don't think you can use that with MinGW. Did you try to compile your client code with visual studio? Regards, Shankar On Thu, Feb 18, 2010 at 7:50 PM, Søren Berggreen shbena...@gmail.com wrote: Hi I'm using Axis2/C version 1.6.0 on a windows client. I've noticed there are differences between windows and linux in the folder layout of Axis2/C. Company rules prohibit me from attaching my client, but I've attached 3 files: SearchDocs_Compile_Log - The log showing all the linker errors as they are outputted from Dec-C++. BuildLog.htm - Build log from Visual Studio also showing linker errors. Makefile.win - The makefile. Regards Søren On Thu, Feb 18, 2010 at 5:38 AM, Selvaratnam Uthaiyashankar uthaiyashan...@gmail.com wrote: Hi, can you attach your client and the makefile? Which Axis2/C version you are using? Regards, Shankar On Wed, Feb 17, 2010 at 6:05 PM, Søren Berggreen shbena...@gmail.com wrote: Hi. I'm trying to build a client to a axis2c service, but I keep getting linker errors saying something like: File: test_client.o In function 'main': [Linker error] undefined reference to '_imp__axutil_env_create_all' [Linker error] undefined reference to '_imp__axutil_strcmp' [Linker error] undefined reference to '_imp__axutil_error_get_message' [Linker error] undefined reference to '_imp__axis2_stub_free' [Linker error] undefined reference to '_imp__axutil_env_free' etc I'm doing the build on a Windows XP Pro. I've also tried on an Ubuntu, which gives me no errors during the linking process, but instead gives me: Segmentation fault: 0xb7f882e6 in __do_global_dtors_aux () I've included the axis2c lib files in the linker options. -- Med venlig hilsen/Best regards Søren H. Berggreen -- S.Uthaiyashankar Software Architect WSO2 Inc. http://wso2.com/ - lean . enterprise . middleware -- Med venlig hilsen/Best regards Søren H. Berggreen -- S.Uthaiyashankar Software Architect WSO2 Inc. http://wso2.com/ - lean . enterprise . middleware -- Med venlig hilsen/Best regards Søren H. Berggreen -- Med venlig hilsen/Best regards Søren H. Berggreen
[jira] Created: (AXIS2C-1453) CDATA is not correctly parsed by guththila
CDATA is not correctly parsed by guththila --- Key: AXIS2C-1453 URL: https://issues.apache.org/jira/browse/AXIS2C-1453 Project: Axis2-C Issue Type: Bug Components: guththila Affects Versions: 1.6.0 Reporter: Olivier Mengué Priority: Critical guththila does not correcly parses ![CDATA[ ... ]] Here is the result of axiom_node_create_from_buffer/axiom_note_to_string: Input: root![CDATA[abc#123;def]]/root Result: root/root Expected: rootabcamp;#123;def/root Input: root![CDATA[abc/rootdef]]/root Result: root/rootgt;def]]gt;/root Expected: rootabclt;rootgt;def/root -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2C-1451) XML numeric entities are not parsed by guththila
[ https://issues.apache.org/jira/browse/AXIS2C-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Mengué updated AXIS2C-1451: --- Attachment: guth_entity_bug.c Here is a more complete test suite (38 tests). It also tests issue AXIS2C-1453 (CDATA parsing). XML numeric entities are not parsed by guththila Key: AXIS2C-1451 URL: https://issues.apache.org/jira/browse/AXIS2C-1451 Project: Axis2-C Issue Type: Bug Components: guththila Affects Versions: 1.6.0, Current (Nightly) Environment: Axis2/C 1.6.0 with the guththilla reader/writer. Reporter: Olivier Mengué Priority: Critical Attachments: guth_entity_bug.c, guth_entity_bug.c The guththila_token_evaluate_references function does not parse numeric entities such as #65; or #x41; (which should map to the letter 'A'). A test case is attached. Here is its output: 1..2 not ok #input: rootabc#x41;#x42;def/root # got: rootabcamp;#x41;amp;#x42;def/root # expected: rootabcABdef/root not ok #input: rootabc#65;#66;def/root # got: rootabcamp;#65;amp;#66;def/root # expected: rootabcABdef/root -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2C-1451) XML numeric entities are not parsed by guththila
[ https://issues.apache.org/jira/browse/AXIS2C-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Mengué updated AXIS2C-1451: --- Attachment: AXIS2C-1451-1.6.0.patch Here is a patch against 1.6.0. All cases fixed (except CDATA which is another issue). XML numeric entities are not parsed by guththila Key: AXIS2C-1451 URL: https://issues.apache.org/jira/browse/AXIS2C-1451 Project: Axis2-C Issue Type: Bug Components: guththila Affects Versions: 1.6.0, Current (Nightly) Environment: Axis2/C 1.6.0 with the guththilla reader/writer. Reporter: Olivier Mengué Priority: Critical Attachments: AXIS2C-1451-1.6.0.patch, guth_entity_bug.c, guth_entity_bug.c The guththila_token_evaluate_references function does not parse numeric entities such as #65; or #x41; (which should map to the letter 'A'). A test case is attached. Here is its output: 1..2 not ok #input: rootabc#x41;#x42;def/root # got: rootabcamp;#x41;amp;#x42;def/root # expected: rootabcABdef/root not ok #input: rootabc#65;#66;def/root # got: rootabcamp;#65;amp;#66;def/root # expected: rootabcABdef/root -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2C-1451) XML numeric entities are not parsed by guththila
[ https://issues.apache.org/jira/browse/AXIS2C-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Mengué updated AXIS2C-1451: --- Attachment: AXIS2C-1451_entities-svn.patch Here is the patch against current SVN (revision 911851). Any reviewer? XML numeric entities are not parsed by guththila Key: AXIS2C-1451 URL: https://issues.apache.org/jira/browse/AXIS2C-1451 Project: Axis2-C Issue Type: Bug Components: guththila Affects Versions: 1.6.0, Current (Nightly) Environment: Axis2/C 1.6.0 with the guththilla reader/writer. Reporter: Olivier Mengué Priority: Critical Attachments: AXIS2C-1451-1.6.0.patch, AXIS2C-1451_entities-svn.patch, guth_entity_bug.c, guth_entity_bug.c The guththila_token_evaluate_references function does not parse numeric entities such as #65; or #x41; (which should map to the letter 'A'). A test case is attached. Here is its output: 1..2 not ok #input: rootabc#x41;#x42;def/root # got: rootabcamp;#x41;amp;#x42;def/root # expected: rootabcABdef/root not ok #input: rootabc#65;#66;def/root # got: rootabcamp;#65;amp;#66;def/root # expected: rootabcABdef/root -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Can not commit to the trunk
hi, I am getting this error when try to commit to the trunk. svn: Commit failed (details follow): svn: Server sent unexpected return value (403 Forbidden) in response to CHECKOUT request for '/repos/asf/!svn/ver/909680/axis/axis2/java/core/trunk/modules/adb/src/org/apache/axis2/databinding/utils/writer/MTOMAwareOMBuilder.java' svn: Your commit message was left in a temporary file: but seems that others can commit to the trunk. what could be the reason for this? thanks, Amila. -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
[jira] Created: (AXIS-2822) Content-Length calculation issue.
Content-Length calculation issue. - Key: AXIS-2822 URL: https://issues.apache.org/jira/browse/AXIS-2822 Project: Axis Issue Type: Bug Components: Basic Architecture Affects Versions: 1.4 Environment: This is the clients environment: Red Hat Enterprise Linux AS release 4 (Nahant Update 4) With kernel: Linux 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:27:17 EDT 2006 i686 i686 i386 GNU/Linux Java Env: Java(TM) SE Runtime Environment (build 1.6.0_13-b03) Java HotSpot(TM) Server VM (build 11.3-b02, mixed mode) Reporter: Vasili Bledar While 99.9% the axis is working perfectly, when trying to send a request of 1.500.000 bytes approximately, the server fails to acknowledge it. While trying to send the same request a few times in a row, it is always sent with different content-length. The element's indexes in the xml file we sent may differ each time, but the actual data are always the same. For example: 1st time we transmit: a nameblabla/name /a a namegluglu/name /a The 2nd time we transmit may be found like this: a namegluglu/name /a a nameblabla/name /a By using a packet sniffer on the server side we can see that our request is successfully transmitted. The soap request is reassembled through the packets recieved and the request body is checked against an xml parser which reveals that everything is ok with the xml data pasted in it. This xml body is different each time, but the length of the body should be the same (I'm not 100% sure on this and I may be missing something essential here). Another fact is that, the content-length parameter could say for example that the content-length is 1.456.321 bytes, but the number of packets size summed together for the specific communication is 1.255.456 or it could be slightly above the content-length which is not correct since there are definetely more data in communication which should increase the bytes sent in the communication much above the content-length. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[Axis2 1.4.1 with Rampart 1.4] - No user value in the rampart configuration policy
Hello everybody, I have a Web Application wich interacts with a Axis2 Web Service. The requests to WS are both free and with secure policy. Web App creates 2 client for my service: first one (free client) call the WS in http without security header; the second (secure client) engages rampart module and adds UsernameToken header to soap message. Consider this situation: - a logged user does a request to WS using secure client = success - immediately after user receive responce, system do: + stub._getServiceClient().getOptions().setUserName(); + stub._getServiceClient().getOptions().setPassword(); + stub._getServiceClient().cleanupTransport(); + stub._getServiceClient().cleanup(); - user logout and does a request to WS using free client = ERROR: No user value in the rampart configuration policy!!! Why does it happen if user calls the WS through free client? If I use forever the same client and engage and disengage rampart when needed, axis2 stack loads on java heap space 2 modules (mex and rampart jars) at any secure request. The garbage collection never deletes these modules and I am obligated to restart Tomcat regularly because heap space is full!!! Have you any solution for my problem? Many thanks in advance and sorry for my bad bad english! :) * F. Giuseppe Atzeni Mail: giuseppe.atz...@gmail.com * Presentaci un amico! Invita i tuoi amici a scoprire i servizi Tiscali: per ogni amico che attiverà un servizio Tiscali, potrai avere 30 euro di sconto e lo stesso sconto di 30 euro verrà poi offerto al tuo amico. Scopri come! http://abbonati.tiscali.it/presentaci_un_amico/?WT.mc_id=01fw
[jira] Created: (AXIS2-4630) ADB generates code that doesn't compile when WSDL has abstract types.
ADB generates code that doesn't compile when WSDL has abstract types. - Key: AXIS2-4630 URL: https://issues.apache.org/jira/browse/AXIS2-4630 Project: Axis2 Issue Type: Bug Components: adb Affects Versions: 1.5.1 Reporter: Aaron Gourley In ADBBeanTemplate.xsl, occurrences of the following exist without taking into consideration the fact that the class may have been declared as abstract: new xsl:value-of select=$name/(); Classes are declared abstract if @isAbstract='true' here (also in ADBBeanTemplate.xsl): xsl:if test=@isAbstract and @unwrapped and not(@skip-write)abstract/xsl:if Obviously, abstract classes can not be instantiated directly. Specifically I am seeing the problem in the generated Factory.fromString() method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (AXIS2-4631) getOMElement() of StubClass: ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter.
getOMElement() of StubClass: ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter. - Key: AXIS2-4631 URL: https://issues.apache.org/jira/browse/AXIS2-4631 Project: Axis2 Issue Type: Bug Affects Versions: 1.5.1 Environment: XP Home DellDimension 2400 Reporter: Prasad Regula Inside get getOMElement(): ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter. It is overriding the serialize method with org.apache.axis2.databinding.utils.writer.MTOMAwareXserializeMLStreamWriter as parameter. I generated the StubClass using the command wsdl2java -uri http://localhost:8080/axis2/services/EchoService?wsdl -O . I even tried axis2 1.4.1 still the same problem -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2-4631) getOMElement() of StubClass: ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter.
[ https://issues.apache.org/jira/browse/AXIS2-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Regula updated AXIS2-4631: - Component/s: wsdl Priority: Blocker (was: Major) getOMElement() of StubClass: ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter. - Key: AXIS2-4631 URL: https://issues.apache.org/jira/browse/AXIS2-4631 Project: Axis2 Issue Type: Bug Components: wsdl Affects Versions: 1.5.1 Environment: XP Home DellDimension 2400 Reporter: Prasad Regula Priority: Blocker Inside get getOMElement(): ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter. It is overriding the serialize method with org.apache.axis2.databinding.utils.writer.MTOMAwareXserializeMLStreamWriter as parameter. I generated the StubClass using the command wsdl2java -uri http://localhost:8080/axis2/services/EchoService?wsdl -O . I even tried axis2 1.4.1 still the same problem -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2-4631) getOMElement() of StubClass: ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter.
[ https://issues.apache.org/jira/browse/AXIS2-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Regula updated AXIS2-4631: - Description: Inside get getOMElement(): ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter. It is overriding the serialize method with org.apache.axis2.databinding.utils.writer.MTOMAwareXserializeMLStreamWriter as parameter. I generated the StubClass using the command wsdl2java -uri http://localhost:8080/axis2/services/EchoService?wsdl -O . from command prompt. I havent used any IDE. I even tried axis2 1.4.1 still the same problem. I am using jdk 1.6 was: Inside get getOMElement(): ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter. It is overriding the serialize method with org.apache.axis2.databinding.utils.writer.MTOMAwareXserializeMLStreamWriter as parameter. I generated the StubClass using the command wsdl2java -uri http://localhost:8080/axis2/services/EchoService?wsdl -O . I even tried axis2 1.4.1 still the same problem Environment: JDK1.6, Axis2, XP Home, DellDimension 2400 (was: XP Home DellDimension 2400) getOMElement() of StubClass: ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter. - Key: AXIS2-4631 URL: https://issues.apache.org/jira/browse/AXIS2-4631 Project: Axis2 Issue Type: Bug Components: wsdl Affects Versions: 1.5.1 Environment: JDK1.6, Axis2, XP Home, DellDimension 2400 Reporter: Prasad Regula Priority: Blocker Inside get getOMElement(): ADBDataSource not overriding serialize method with MTOMAwareXMLStreamWriter. It is overriding the serialize method with org.apache.axis2.databinding.utils.writer.MTOMAwareXserializeMLStreamWriter as parameter. I generated the StubClass using the command wsdl2java -uri http://localhost:8080/axis2/services/EchoService?wsdl -O . from command prompt. I havent used any IDE. I even tried axis2 1.4.1 still the same problem. I am using jdk 1.6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
