Hello
Does AXIS1.2 support SOAP1.2
When it doesnt in which
release it will?
Met Vriendelijke Groet,
Dirk Joosen
Postbus 28129
3828 ZJ Amersfoort / Groningen
Tel: 030-6588500
Fax: 033-4513101
E-mail:[EMAIL PROTECTED]
Could you send me a smaple wsdl and deploy files for this example?
-Henry
[EMAIL PROTECTED] 11/28/2004 5:47:08 PM
Please read about wrapped vs. not-wrapped doc/lit web services in the Axis
user guide and wiki.
You need to define (in the wsdl) a WS that takes a single document. The
root
The wsdl might contain something like this:
types
schema targetNamespace=ns elementFormDefault=qualified ...
xmlns=http://www.w3.org/2001/XMLSchema;
element name=echo2
complexType
sequence
element name=s1
Jaya,
Are u past this problem? how?
thanks,
dims
On Thu, 16 Sep 2004 17:50:11 +0530, jayachandra [EMAIL PROTECTED] wrote:
The HTTP response that included the server side error looks as follows.
**
HTTP/1.1 500 Internal Server Error
Content-Type: text/html;charset=ISO-8859-1
Yes it does.
-Sharam
From: Dirk Joosen
[mailto:[EMAIL PROTECTED]
Sent: Monday, November 29, 2004 3:50
AM
To: [EMAIL PROTECTED]
Subject: SOAP 1.2
Hello
Does AXIS1.2 support SOAP1.2
When it doesnt in which release it will?
Met Vriendelijke Groet,
Why not implement a LogHandler and log client activities to a repository of
your preference.
Jai
-Original Message-
From: James Black [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 25, 2004 11:07 AM
To: [EMAIL PROTECTED]
Subject: Re: Monitor Client usage of WS
-BEGIN PGP SIGNED
Viktor,
how about creating a JIRA ticket
(http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10460)? Please
attach your sample java class.
- Dominik
-Original Message-
From: Viktor Vojnovski [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 25, 2004 1:22 PM
To: [EMAIL
Hi,
I am looking for a simple DOC-LIT sample. I looked around in samples
folder, but probably missed it if it was there. I would appreciate any
help.
Regards
sagar
I guess at the java class level DOC-LIT is no different than any other
style of web service. Only the binding is different in the wsdl and rest
is taken care of at Axis level.
I converted my rpc-encoded web service to a doc-lit and manually changed
the wsdl and re generated the stubs for the
Since this is a very serious problem and I haven't got any reponse,
please someone in the know throw me some bones on what's going on with
this. Is this being addressed? No body care? I need to file a bug
report for it to go anywhere? Already fixed in the nightly?
Thanks,
vh.
V D wrote:
I
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
I am deploying a slightly modified version of
Calculator service with the following wsdd.
?xml version=1.0 encoding=utf-8?
deployment xmlns=http://xml.apache.org/axis/wsdd/;
xmlns:java=http://xml.apache.org/axis/wsdd/providers/java;
service name=Calculator
provider=java:RPC
Title: Configuration File problem
Hi,
I am relatively new to this list and have a question about Axis. We are using Axis on WAS 5.0 and when we attempt to access the wsdl for our service by appending ?wsdl to the end of the service URL, we get the following error message:
[11/23/04
Here you will find an example, and you can download the code at the
bottom.
http://www.sosnoski.com/presents/cleansoap/axis.html
-Enric
Hi,
I am looking for a simple DOC-LIT sample. I looked around in samples
folder, but probably missed it if it was there. I would appreciate any
Thanks Enric and Vikas for your replies.
Correct me if I am wrong.
If I have an RPC service, all I need to do is to use -y option and
specify DOCUMENT and regenerate my stubs, re deploy the wsdd file and
run my client.
Thanks.
Sagar
PS :
-y, --style argument
The style of binding in the
This should do the job, although I haven't tried the -y option because
my WSAD IDE did that for me.
RPC-Encoded and DOC-Literal only differ in the format of the SOAP
message (and of course the WSDL). And parsing of the SOAP message is
taken care of by Axis, so your web service java classes don't
How to get the absolute URL of the deployed service (to which the
request is going) in the handlers ?
thx
Hello,
I am trying to determine what the value of (wsdl)soap:address attribute should
be, and to what extent that value is supposed to reflect the real URL at which
the corresponding service is avaliable.
In a WSDL, the following sample section describes a service itself:
wsdl:service
Hello,
I am trying to secure the web service I have written using Axis as the
framework and running on tomcat. I got SSL client authentication
working. Problem is, Axis seems to respond to client requests on both
the encrypted SSL port 8443 and the un-encrypted port 8080 - port 8080
does not
Luke, use the MessageContext
From within your handler call
HttpServlet
serv=(HttpServlet)MessageContext.getCurrentContext()getProperty(HTTPConstant
s.MC_HTTP_SERVLET);
URL myURL = serv.getServletContext().getResource(/);
This will give you the context root of your application.
-Original
Comment out the Connector definition in the server.xml file under
$CATALINA_HOME$/conf/server.xml
On Mon, 29 Nov 2004 12:27:14 -0800, Lyndon Tiu [EMAIL PROTECTED] wrote:
Hello,
I am trying to secure the web service I have written using Axis as the
framework and running on tomcat. I got SSL
If the clients can be told by some other means what URL to use to access
your service, and all know to ignore what's in the wsdl, then anything goes.
If *any* client (existing now or in future) must figure it out from the
wsdl, then the wsdl must contain a usable URL for the service, in the sense
The entire point of WSDL is to allow automatic code generation. The
automatically generated code allows a developer to make calls to a
webservice as if it were a local call. Many generators (including wsdl2java)
embed the endpoint into the client stubs (the same endpoint that is
specified in the
John Walker wrote:
Comment out the Connector definition in the server.xml file under
$CATALINA_HOME$/conf/server.xml
Thanks.
That worked.
--
Lyndon Tiu
I'm trying to install Axis 1_2RC2 on Jetty 4.2.22 with JDK 1.5. I've never
before used Axis or SOAP, so I'm a total newbie in this respect.
After several hours I have successfully deployed a very simple web service
that I was able to call with a client (manually constructing the calls).
When I
Hello,
Anyone here ever used custom soap headers for authentication purposes?
How about WS-Security (Axis-WSSE)?
Any tips and suggestions and comments about how well these work and how
effective these are?
Thanks.
--
Lyndon Tiu
Hi,
I downloaded the Release Candidate #2 for
version 1.2 (1.2RC2).
However, I found out that the package org.apache.axis.encoding.ser.castor and
its classesare missing from the axis.jar file that comes with the binary
version.
For this reason, I could not integrate axis with
castor
Hello,
Has anyone here used WS-Security on Axis?
Thanks.
--
Lyndon Tiu
http://ws.apache.org/ws-fx/wss4j/
On Mon, 29 Nov 2004 15:34:58 -0800, Lyndon Tiu [EMAIL PROTECTED] wrote:
Hello,
Has anyone here used WS-Security on Axis?
Thanks.
--
Lyndon Tiu
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Hello !
We are using message-style argument passing with Axis both on the client
and the provider. The signature of all the methods is
Element[] method(Element[]), but in one instance we don't need to read
any arguments. When we invoke this method with
call.invoke((SOAPBodyElement[]) null),
Hi,
Here's the dilemma that I am facing and I am looking for your
experiences and recommendation.
I need to expose a lot of methods (over 200 with over 20 custom types).
The business logic on the server is implemented, very modular, such as
SessionModule, FileModule, UserModule, etc.
There
[EMAIL PROTECTED] wrote:
Tim,
I've just come across the fact that the BeanSerializer does make use of
a BeanInfo class. Have you tried using a BeanInfo class with your bean?
I don't know if Java2WSDL makes use of it, but the bean serializer seems
to, at run time. Give it a go and let us know.
I have a simple test method:
Long foo(Long bar)
Java2WSDL maps the Long to xsd:long and the client stub contains the
method as:
long foo(long bar)
How does the WSDL look like ? The parameter and return value should
have a nillable='true' attribute, otherwise I guess it's a bug in
the
In circumstances I have not yet fully figured out---but may be
associated with the Oracle parser required by Oracle's jdbc---my
lightweight Oracle based service will cause all of axis service to
collapse and throw http 500 with a stack usually, but not always, going
through the Oracle parser
Hi,
1) What level of support currently there is inAXIS 1.2 for message attachments.
E.g., does it support both DIME and and SwA?
2) WS-I has SOAP attachment profile finalized in August 2004. Does AXIS support SOAP attachment profile:
Hi All,
I am new to Axis. I have a simple SOAP service which returns a datahandler.
I also want to return another paramater such as filesize or filename in my message body. What is a good way to do this? Does anyone have any code examples? I am using Axis 1.1.
Basically I want the body to
37 matches
Mail list logo