|
| 1.3 | modified | loubyansky | common/src/main/org/jboss/xml/binding/Content.java | added prefix resolving functionality to ContentNavigator |
| 1.3 | modified | loubyansky | common/src/main/org/jboss/xml/binding/ContentNavigator.java | added prefix resolving functionality to ContentNavigator |
| 1.6 | modified | loubyansky | common/src/main/org/jboss/xml/binding/ObjectModelBuilder.java | added prefix resolving functionality to ContentNavigator |
| 1.27 | modified | ejort | jmx/src/main/org/jboss/mx/modelmbean/ModelMBeanInvoker.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.8 | modified | ejort | jmx/src/main/org/jboss/mx/interceptor/AbstractInterceptor.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.9 | modified | ejort | jmx/src/main/org/jboss/mx/interceptor/Interceptor.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.9 | modified | ejort | jmx/src/main/org/jboss/mx/interceptor/ModelMBeanAttributeInterceptor.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.7 | modified | ejort | jmx/src/main/org/jboss/mx/interceptor/ModelMBeanInfoInterceptor.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.11 | modified | ejort | jmx/src/main/org/jboss/mx/interceptor/PersistenceInterceptor.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.7 | modified | ejort | jmx/src/main/org/jboss/mx/interceptor/StandardMBeanInfoInterceptor.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.23 | modified | ejort | jmx/src/main/org/jboss/mx/server/AbstractMBeanInvoker.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.4 | modified | ejort | jmx/src/main/org/jboss/mx/server/AttributeDispatcher.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.6 | modified | ejort | jmx/src/main/org/jboss/mx/server/Dispatcher.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.3 | modified | ejort | jmx/src/main/org/jboss/mx/server/ExceptionHandler.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.7 | modified | ejort | jmx/src/main/org/jboss/mx/server/Invocation.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.12 | modified | ejort | jmx/src/main/org/jboss/mx/server/InvocationContext.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.5 | deleted | ejort | jmx/src/main/org/jboss/mx/server/InvocationException.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.14 | modified | ejort | jmx/src/main/org/jboss/mx/server/ReflectedDispatcher.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.6 | modified | ejort | jmx/src/main/test/implementation/interceptor/support/MySharedInterceptor.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.4 | modified | ejort | testsuite/src/main/org/jboss/test/naming/interceptors/ProxyFactoryInterceptor.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.5 | modified | ejort | testsuite/src/main/org/jboss/test/jmx/interceptors/JNDIPersistence.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.5 | modified | ejort | testsuite/src/main/org/jboss/test/jmx/interceptors/JNDISecurity.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.5 | modified | ejort | testsuite/src/main/org/jboss/test/jmx/interceptors/PrincipalInterceptor.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.5 | modified | ejort | testsuite/src/main/org/jboss/test/jmx/interceptors/SecurityInterceptor.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.5 | modified | ejort | testsuite/src/main/org/jboss/test/security/interceptors/SRPCacheInterceptor.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.3 | modified | ejort | server/src/main/org/jboss/jmx/connector/invoker/AuthenticationInterceptor.java | Remove the use InvocationException from the JMX container - replaced with direct use of Throwable.Also fixed the stupid exception handling wrapping (still need to check a couple of the more obscure JMX exception types).1) The invokers and interceptors are a DynamicMBean implementation - as such they should be throwing JMX compatibleexceptions. Since most of our interceptors are lazy, I have left plain->JMX wrapping in place (for now).2) The dispatcher is responsible for wrapping a POJO in a Dynamic/ModelMBean. It is at this level that theplain->JMX exception wrapping should take place. The invoker or interceptors cannot do this, since they also have tocope with DynamicMBeans where the correct exceptions are already being thrown. |
| 1.11 | modified | ejort | jmx/src/main/javax/management/relation/RelationService.java | Add missing exception handling to the relation service and fix some bugs in findReferencingRelations/getAssociatedMBeans |
| 1.13 | modified | ejort | jmx/src/main/javax/management/relation/RelationSupport.java | Add missing exception handling to the relation service and fix some bugs in findReferencingRelations/getAssociatedMBeans |
