.
cheers,
Christoph
Jørgen Austvik wrote:
On Tue, 2004-01-13 at 17:44, Christoph Tratter wrote:
Hi Jørgen,
The problem is, where you like it to have.
In SOAP versioning is accomplished by means of the namespace name for
the SOAP envelope.
In your case the Axis client (presumably you have
Hi Jørgen,
The problem is, where you like it to have.
In SOAP versioning is accomplished by means of the namespace name for
the SOAP envelope.
In your case the Axis client (presumably you have version 1.1 final of
Axis) uses Version 1.1 of SOAP as default. This can be seen from the use
of the
Hi!
If passing "true" solves your problem and you're sure that actors will
not be involved in any way, then stick to it.
If you want to program defensively, you could still do something like
the following:
org.apache.axis.message.SOAPHeaderElement header;
header = env.getHeaderByName(namespace,
Hi, Ranjith!
Maybe this won't bring much light into your case, but as any help is
deeply appreciated...
In org.apache.axis.message.SOAPEnvelope, where both methods are defined,
the method nr. 1) just does the following:
public SOAPHeaderElement getHeaderByName(String namespace,
Hi Thilo!
In the Axis Architecture Guide
(http://ws.apache.org/axis/java/architecture-guide.html) the behaviour
you describe is explained to be intended.
(Beside points 3 and 7, which are not explained).
Imho the figures show very well, why there's a different order of chains
on server and clie
Hi Greg!
Just a little remark. It should not be a problem, but maybe in the
future cause for undetectable bugs:
The Extensible Markup Language (XML) 1.0 (Second Edition)
W3C Recommendation 6 October 2000 states in its section 3 "Logical
Structures" (http://www.w3.org/TR/REC-xml#sec-logical-stru
= testMsg.getSOAPEnvelope().getAsDOM();
}
catch ( Exception ex )
{
throw new AxisFault("could not get body.");
}
...
}
regards,
Christoph
Christoph Tratter wrote:
Hi Valerie!
You can try something like this:
In the method invoke of your handler (as it extends BasicHa
Hi Valerie!
You can try something like this:
In the method invoke of your handler (as it extends BasicHandler) you
have the following signature:
void invoke(MessageContext msgContext)
So you can try something like:
void invoke(MessageContext msgContext)
{
org.apache.axis.Message testMsg = c
Hi Pradeep,
by the way, I forgot to mention, that there's a link that explains the
use of axis and castor quite well:
http://www-106.ibm.com/developerworks/webservices/library/ws-castor/?Open&ca=daw-ws-news
regards,
Christoph
Pradeep Jonnalagadda wrote:
Guys,
I'm trying to use axi
Hi Pradeep!
I cannot see your *.bat files as they have "... been removed by eManager."
Do you use the option -W (--noWrapped) to create your "things"?
Christoph
Pradeep Jonnalagadda wrote:
Guys,
I'm trying to use axis with castor.The way i do it is
1. Define a wsdl which imports
Hello to everyone!
I use axis 1.1 and I try to create stubs, typeMappings etc. for a
handmade wsdl file using WSDL2Java.
If I use the wsdl file that I attached to this mail, no
typeMapping-classes are created. In other words the class
TServiceID.java is not created. Never the less the created
Hi Håkan!
Have you created the stub using WSDL2Java?
Then maybe the problem is that in the WSDL-file there's something like:
http://localhost:8080/axis/services/HakansService"; />
By letting WSDL2Java create the stubs automatically, then of course the
location in s
12 matches
Mail list logo
