Re: Fwd: Axis response n namespace in array
Hi, I agree that the SOAP response does look wrong. On just the element below, ns2 is declared twice (with different values), which makes for invalid SOAP, and looking at your response message ns2 was already declared on the parent element. ns2:lineupTypeArray xmlns:ns2= xmlns:enc= http://www.w3.org/2001/06/soap-encoding; xmlns:ns2= http://gti-ia-zo.nl/ettTypes.xsd; enc:arrayType=ns2:lineupType[0] I've checked your WSDL, and there's nothing obvious that would cause problems. I believe there may have been some fixes relating to namespaces applied since 1.5, so can you check if this is still a problem in the 1.6beta release? Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Roel Bindels [EMAIL PROTECTED] wrote on 03/04/2006 21:22:31: Hello listers, I'm having some troublems with the response message. I'm using axis 1.5 as soap server and the Python ZSI library as a client. There are some differences between the approach of the both framework, but I was able to conquer those. But now I'm getting a strange response from axis, wich I doubt to be correct. Can somebody please take a look at my wsdl and the response in my attachments. specially to the next line: ns2:lineupTypeArray xmlns:ns2= xmlns:enc= http://www.w3. org/2001/06/soap-encoding xmlns:ns2= http://gti-ia-zo.nl/ett Types.xsd enc:arrayType=ns2:lineupType[0] This tells me that there should be a lineupTypeArray in my wsdl since this is pointing to ns2. I guess thet this should be an ampty namspace and that the namspace of my wsdl should be ns3. Can somebody verify this or not greetings Roel Bindels [attachment ett.wsdl deleted by Adrian Dick/UK/IBM] [attachment getLineup.txt deleted by Adrian Dick/UK/IBM]
(Probably dumb) Problems with install
G'day,
I have downloaded the current axis-c binary package and the install
instructions and scripts do not match the directory lay out.
Is there a step missing in the install instructions?
I have expanded the tar file in a working directory ($AXISCPP_HOME) and
I create a deploy directory ($AXISCPP_DEPLOY).
What commands should be used to populate the $AXISCPP_DEPLOY directory
if not building from source?
For example
$AXISCPP_HOME/deploy/bin/deploy_Apache2 has the line
cp -f ${AXISCPP_DEPLOY}/lib/libaxiscpp_mod2.so ${APACHE2_HOME}/modules/
where the distribution has the module at
$(AXISCPP_HOME)/lib/axis/libaxis_mod2.so
BTW which are the real install instruction as there are some on the web
site and different instructions in the distribution.
Cheers
David Bernard
service archiver eclipse plugin
Hi, I am using the service archiver eclipse plugin with 3.2m5a on osx and its broken. on service xml page of the wizard: 1. the generate the xml automatically option never becomes enabled. 2. even if you chose a service.xml, you get Please select a file named service.xml error that never goes away and the next or finish button that never becomes enabled. so your stuck, the only option is to cancel. has anyone else encountered this? regards Anthony
Order of SOAPHeader and SOAPBody
I am using the following function to add UsernameToken to my security
header. But the processed envelope get some problems.
1. The Header is placed after the body. How can I insert SOAPHeader
before SOAPBody?
2. The security header defines the xmlns:xsd and xmlns:xsi again,
which have already been defined in SOAP-ENV:Envelope.
Could you give me some advice on how to solve the above two problems?
Attached:
1) The function used for adding username token to the envelope:
public void addUsernameTokens(UsernameToken token, final SOAPEnvelope
envelope) throws Exception {
Document domDoc = Axis2Util.getDocumentFromSOAPEnvelope(envelope);
WSSAddUsernameToken builder = new WSSAddUsernameToken(, false);
if (token.isDigested()) {
builder.setPasswordType(WSConstants.PASSWORD_DIGEST);
} else {
builder.setPasswordTyp(WSConstants.PASSWORD_TEXT);
}
builder.build(domDoc, token.getUsername(), token.getPassword());
Element header = (Element)
(domDoc.getElementsByTagName(wsse:Security).item(0));
OMElement headerElm = (OMElement) (Axis2Util.toOM(header));
SOAPFactory factory = Axis2Util.getSOAPFactory(envelope);
factory.createSOAPHeader(envelope);
envelope.getHeader().addChild(headerElm);
}
2): The original soap envelope:
?xml version='1.0' encoding='utf-8'?SOAP-ENV:Envelope
xmlns:SOAP-ENV=http://www.w3.org/2003/05/soap-envelope;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
SOAP-ENV:Body
sayHello xmlns=http://services/helloworld;
valueHello world!/value
/sayHello
/SOAP-ENV:Body
/SOAP-ENV:Envelope
3): The processed soap envelope:
?xml version='1.0' encoding='utf-8'?SOAP-ENV:Envelope
xmlns:SOAP-ENV=http://www.w3.org/2003/05/soap-envelope;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
SOAP-ENV:Body
sayHello xmlns=http://services/helloworld;
valueHello world!/value
/sayHello
/SOAP-ENV:Body
SOAP-ENV:Headerwsse:Security
xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
wsse:UsernameTokenwsse:Usernamexinjun/wsse:Usernamewsse:Password
Type=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText;password/wsse:Password/wsse:UsernameToken/wsse:Security/SOAP-ENV:Header/SOAP-ENV:Envelope
Re: [AXIS2] Classloader problem
Hi ; Axis2 service classloaders work in child first scenario by default , what that mean is it load classes from child class loader before loading from parent class loader, so according to ur picture , if there is some class in foo.jar inside myService.aar then for the service it will use class in myService.aar/lib/foo.jar not from web-inf/lib/foo.jar. So you dont need to do anything to get this is done , by default Axis2 does the class loading as you require. Arnaud Blandin wrote: Hi, I am sure you have been discussing about this problem in the past but I couldn't find the relevant thread. I apologize in advance if I am describing a known problem. I am currently building a service on top of AXIS2. This service is using classes that are conflicting with the classes distributed with the Axis2 web app. The service is deployed as an aar file in the service directory of the axis2 web application. My question is simple: how can I ensure that the ClassLoader tries to load first the classes packaged in my lib directory from the aar instead of looking at the 'lib' directory of the axis2 webapp. |_WEB-INF |_lib |_foo.jar |_services |_myService.aar |_lib |_foo.jar I want to ensure that my service looks first for the myService.aar/lib/foo.jar As a workaround I tried to set the following with no luck before invoking the Skeleton: ClassLoader previous = Thread.currentThread().getContextClassLoader(); ClassLoader loader = msgContext.getAxisService().getClassLoader(); Thread.currentThread().setContextClassLoader(loader); Thanks, Arnaud -- Thanks, Deepal ~Future is Open~
