Hi
I am trying to use a webservice written in .net, for Sharepoint Portal.
Am using axis2-1.3
Have generated WebService client using eclipse pluggin
In the generated class ServiceServiceSoapStub looks like this,
//.snippet
OperationClient _operationClient =
_serviceClient.createClient(_oper
Hi Saminda,Is this the perfect solution. The reason is that if you look at HttpClient code, you will notice that whether to use Basic or NTLM, it is resolved at runtime. (There is a message of "NTLM scheme selected" or something like that.
Let's say the user specifies "domain/user, password", I gu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jeff, Dims, Paul and all,
To do NTLM Authentication one has to do the following now,
...
HttpTransportProperties.NTLMAuthentication ntlmAuthentication =
new HttpTransportProperties().new NTLMAuthentication();
ntl
Hi Dims,Thanks a lot! When would it be patched? And what's the plan for the next stable release? Thanks!JeffOn 6/8/06, Davanum Srinivas
<[EMAIL PROTECTED]> wrote:Jeff,
Yep. that's the one. Basically http client tries to send the data andwhen it fails tries to send it again. serializeAndConsume by
Jeff,
Yep. that's the one. Basically http client tries to send the data and
when it fails tries to send it again. serializeAndConsume by design
does not cache the information (does not build the om tree). This is
good news just replacing one for the other. We'll take this account
and may be add a
Hi Paul,I assume you meant the element.serializeAndConsume(bytesOut, format);in public byte[] writeBytes() right? No, that didn't work. However, following your lead, I changed the same function in
private void handleOMOutput(OutputStream out, boolean doingMTOM)
Jeff
We have an idea :-) Can you help us test if its any good?
Can you please try this fix:
At line 194 in org.apache.axis2.transport.http.SOAPOverHTTPSender.
Please change
element.serializeAndConsume(out, format); to
element.serialize(out, format);
If that works for you then we can craft a p
Hi Ajith,I still got the same error with the nightly build. Did you ever find what the problem was?Thanks,JeffERROR [main] (WSS.java:65) - problem accessing the parser. Parser already accessed!; nested exception is:
javax.xml.stream.XMLStreamException: problem accessing the parser. Parser alre
Ajith,I tried it. The NTLM seems to be working. However, OM part is still not. Has it been fixed in last night's build?My "fix" of the OMElement doesn't work for some other situations. It throw NULLPointer exception while processing some other returns. Shall I file another bug?
Thanks,JeffOn 6/2/06
Hi Ajith and Paul,Yes, it sounds right: Parser was accessed when not supposed to be, so a calling sequence might be the reason.Thanks for taking care of this so promptly. Let me know if there is anything else I can help with. (Such as a particular build I can test?)
JeffOn 6/2/06, Ajith Ranabahu <[
hi,
Ooops, hit the send by mistake. Please ignore the last post
The reason for this is that the OMElement.serializeAndConsume() has
been called twice
It is not supposed to be! So my guess is the NTLM authentication pat
has to call OMElement.build() first
Ajith
On 6/2/06, Ajith Ranabahu <[EMAIL
Hi,
The reason for this is that OMElement
On 6/2/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Jeff
Thanks for the update. We took a look at it (Saminda and me) and the
update you made to AbstractHttpSender is great. We will add it into
the core tree.
However we still don't understand why you
Jeff
Thanks for the update. We took a look at it (Saminda and me) and the
update you made to AbstractHttpSender is great. We will add it into
the core tree.
However we still don't understand why you are getting into the second
issue and the need to patch OMElementImpl.
Can you please give us so
13 matches
Mail list logo
