jboss-development February 2007

jboss-development@lists.jboss.org

33 participants
860 discussions

Start a nNew thread

jbossretro-testsuite Build Completed With Testsuite Errors

by qa＠jboss.com

18 years, 10 months

1
0
0 / 0

jbpm.3 Build Failed

by qa＠jboss.com

18 years, 10 months

1
0
0 / 0

jboss-head-testsuite-1.6 Build Failed

by qa＠jboss.com

18 years, 10 months

1
0
0 / 0

jboss-3.2-testsuite Build Completed With Testsuite Errors

by qa＠jboss.com

18 years, 10 months

1
0
0 / 0

jboss-4.2-testsuite-sun-1.5 Build Completed With Testsuite Errors

by qa＠jboss.com

18 years, 10 months

1
0
0 / 0

ejb3-4.2-testsuite Build Failed

by qa＠jboss.com

18 years, 10 months

1
0
0 / 0

microcontainer-head-testsuite Build Completed With Testsuite Errors

by qa＠jboss.com

18 years, 10 months

1
0
0 / 0

jboss-4.2-testsuite-1.6 Build Failed

by qa＠jboss.com

18 years, 10 months

1
0
0 / 0

ObjectName property order

by Carlo de Wolf

After breaking my head for two days why dependencies aren't working anymore, Ales kindly pointed out to me that my properties are in the wrong order. It turns out this is a global problem. If I deploy this: <?xml version="1.0" encoding="UTF-8"?> <server> <mbean code="org.jboss.mq.server.jmx.Topic" name="jboss.mq.destination:service=Topic,name=myTestTopic"> <attribute name="JNDIName">topic/myTestTopic</attribute> <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends> </mbean> </server> I get this in jmx-console: jboss.mq.destination * name=myTestTopic,service=Topic Note the reversal of the properties. I'm digging down into this, but maybe this will ring a bell to someone. Carlo

18 years, 10 months

3
2
0 / 0

jboss-4.2-testsuite-sun-1.5 Build Completed With Testsuite Errors

by qa＠jboss.com

18 years, 10 months

1
0
0 / 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-development February 2007