I need a little help. To model Christine's problem, I'm trying to set up a version of a JS sample in which Jetty is running on two ports: one entirely static, one with the web service.
So I have a cxf.xml that has an engine spec for the static content on one port, and then I use the other port in the endpoint. Due to the way we set up the demos for use with ant, I don't get much log traffic, but it looks as if nothing actually starts Jetty on the extra port for the static content. I am tempted to switch the whole thing over being a main program that creates a spring app context and launches the endpoints from there instead of 'programmatically', and it could do likewise for Java if I had to, but if anyone can help me make js_browser_client_cross_url launch the extra jetty from the CXF http-engine config I'd be grateful. On Thu, Jul 10, 2008 at 9:46 AM, Daniel Kulp <[EMAIL PROTECTED]> wrote: > > On Jul 10, 2008, at 7:59 AM, Benson Margulies wrote: > > Can you remind me of the process for building the demos 'where they sit' >> in the regular build hierarchy? >> >> > Once you run "mvn install" in the distribution directory, they should build > fine after that. The mvn install creates some classpath things that the > demos look for. > > --- > Daniel Kulp > [EMAIL PROTECTED] > http://www.dankulp.com/blog > > > > >
