I am using CXF 2.2.3 so things may be a little different for you. I don't
know if the following workaround is acceptable, but it works.
I modified org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker by adding this to
the updateWebServiceContext method:
sm.setVersion(((SoapMessage)exchange.getInMessa
I found an answer to this, but it's rather ugly.
The autoRewriteSoapAddress is the key, but I couldn't find any way to
specify it in the Spring beans file.
Instead I have another bean that, on startup, runs through all the CXF
endpoints and sets the autoRewriteSoapAddress on each of them:
Hi Dan,
I have changed the HelloWorldServer class as
Object implementor = new HelloWorld();
String address = "/helloworld";
Endpoint.publish(address, implementor);
Now it works fine.
Thanks for your help.
When I entered the url http://localhos
Hi Dan,
I have changed the web.xml , now it throws the following error.
javax.xml.ws.WebServiceException:
org.apache.cxf.service.factory.ServiceConstructionException
Regards
Saravanan R
dkulp wrote:
>
>
> I think your web.xml would just be something like:
>
>
> CXFServlet
> com.test
On Thu February 18 2010 8:39:44 am eax wrote:
> Hi everybody,
>
> I am new in CXF (but the topic of the web service is not new for me). I am
> trying to write a CXF-WS with wsdl-first mode using CXFNonSpringServlet
> based servlet.
> I started from a wsdl, then I generated the classes. My first pr
On Fri February 19 2010 2:18:59 pm M Stewart wrote:
> dkulp wrote:
> > The only way I know around it is to write your own
> > com.sun.xml.bind.marshaller.NamespacePrefixMapper
> > and override the methods:
> > String[] getPreDeclaredNamespaceUris()
> > String[] getPreDeclaredNamespaceUris2()
> > to
dkulp wrote:
>
> The only way I know around it is to write your own
> com.sun.xml.bind.marshaller.NamespacePrefixMapper
> and override the methods:
> String[] getPreDeclaredNamespaceUris()
> String[] getPreDeclaredNamespaceUris2()
> to just declare the ones you think are needed up front and th
I think your web.xml would just be something like:
CXFServlet
com.test.HelloWorldServer
1
CXFServlet
/*
Dan
On Thu February 18 2010 6:32:48 pm SaravananRamamoorthy wrote:
> Hi Johan Edstrom,
>
>
> After creating HelloWorld webservice class. I have created a class calle
Are you using WS-SecurityPolicy? If so, you can just set the username on the
RequestContext and the SecurityPolicy engine would pick it up for that
request. You may be able to do it with older WSS4JOutInterceptor, I'm just
not sure how. You may be able to do it similarly with:
((BindingP
Well, you would need to configure something in to handle WS-Security. There
are really two options:
1) Configure in the older WSS4JInInterceptor to handle it
2) Define a WS-SecurityPolicy in the wsdl that defines what is expected.
Some docs at:
http://cxf.apache.org/docs/ws-security.html
Dan
Well, there is a third option you may want to consider: JAX-RS You could
easily create a service that accepts an XML POST and returns a new XML. You
could then extend it later to provide other RESTful methods and such if need
be. Just a thought to throw out there. :-)
Of the two you pr
Yea. Dispatch isn't a proxy. It's a concrete class. You can do
((org.apache.cxf.jaxws.DispatchImpl)dispatch).getClient() to get the client
out of it.
Dan
On Fri February 19 2010 10:08:01 am doug.harmon wrote:
> The "Using java code" section does not show an example for setting a
> timeou
The "Using java code" section does not show an example for setting a timeout
on a javax.xml.ws.Dispatch object. When attempting to pass a dispatch object
to ClientProxy.getClient() I get an "IllegalArgumentException: not a proxy
instance" using cxf 2.2.2. How can I set the timeout in java using th
Hi
I've updated WADLGenerator to check for Aegis IgnoreProperty or JAXB
XmlTransient when listing bean properties as WADL request/representation
parameters. If you use 2.2.6 then you can do the following workaround :
extend WADLGenerator and override a protected doWriteParam(...) method so
that i
Hi there
I use CXF usually to implement web services for wsdl-first approach with a
JAXB/SOAP.
Now, all I have are two samle XML requests and responses which are sent over
HTTP. I have to implement a tactical solution which will be replaced at some
stage.
I've found two approaches to implemen
15 matches
Mail list logo
