OMG! I just make some progress... I noticed that it was missing a library. One
of our guys here changed the maven pom b/c it caused some conflicts with
other libraries we use (for the record, I hate maven). Anyway, I got the
neethi jar and it works now.
Thanks, and sorry that the problem
So I do that, and I get these log messages:
2007-10-29 17:45:47.094::INFO: Logging to STDERR via
org.mortbay.log.StdErrLog
2007-10-29 17:45:47.181::INFO: jetty-6.0.2
Oct 29, 2007 5:45:47 PM org.apache.cxf.transport.servlet.CXFServlet
loadBusNoConfig
INFO: load the bus without application
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
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.
Miguel De Anda wrote:
So
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
What version of jetty?
-Original Message-
From: Miguel De Anda [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 24, 2007 10:29 PM
To: cxf-user@incubator.apache.org
Subject: undocumented configuration with jetty
i've got an application (my server) that launches its own jetty
message and attachments.
www.tandbergtv.com
**
--
View this message in context:
http://www.nabble.com/undocumented-configuration-with-jetty-tf4688264.html#a13407166
Sent from the cxf-user mailing list archive at Nabble.com.
using jetty 6.0.2
On Thursday 25 October 2007, Benson Margulies wrote:
What version of jetty?
-Original Message-
From: Miguel De Anda [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 24, 2007 10:29 PM
To: cxf-user@incubator.apache.org
Subject: undocumented configuration
I tried that and nothing changed. I tried moving that block to after the jetty
server is running and it doesn't make that much of a difference.
Should I be worried that I have to use a full url as the first parameter to
Endpoint.publish? In the example I saw, it only had the path.
On Thursday
I've done this by letting CXF configure Jetty for me. (Example at the
end). You then need to write code in your application to locate the
Jetty server and anything you need to connect up to it.
If you don't want to do that, I'd suggest configuring your CXF service
as a full webapp that deploys
Hi ,
I write a simple test with your case.
The services are all published :)
Please see the below code.
public class JettyServer {
public static void main(String[] args) throws Exception {
org.mortbay.jetty.Server httpServer = new Server(9000);
ContextHandlerCollection
i've got an application (my server) that launches its own jetty server for
sending files to external nodes. they currently talk to each other using
simple xml passed in as a post request and in the response. the external
nodes don't run a web server of any kind.
i now need to add a soap
12 matches
Mail list logo
