My best guess are that its a spring error that tells you that it could
not call the default constructor of the class backing the MessageRouter.
In your case its the messagerouterservice..
Do this seem to give any hints?
regards
Barlotta, Michael [USA] wrote:
Hello, I am using CXF 2.0.3 and
That's pretty interesting all right.
I would say that there might not be much point in dealing directly with
JAXBContext and pretend
that your code is so light and free :-)
Cheers, Sergey
- Original Message -
From: Liu, Jervis [EMAIL PROTECTED]
To: cxf-user@incubator.apache.org
Sent:
Hi
In my tour de cxf, i've now come to the point where I have a test that
checks that the wsdl scheme are registered, and another test that checks
that its looking okay. Next step are to test if the endpoints are
working. Since im using jaxws it seems that I need a wsdl for this,
inorder to
Well, if you REALLY want, you can hide the calling of JAXB in an util, for
example you can extend HTTP Client to make it aware of a JAXBContext and be
able to accept and return a JAXB object, for example following code:
String inputFile =
Jervis,
Thanks for the tips which was exactly what I had been expecting
[Liu, Jervis] You don't have to use JAX-WS Dispatch API in this case. Once
you grab the InputStream from HTTPClient (or other lightweight http client
stack), you can call JAXB to marshal the response to your Customer
This is a nice refactoring effort and indeed the code looks simplier.
My point was not really to do with the fact that the code in your original
proposal was a bit verbose.
IMHO it's kind of trying to catch 2 rabbits at the same time : attempt to write
just a simple HTTP code and still expect
it's my fault I pointed the java2wsdl to a interface and not the actual
implementation.
Nino Saturnino Martinez Vazquez Wael wrote:
Hi
In my tour de cxf, i've now come to the point where I have a test that
checks that the wsdl scheme are registered, and another test that
checks that its
Here's a slightly different point. Look at a JAX-RS demo, at a CustomerService
code [1].
This server code is a receiver when POST/PUT requests are issued to it. For ex,
CustomerService.updateCustomer(Customer).
We don't expect the developers to write their own code to unmarshall it all
Hi I've taken the liberty to write some tests to the archetype, and as
the project im on now needed to use soap its targeted towards soap.
The tests I've done should be incorporated into the archetype so that it
comes with tests (I could go and make the templates if wanted). Although
the
I also need to add some more to the example. I ran out of time before
adding the complex-object input case.
Hi,
I have done some testing to the page test.html.
Two fixes:
1) works with IE 6 and FireFox 2 now;
2) customers table is refreshed, not appended.
Please validate.
Cheers,
YI ZHU
http://www.nabble.com/file/p14437670/test.html test.html
dkulp wrote:
I think these are logged as:
Adding portions of the WSDL in case it helps:
wsdl:definitions name=MessageRouter
targetNamespace=http://x/;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
Nino,
Can you file an enhancement request in our JIRA and attach it there? We
cannot really accept patches/changes except for those that come through
there with the Grant permissions for apache to redistribute check box
checked. It's a legal thing to protect Apache and to protect the users
On Wednesday 19 December 2007, MyScreenName wrote:
Any idea when 2.1 will be declared stable (not snapshot)?
Just out of curiosity, is there a particular feature/fix that you need
from 2.1?
Most BUG FIXES are being back ported to the 2.0.x branch and we are
planning a 2.0.4 patch release with
I believe portName should map to the name of the port in the service.
Not the portType name.
Dan
On Thursday 20 December 2007, Barlotta, Michael [USA] wrote:
@WebServiceProvider(
serviceName=MessageRouterService, mapped to
wsdl:service name
portName=RoutePortType,
Hi,
I try to get used to the inner workings of cxf. I suppose it is possible
to add new ServiceFactories to cxf, but how would this be done?
If I create a new ServiceFactory by subclassing AbstractServiceFactory,
how do I add it to cxf?
Another thing: the documentation talks about customizing
I'm interested in opinions about how the XML Schema 'any' construct
could be mapped to Javascript. Obvious possibilities include:
a) a string of XML
b) a DOM node
c) a function that returns a string of XML, since that could be a
closure over DOM or E4X or whatever someone likes.
Anyone have an
I have always been using CXF deployed on tomcat.
Switching to Jetty embedded I have some problems trying to understand some
things.
When I first publish and Endpoint CXF such as:
Endpoint.publish(address, implementor);
CXF loads the cxf.xml file and the Bus and everything else are instantiated,
hello Jervis,
i'm try to use cxf with a developed framework. This are 3 kind of
problem that i have:
1). when a web service return an application object, the generated
wsdl return more
fields than the necessary to transfer. how can i configure cxf to
define the fields
to transfer?
2). when a
I'm considering implementing (or re-implementing) a service from
REST/SOAP to JSON. I'm wondering if someone has a workable example (the
docs I've found are a bit sparse) in terms of how to configure my
beans.xml and how to set up the SEI.
Thanks!
Thanks Dan, I re-read the docs and you are right. Unfortunately that did not
fix the problem.
I checked the code and the line that generates the NPE is 226 of
WSDLServiceBuilder:
223 PortType bindingPt = binding.getPortType();
226 PortType pt =
All I can think of to try is to run the validator (in our bin directory)
on the wsdl and see if it has any issues with it. Maybe the binding
node doesn't point to the correct portType or something.I don't
really know without looking more at the wsdl.
Dan
On Thursday 20 December 2007,
I have a simple Hello World application that is configured following:
HelloWorld.java Interface
@WebService
public interface HelloWorld
{
String sayHello( @WebParam(name=text) String text );
}
HelloWorldImpl.java
@WebService(endpointInterface = test.jws.HelloWorld)
public class HelloWorldImpl
Hi ,
You can find the example in the CXF_KIT/samples/restful_http_binding
Willem.
Vespa, Anthony J wrote:
I'm considering implementing (or re-implementing) a service from
REST/SOAP to JSON. I'm wondering if someone has a workable example (the
docs I've found are a bit sparse) in terms of how
Hi ,
I think Resin 3.1.3 may ship a earlier version of jaxws-api.jar and CXF
need to use the jaxws-api.2.0.jar.
As you know , JDK 1.60_02 ships with jaxws-api.2.0 jar , so Resin's
jaxws-api jar will get no chance to be loaded.
But there is no any jaxws-api.jar in JDK 1.5.0_06, and the Resin's
Thanks. Putting jaxws-api.jar in jre/lib/ext did the trick. The problem I
have is that I can not put the jar file production environment in the jre
directory. Also, loading war libs first is out of question. Is there a way
to configure Resin to load the jar from a different directory before the
I have never used Resin, I just got some experience from some other
web containers, they provide some kind of configuration to load your
application JAR first.
May be you can ask help from Resin.
Willem.
Atif Khan wrote:
Thanks. Putting jaxws-api.jar in jre/lib/ext did the trick. The
I would encourage you to try CXF JSR-311 (JAX-RS) implementation instead. It is
standard based (CXF HTTP binding is not standard based), and the development
activities around CXF JSR-311 are much more active.
CXF JSR-311 (JAX-RS) demo: samples\restful_jaxrs
System test:
28 matches
Mail list logo
