Hi Deno,
You can use the jaxws syntax to deal with your annotated service class.
Please ref this URL [1] for more information.
http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html
Cheers,
Willem.
Deno Vichas wrote:
Thanks willem, that was the one.
Now could somebody clue me into the
Thanks for the link. I think I'm close to getting it ported. i'm not
getting a null pointer exception that I don't understand.
My service config looks like;
jaxws:endpoint id=VehicleLookupService
implementor=com.autoreturn.service.VehicleLookupServiceImpl
Benson,
I just noticed that you can get the context handler by the below code
when you get the service engine.
...
JettyHTTPDestination destination = (JettyHTTPDestination)df.getDestination(epi);
ServerEngine engine= destination.getEngine();
ContextHandler context = (ContextHandler)
Hi Luca, the parameter orders on the client side should not matter. The server
retrieves input using name/value pairs. Having this said, I cant guarantee you
that it is bug-free. ;-) I just added a REST system test using JSON as content
type
Hi Jason,
I'm not sure I understand what your outstanding question is, but here's a
quick stab at it. The way to eliminate the outer wrapping is to run it in
unrwapped mode. :-) Wrapped mode allows you to send multiple parameters in
your operation at the cost of creating a wrapper XML element.
JAXB tends to not work very well with Collections/Lists IMO - at least not
right on the parameter class. You may want to try using the Aegis
databinding which works quite well with them. I'll see if I can churn out a
test case though for this and see what might be wrong.
- Dan
On 7/15/07, Brad
Hello all,
it seems WHICH_JARS file is not actual. CXF itself needs
xml-resolver.jar and I am sure there will be other JARs that should be
included in the minimal CXF install.
The second issue about the libraries is that CXF depends on Spring
even when I do not use it. I have created just a
Willem,
When I call getServant, I get back the JettyHTTPHandler. Which,
interestingly enough, will cheerfully return the Jetty Server object
which I was asking for in the first place.
The ContextHandler in which the JettyHTTPHandler lives is somewhat
obscurely connected, I haven't found the
Hello,
I need to set up invoker for my service but I cant find the proper XML
tags for the configuration in the documentation:
http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html
How to do this?
And if I like to do this from the code where should I put it? I mean
when CXF run as
Hello,
I need to create a service that will accept all incoming requests and
relay them to other web service. It seems Invoker can help me over
here. Is it possible to register some global invoker or do I have to
create endpoint+invoker for each service I want to track?
Thanks for help
--
I published new CXF snapshots Saturday morning.If you're using the
snapshots, that could have done it.
Dan
On Monday 16 July 2007 00:51, Brad O'Hearne wrote:
The plot thickens. I changed the code back, so that Collection was no
longer there, and the orginal ArrayList is there. The code
Dan,
Thanks for the reply. I think I may have been in error, but perhaps I
stumbled across something new. I actually did have one more change. The
two methods mentioned were both annotated with the same @WebResult name,
though the types were different, as follows:
@Post
Hi Beanson,
My bad to take the JettyHTTPHandler as ContextHandler.
I just checked the Jetty's handler api, and I didn't find a way to get the
parent handler form a childer handler.
Maybe you can find the Context handler by looking up the context path from
server, or we can add the
MayBe you can try the replace the cxf orignal ServiceInvokerInterceptor in the
bus,
You can find ServiceInvokerInterceptor in the
trunk\rt\core\src\main\java\org\apache\cxf\interceptor\ServiceInvokerInterceptor.java
Willem.
-Original Message-
From: Lukas Zapletal [mailto:[EMAIL
For now, I can ask the org.mortbay.jetty.Server for its list of
Handlers. There is only one in this case, and it's the ContextHandler. I
think that your proposed accessor makes perfect sense when you get
around to it.
-Original Message-
From: Jiang, Ning (Willem) [mailto:[EMAIL
Thanks Dan. That worked.
from the cxf.xml I would like to refer to a bean defined else where like,
simple:server id=Test address=
http://localhost:8081/tes/cxfservices/HelloWorld;
serviceClass=com.test.HelloWorld
simple:serviceBean#helloService/simple:serviceBean
/simple:server
This is
David,
Most likely, it cannot find that class on the classpath. For java2wsdl
to work, the class needs to be compiled and available on the classpath.
You can also run the tool with the -verbose option. That may produce a
better error.
Dan
On Monday 16 July 2007 12:25, Du, David
Hi, Dan,
Thanks for your response, because of your advice, finally I got this
thing working, I misspelled HelloWorld as HellowWorld.
Thanks again
David
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Monday, July 16, 2007 3:08 PM
To: cxf-user@incubator.apache.org
I'm looking for any help I can get on debugging a wrong number of
arguments error. I'm getting from a cxf service hosted via the
embedded Jetty server. We just started a new project and used XFire for
the web services and then ripped it out and put in CXF and don't have
much experience with
Is this a java first case or a wsdl first case? Are there headers
or soap w/ attachments involved? Also, is it a wrapped
doc/lit, bare doc/lit, or rpc/lit?
If it's a java first case with a wrapped doc/lit endpoint, can you try
running java2wsdl with the -s dir flags to generate the
Hi all,
I followed the documentation for converting an XFire services to an
equivalent cxf.xml with no luck. The sample cxf.xml given in the
documentation is broken. It is not a valid xml file.
(http://cwiki.apache.org/CXF20DOC/xfire-migration-guide.html#XFireMigrationGuide-services.xml
)
My
Well, you can ignore the first paragraph. The rest of my analysis turned
out to be correct.
Would anyone care to see the following on a wiki?
EndpointInfo ei = new EndpointInfo();
ei.setAddress(serviceFactory.getAddress());
Destination destination =
You understood it. Thanks. I was hoping that I could control the outer
wrapping markup without having to go to unwrapped mode. It's starting to
look like I'll have to roll my own at this point, as I'd rather have my XML
structured like this:
clients
client
...
/client
/clients
23 matches
Mail list logo
