Sorry - I made a typo, that should be port 4204. On Wed, Apr 8, 2009 at 10:08 PM, Jonathan Gallimore < [email protected]> wrote:
> If you haven't already, check out the webservice examples here: > https://svn.apache.org/repos/asf/openejb/trunk/openejb3/examples/ - > specifically the simple-webservice, webservice-security and > webservice-ws-security which I think do you what you want. > > When you start OpenEJB by creating an InitialContext, make sure you have > the remoteable setting on: > > Properties properties = new Properties(); > properties.setProperty(Context.INITIAL_CONTEXT_FACTORY, > "org.apache.openejb.client.LocalInitialContextFactory"); > > properties.setProperty("openejb.embedded.remotable", "true"); > > initialContext = new InitialContext(properties); > > This will ensure that the webservice part of the container is started and > your webservice is deployed. By default, your test will expose webservices > on port 4202. > > Hope that helps. > > Jon > > > > On Wed, Apr 8, 2009 at 4:58 PM, Laird Nelson <[email protected]> wrote: > >> Hello; is there an example out there of how to get a JAX-WS web service >> running in a local container? >> >> With Glassfish, I can mark an SLSB implementation class with the >> @WebService >> annotation, drop the .jar file into the autodeploy directory, and the >> webservice is available. >> >> Currently, I have an OpenEJB container running locally as part of my test >> suite, but I don't see evidence that the same EJB is deployed as a web >> service. I'd like to have that local container automatically deploy my >> web >> service so that I can write a stupid little test case that hits the >> service >> via a URL and verify that it comes up. >> >> I searched the openejb.apache.org site, and didn't find anything that >> addresses this issue specifically--there was a pointer to the Apache CXF >> project, but that kind of left me high and dry. >> >> Any thoughts heartily appreciated. >> >> Best, >> Laird >> > >
