Hi Alain,
why not go with spring.xml and jndi?
Spring allows you to do nice injection of properties with jndi as
datasource. Alternatively you can also write your own
PropertyPlaceHolderConfigurer with a db backend. After a change you can
refresh the spring context.
Together with a jndi implementation with a user interface like in
geronimo you can nicely reconfigure your application.
Greetings
Christian
Am 28.05.2010 16:59, schrieb Alain PANNETIER:
Dear list,
I've started using CXF a few days ago and now find myself already stumbling
on some stump !
My initial goal was to let my Service Endpoint Implementation (say MyWsImp)
acquire some basic configuration parameter (you know, the usual JDBC
connection string parameters etc..., corba ORB port etc).
I do not like these kind of stuff to live under WEB-INF because I do not
want settings to get lost when a redeploy happens.
My Web Container is Tomcat 6, and I thought I'd use some context.xml under
the $CATALINA_HOME conf subfolder because Tomcat is smart enough not to
overwrite an existing context file under this subfolder.
You probably already understood what I just discovered : Spring first
instantiate the endpoint implementation bean and then only the servlet.
I ended up subclassing the CXFServlet (to access the parameters from the
init method).
What I still need is a way to access my endpoint implementation from this
init method to invoke its own init method.
Can someone point me in the right direction ?
Does all that make sense ?
Also I'm interested if you guys have a more direct/preferred way of doing
configuration things (please no web.xml, myWs.properties, spring xml or even
JNDI settings).
I plan to have dynamically changeable settings settable through JMX and the
MBeans persisting themselves in the DB (the
$CATALINA_HOME/conf/<Engine>/<serverNode>/myWs.xml is only to access the
bootstrap parameters)
Thx in advance for your insights,
Alain
--
----
http://www.liquid-reality.de
