6.0.0.M3 (HornetQ) - JMS destinations not listed in admin-console

[jaikiran]

Unlike the earlier versions of the AS, the default destinations (DLQ and ExpiryQueue) which are deployed in AS 6.0.0.M3 are no longer listed in the admin-console (under Admin console ->  JMS destinations -> Queues/Topics).

Furthermore, clicking on "Add new resource" under the queue/topic to create a new queue/topic throws an exception. Are the queue/topic templates in 6.0.0.M3 changed to handle HornetQ?

[jmesnil]

I see all the Queues under "JMS Manager > JMS Queues".

I am not sure why we left the "JMS Destinations > Queues/Topics". All JMS stuff should go under "JMS Manager" now.

I can't create a queue either, it throws an error:

Caused by: java.lang.NoClassDefFoundError: org/richfaces/validator/NullValueValidator

at org.richfaces.component.UIRichInput.validateInput(UIRichInput.java:42) [:3.3.3.Final]

at org.richfaces.component.html.HtmlInputText.validateValue(HtmlInputText.java:46) [:3.3.3.Final]

at javax.faces.component.UIInput.validate(UIInput.java:941) [:2.0.2-FCS]

at javax.faces.component.UIInput.executeValidate(UIInput.java:1189) [:2.0.2-FCS]

at javax.faces.component.UIInput.processValidators(UIInput.java:691) [:2.0.2-FCS]

However, it is not specific to the JMS resources. Creating a new service binding set throws the same error.

[jaikiran]

So both these appear to be more of admin-console issues, than HornetQ/AS integration.

Jeff Mesnil wrote:

I see all the Queues under "JMS Manager > JMS Queues".

I am not sure why we left the "JMS Destinations > Queues/Topics". All JMS stuff should go under "JMS Manager" now.

Created a discussion here http://community.jboss.org/thread/151845?tstart=0

Jeff Mesnil wrote:

I can't create a queue either, it throws an error:

Caused by: java.lang.NoClassDefFoundError: org/richfaces/validator/NullValueValidator

at org.richfaces.component.UIRichInput.validateInput(UIRichInput.java:42) [:3.3.3.Final]

at org.richfaces.component.html.HtmlInputText.validateValue(HtmlInputText.java:46) [:3.3.3.Final]

at javax.faces.component.UIInput.validate(UIInput.java:941) [:2.0.2-FCS]

at javax.faces.component.UIInput.executeValidate(UIInput.java:1189) [:2.0.2-FCS]

at javax.faces.component.UIInput.processValidators(UIInput.java:691) [:2.0.2-FCS]

However, it is not specific to the JMS resources. Creating a new service binding set throws the same error.

Right, that's the same error I get. I have created a separate thread for this one here http://community.jboss.org/thread/151843?tstart=0

[timfox]

This is odd, Jeff and Andy definitely had the admin console working with HornetQ for the M3 release....

I'm assuming it was actually tested?