> Question: Can I use anycast prefix to still have 'jms.queue' appended?
Yes, I believe that will work.
Justin
- Original Message -
From: "abhijith"
To: users@activemq.apache.org
Sent: Wednesday, May 10, 2017 3:02:56 PM
Subject: Re: Artemis v2.0 JDK8 dep
Thanks for the clarification. I will use CLI tool.
Question: Can I use anycast prefix to still have 'jms.queue' appended? We
have built some conventions around this prefix and checking if we have
change it.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-v2-0
rs@activemq.apache.org
Sent: Wednesday, May 10, 2017 10:16:34 AM
Subject: Re: Artemis v2.0 JDK8 dependency
Thanks for the clarification.
Since we are talking about upgrade had one more question.
Is defining JMS queues using tag in broker.xml not valid anymore in
Artemis v2.0? I looked at J
Pull request ? :)
On Wed, May 10, 2017 at 1:35 PM abhijith wrote:
> You have downgrade dependencies to be JDK7 compatible. You could just
> include
> http://www.mojohaus.org/extra-enforcer-rules/enforceBytecodeVersion.html
> and
> it will flag any issues including dependencies.
>
>
>
> --
> V
You have downgrade dependencies to be JDK7 compatible. You could just
include
http://www.mojohaus.org/extra-enforcer-rules/enforceBytecodeVersion.html and
it will flag any issues including dependencies.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-v2-0-JDK8-d
We can probably fix 1.5.x.. I'm not sure about the dependencies.
On Wed, May 10, 2017 at 1:11 PM, abhijith wrote:
> Another note which is on v1.5.4. This version also suffers from same
> bytecode compatibility issues.
>
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce) @
> credit-artemi
Another note which is on v1.5.4. This version also suffers from same
bytecode compatibility issues.
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce) @
credit-artemis-client ---
[INFO] Restricted to JDK 1.7 yet
org.apache.activemq:artemis-journal:jar:1.5.4:test contains
org/apache/activemq
below are the files
➜ activemq-artemis git:(master) grep -rnw . -e ""
./artemis-cli/src/test/resources/broker-reload.xml:25:
./artemis-cli/src/test/resources/broker.xml:25:
./artemis-features/src/main/resources/artemis.xml:28:
./artemis-junit/src/test/resources/embedded-artemis-jms-only.
On Wed, May 10, 2017 at 11:16 AM, abhijith wrote:
> Thanks for the clarification.
>
> Since we are talking about upgrade had one more question.
>
> Is defining JMS queues using tag in broker.xml not valid anymore in
> Artemis v2.0?
Yes.. it's not valid any longer... you may use the import
confi
Thanks for the clarification.
Since we are talking about upgrade had one more question.
Is defining JMS queues using tag in broker.xml not valid anymore in
Artemis v2.0? I looked at JMS examples and it has been moved to new
model. But I could still see bunch of references of it under
tests/
If you don't need AMQP and just JMS I would stick with 1.5.5.
If you need AMQP or other clients beyond Java then get 2.0 and use an 1.5.5
client for what you need.
On Wed, May 10, 2017 at 9:53 AM abhijith wrote:
> sorry, any suggestion here?
>
>
>
> -
> View this message in context:
> http://ac
sorry, any suggestion here?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-v2-0-JDK8-dependency-tp4725798p4725888.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Thanks for the info. Our broker itself is running on Jdk8, so that is not a
problem.
Its the client I am concerned about. We have a mixture of Jdk7 and jdk8
clients(publishers and consumers). So, we would like to give them an option
to use either and upgrade to jdk8 at their convenient time.
There are a few lambda uses on Artemis. You can probably bypass them on a
fork and some consulting gig. Although you could maybe use AMQP client or
openwire client?
I'm not sure about netty. What's the requirement. I would suggest an older
AMQP or openwire client thought.
On Mon, May 8, 2017
14 matches
Mail list logo
