Hi,
I had got to ask you what version of CXF are you using.
I just traced the code which I had showed to you, I did not step into
the loadBusNoConfig method, because I had the spring-context-*.jar in my
class path.
But I found the key, we should call replaceDestinationFactory() before
createServletController in loadBusNoConfig to avoid passing the NP
(ServletTransport) to the ServletController.
If you are using CXF 2.0.2 , I think adding the spring-context-2.*.jar
into your class path will solve this problem.
My coming up fixing will help you to solve the NPE in most case.
BTW, you do not need to do any configuration on Jetty as the
Jetty-configuration said. Because it is for using Jetty-http transport
and not for the Servlet-http transport.
Willem.
Miguel De Anda wrote:
Actually I do like spring. However, we are currently using it to allow the
customer to configure the app and I don't feel its appropriate for them to
configure the soap interface this way. Our app runs as a standalone java app
and doesn't use an application context. I'm just loading objects using the
following:
Resource resource = new FileSystemResource(config);
BeanFactory factory = new XmlBeanFactory(resource);
Object o = factory.getBean(bean);
After I have "o" I don't keep a bean factory or anything around.
So after looking at that bug report, it makes me wonder if there is something
else. The bug says that it has something to do with an application context
class not being around. Could it be that I'm getting "nulls" because there is
an application class? What can I do to make it work? Should I load my jetty
server from a bean and through the application context so that cxf can find
it and register the endpoints properly?
In other words, if I make my xml config look like what you have in
http://cwiki.apache.org/CXF20DOC/jetty-configuration.html how can I get
reference to the server in my app so that my other servlets can be registered
as well?
Thanks for all your help so far.
On Monday 29 October 2007, Willem Jiang wrote:
O, I can tell the reason form your stack trace, you are not the fans of
Spring ;).
It's definitely a bug of CXFServlet, here is a JIRA[1] for it and I will
do a quick fix for it.
Please have an eye on JIRA[1].
[1]https://issues.apache.org/jira/browse/CXF-1072
Willem.
**********************************************************************
This email, its content and any attachments is PRIVATE AND
CONFIDENTIAL to TANDBERG Television, Part of the Ericsson Group.
If received in error please notify the sender and destroy the original
message and attachments.
www.tandbergtv.com
**********************************************************************
