-
1. Re: JDK 1.5 clients
leosbitto Jun 19, 2010 5:53 PM (in response to clebert.suconic)Clebert Suconic wrote:
I just looked at HornetQConcurrentLinkedQueue, and it seems it is being used at ClientConsumer. (At least Eclipse tells me HornetQConsumerLinedQueue is used by PriorityLinkedListImpl which is used by the ClientConsumer. (unless I'm missing something).
Isn't there a version of the class we need outside of the JDK 1.6? that would make our lifes easier on supporting 1.5.
It seems to me that in HornetQConcurrentLinkedQueue it is only the method lazySet of AtomicReferenceFieldUpdater which prevents it to be used with Java 5. Maybe that lazySet could be omitted (replaced with a direct access to the volatile field) with only a negligable performance penalty? Check the attached patch.
-
2. Re: JDK 1.5 clients
timfox Jun 20, 2010 3:20 AM (in response to leosbitto)The issue here is not technical, producing a Java 5 client would be simple.
The issue is on product policy - whether EAP will accept and support a Java 5 client. Currently EAP 5+ is Java 6 only.
-
3. Re: JDK 1.5 clients
leosbitto Jun 20, 2010 4:47 AM (in response to timfox)Tim Fox wrote:
The issue here is not technical, producing a Java 5 client would be simple.
The issue is on product policy - whether EAP will accept and support a Java 5 client. Currently EAP 5+ is Java 6 only.
This brings another question regarding the product policy: Will it be possible to buy support for running HornetQ standalone, without EAP? There are situations where messaging provider is all that is needed, without (the need to pay for) the whole EAP...
-
4. Re: JDK 1.5 clients
timfox Jun 20, 2010 5:09 AM (in response to leosbitto)Leos Bitto wrote:
Tim Fox wrote:
The issue here is not technical, producing a Java 5 client would be simple.
The issue is on product policy - whether EAP will accept and support a Java 5 client. Currently EAP 5+ is Java 6 only.
This brings another question regarding the product policy: Will it be possible to buy support for running HornetQ standalone, without EAP? There are situations where messaging provider is all that is needed, without (the need to pay for) the whole EAP...
The million dollar question
I quite agree we need HornetQ to be supported standalone. But these kinds of decisions are not mine to make.