forcing the 3.4 validating service registration should not disallow 3.5 service to be accessed when it's present
diff --git a/modeling/plugins/org.eclipse.pde.emfforms/src/org/eclipse/pde/emfforms/internal/validation/ValidatingEContentAdapter.java b/modeling/plugins/org.eclipse.pde.emfforms/src/org/eclipse/pde/emfforms/internal/validation/ValidatingEContentAdapter.java
index e24adda..ebea020 100644
--- a/modeling/plugins/org.eclipse.pde.emfforms/src/org/eclipse/pde/emfforms/internal/validation/ValidatingEContentAdapter.java
+++ b/modeling/plugins/org.eclipse.pde.emfforms/src/org/eclipse/pde/emfforms/internal/validation/ValidatingEContentAdapter.java
@@ -8,7 +8,7 @@
* Contributors:
* Anyware Technologies - initial API and implementation
*
- * $Id: ValidatingEContentAdapter.java,v 1.7 2009/08/28 09:43:26 bcabe Exp $
+ * $Id: ValidatingEContentAdapter.java,v 1.8 2009/09/02 14:09:35 bcabe Exp $
*/
package org.eclipse.pde.emfforms.internal.validation;
@@ -67,9 +67,7 @@
BundleContext context = Activator.getDefault().getBundle().getBundleContext();
Properties serviceProperties = new Properties();
serviceProperties.put(Constants.SERVICE_RANKING, 10); //$NON-NLS-1$
- validatingService = new ValidatingService34();
- context.registerService(ValidatingService.class.getName(), validatingService, serviceProperties);
-
+ context.registerService(ValidatingService.class.getName(), new ValidatingService34(), serviceProperties);
}
}
