I'm not sure if this is a bug in the test or a bug in
org.jboss.as.ejb3.timerservice.schedule.CalendarBasedTimeout. But I'm
pretty sure that the build will be working again in a few hours.
Happy New Year!
according tot he new JMS API 2.0 you can use the @JMSDestinationDefinition
to define the queue resources you want to have. The functionality is
correct. When I deploy my module I can see it creates the resource as
expected. But when I go to the admin console interface, under the queue I
don't see this resource. Only the ones defined through the jboss-cli or
directly by editing the *.xml configuration file, will be available to be
monitored by the console? Shouldn't the console provide insights for the
other stuff also?
"camel is a horse made up in a laboratory"