Hi,

started to refactor the way we are configuring webservices (jaxws/jaxrs),
it is mainly based on David work around Services.

Here a little sample to configure wss4j:
http://svn.apache.org/repos/asf/openejb/trunk/openejb/examples/webservice-ws-with-resources-config/

The idea is to get a service by implementation (recognized by the
class-name) then all properties are dependent of the need (jaxws, jaxrs,
...).

The values are resolved in available services when
necessary (often application services === resources.xml; it can be
features, interceptors, ...).

For resolved values you can use "$" prefix for a property value to say it
is another bean.

We probably miss some default Service class to ease completely the usage (i
added a MapFactory for instance) and maybe some wrappers
(WSS4JInInterceptor can't be fully used today out of the box because of the
map of validator/processor and the fact there are 2 constructors with the
same number of parameters) but since it can be provided in the app it is
not very limitating.

any comments are welcomed ;)

*Romain Manni-Bucau*
*Twitter: @rmannibucau*
*Blog: http://rmannibucau.wordpress.com*

Reply via email to