Hi All,
Just wanted to know if anybody is executing SOAP Client using Axis on
Linux.
We are having issues getting the serviceLocator on the client side. It is
taking 5 secs to create a servicelocator itself.
Thanks,
Hrishikesh.
We have our local host in the /etc/hosts directory
127.0.0.1 localhost.localdomain localhost
6.6.6.5 applinux1.interact.nonreg applinux1
This is the line which is taking 5 secs:
getSubscriberDetailsLocator = new GetSubscriberDetailsServiceLocator();
Hi,
I'm testing out the feature for INOUT params
and I almost got it but stuck with a bug (which I
believe is part of Axis 1.1).
String methodName = "getString";
Service service = new Service();
Call call = (Call) service.createCall();
call.setTargetEndpointAddress(new
java.net.URL(endpointURL));
Hi, All,
I have a question on cookie or session management. This has
been baffling me for a while. Hope that someone there has solved a similar
problem.
In the application I am running there are two cookies from
server. First one is the “JSESSIONID” and the second one is
application
Vikas
DOM is quite a good thing to
solve your problem once u get the document object.
There are tutorials and articles in
the ibm.com/developerworks site or you can refer to the book Java and XML by
Brett McLaughlin , OReilly ... Thats the best book available in the market as
far as I
I get this same exception for every beanMapping specified in my config
file. If I move back to Axis 1.1 the error disappears. But running
under the latest Axis 1.2beta3 in CVS I get that same error.
Even though I get this error in Axis the service seems to still run properly.
- Brent
- Ori
I have a web service that returns an
array of objects. Upon startup, Axis complains about not being able to
find the ArrayDeserializerFactory.create(java.lang.Class, javax.xml.namespace.QName)
method. This is invoked by
org.apache.axis.encoding.ser.BaseDeserializerFactory.createFactory().
The se
I suggest that you add a handler that validates the message (which will
identify messages from this recalcitrant Seibel application) and does an
XSLT transform of the input message so that it conforms to the schema.
-Original Message-
From: Vikas Phonsa [mailto:[EMAIL PROTECTED]
Sent: Wed
Thomas,
I agree that client is the one that needs to be fixed.
The client is being generated by Siebel tools and they say the problem would
be fixed in their next version and upgrading the version is not an option
right now cause it would break lot of other things. So we are trying to hack
our wa
I am getting the following error when I submit a call in an application
I am building:
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.SocketTimeoutException: Read timed out
faultActor:
faultNode:
faultDetail:
I think that you have to write a cron job to do it
else It does not delete attachments.
mayur
--- Praveen Peddi <[EMAIL PROTECTED]> wrote:
> Hi all,
> I am using Apache Axis 1.1 and I use
> attachments.Directory=axis/attachments in
> server-sonfig.wsdd file. But I noticed that axis is
> putting
Vikas,
Since you are using doc/lit, you should be able to get the DOM object and get hold of
'arrayOfaddresses' nodes.
Now my question would be, why do you want to change the server behavior (which is
neater) just so
a buggy client can work? I would rather fix the client to send correct xml doc.
Hi all,
I am using Apache Axis 1.1 and I use attachments.Directory=axis/attachments in server-sonfig.wsdd
file. But I noticed that axis is putting the attchments files in this directory
and not deleting it. Is there any way to delete these files after the
attachments are processed. Otherwise
Hi Everybody,
I am developing a doc/literal style web service and the implementation java
class has only one method:
Public String insertOrUpdate(Contact contact).
And the contact object has an array of addresses. So the SOAP message should
look like this:
addr1
addr2
There is an in
No change when removing the encoding line from the typemapping :(
Bug report filed
jd
-Original Message-
From: John D'Ausilio
Sent: Wednesday, August 04, 2004 8:38 AM
To: [EMAIL PROTECTED]
Subject: RE: M$ interoperability and Arrays
I noticed that but wasn't sure .. this would then be
We have some testing code that starts a Tomcat/Axis server in one jvm,
then sends test soap calls from a different jvm. To avoid having the
client test code send soap calls before Axis is ready we have added a
ServletContextListener to the Axis server code:
public class StartupListener implemen
Please send us your WSDL.
-Original Message-
From: Christian Campo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 04, 2004 2:56 AM
To: [EMAIL PROTECTED]
Subject: Re: convert rpc/encoded to rpc/literal
good point.
However not I am sending the xsi:types but Axis is doing that. I am
usin
If you add a header to your SOAP message, you must provide a handler to
process it. If you don't and the mustUnderstand attribute is set to "1",
then the SOAP runtime is required to return a MustUnderstand fault.
Here's an article about configuring a handler chain. You must configure a
handler ch
Robert,
I agree with you that the rule stipulates only that a SOAP node MUST NOT
mandate use of the xsi:type attribute. I also agree that a SOAP node MUST be
able to process messages containing the xsi:type attribute.
The text above the rule, though, indicates the best practice: you SHOULD NOT
u
I suspect the problem is caused by the fact that your source WSDL has an
element in the Caller type called "Id", but the service is expecting an
element called "id".
I'm not sure why your service changed the element definition.
Anne
-Original Message-
From: Ivan Venuti [mailto:[EMAIL P
I noticed that but wasn't sure .. this would then be an issue in the
jboss-net xdoclet stuff. I've got to hack it in any case to support
wrapped style, so I'll see if I can fix the templates to get rid of that
as well .. and comment it out in the meantime
Thanks again ..
John d
-Original Me
Hi,
I have a WSDL file (you can see it, wsdlModuloIR.xml attached to this
email). From it I have generated server side code to implement the described
services.
I have also generated client side code in order to access it.
Doing so I've got this exception:
AxisFault
faultCode: {http://schemas.x
Hi,
I have tested this with AXIS 1.2alpha and
axis 1.1rc2, and get the same result from
both.
After generating the Java Stubs from this WSDL
http://soap.smscreator.de/send.asmx?WSDL
using WDLS2Java
the body of the public method calls have the
following lines:
org.apache.
Hi,I've package my web service into a .JAR file and put it into the
lib directory, then deployed and reloaded the web app. Everything works like
a charm.However, as the projects grow I will be adding alot of other
.JAR files (3PP dependencies) and it feels abit unorganized to just cram
everything i
Hi Dhanush,
casting the object[]
to AttachmentPart fixed the problem. ;-)
Now everything works
fine!
Thanks for your tips!
Cheers
Alex
Von: Dhanush Gopinath
[mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 4. August 2004
06:38
An: [EMAIL PROTECTED]
Betreff: Re:
Hi Dhanush,
casting the object[]
to AttachmentPart fixed the problem. ;-)
Now everything works
fine!
Thanks for your tips!
Cheers
Alex
Von: Dhanush Gopinath
[mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 4. August 2004
06:38
An: [EMAIL PROTECTED]
Betreff: Re:
good point.
However not I am sending the xsi:types but Axis is doing that. I am
using Axis on both ends (same version).
But you are right, the request contains xsi:type info for all fields
which probably helps to find the beanDeserializer on the server for
that xsi:type and there is no xsi:type at
27 matches
Mail list logo
