Hi Kumar,
WS features can be used on both sides. You can either pass them
directly during WS endpoint/proxy instantiation, which is on the
server side possible only in WS Provider scenario. Another option how
to pass in a WS feature on the server side in a "From Java" scenario
is to use an annotation that is bound to a feature (via
@WebServiceFeatureAnnotation meta-annotation). Last option is to
implement PolicyFeatureConfigurator and PolicyMapConfigurator SPI and
implement the bi-directional transformation between policy
assertion(s) and WS feature(s) during a deployment.
By doing the above you can consolidate all your domain configuration
into a WS feature (or set of WS features). This also let's you to use
different ways of configuring your domain without a need to process
all the config ways separately at runtime. At the same time, it will
automatically expose your runtime configuration (via features/
annotations) as WS policies in the generated WSDL.
For a simple example see how MakeConnection configuration is
implemented:
com.sun.xml.ws.rx.mc.MakeConnectionSupportedFeature -
MakeConnection feature class
com.sun.xml.ws.rx.mc.MakeConnectionSupported -
MakeConnection feature-bound annotation class
com.sun.xml.ws.rx.policy.spi_impl.RxFeatureConfigurator - policy
assertion to policy feature transformation
com.sun.xml.ws.rx.policy.spi_impl.RxPolicyMapConfigurator - policy
feature to policy assertion transformation
Marek
On 4.11.2009, at 10:21, Kumar Jayanti wrote:
> Hi,
> Can JAXWS Feature's be used on the server side. I always thought
> Features are client side things which can be passed to the Service
> in the getXXPort() calls. How do we configure a service with a
> Feature (is it via Annotation ?).
>
> regards,
> kumar
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...
