Hessian/Burlap support (startup order)

[aomarjee]

I am having a problem deploying two separate web applications into jboss. The first application exposes a hessian web service (server application for all intensive purposes), and the second application is intended to be a client of the exposed web service. If the client application is deployed before the server application jboss hangs, seemingly as if waiting to connect to the server application. Can this be resolved?

I can also duplicate this behaviour in standalone Tomcat?

[Alef Arendsen]

Declare the client proxy as lazy initializing (lazy-init="true"), this should help a bit I guess... Also, jboss has means to specify ordering in which deployment occurs (depends-on), but I don't know if this is the case for wars/ears as well...

Alef