RE: No headers in response

Martin, I tried that as well and the response still came back with no headers. Somehow the STS service manages to get a header in the response (missing must understand in the addressing); but it’s a start. Brian From: Martin Gainty [mailto:[email protected]] Sent: Thursday, Septembe

what components handle wsdl generation given POJO?

Trying to figure out all the components involved in generating WSDL from a POJO. My main goal is trying to determine how type names and parameters are generated (I have an idea, but want to look at the code). Can anyone point me to where to look? I have been to org.apache.axis2.description.j

RE: No headers in response

Martin, Okay, I will give it a try. I put the configuration in the application’s service.xml and not the axis2.xml Brian From: Martin Gainty [mailto:[email protected]] Sent: Thursday, September 27, 2012 9:30 AM To: [email protected] Subject: RE: No headers in response Hi B

RE: No headers in response

Hi Brian i'll take the last question.. from axis2.xml i assume you have included optional Headers axis2.xml contains: true run this test where axis2-IncludeOptionalHeadersTrue.xml contains true

Jenkins build is back to normal : Axis2 » Apache Axis2 - Integration #1810

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

No headers in response

I am re-opening a question I saw no answer to asked in this forum quite a while ago. In the STS service requesting a SMAL20 token the response is okay. But in the service that needs to have the SAML20 token, the response has no headers at all. This is in spite of the must understand setting in