Just wanted to mention something I ran across so others are aware of it.
If you deploy a bean via -beans.xml (say for example an instance of ClusterPartition) and register it in JMX using the @JMX annotation, queries like this won't work any more:
| MBeanServer server = MBeanServerLocator.locate();
| QueryExp exp = Query.and(
| Query.eq(
| Query.classattr(),
| Query.value(ClusterPartition.class.getName ())
| ),
| Query.match(
| Query.attr("PartitionName"),
| Query.value(name)
| )
| );
|
| Set mbeans = server.queryMBeans (null, exp);
Problem is the restriction using the ClusterPartition class -- the object registered in JMX is an instance of AopContainerProxy, not ClusterPartition.
I found workarounds for this exact issue; this post is just an FYI for others.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987034#3987034
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987034
Dude, please throw us a bone regarding the status/roadmap.
Seriously though, we are looking to replace our qmail implementation no later than 1Q 2007 and would love to use a Java based mail solution. At a minimum we need IMAP and processing rules sufficient to explode mail to multiple recipients. Virtual domain support would be great too.
Thanks in advance for any little hint as to what lies ahead and when it's coming.
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987030#3987030
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987030
Hey there.
Yeah, a lot of this is due to be sorted out now that 2.0.0 is in focus again. The TCPI stuff has been a bit of a hack as a temporary fix to get around making specific design decisions - such as methods like getChildren() and the bazillion casts. A lot of this goes away once we identify better what needs to be in the SPI interface. I don't expect there to be more than a couple of casts to TCPI, if at all, as this breaks the whole purpose of the interface.
You are looking at incomplete code, stitched together to make the Cache interface workable. Once the internals are complete things will be a lot quicker.
Cheers,
Manik
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987023#3987023
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987023