Per this message in the February 2007 thread entitled "HTTP
dependency/decoupling issue", Jetty is supposed to be an optional
dependency for the client side:
http://mail-archives.apache.org/mod_mbox/incubator-cxf-dev/200702.mbox/[EMAIL
PROTECTED]
Specifically, it says:
Of course, there may
My CXF client is using SOAP 1.2 over HTTP. I have specified a SOAP
action in my WSDL for my one bound operation. This action value is
getting sent as follows:
,
| POST /my/service/location HTTP/1.1
| Content-Type: application/soap+xml; charset=UTF-8
| action: "http://my/operation/action";
| ..
I generated a client stub from my WSDL and am testing it against an
existing service of mine. It was amazing to see a default SOAP client
rise to the occasion when I first tried to run my test; it took a
moment to realize that this was not CXF's implementation, as I had not
yet added the proper CXF
I'm using the Maven plugin (artifactId cxf-codegen-plugin, version
2.0-incubator-RC-SNAPSHOT) to generate Java source from my WSDL
document. This is mostly working as expected. Reading the User's Guide
on "Developing a Consumer with CXF"ยน includes instructions for
generating an asynchronous client
Ok, that's fine with me.
Btw, are all these features documented somewhere ? is there as well a good
book covering the WS-* features (-Policy, Security, ...)
Cheers
Guillaume
On 4/30/07, Daniel Kulp <[EMAIL PROTECTED]> wrote:
Guillaume,
On Monday 30 April 2007 10:49, tog wrote:
> I have this i
Whoops. I was wrong about removing the "address" attribute-- it still
doesn't work in the CXFServlet if the address attribute is removed from
the config. Doh.
-Chris
-Original Message-
From: Christopher Moesel [mailto:[EMAIL PROTECTED]
Sent: Monday, April 30, 2007 12:46 PM
To: cxf-user
Sure thing:
https://issues.apache.org/jira/browse/CXF-617
Thanks,
Chris
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Monday, April 30, 2007 12:17 PM
To: cxf-user@incubator.apache.org
Subject: Re: Defining an Endpoint for Standalone AND Webapp Use
On Monday 30 Apr
On Monday 30 April 2007 12:09, Christopher Moesel wrote:
> UPDATE: I've found that if I leave the "address" attribute out of the
> jaxws:endpoint configuration, it then defaults to sensible values
> (from the wsdl binding?) for both standalone and CXFServlet
> deployments.
>
> Which leads to a que
Guillaume,
On Monday 30 April 2007 10:49, tog wrote:
> I have this in my code, isn't it the same ?
>
> if (host != null) {
> conduit.getClient().setProxyServer(host);
> if (port != null) {
>
> conduit.getClient().setProxyServerPort(In
UPDATE: I've found that if I leave the "address" attribute out of the
jaxws:endpoint configuration, it then defaults to sensible values (from
the wsdl binding?) for both standalone and CXFServlet deployments.
Which leads to a question:
Is there a way to make the standalone deployment be portable
Just one thing,
although
conduit.getAuthorization().setUserName(username);
works, I would like to follow the pattern of
AuthorizationPolicy policy conduit.getProxyAuthorization();
policy.setUserName(username);
to modify an existing policy (you may want to clone it for safety)
or just do a
Hello All,
I would like my CXF service to be able to run standalone or within a web
container, depending on the environment... I am using Spring to do my
configuring. My problem is this:
In the config tag, the "address" attribute means
different things depending on how the service is deployed:
Polar
Thanks very much, my problem is solved. I will then provide a small patch to
URIResolver so that proxies are fully supported.
Cheers
Guillaume
On 4/30/07, Polar Humenn <[EMAIL PROTECTED]> wrote:
Hi,
Code correct below:
tog wrote:
> I have this in my code, isn't it the same ?
>
>
Hi,
Code correct below:
tog wrote:
I have this in my code, isn't it the same ?
if (host != null) {
conduit.getClient().setProxyServer(host);
if (port != null) {
conduit.getClient().setProxyServerPort(Integer.parseInt
(port));
I have this in my code, isn't it the same ?
if (host != null) {
conduit.getClient().setProxyServer(host);
if (port != null) {
conduit.getClient().setProxyServerPort(Integer.parseInt
(port));
}
if ((username
You have to set the "ProxyAuthorization" property
or
AuthorizationPolicy policy = httpConduit.getProxyAuthorization();
policy.set
httpConduit.setProxyAuthorization(policy);
Cheers,
-Polar
tog wrote:
Hi Polar,
Thanks for the answer, it's better. Now I have the problem that the
requ
Nevermind-- it looks like the problem is caused because I'm trying to
run it from inside my IDE-- which is using the same java process and
already had jetty loaded.
Running it outside of the IDE fixed the problem.
-Chris
-Original Message-
From: Christopher Moesel [mailto:[EMAIL PROTECTE
Thanks for the pointers, Willem. Now when I load the spring config
files (just via a main method in a Java class), I get an error when it
tries to load the jetty classes. Any ideas what might be going on here?
-Chris
Apr 30, 2007 9:58:09 AM
org.apache.cxf.transport.http_jetty.JettyHTTPDestinati
Hi Polar,
Thanks for the answer, it's better. Now I have the problem that the request
looks like this:
POST http://www.webservicex.net/CurrencyConvertor.asmx HTTP/1.1
Content-Type: text/xml
Authorization: Basic c3UxNjc2NjpraXJhdmk5OA==
SOAPAction: "http://www.webserviceX.NET/ConversionRate";
Cac
To try to answer my own question I think this can be done by creating a
new data-binding class (MessagePartDataBinding) together with a service
factory bean (derived from ReflectionServiceFactoryBean) so that the
each data binding interceptors will call the MessagePartDataBinding
class to create a
Hi Guzillaume,
Yes, you can turn "chunking" off on the client side.
You can "config" it the "Springway"
Or you can do it programatically by
SomePort port = service.getPort(...);
Client client =
ClientProxy.getClient(port);
HttpConduit httpCon
Hi,
I am preparing a patch for being able to use cxf with proxies. I was stuck
till recently by a weird problem after playing and forging the POST request
that cxf is using, I found that my proxy was not supporting chunking. Is
there a way to turn this feature off ?
Cheers
Guillaume
22 matches
Mail list logo