"julien(a)jboss.com" wrote :
| for point 2/ : what would be the behavior ? follow the link or skip it ?
If we follow the links we could get into an infinite loop situation. For example
/a1/
/a1/b1 -> /a1/ [b1 links back to a1]
The other issue is how can this test be integrated into the testsuite? I don't believe Windows has the concept of links (although I could be wrong)
I also think I need to look a bit more into how java handles symlinks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045010#4045010
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045010
I have committed changes...
Basically tasks like scoped-sar were renamed to just sar...
Also release-admin was modified... I have to double check the standalone configuration as that is causing some smoke tests to fail. But most of the work is already done.
As part of this I also did some tests with copying all to messaging, and all worked fine if I removed ha-deployment. I will change deployment descriptors on monday to work fine with that.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4044867#4044867
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4044867
The Configuration class has a "serviceName" property that I can't find a good use for. I'd like to get rid of it as it leaks JMX concerns into the core code.
CacheMgmtInterceptor was using it to figure out a value to add a data to a Notification. With JBCACHE-855 that's no longer the case.
JmxUtil has some static methods that try to use the value to figure out an ObjectName. I don't think that's valid; any code (e.g. xxxJmxWrapper) that's doing a registration should know it's own ObjectName from MBeanRegistration. So, I'll clean that up.
Any objections?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4044768#4044768
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4044768