AW: Howto get extended log information in case of ClientAbortException

2011-06-27 Thread Stadelmann Josef
Gentlemen's I cannot give you just out of pocket a precise answer, but maybe some idea about how to approach. The issue is most then same: where are the boundaries? In this case I can see about 3 boundaries: a) Your web service method - must be able to log the time of entrance into a

Axis2 Web service - startUp getting called many times

2011-06-27 Thread Sujata Galinde
Hi, I am developing a Web Service using Apache Axis2(axis2-1.5.4). I want to utilize power of ServiceLifeCycle to perform some tasks during service deployment & undeployment. I have - 1. TESTServiceLifeCycle implements ServiceLifeCycle 2. TESTService implements L

Re: Axis2 Web service - startUp getting called many times

2011-06-27 Thread Sadeep Jayasumana
Hi Sujata, Try changing the scope of the service deployment. ... Thanks, Sadeep On Mon, Jun 27, 2011 at 2:26 PM, Sujata Galinde wrote: > Hi, > > I am developing a Web Service using Apache Axis2(axis2-1.5.4). I want to > utilize power of ServiceLifeCycle to perform some tasks during service >

Issue when Set Soap header child elements in apache axis stubs

2011-06-27 Thread Rache1
I am using apache axis 1.4. I generated the stubs from wsdl using WSDL2JAVA in apache axis1.4. The SOAPAction request has a header part and body. SOAP method request looks like this http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/

RE: Howto get extended log information in case of ClientAbortException

2011-06-27 Thread Menzner, Rainer
Guys, in the meantime I found the following solution for us to be acceptable: 1. By exploiting the named properties in the In-Message-Context, the WS method implementations put everything required to do application-specific logging into the Axis2 In-Message-Context 2. The default

NTLM authentication failed (password with non-latin characters)

2011-06-27 Thread Muller Pierre
Hello, I'm working on a web application consuming web services with Axis2. Client classes are generated from a WSDL file with the XMLBeans method. The web services require NTLM authentication, which I set up in my application. Everything's fine, the application works as expected (able to authent

AW: NTLM authentication failed (password with non-latin characters)

2011-06-27 Thread Stadelmann Josef
Somewhere there is a password data base which has stored password-hashes or the like. Lets refer to it as stored-hashes. If the way hashes are generated from passwords, then transferred, then stored by some tool differs from the way hashes are generated, transferred and used toward th

Problem with header annotations - axis 1.6.0

2011-06-27 Thread André Lemos
Hi, I'm having some trouble using the echoString used on the unitary tests. I've created a class with: @WebMethod @WebResult(name = "headerReturn", header = true) public String echoString( @WebParam(name = "renamedParam1", header = true) String

Re: Axis2 1.4 not preserving CDATA

2011-06-27 Thread pchandr
This is a known problem with xmlbeans and axis2. Since Axis2 uses AXIOM to convert the XML Bean Object, conversion has to happen in 2 places. The First Place itself is when using XMLBeans XMLBeans: In XMLBeans there are 2 settings that have to happen they are XmlOptions xmlOptions = new XmlOpt

Re: Problem with header annotations - axis 1.6.0

2011-06-27 Thread André Lemos
PPS: This was done by using the deployServer() method (integrated into our code). axisServer = new AxisServer(true); axisServer.deployService(classWSDL.class.getName()); On 27/06/2011, at 17:32, André Lemos wrote: > Hi, > > > I'm having some trouble using the echoString used on the unitary

Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : Security

2011-06-27 Thread Mike Pettigrew
Hello; Does anyone have a solution for this problem? It seems to be a long-standing issue. Must Understand check failed for header http://.secext-1.0.xsd : Security It occurs in the client when receiving a response from a service. The "mustUnderstand" flag is set in the respo

RE: Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : Security

2011-06-27 Thread Martin Gainty
mustUnderstand attribute is added to SOAPEnvelope (element) before transmission e.g. env.addAttribute(Constants.URI_SOAP11_ENV, "mustUnderstand", "1"); here is the entire file: /* * The Apache Software License, Version 1.1 * Copyright (c) 2001-2003 The Apache Software Foundation.

RE: Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : Security

2011-06-27 Thread Mike Pettigrew
Martin Gainty; Thanks for your response. I am dealing with a third-party server which I cannot modify. That server will accept a Security header with a UsernameToken and ""mustUnderstand" flag set. I have been able to send that message successfully and the server processes it.. Unfor

Re: Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : Security

2011-06-27 Thread Michal Niklas
Hello, W dniu 2011-06-28 01:09, Mike Pettigrew pisze: > Martin Gainty; > [...] > > I have written a custom handler per some other sample codes, but I > cannot get it to engage. I don’t know what is missing. > Have you tried to communicte with server using soapUI? This program can use WS-Securi