There are two basic deployment configurations for ActiveMQ brokers: embedded and standalone.
An embedded broker executes within the same JVM process as the client(s) that is using its services. The client communicates with the embedded broker via direct method invocation. Standalone brokers do not have any client applications that co-reside within its JVM. Clients communicate with standalone brokers through TCP/IP network connections. You will need a bridge in order to have ActiveMQ interoperate with BEA's implementation of JMS. Or you could 'embed' ActiveMQ within the WebLogic server d:-) Joe azbel wrote: > > Thanks for replying, Joe. > The client application won't be transitory, but I wonder what you mean by > standalone broker. Do you mean developing it from scratch? That would > require to implement all the polling to the server and the persistance > feature among other things. My idea is to leverage existing projects, but > I'm open to develop something from scratch if it's the only option. > > By the way, the JMS server is WebLogic. Won't there be a problem? > Greetings. > -- View this message in context: http://www.nabble.com/Is-ActiveMQ-suitable-for-this-Store-And-Forward-scenario--tf4693669s2354.html#a13419222 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
