Title: RE: data transmission with SOAP
Hi,
We are using DIME attachments to send files, because Base64 encoding is apparently too slow for large files. We are using VB and Java clients of this service without problem.
Hope it helps,
Diego Fontd
Title: RE: SOAP AXIS INCOMPATIBILITIES
I am compiling a list. Basically, the differences are:
1/ The xsi:dateTime type is deserialized in SOAP as a Date and in Axis
as a Calendar. This requires configuring a custom mapping.
2/ Serialization frameworks are different, so custom serializers/d
Title: Out of memory error
Hi,
I'm testing my service to its limit, having it return 11,000 rows, and having trouble.
I'm getting an OutOfMemoryError (in both the client and server) while serializing the result set with some custom serializers, written as imitations of the on
ough this is not part of the documented class contract I'm taking my chances with it).
I'm writing now a doc on how to migrate from Apache SOAP, and this will be included.
-Original Message-
From: FONTDEVILA Diego [mailto:[EMAIL PROTECTED]]
Sent: Miércoles 21 de Enero de 2004 1
Title: How can I get a Date object from a xsd:dateTime
I'm migrating a service that used Apache SOAP. I need to get Date instances for my service to work. The standard Axis mapping is xsd:dateTime -> Calendar.
Is there any way I can change the default mapping? (it yields Calendar objects)
I h
Title: ManagedMemoryDataSource cleanup
Hi
I'm using the ManagedMemoryDataSource as my attachment's DataSource. I'm having trouble because I can't find a way to delete the used up instances so that if they have created a temporary disk file, it is deleted. I tried to delete them after a
Title: RE: How to create the server-config.wsdd file in a script (without any running server)
What I did was use the AdminClient to publish my service with the server running, and it created the service section in server-config.wsdd (saved in WEB-INF in the axis webapp directory in Tomcat), th
Title: RE: deserialization error: no deserializer is registered
You probably have not registered correctly the bean serialization classes to handle your bean (the SOAP serialization issue is independent from the information you give the JVM when you say Serializable).
Here is a code example.
Title: RE: Problem with the sample Attachment (Axis Java)
Hi,
Seems to me from the code in org.apache.axis.Message that maybe you don't have activation.jar in your classpath, and so attchments are not available (I don't actually have a line 639 in Message.java but assume the error is t
ne instance and the is no easy way to use
the bean serializer from the
server side code that is generated by wsdl.
Any ideas,
Thx,
-Vinod
>From: FONTDEVILA Diego
<[EMAIL PROTECTED]>
>Reply-To:
[EMAIL PROTECTED]
>To:
"'[EMAIL PROTECT
Title: RE: serialize a Bean with Axis
You should first try the Bean serialization classes, which require your bean class to have getters and setters (as any bean should) or public fields. Your elements should have the same name as the fields, otherwise you'd need to provide a mapping through s
11 matches
Mail list logo
