We've been seeing some problems with SOAP clients
that use WSDL to access web services. It seems that if we change the order of
some of the WSDL elements that things start to work.
What we're wondering is if this is a legitimate
problem, or is it just a problem with SOAP clients that have i
We've been successful at doing this using the Axis Session object to store
'tokens' or other items that are commonly accessible by multiple published
SOAP services.
- Original Message -
From: "Alex Dovlecel" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 21, 2002 6:02
I haven't seen anyone respond on this thread so
I'll poke in.
I found the same problem and we really don't want
to be signing applets, etc. so we found a lightweight SOAP 1.1 client on
sourceforge.net - Spheon JSoap. We've found it works really well so far but I we
have fairly limited need
be using the Emitter Object API for best results. :-)
>
> --
> Tom Jordahl
> Macromedia Server Development
>
>
>
> -Original Message-
> From: Grant Echols (JanusLogix) [mailto:gechols@;januslogix.com]
> Sent: Thursday, October 17, 2002 3:57 PM
> To: [EMA
an" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 17, 2002 11:04 AM
Subject: Re: How to use the Java2WSDL class inside a java program
>
> - Original Message -
> From: "Grant Echols (JanusLogix)" <[EMAIL PROTECTED]>
> To: <
That problem has bitten me too. We want to do a dynamic publish which we try
to use the Java2WSDL and WSDL2Java so we get a deploy.wsdd file. We found a
couple of things that seemed to help. The biggest is we load a custom
SecurityManager just before running the .main() methods. The primary
objecti
u're interested, take a look at
> http://www.themindelectric.com
> >
> > However, I really do hope that there is a clean solution using Axis.
> Probably in near future.
> >
> > Cheers,
> >
> > Tuan
> >
> > -Original Message-
> > From:
or require a flag to enable it like Axis clients do. As far as
HTTP sessions go this is all you need to support them.
Alex
-Original Message-From: Grant Echols (JanusLogix)
[mailto:[EMAIL PROTECTED]]Sent: Friday, September 27, 2002
3:48 PMTo: [EMAIL PROTECTED]Subject
I don't know if this is a bug or not, but I've been trying to clear a
previously set username/password from a Call object and it seems to make no
difference. I'd like to essentially have the 'authentication' process done
with and over and have a 'session' established at which point I can quit
exch
Just an idea, but if the handler set a property in the session (e.g.
session.set(String name, Object value)) then it could check for the
existence of this property and act accordingly. I'm doing something like
this with a 'login' service right now.
Grant
- Original Message -
From: "Ricky
Tuan,
I have a similar need but for a totally different reason. We have a services
framework and want to dynamically publish public 'service entry points' at
runtime through Axis SOAP. We only have a Java class file and an associated
interface as parameters so we have to make up the rest of the d
nce returned by the ServiceLocator class
implementation in Axis client generated code terms.
Alex
-Original Message-From: Grant Echols (JanusLogix)
[mailto:[EMAIL PROTECTED]]Sent: Thursday, September 26, 2002
3:12 PMTo: [EMAIL PROTECTED]Subject:
MessageContext.setMaintain
Ok, so is it Tomcat 4.1.12 that solves the problem or the latest Axis build,
or both?
- Original Message -
From: "Jinghua Gu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, September 26, 2002 12:33 PM
Subject: Re: 1.0RC bug? H
Title: Message
I'm trying to understand the MessageContext session
management and I'm confused by what its supposed to do. On the first request
from a client I see that the session management is not turned on so I turn it
on. On the second request the session management is still not turned on
14 matches
Mail list logo
