Removal of migrated or obsolute artifacts.

[yangtools.git] / yang / yang-binding / src / main / java / org / opendaylight / yangtools / yang / binding / DataObjectSerializerRegistry.java

diff --git a/yang/yang-binding/src/main/java/org/opendaylight/yangtools/yang/binding/DataObjectSerializerRegistry.java b/yang/yang-binding/src/main/java/org/opendaylight/yangtools/yang/binding/DataObjectSerializerRegistry.java
deleted file mode 100644 (file)
index 3c6a74b..0000000
--- a/yang/yang-binding/src/main/java/org/opendaylight/yangtools/yang/binding/DataObjectSerializerRegistry.java
+++ /dev/null
@@ -1,29 +0,0 @@
-/*
- * Copyright (c) 2014 Cisco Systems, Inc. and others.  All rights reserved.
- *
- * This program and the accompanying materials are made available under the
- * terms of the Eclipse Public License v1.0 which accompanies this distribution,
- * and is available at http://www.eclipse.org/legal/epl-v10.html
- */
-package org.opendaylight.yangtools.yang.binding;
-
-/**
- * SPI-level contract for registry of {@link DataObjectSerializer}.
- * The contract is kept between implementation of {@link DataObjectSerializerImplementation},
- * Registry provides lookup for serializers to support recursive
- * serialization of nested {@link DataObject}s.
- *
- * FIXME: this interface needs to be moved into .spi, but due to classpath funkyness
- *        of OSGi, that change has to be carefully orchestrated to ensure proper imports
- *        exist in all generated pacakges. One avenue how to achieve that is to move
- *        {@link YangModuleInfo} and modify code generator to add a static field
- *        to all generated classes which will point to the per-model YangModuleInfo
- *        (currently all users of it have to walk the package hierarchy, so that
- *        is an improvement in and of itself).
- *
- */
-public interface DataObjectSerializerRegistry {
-
-    DataObjectSerializer getSerializer(Class<? extends DataObject> binding);
-
-}