If you only want to inspect the messages then use a monitor tool.
tcpTrace is excellent for this (thank you simon and matt)
Raul
-Original Message-
From: Alex Chen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 12, 2005 3:39 PM
To: [EMAIL PROTECTED]
Subject: How to get HttpServl
I found the following in this article:
http://www.fawcette.com/javapro/2003_04/online/wsdl_kjones_04_29_03/defa
ult_pf.aspx
To create an Axis client that uses simple sessions, you need to
configure the Axis client-side framework to use the handler. The
procedure is similar to that for the server,
Title: Message
The code below uses a keystore to validate sites. Check
sun site or other resources to find out how to build a keystore/truststore from:
keytool
I generate a self signed cert in the keystore and then
import remote client certs.
// If we are running https protocol
(
attachments
Do you mean you succeeded to automatically generate a WSDL with
java2wsdl containing attachment information on operations?
If yes what's the method for that, I have been asking that several time
in this mailing list but no answer so far ;)
Cheers,
Patrick.
Flores, Raul wrote:
>
I don't believe there is a way to define this in wsdl so that both .Net
and Java(axis) can consume the wsdl. Someone please correct me if I am
wrong. My clients just have to understand that certain methods have
filles attached. I also allow them to set a request parameter do define
whether the atta
http://www.capescience.com/soa/index.shtml
-Original Message-
From: Henry Lu [mailto:[EMAIL PROTECTED]
Sent: Monday, October 11, 2004 9:54 AM
To: [EMAIL PROTECTED]
Subject: RE: WSDL2Java and Basic Profile
Could you provide the web site for downloading "a free WSDL editor with
a validato
Cap Science provides a free WSDL editor with a validator.
Raul
-Original Message-
From: Dan Ciarniello [mailto:[EMAIL PROTECTED]
Sent: Friday, October 08, 2004 5:08 PM
To: [EMAIL PROTECTED]
Subject: WSDL2Java and Basic Profile
I am trying to follow the advice that I've seen in this ma
I don't think you can use client.Call for a doc/lit service.
Build client stubs from wsdl and then use the XXXLocator and getXXXPort
to obtain a handle to the service.
Locator l = new Locator();
PortType pt = locator.getPortType();
pt.doSomeMethod(RequestClassGoesHere);
Raul
-Original Mes
The deploy.wsdd file (via AdminClient) creates/modifies the
server-config.wsdd file found in the webapp (under WEB-INF).
You can jar your war file with the server-config.wsdd included.
Raul
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 30
Title: What is the right WSDL for DIME, to support .NET and Axis consumers
How can I support DIME in wsdl for both .NET and java?
Raul
How can I support DIME in wsdl for both .NET and java?
Raul
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 25, 2004 8:58 PM
To: [EMAIL PROTECTED]; 'Anand Natrajan'
Subject: RE: What's the right WSDL for MIME?
Btw -- WS-I just published the
[mailto:[EMAIL PROTECTED]
Sent: Friday, August 20, 2004 12:34 PM
To: [EMAIL PROTECTED]
Subject: Re: Axis and SSL
Make sure that your client is connecting via a https url and not a http
url. --m
Flores, Raul wrote:
> Hi,
>
> I am having the following problem when running axis 1.2 beta 2 o
Title: Axis and SSL
Hi,
I am having the following problem when running axis 1.2 beta 2 over Tomcat with https.
When my client connects to port 8080, everything works fine.
When I try to run the same code against port 8443 (ssl) the client bombs after the first for loop iteration.
Any
One possibility is that you are using an earlier version of axis with a
doc/lit wsdl where your input parameter is empty.
Is HelloWorldRequest a complex type with no elements?
Which version of axis are you using?
This scenario does work with axis 1.2.
Hope this helps,
Raul
-Original Messa
Try setting the classpath for the java2wsdl task with a taskdef tag:
http://localhost:8080/axis/services/dataservice";
output="${build.home}/generated/MyGenerated.wsdl"
namespace=
Title: Wrapped style doc/lit and generated WSDL element names
Hello,
I am trying to implement wrapped style in axis 1.2 and am getting strange element names produced by axis when I generate the wsdl via http://servername?wsdl The strange element names are a combination of the complexType n
Title: Pachage name of generated Holder classes
Help,
I am using axis 1.2 beta (march 04) and generating classes with wsdl2java.
I have things setup for style="wrapped" and use="literal".
When axis generates the StringArrayHolder class, it uses a pachage name of: java.lang.holders
Is t
Title: Package names of generated Holder classes
Hello,
I am using axis 1.2 beta (march 04) and generating classes with wsdl2java.
I have things setup for style="wrapped" and use="literal".
When axis generates the StringArrayHolder class, it defines a package name of: java.lang.holders
The following article is short and to the point:
Which style of WSDL should I use?
RPC/encoded, RPC/literal, document/literal? Which one?
By: Russell Butek
Software Engineer, IBM
31 October 2003
http://www-106.ibm.com/developerworks/webservices/library/ws-whichwsdl/
Raul Flores
-Origina
19 matches
Mail list logo
