Done. Here is the URL http://cwiki.apache.org/confluence/display/CXF20DOC/Standalone+HTTP+Transport
-----Original Message----- From: Clough, Samuel (USPC.PRG.Atlanta) [mailto:[EMAIL PROTECTED] Sent: Tue 7/17/2007 20:39 To: [email protected] Subject: RE: Getting the HTTP server off the bus I think it would be helpful on a wiki... -----Original Message----- From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: Monday, July 16, 2007 8:55 PM To: [email protected] Subject: RE: Getting the HTTP server off the bus 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 = df.getDestination(ei); JettyHTTPDestination jettyDestination = (JettyHTTPDestination) destination; ServerEngine engine = jettyDestination.getEngine(); Handler handler = engine.getServant(new URL(serviceFactory.getAddress())); org.mortbay.jetty.Server server = handler.getServer(); Handler serverHandler = server.getHandler(); ContextHandlerCollection contextHandlerCollection = (ContextHandlerCollection)serverHandler; HandlerList handlerList = new HandlerList(); ResourceHandler resourceHandler = new ResourceHandler(); handlerList.addHandler(resourceHandler); handlerList.addHandler(contextHandlerCollection); server.setHandler(handlerList); handlerList.start(); File staticContentFile = new File(staticContentPath); URL targetURL = new URL("file://" + staticContentFile.getCanonicalPath()); FileResource fileResource = new FileResource(targetURL); resourceHandler.setBaseResource(fileResource); > -----Original Message----- > From: Benson Margulies [mailto:[EMAIL PROTECTED] > Sent: Monday, July 16, 2007 8:48 PM > To: [email protected] > Subject: RE: Getting the HTTP server off the bus > > Dan and Willem, > > It looks to me like I'm fairly nearly stuck until you let me fully > control the server wiring unless I'm willing to do some fairly extensive > rewiring of your wiring. > > The jetty doc isn't precisely helpful here, but I have reached the > following tentative view of the situation: > > As things are, the org.mortbay.jetty.Server has, as its singular > handler, a ContextHandlerCollection, which has (at least one) > ContextHandler. ContextHandlers are all about Servlet contexts, of > course. > > Once a ContextHandlerCollection has at least one ContextHandler, it > ignores any ordinary handlers that it has when handling any request that > begins with '/'. > > So, to get a ResourceHandler into the game, I think that I'd have to > create a HandlerList and have that point off to the > ContextHandlerCollection as well as the ResourceHandler, and install it > as the server's handler. > > I have a giant feeling here that there's something basic I'm missing > about Jetty that is supposed to make this easier, but I'm pretty near to > accusing the folks who run the Jetty web site of intentionally making > the version 6 docs less helpful than the version 5 docs to sell more > consulting. > > Probably just sour grapes on my part. > > --benson -------------------------------------------------------- Princeton Retirement Group, Inc - Important Terms This E-mail is not intended for distribution to, or use by, any person or entity in any location where such distribution or use would be contrary to law or regulation, or which would subject Princeton Retirement Group, Inc. or any affiliate to any registration requirement within such location. This E-mail may contain privileged or confidential information or may otherwise be protected by work product immunity or other legal rules. No confidentiality or privilege is waived or lost by any mistransmission. Access, copying or re-use of information by non-intended or non-authorized recipients is prohibited. If you are not an intended recipient of this E-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute any portion of this E-mail. The transmission and content of this E-mail cannot be guaranteed to be secure or error-free. Therefore, we cannot represent that the information in this E-mail is complete, accurate, uncorrupted, timely or free of viruses, and Princeton Retirement Group, Inc. cannot accept any liability for E-mails that have been altered in the course of delivery. Princeton Retirement Group, Inc. reserves the right to monitor, review and retain all electronic communications, including E-mail, traveling through its networks and systems (subject to and in accordance with local laws). If any of your details are incorrect or if you no longer wish to receive mailings such as this by E-mail please contact the sender by reply E-mail. --------------------------------------------------------
