parser problem when compiling Axis2/C

2006-05-12 Thread Irfan Habib
Hi, I'm unable to compile Axis2/C manually, because I think of a problem with the parser. I have libxml2 2.6.16 installed in redhat 7. (Another machine with slackware 10.2 works fine). When I run ./configure it says checking whether to build guththila xml parser library... no checking whether

Re: parser problem when compiling Axis2/C

2006-05-12 Thread Nabeel
Irfan, Out of guththila and libxml2, currently you can use only libxml2 since there are some issues with guththila that need to be sorted out. I am using libxml2 2.6.19 on FC4. When you are using libxml2, you usually don't need to set the paths to lib and include dirs manually, configuration

Re: [AXIS2] MTOM performance Measuring

2006-05-12 Thread Samisa Abeysinghe
Nabeel wrote: Kapila, With your latest changes you always read the file in one go (i.e. not in chunks) and you don't need a loop. The attached compact code does the same thing. Suggestion: When we need to attach *very* large file, we may not be keep the whole file in memory. IMO,

Re: [AXIS2] MTOM performance Measuring

2006-05-12 Thread Samisa Abeysinghe
BTW, If we are going to use chunking at some point in time, then the data handler logic for reading file too has to change to keep track of the amount of chunks already read, and current position of read pointer. There is no provision for such reading in the code as of now, neither in the

Re: [Axis2][VOTE] Axis2C 0.91 Release Plan

2006-05-12 Thread Samisa Abeysinghe
Write access to the Subversion repository is now on. Hopefully we could be able to do the release by Monday, 15th of May. Thanks, Samisa... Samisa Abeysinghe wrote: Write access to the Subversion repository is still not on. We have read only access. Apache infrastructure team is doing a

Re: [AXIS2] MTOM performance Measuring - http_transport_utils.c modified

2006-05-12 Thread Samisa Abeysinghe
Wow!!! This is fantastic; At last we are up to the expected speed of C. Many thanks for looking into this. This has been very useful. Please have a look into chunking if you get some time. Thanks, Samisa... Kapila Dissanayake wrote: Hi , I did another modification to improve the messege

Re: [AXIS2] MTOM performance Measuring

2006-05-12 Thread Samisa Abeysinghe
Samisa Abeysinghe wrote: Nabeel wrote: Kapila, With your latest changes you always read the file in one go (i.e. not in chunks) and you don't need a loop. The attached compact code does the same thing. Suggestion: When we need to attach *very* large file, we may not be keep the

[jira] Updated: (AXIS2-704) Extract and support wsaw:UsingAddresing on service side

2006-05-12 Thread David Illsley (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-704?page=all ] David Illsley updated AXIS2-704: Attachment: patch.txt New patch with copyright notice moved to NOTICE.txt David Extract and support wsaw:UsingAddresing on service side

[jira] Created: (AXIS2-715) WSDL2Java generates faulty code when using XMLBeans databinding

2006-05-12 Thread JIRA
WSDL2Java generates faulty code when using XMLBeans databinding --- Key: AXIS2-715 URL: http://issues.apache.org/jira/browse/AXIS2-715 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: databinding

[jira] Updated: (AXIS2-715) WSDL2Java generates faulty code when using XMLBeans databinding

2006-05-12 Thread JIRA
[ http://issues.apache.org/jira/browse/AXIS2-715?page=all ] Pascal Dihé updated AXIS2-715: -- Attachment: build.txt build output WSDL2Java generates faulty code when using XMLBeans databinding

Re: RV: Axis2 service without Apache

2006-05-12 Thread Rajith Attapattu
Hi Villalba,Use the WSDL2Java tool to generate the code from a wsdl fileHere is the code sample to start a simple HTTP server-- SimpleHTTPServer receiver = new SimpleHTTPServer(

[jira] Created: (AXIS2-717) WSDL2Java Tool generates WSDL with linebreak inside an attribute name from valid WSDL

2006-05-12 Thread Rincewind Wizard (JIRA)
WSDL2Java Tool generates WSDL with linebreak inside an attribute name from valid WSDL - Key: AXIS2-717 URL: http://issues.apache.org/jira/browse/AXIS2-717 Project: Apache Axis 2.0 (Axis2)

[jira] Commented: (AXIS2-717) WSDL2Java Tool generates WSDL with linebreak inside an attribute name from valid WSDL

2006-05-12 Thread Rincewind Wizard (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-717?page=comments#action_12383208 ] Rincewind Wizard commented on AXIS2-717: ... description got sent without me finishing it: When running WSDL2Java to create a service (actual command line switches: -o

[jira] Updated: (AXIS2-717) WSDL2Java Tool generates WSDL with linebreak inside an attribute name from valid WSDL

2006-05-12 Thread Rincewind Wizard (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-717?page=all ] Rincewind Wizard updated AXIS2-717: --- Attachment: TextLocService.wsdl This is the WSDL that was created WSDL2Java Tool generates WSDL with linebreak inside an attribute name from valid

[jira] Created: (AXIS2-718) WSDL2Java Tool should pretty-print its WSDLs like the service.xml is already pretty-printed

2006-05-12 Thread Rincewind Wizard (JIRA)
WSDL2Java Tool should pretty-print its WSDLs like the service.xml is already pretty-printed --- Key: AXIS2-718 URL: http://issues.apache.org/jira/browse/AXIS2-718 Project: Apache Axis

[jira] Updated: (AXIS2-718) WSDL2Java Tool should pretty-print its WSDLs like the service.xml is already pretty-printed

2006-05-12 Thread Rincewind Wizard (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-718?page=all ] Rincewind Wizard updated AXIS2-718: --- Attachment: TextLocService.wsdl One example WSDL that is not pretty-printed but rather has all its info in the top and bottom lines. WSDL2Java Tool

[jira] Commented: (AXIS2-715) WSDL2Java generates faulty code when using XMLBeans databinding

2006-05-12 Thread Ken Campbell (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-715?page=comments#action_12383211 ] Ken Campbell commented on AXIS2-715: You may be able to compile if you alter your targetNamespace to exclude '/' characters. However, I still have data binding problems

[jira] Created: (AXIS2-719) Please create a service and most important, a client using WSDL2Java from this WSDL and test it

2006-05-12 Thread Rincewind Wizard (JIRA)
Please create a service and most important, a client using WSDL2Java from this WSDL and test it --- Key: AXIS2-719 URL: http://issues.apache.org/jira/browse/AXIS2-719 Project:

[jira] Updated: (AXIS2-719) Please create a service and most important, a client using WSDL2Java from this WSDL and test it

2006-05-12 Thread Rincewind Wizard (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-719?page=all ] Rincewind Wizard updated AXIS2-719: --- Attachment: EpiLocService.wsdl This is the valid WSDL that we would like to use to create a service. You can simplify the types even more if you wish,

[jira] Commented: (AXIS-1720) Java2WSDL, repeated types auto-mapping to xsd:anyType causes bad definition in schema

2006-05-12 Thread Jeff Fassler (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-1720?page=comments#action_12383215 ] Jeff Fassler commented on AXIS-1720: If you replace the code: if (!addToTypesList(qName) !anonymous) { if (containingElement != null) {

[jira] Created: (AXIS2-720) Data binding Error after using WSDL2Java to generate xmlbeans code

2006-05-12 Thread Rincewind Wizard (JIRA)
Data binding Error after using WSDL2Java to generate xmlbeans code -- Key: AXIS2-720 URL: http://issues.apache.org/jira/browse/AXIS2-720 Project: Apache Axis 2.0 (Axis2) Type: Bug Components:

[jira] Commented: (AXIS2-720) Data binding Error after using WSDL2Java to generate xmlbeans code

2006-05-12 Thread Rincewind Wizard (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-720?page=comments#action_12383217 ] Rincewind Wizard commented on AXIS2-720: The stack trace: org.apache.axis2.AxisFault: Data binding error at

[jira] Updated: (AXIS2-720) Data binding Error after using WSDL2Java to generate xmlbeans code

2006-05-12 Thread Rincewind Wizard (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-720?page=all ] Rincewind Wizard updated AXIS2-720: --- Attachment: EpiLocService.wsdl The WSDL used to create this service Data binding Error after using WSDL2Java to generate xmlbeans code

[jira] Created: (AXIS-2476) Multiple java or javax types not generated as AnyType in wsdl

2006-05-12 Thread Jeff Fassler (JIRA)
Multiple java or javax types not generated as AnyType in wsdl - Key: AXIS-2476 URL: http://issues.apache.org/jira/browse/AXIS-2476 Project: Apache Axis Type: Bug Components: WSDL processing

[jira] Created: (AXIS2-721) WSDL generated specifies a namespace for the soap:body elements even though it is a doc/literal binding

2006-05-12 Thread Junaid (JIRA)
WSDL generated specifies a namespace for the soap:body elements even though it is a doc/literal binding - Key: AXIS2-721 URL: http://issues.apache.org/jira/browse/AXIS2-721

[jira] Created: (AXIS2-722) WSDL generated specifies an invalid endpoint address location

2006-05-12 Thread Junaid (JIRA)
WSDL generated specifies an invalid endpoint address location - Key: AXIS2-722 URL: http://issues.apache.org/jira/browse/AXIS2-722 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: wsdl

RE: [Axis2] My experience creating a WSDL2Java generated ADB service

2006-05-12 Thread Tom Jordahl
+1 to that! This is exactly the kind of feedback the Axis2 team needs! Thanks Mike! -- Tom Jordahl Adobe -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 11:50 PM To: axis-dev@ws.apache.org Subject: Re: [Axis2] My experience creating a

[jira] Resolved: (AXIS2-714) ConverterUtil#getStringFromDataHandler chops up the data into 1K chunks

2006-05-12 Thread Davanum Srinivas (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-714?page=all ] Davanum Srinivas resolved AXIS2-714: Resolution: Fixed Fixed. ConverterUtil#getStringFromDataHandler chops up the data into 1K chunks

[jira] Resolved: (AXIS2-712) [ADB] convertTobase64Binary (?)

2006-05-12 Thread Davanum Srinivas (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-712?page=all ] Davanum Srinivas resolved AXIS2-712: Resolution: Fixed fixed. [ADB] convertTobase64Binary (?) --- Key: AXIS2-712 URL:

[jira] Resolved: (AXIS2-694) Soap:Body is serialized inside of a soap:Header element

2006-05-12 Thread Davanum Srinivas (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-694?page=all ] Davanum Srinivas resolved AXIS2-694: Resolution: Fixed Fixed. Soap:Body is serialized inside of a soap:Header element ---

[Axis2] Re: WS-Security and Rampart

2006-05-12 Thread Ruchith Fernando
Hi, I see that you are using the code generated stub. In this case when you create a new options object and set it in the ServiceClient instance used in the stub the options instance in the stub gets overridden. This options instance contains the address etc. that you provided when creating the

[Axis2] How to run multiple clients using same ConfigurationContext

2006-05-12 Thread Jaliya Ekanayake
Hi Devs,I wanted to run several clients to measure some performance. The attached client does not get the result for all the threads and it hangs. IMHO the problem is due to the way we use the client side transport listener. If client has some control at least to stop it then we will be able to

Re: [Axis2] How to run multiple clients using same ConfigurationContext

2006-05-12 Thread Jaliya Ekanayake
Oops wrong file. Please use the attachedOn 5/12/06, Jaliya Ekanayake [EMAIL PROTECTED] wrote: Hi Devs,I wanted to run several clients to measure some performance. The attached client does not get the result for all the threads and it hangs. IMHO the problem is due to the way we use the client side

[jira] Resolved: (AXIS2-696) ADB doesn't appear to support wildcard elements in the schema

2006-05-12 Thread Davanum Srinivas (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-696?page=all ] Davanum Srinivas resolved AXIS2-696: Resolution: Fixed Fix in latest SVN. thanks, dims ADB doesn't appear to support wildcard elements in the schema

[jira] Created: (AXIS2-723) Ant Task Documentation Error

2006-05-12 Thread Davanum Srinivas (JIRA)
Ant Task Documentation Error Key: AXIS2-723 URL: http://issues.apache.org/jira/browse/AXIS2-723 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: samples, build,site docs Reporter: Davanum Srinivas FYI, the

[jira] Created: (AXIS2-724) [ADB] xsd:all deserialization should support out-of-order elements

2006-05-12 Thread Davanum Srinivas (JIRA)
[ADB] xsd:all deserialization should support out-of-order elements -- Key: AXIS2-724 URL: http://issues.apache.org/jira/browse/AXIS2-724 Project: Apache Axis 2.0 (Axis2) Type: Bug Reporter: Davanum

[jira] Resolved: (AXIS2-704) Extract and support wsaw:UsingAddresing on service side

2006-05-12 Thread Davanum Srinivas (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-704?page=all ] Davanum Srinivas resolved AXIS2-704: Resolution: Fixed Applied. thanks. -- dims Extract and support wsaw:UsingAddresing on service side

Re: [Axis2] How to run multiple clients using same ConfigurationContext

2006-05-12 Thread Chamikara Jayalath
Hi Jaliya, I could get this working after two changes. Firstly Axis2 stops the SAS listner when the serviceClient.finalizeInvoke () is called. so I commented out the following line in the finally block. sender.finalizeInvoke(); Secondly there seems to be a bug in the

Re: [AXIS] 1.4 WSDL2Java generates non-compilable code

2006-05-12 Thread Davanum Srinivas
Sure. Please submit a patch thanks, dims On 5/10/06, Remy Bertrand [EMAIL PROTECTED] wrote: When WSDL contains xsd:extension in type definitions, wsdl2java can generate non compilable code. I have identified 2 cases of non compilable code : - Generated class don't extends anything, but a

Re: [Axis2] How to run multiple clients using same ConfigurationContext

2006-05-12 Thread Davanum Srinivas
Please don't forget to log a bug and upload a diff :) thanks, dims On 5/12/06, Chamikara Jayalath [EMAIL PROTECTED] wrote: Hi Jaliya, I could get this working after two changes. Firstly Axis2 stops the SAS listner when the serviceClient.finalizeInvoke () is called. so I commented out the

[jira] Created: (AXIS2-725) Address already in use: JVM_Bind exception while creating second SimpleHTTPServer instance

2006-05-12 Thread Ali Sadik Kumlali (JIRA)
Address already in use: JVM_Bind exception while creating second SimpleHTTPServer instance Key: AXIS2-725 URL: http://issues.apache.org/jira/browse/AXIS2-725 Project: Apache Axis

[jira] Created: (AXIS2-726) CallbackReceiver should not be a instance variable of the ServiceClient

2006-05-12 Thread Chamikara Jayalath (JIRA)
CallbackReceiver should not be a instance variable of the ServiceClient --- Key: AXIS2-726 URL: http://issues.apache.org/jira/browse/AXIS2-726 Project: Apache Axis 2.0 (Axis2) Type: Bug

Re: [Axis2] How to run multiple clients using same ConfigurationContext

2006-05-12 Thread Chamikara Jayalath
Done http://issues.apache.org/jira/browse/AXIS2-726 Chamikara On 5/13/06, Davanum Srinivas [EMAIL PROTECTED] wrote: Please don't forget to log a bug and upload a diff :)thanks,dimsOn 5/12/06, Chamikara Jayalath [EMAIL PROTECTED] wrote: Hi Jaliya, I could get this working after two

Re: [Axis2] How to run multiple clients using same ConfigurationContext

2006-05-12 Thread Jaliya Ekanayake
Thanks Chamikara. Jaliya - Original Message - From: Chamikara Jayalath To: axis-dev@ws.apache.org Sent: Friday, May 12, 2006 4:25 PM Subject: Re: [Axis2] How to run multiple clients using same ConfigurationContext Hi Jaliya,I could get this working after two

[jira] Commented: (AXIS2-725) Address already in use: JVM_Bind exception while creating second SimpleHTTPServer instance

2006-05-12 Thread Chamikara Jayalath (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-725?page=comments#action_12383352 ] Chamikara Jayalath commented on AXIS2-725: -- You can avoid this by sharing your configuration context between the invocations. But if ur requirement is to use

[jira] Resolved: (AXIS-2362) Re-use of MultiThreadedConnectionManager in CommonsHTTPSender

2006-05-12 Thread Jarek Gawor (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-2362?page=all ] Jarek Gawor resolved AXIS-2362: --- Resolution: Fixed The CommonsHTTPSender was updated to reuse the MultiThreadedConnectionManager. Re-use of MultiThreadedConnectionManager in

[jira] Resolved: (AXIS-2030) Singleton getInstance returns new instances each time ?

2006-05-12 Thread Jarek Gawor (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-2030?page=all ] Jarek Gawor resolved AXIS-2030: --- Resolution: Fixed The CommonsHTTPSender was updated to reuse the MultiThreadedConnectionManager. Singleton getInstance returns new instances each time ?

[jira] Resolved: (AXIS-2220) one-way invokes result in error parsing response message from CommonsHTTPSender

2006-05-12 Thread Jarek Gawor (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-2220?page=all ] Jarek Gawor resolved AXIS-2220: --- Resolution: Fixed The CommonsHTTPSender was updated to check for an empty response, and if so it releases the connection immediately and returns without

[jira] Resolved: (AXIS-2394) SOAPFaultBuilder throws DOMException WRONG_DOCUMENT_ERR

2006-05-12 Thread Jarek Gawor (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-2394?page=all ] Jarek Gawor resolved AXIS-2394: --- Resolution: Fixed Patch committed. SOAPFaultBuilder throws DOMException WRONG_DOCUMENT_ERR ---