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
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
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,
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
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
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
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
[ 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
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
[ 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
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(
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)
[
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
[ 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
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
[ 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
[
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
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:
[ 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,
[
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) {
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:
[
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
[ 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
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
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
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
+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
[ 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
[ http://issues.apache.org/jira/browse/AXIS2-712?page=all ]
Davanum Srinivas resolved AXIS2-712:
Resolution: Fixed
fixed.
[ADB] convertTobase64Binary (?)
---
Key: AXIS2-712
URL:
[ 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
---
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
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
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
[ 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
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
[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
[ 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
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
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
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
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
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
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
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
[
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
[ 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
[ 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 ?
[ 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
[ 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
---
49 matches
Mail list logo