public final class HttpEndpoint extends HttpEndpoint
HttpContext so that EndpointImpl
may load even without HttpContext.
TODO: But what's the point? If Light-weight HTTP server isn't present,
all the publish operations will fail way. Why is it better to defer
the failure, as opposed to cause the failure as earyl as possible? -KK| Constructor and Description |
|---|
HttpEndpoint(Executor executor,
HttpAdapter adapter) |
| Modifier and Type | Method and Description |
|---|---|
(package private) HttpAdapterList |
getAdapterOwner() |
<T extends EndpointReference> |
getEndpointReference(Class<T> clazz,
Element... referenceParameters) |
void |
publish(Object serverContext) |
void |
publish(String address)
Publishes this endpoint at a localhost's http address.
|
void |
stop()
Stops the published endpoint
|
createpublic HttpEndpoint(Executor executor, HttpAdapter adapter)
public void publish(String address)
HttpEndpointpublish in class HttpEndpointaddress - endpoint's http address
for e.g http://localhost:8080/ctxt/patternpublic void publish(Object serverContext)
HttpAdapterList getAdapterOwner()
public void stop()
HttpEndpointstop in class HttpEndpointpublic <T extends EndpointReference> T getEndpointReference(Class<T> clazz, Element... referenceParameters)
Copyright (c) 1997-2012 Oracle and/or its affiliates. All rights reserved.