OK Dan, I finally got back to this problem I was having and thought I would
post what I've found in case you have a simple solution. Spring property
resolution works fine for http:client http:proxyAuthorization and
http:tlsClientParameters as you said...however...
What I found is that having a
Alright, I dug into this one a bit more and learned that this is one of the
features they are trying to fix in Spring 3.*. For now, I will post my
solution so that others may benefit...
CXF has a solution for turning off schema validation if you are using their
application context. Since I
Thank you for you answer, Dan.
The problem is trickier, as the configuration works with HTTP (I can pass
through the corporate proxy), and not HTTPs.
With HTTP, Proxy-Authorization and Authorization request headers are already
set in the first POST request (see my previous message). But with
Hi all,
I still have a problem against corporate proxy authentication.
To help solve this, it works against standard HTTP connection, but not if
the endpoint is reached through HTTPS. I have to add the following code (not
production code for the moment) in my client to configure proxy
From TCPmon :
With an HTTP URL endpoint :
POST http://endpoint-server/endpoint-url Content-Type: text/xml;
charset=UTF-8
Authorization: Basic snip/
SOAPAction:
Accept: *
Connection: Keep-Alive
Cache-Control: no-cache
Pragma: no-cache
User-Agent: Java/1.6.0_07
Host: proxy-server:proxy-port
It looks like you set the:
http-conf:authorization
stuff (through config or through code), but didn't set the
http-conf:proxyAuthorization
which would provide the basic auth stuff for communicating with the proxy
server.
Dan
On Mon March 9 2009 9:56:18 am Olivier Billard wrote:
From
Just to add to this thread, I am having trouble with Spring property
resolution in http:client and http:proxyAuthorization as well.
http:tlsClientParameters works fine however.
jmdev wrote:
It appears to work for the conduit now. Thanks! The address property
of jaxws:client does not
Any chance you could produce a small sample for this? I just tried and it
seemed to work fine.
Dan
On Tuesday 27 January 2009 2:16:30 pm jmdev wrote:
Just to add to this thread, I am having trouble with Spring property
resolution in http:client and http:proxyAuthorization as well.
On Tuesday 09 December 2008 8:44:46 am jmdev wrote:
I am using 2.1.4 SNAPSHOT and am still not able to get this working. Is
there anything special one needs to do to get the
PropertyPlaceholderConfigurer to be recognized? Is there an example or
test case that you could refer me to if
On Tuesday 09 December 2008 11:23:35 am Daniel Kulp wrote:
On Tuesday 09 December 2008 8:44:46 am jmdev wrote:
I am using 2.1.4 SNAPSHOT and am still not able to get this working. Is
there anything special one needs to do to get the
PropertyPlaceholderConfigurer to be recognized? Is there
It appears to work for the conduit now. Thanks! The address property of
jaxws:client does not appear to work however. Does that require a similar
fix?
dkulp wrote:
On Tuesday 09 December 2008 11:23:35 am Daniel Kulp wrote:
On Tuesday 09 December 2008 8:44:46 am jmdev wrote:
I am using
On Tuesday 11 November 2008 12:31:32 pm Harry van Rijn wrote:
Hi,
It looks like that properties in the http:conduit element are NOT resolved.
Is there a way out?
This SHOULD be working in CXF 2.1.3, maybe 2.1.2. What version of CXF are
you using?
Dan
I want to refer to configuration
12 matches
Mail list logo
