Hello,
I'm really new to Axis, and I am trying to use it for running a
webservices server only.
I have seen that the Axis Engine requires a DOM Parser to be present in
the system in order to work correctly. However, in the purpose of just
answering SOAP requests, I cannot understand why a SAX
Hallo,
I am trying to call a webservice through ssl and I am getting the following exception.
I am able to initate to call without ssl.
thanks for any idea
Mohammed
java.io.IOException: Write Channel Closed, possible SSL handshaking or
trust failure
java.io.IOException: Write Channel
Mohammed,
you could check/try the following to narrow down the problem:
1. Enable SSL logging by setting the system property
java.security.debug=ssl.
2. Does your client recognize the certificate the server presents as part of
the SSL handshake?
3. Try connecting to the webservice using your
I'm using AXIS in a JSP/Tomcat environment to provide SOAP client facilities
through to a gSOAP C++ server.
A 'thin' JSP that simply calls SOAP functions and displays the results on
the web site is running 3 times slower than an equivalent client written in
C using gSOAP.
Naturally I'd expect
Hi
among other thing the wsdd package depends on the DOM parser so the
deployment reqiure DOM parser to be in the class path. But the
desiralization work without help from DOM parser
Am not sure am this answers your Q. hope this help
Srianth
On Fri, 2003-09-26 at 12:17, Simon Bretin wrote:
Hi Axis Users,
I am currently using axis in a tomcat and jsp environment for the
clients. When I use the client to invoke the web -service without my
custom handlers, it works okay, but as soon as I include the handlers in
the deploy.wsdd file for that service, the client creates the request
using
Greetings,
Axis defines 3 levels of scope that I would like to understand it well:
Request - the default, will create a new object each time a SOAP request
comes in for your service.
Application - will create a singleton shared object to service all
requests.
Session - will create a new object
Hi,
Thanks for the answer. This is exactly the confirmation I needed.
Any ideas why the deployment absolutely requires the DOM parser and
cannot be SAXified ?
Thanks,
Simon
Srinath Perera wrote:
Hi
among other thing the wsdd package depends on the DOM parser so the
deployment reqiure
Hi,
I am new to Web Services.
I first tried Apache Axis 1.1 with Tomcat
4.1 and was successful in writing a WebService, deploying it and calling it from
a Test Client.
Now I have to deploy the same WebService on
IBM WebSphere 5.0, but using Apache Axis framework.
First, how do I install
Dear All,
Thank you Stephen, for you're input.
I noticed that when I create a file without specifying a path, it goes
in the tomcat home folder.
My problem now lies in the fact that in the course that I'm developping
there will be as much as 1000 webservices deployed on a central server.
Hi
Axis uses *soapenc:arrayType* for
encoding the *arrays* in wrapped/literal type of services..
Due to this fact,
axis services, which returns array _CAN_NOT_ be consumed by .Net
clients.
Is anyone looking
into this issue. Are there any workarounds? Any help will be greatly
Hi everyone,
I am using an axis webservice (wrapped/literal) return a bean(object) containing an
array
of integers.
This service works fine with Axis client but when I try to use this service using .Net
client, I get the following error:
---
message=(0x04a772d0) There is an error in
Experts,
I'm having a problem with null tags. I have simulated this problem using the
samples/message application provided with axis. When I send the following tag:
..other tags
role xsi:nil=true/
...other tags
I get an axis fault:
faultstringjava.lang.Exception: Could not get DOM document:
Hi Jens,
RE: http://marc.theaimsgroup.com/?l=axis-userm=106449952803414w=2
Thanks for your help. Every things working fine now.
Cheers,
Nim
**
This email is intended solely for the use of the addressee
and may contain
I agree that a web-service specific location for storing files would be
ideal for you, however I'm not sure there is any way of doing so.
An alternative is to read the information in the file some other way
e.g. from a remote file-server, or maybe a database ??
stephen
Wouter Westenbrink
Hi Simon
I think it can be SAXified .. with more more hardwork
I belive at the end of the day it will not give you anything as you have
to get the all info to memory anyway. Using DOM (only prob is you need
DOM parser and xerces will have SAX and DOM anyway) can be justified as
it run only
Axis 1.1? WSDL?
-Original Message-
From: Gupta, Ankit [mailto:[EMAIL PROTECTED]
Sent: Friday, September 26, 2003 3:48 AM
To: [EMAIL PROTECTED]
Subject: Axis using wrong encoding for array in Doc/literal
Hi everyone,
I am using an axis webservice (wrapped/literal) return a
After seeing some of the public web services(or read somewhere on the net), with rpc style,i wasunder the assumption that all rpc style responses will have a 'return' node under the soapenv:Body but when used some of the axis samples it looks the node name can be anything defined on the wsdl.
But
Gary and Anne,
Thanks for the excellent answers. I was not aware of this attribute and it
all now makes complete sense. I was confused because the TerraService web
service (if you have ever seen it) requires qualified namespaces whereas the
axis examples I was working with do not. And I was
When using rpc/encoded, both the request and the response messages must be
formatted as a struct -- essentially a single wrapper element that is the
only child of the SOAP body.
The name of the request message wrapper element is equal to the operation
name. The subelements in the request
Could we take a look your jova code and .NET code? I think the problem is
that the tools to interplate wsdl is a little bit different between AXIS
java and .NET framework.
From: Mike Perham [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: Axis using wrong
I have a very simple web service that echos back the xml given that
looks like this:
public class MessageService
{
public Document echoDocument(Document doc) throws Exception
{
return doc;
}
}
On the client I have the various methods setup to retrieve the result
vector and
Steve,
I don't think fault/exception behavior has been sufficiently specified --
hence the interop issues.
The way it should work is thus:
On the server side:
Application throws an exception in its native language. The exception
routine should map the error to a SOAP fault. The SOAP engine
I have a few followup questions about this.
1) What is the preferred way to do this? Is it preferred to use
elementFormDefault=qualified or not? Is there anything mentioned about
this in ws-i or any other spec that tries to standardize web services?
2) So if elementFormDefault=qualified is not
hi,
i am trying to implement a webservice via axis
based on an existingwindows COM+ component. sounds odd since there is
already a perfect webservice environment... but: other services are implemented
in java and this is sort of a migration approach...
ok. i found in the source
http://marc.theaimsgroup.com/?l=axis-devw=2r=1s=COMProviderq=b
--- Sigi Jeske [EMAIL PROTECTED] wrote:
hi,
i am trying to implement a webservice via axis based on an existing windows COM+
component.
sounds odd since there is already a perfect webservice environment... but: other
services
Ann, Steve --
I am working on a patch for Axis to implement just this functionality.
There is one small clarification, however. The Axis engine is invoked on
the client side via a call to javax.xml.rpc.Call.invoke(...). In Axis, this
is actually implemented in org.apache.axis.client.Call.
There's isn't a preferred way to do it. You may design your schema however
you like. When using Doc/literal, the SOAP engine MUST generate SOAP
messages that conform to the schema.
Anne
At 11:35 AM 9/26/2003 -0500, you wrote:
I have a few followup questions about this.
1) What is the
I would add this to Anne's comments:
An rpc/encoded response can and often will have more than one child of
Body element - provided all but one is marked with the soapenc:root=0
attribute this is fine.
It's common in array serialization where the array itself is nested in
the main return
What does 'did not find prefix' mean? Is it something that could cause
problems? /Anders
xsi:type=dateTime2003-09-17T16:17:34.107/NS1:NAV_DateTime/
NS1:TNAVNS1:TNAVNS1:NAV_Code463/NS1:NAV_CodeNS1:NAV_DateTime
xsi:type=dateTime2003-09-18T16:15:06.943/NS1:NAV_DateTime/
Yeah I just wasn't sure if there are specific benefits of either way. I
guess it is message size vs. stricter validation.
Thanks again.
Chris
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Friday, September 26, 2003 12:01 PM
To: [EMAIL PROTECTED]
Hello,
I'm fairly new to this world of beans and serialization, so I need some help
determining why a custom class would not be serializable.
Here is what I get when I run SerializationTester:
Your class : [Company]
*** Can't get a serializer for 'Company' !! ***
=== 'Not supported' or
Please see my answers below.
Gary
-Original Message-
From: Chris Williamson [mailto:[EMAIL PROTECTED]
Sent: Friday, September 26, 2003 9:35 AM
To: [EMAIL PROTECTED]
Subject: RE: namespace question
I have a few followup questions about this.
1) What is the preferred way to
Thanks Gary! That is exactly what I needed to know. That was very helpful.
Chris
-Original Message-
From: Gary L Peskin [mailto:[EMAIL PROTECTED]
Sent: Friday, September 26, 2003 12:25 PM
To: [EMAIL PROTECTED]
Subject: RE: namespace question
Please see my answers below.
Gary
Hey I have a question about arrays.
In the ws-i spec it states that arrays should be defined such as...
complexType name=StringArray
xsd:sequence
xsd:element name=str type=xsd:string minOccurs=0
maxOccurs=unbounded/
/xsd:sequence
/complexType
And this turns out...
StringArray
Sorry I neglected to answer #2:
If elementFormDefault=qualified then all elements in the schema --
whether local or global -- are in the targetNamespace, and all elements in
a schema instance must be namespace qualified. If
elementFormDefault=nonqualified, or if the attribute is not specified,
Chris:The difference between the two examples you show amounts to whether or not there's a parent element, or wrapper,specified that's dedicated to containing the array. The first example uses a parent/wrapper; the second example does not because it throws theint-type element at the same level
Yeah
it seems odd that all they say isnot to use ArrayOf in the ws-i
spec. It almost seems like they want you to not use the wrapper but they
don't say it. I mean otherwise maybethey should outlaw anything
beginning with my like myOperation. Seems odd.
I
think the wrapper is
Excellent thanks Anne. That is a big help.
So that means that if the form is qualified it takes on the targetNamespace.
I think I got it.
Thanks,
Chris
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Friday, September 26, 2003 3:50 PM
To: [EMAIL
Hi Findlay
I think you should be more specific on what you want to do.
If Company is bean it can be serialized but you should registor it with
a BeanSerializer in the client/Server.
regards
Srinath
On Fri, 2003-09-26 at 23:20, Adhamh Findlay wrote:
Hello,
I'm fairly new to this world of
Hi Sunnay
does your endpoint uri is right
means is it like http://host:port/axis/services/servicename
e.g. http://127.0.0.1:8080/axis/services/Calculator
hope this helps.
Srianth
On Fri, 2003-09-26 at 17:25, Sunil Iyengar wrote:
Hi Axis Users,
I am currently using axis in a tomcat and jsp
41 matches
Mail list logo
