Hi,
I've added an option to the messagecontext to control the cookie policy on
http Request. This can be set as follows
options.setProperty(HTTPConstants.COOKIE_POLICY, CookiePolicy.IGNORE_COOKIES
);
Valid values for cookie policy are
public static final java.lang.String BROWSER_COMPATIBILI
Alastair,
Both xml documents are technically equivalent. The
clients that are having a problem are not xml-aware
readers. They scan for text and then pick up what they
need.
Since, both the documents are equivalent, is there a
way to configure axis2 to use one style. The
difference is between ax
Hi Samir.
First off let me state that I understand about not changing the clients
of your webservice and feel your pain. I agree that you can't just go
changing your clients because of a COTS product upgrade. :)
My point was more along the lines of the fact that I wasn't sure _why_
they have to
Raghu,
I tried that and it generates code and services.xml
for me. Its a lot of stuff to comb thru, do you know
exactly what I need to pick up from this generated
code and introduce in my server code which will then
suppress the namespace prefix from going out.
Thanks for your help.
Samir
---
Alastair,
I have a very convincing argument for glorified text
readers who want to hit a url and get text back to use
my service. Rather then custom coding all that I've
configured Axis2 to accept HTTP GET parameters as
input and return back an xml, just as it would for an
xml call. If I can someh
Samir.
If your clients can't handle the difference between 0 and 0
then I wouldn't bother using SOAP or web services. These are equivalent
in XML. I can understand suppressing the prefix in regards to efficency
and the size of the message but not to support a client that doesn't
handle XML prope
Samir,
WSDL2Java can also be used to generate serverside code. Check
WSDL2Java options, to create serverside code you need to specify the
options -ss -sd -ssi (check the description for these options in
WSDL2Java)
You can use -sp option with WSDL2Java when you generate the serverside
code
Martin,
You mean using QName in the client code?
I'm trying to tune my server to not send back
excessive xml. I cannot change the xml I send back to
my clients. the extra "ns:" is causing me trouble
after upgrading from axis2 1.1.1 to axis2 1.3 e.g.
0. My clients expect
0.
Samir
--- Martin Gain
you can always use null..e.g.
QName paramQName = new QName("", paramName);
M--
- Original Message -
From: "samir shaikh" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, December 12, 2007 7:20 PM
Subject: RE: [Axis2] trimming down the xml in axis2 1.3
> Raghu,
>
> Thanks for your help. I tried
Hi Mr Smith,
I'm having exactly the same problem -- were you able to modify the wsdl file
to fix this problem?
Thanks,
John
Mr Smith wrote:
>
> On Dec 10, 2007 2:07 PM, Mr Smith <[EMAIL PROTECTED]> wrote:
>
> I found the problem. The fault element didn't have a namespace for the
> operation
Raghu,
Thanks for your help. I tried that out but I want to
suppress it on the server. I think WSDL2Java is for
generating a client, right?
I'm hoping to find some configuration in services.xml
or axis2.xml... any idea?
Samir
--- Raghu Upadhyayula <[EMAIL PROTECTED]>
wrote:
> Samir,
>
>
Samir,
Try WSDL2Java with -sp option to suppress the namespace prefix.
Thanks
Raghu
-Original Message-
From: samir shaikh [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 12, 2007 2:20 PM
To: axis-user@ws.apache.org
Subject: [Axis2] trimming down the xml in axis2 1.3
Hi,
I'
Hi,
I'm trying to trim down the xml exchanged when using a
axis2 client and server. Is there a way I can
configure the serializer to not prefix namespace with
every element e.g. 0 can
just be 0. Also not send back
the additional headers and field types with each call.
I was able to do that in Axis
I have a stumbled upon a rather peculiar issue regarding the naming
convention of elements being returned by a service. If the second character
of the element's name is uppercase, the service's response does not contain
the element even when the WSDL shows the element correctly. The contents of
the
Hi folks,
I'm wondering if anyone has compared the real performance results of sync vs
async SOAP invocation using AXIS2. My SOAP application (time-consuming
operation in server) currently uses sync in both server and client, and I'm
wondering if I can improve the performance by switching to async
Hi chaps,
I am quite new to axis, I have developed a simple web service and it's
working in my local machine however it's not working from remote machine
althought they can view the wsdl file, I wonder is there anything I need to
set to enable this ?
Many thanks,
ray
--
View this message in co
Anthony
Also the NIO transport was designed to be run in a long-running server
environment where its ok to start threads. The default Axis2 client was
designed to be run in a blocking way with no new threads started. Also the
NIO HTTP client is new-ish, so conservatism (i.e. don't break people's
e
Massimiliano
Firstly you might want to have this discussion on a Rampart list - it might
get more involvement from real sec experts.
My question is why do you need to write your own HTTPClient? I thought we
already supported SSL/TLS.
Paul
On Dec 12, 2007 1:59 PM, Massimiliano Masi <[EMAIL PROTE
Hi everybody,
I am sending a request to the service which combines its response from various
sources, then creates an OMElement and sends it back. The databinding and
deserialization is made with Castor and Stax APIs basically as it is described
in the "databinding" example from Axis2 distribut
sort it!
Service service = new Service();
Call call = (Call)service.createCall();
URL url = new
URL("http://localhost:8080/axis/services/MyService";);
call.setTargetEndpointAddress(url);
QName qname = new QName("urn
Thanks Paul, you mentioned a good point about async invocation which was my
next question, whether asycn SOAP invocation can provide a better
performance results for time-consuming server operations.
Joe
On Dec 11, 2007 3:36 PM, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> Its possible another
On Dec 10, 2007 2:07 PM, Mr Smith <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I'm trying to use a web service located here:
> http://soap.towerdata.com/validate.wsdl but I'm getting an error with
> axis 1.4 (I'm consuming the web service with ColdFusion which comes
> with axis 1.2 but I also downloaded ax
Hi,
Quoting Massimiliano Masi <[EMAIL PROTECTED]>:
I don't understand exactly where to put my code, I think as options
for the service client.
I created MySTSClient, that extends STSClient. Here I did like this:
Protocol myProtocolHandler = new Protocol("https",
new
I am working on the same issue - trying to get NTLMv2 support in an AXIS
client. Have you been able to leverage the NTLMv2 capabilities in jdks 5 &
6 as Commons HTTP Sender doesnt support this protocol? Having trouble
finding any software out there that does this.
Thanks
Colum Daly wrote:
>
I have did a simple web service using axis, which i think it is very good as
I can pretty much reuse my business/data access class and just need to
create a wsdd file, anyway, it's working I think, but I got problem when I
try to create a client test class.
However the webs
Nunny wrote:
>
> Hi Kent,
>
>> This won't work if the client
>> is unknown (being unknown is fine as long as the certificate can be
>> verified
>> by a trusted CA). Is rampart designed to be used for known/fixed clients
>> only?
>
> No, Rampart can be used in this kind of scenario. You have to
Some more details. I don't know whether this is a Tomcat or Axis2
issue, but the problem seems to be that the axis2 directory does not
exist under $CATALINA_HOME/work/Catalina/localhost.
Michele
Begin forwarded message:
From: Michele Mazzucco <[EMAIL PROTECTED]>
Date: 12 December 2007 10:
On 11 Dec 2007, at 20:26, Anthony Bull wrote:
Hi,
is there any reason that the NIO transports are commented out in
the Axis 2 default axis2.xml config file?
I have been running a separate axis 2 with Synapse in it as an ESB
(which proxies a separate Axis2/Tomcat on another server) and the
Hi Narayan,
Could some one please help me to understand why
> org.apache.rampart.handler.WSDoAllReceiver/Sender handlers are
> deprecated and still configured in rampart-1.3 module.xml? Is there any
> substitute for them or is Developer need to develop its own?
WSDoAllReceiver/Sender is used whe
Hi,
I have a requirement in which I have to programatically read a webservice's
WSDL, and construct the SOAP request to consume the service.
Reading the WSDL can be accomplished with WSDL4J. But I am having problems
constructing the request message from the schema.
Is there some API which can do
Hi Kent,
This won't
> work if the client
> is unknown (being unknown is fine as long as the certificate can be
> verified
> by a trusted CA). Is rampart designed to be used for known/fixed clients
> only?
No, Rampart can be used in this kind of scenario. You have to set the
encryption user as
Hi Axis Users,
Could some one please help me to understand why
org.apache.rampart.handler.WSDoAllReceiver/Sender handlers are
deprecated and still configured in rampart-1.3 module.xml? Is there any
substitute for them or is Developer need to develop its own?
Regards, Narayan
32 matches
Mail list logo
