> I don't really want to open up the discussion about the low level API > here again, but in 99% of cases any Java developer is going to want > to > use JMS so splitting off the JMS 'layer' so we have amqp-client.jar > and amqp-jms-client.jar is IMO not really what we are after. The Java > client should always be capable of talking JMS from the core client > package. > > Martin >
that's certainly a strong statement. As the code is currently written there is already a clear separation between an AMQP API and JMS. So it would not be a big deal to deliver two jars. That would certainly not prevent any java client to use JMS and it would have the advantage for the 1% (that I believe will be greater than that) java user to not load the JMS layer. Note that this approach could reveal as being very useful when it'll come to support small devices. Arnaud
