My question was not about service dependencies. I want a particular service to stay in
CREATED state for a long time after the deployment is finished. At some point in time
later (which is determined by an external event) it will be started. Essentially I'm
talking about ability to pre-create a
I want to configure jboss service in such a way that when it's deployed it would
remain in CREATED state until some other service makes it transition into STARTED
state later on. Is there a way to specify this in jboss-service.xml or in any other
config file? Is this a bad idea in general?
Thank
anonymous wrote : The session that creates the temporary queue must be the one that
creates the receiver otherwise it won't work.
|
Well, how do you explain the fact that the design that I outlined below works for me?
What is the right way of achieving the functionality that I need, i.e.
- crea
Darran, Adrian,
thank you for your responses. They do shed some more light on the issue,
however my main problem is still unresolved. Perhaps I didn't make myself clear, so
let me try to do this one more time.
My design:
A single Jboss service, multiple remote clients. There is a 2-way communicat
I'm aware of that, but I don't see how this answers my questions. I was trying to show
that _I am_ trying to delete this topic earlier then closing the queue connection, but
getting an exception.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3846164#3846164
I create a temporary queue for each new client connecting to my "server" (a service
running in JBoss). On the server side, I call
TemporaryQueue q = qsession.createTemporaryQueue();
and than pass the value of
tempQueueTopic = q.getQueueName ();
back to the client.
The client than calls
Queue q
