hmm,
you want some kind of hot deployment ? Copy jars with with you service
classes and configs and the new service is automatically registered ?
You can try to create your own servlet which extend
XFireSpringServlet and try to reload all services when you discover
some changes in given folder.
On 3/12/07, Vinicius Carvalho <[EMAIL PROTECTED]> wrote:
Hello there! I've already asked this, sorry for the duplicate entry,
but could not find related issues on the list.
Our project developed on XFire is almost 1 year now :D Great! Our
client is very pleased and wants something else... He wants to
register new services, as standalones (just like axis2). We would like
that too :(. I'm having few ideias, and if xfire does not support
already, anyone have tried it before?
My idea is to have a webapp that register the services. A service
would be a jar file + application context of that jar. This webapp
would destroy the spring context on the ServletContext, and re-create
it appending the new jar on the classpath. Every time a new service
was added the webapp would do the same, adding new services to the
"bus".
Any suggestions?
That could be easily done on jboss using deployers, but I do not want
to tie it to a specific AS.
Regards
--
JBoss Certified Advanced J2EE Developer
IBM Certified SOA Solution Designer
IBM Database Associate - DB2 UDB V8.1 Family
Sun Certified Enterprise Architect (Part I)
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
--
-----
When one of our products stops working, we'll blame another vendor
within 24 hours.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
