Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Minor
    • Resolution: Implemented
    • Affects Version/s: Trunk
    • Fix Version/s: Upcoming Release
    • Component/s: framework
    • Labels:
      None

      Description

      • ByAndFinder.java:37, SE_NO_SERIALVERSIONID
        SnVI: org.apache.ofbiz.entity.finder.ByAndFinder is Serializable; consider declaring a serialVersionUID

      This class implements the Serializable interface, but does not define a serialVersionUID field. A change as simple as adding a reference to a .class object will add synthetic fields to the class, which will unfortunately change the implicit serialVersionUID (e.g., adding a reference to String.class will generate a static field class$java$lang$String). Also, different source code to bytecode compilers may use different naming conventions for synthetic variables generated for references to class objects or inner classes. To ensure interoperability of Serializable across versions, consider adding an explicit serialVersionUID.

      • ByConditionFinder.java:39, SE_NO_SERIALVERSIONID
        SnVI: org.apache.ofbiz.entity.finder.ByConditionFinder is Serializable; consider declaring a serialVersionUID

      This class implements the Serializable interface, but does not define a serialVersionUID field. A change as simple as adding a reference to a .class object will add synthetic fields to the class, which will unfortunately change the implicit serialVersionUID (e.g., adding a reference to String.class will generate a static field class$java$lang$String). Also, different source code to bytecode compilers may use different naming conventions for synthetic variables generated for references to class objects or inner classes. To ensure interoperability of Serializable across versions, consider adding an explicit serialVersionUID.

      • EntityFinderUtil.java:166, SE_NO_SERIALVERSIONID
        SnVI: org.apache.ofbiz.entity.finder.EntityFinderUtil$ConditionExpr is Serializable; consider declaring a serialVersionUID

      This class implements the Serializable interface, but does not define a serialVersionUID field. A change as simple as adding a reference to a .class object will add synthetic fields to the class, which will unfortunately change the implicit serialVersionUID (e.g., adding a reference to String.class will generate a static field class$java$lang$String). Also, different source code to bytecode compilers may use different naming conventions for synthetic variables generated for references to class objects or inner classes. To ensure interoperability of Serializable across versions, consider adding an explicit serialVersionUID.

      • EntityFinderUtil.java:265, SE_NO_SERIALVERSIONID
        SnVI: org.apache.ofbiz.entity.finder.EntityFinderUtil$ConditionList is Serializable; consider declaring a serialVersionUID

      This class implements the Serializable interface, but does not define a serialVersionUID field. A change as simple as adding a reference to a .class object will add synthetic fields to the class, which will unfortunately change the implicit serialVersionUID (e.g., adding a reference to String.class will generate a static field class$java$lang$String). Also, different source code to bytecode compilers may use different naming conventions for synthetic variables generated for references to class objects or inner classes. To ensure interoperability of Serializable across versions, consider adding an explicit serialVersionUID.

      • EntityFinderUtil.java:317, SE_NO_SERIALVERSIONID
        SnVI: org.apache.ofbiz.entity.finder.EntityFinderUtil$ConditionObject is Serializable; consider declaring a serialVersionUID

      This class implements the Serializable interface, but does not define a serialVersionUID field. A change as simple as adding a reference to a .class object will add synthetic fields to the class, which will unfortunately change the implicit serialVersionUID (e.g., adding a reference to String.class will generate a static field class$java$lang$String). Also, different source code to bytecode compilers may use different naming conventions for synthetic variables generated for references to class objects or inner classes. To ensure interoperability of Serializable across versions, consider adding an explicit serialVersionUID.

      • EntityFinderUtil.java:340, SE_NO_SERIALVERSIONID
        SnVI: org.apache.ofbiz.entity.finder.EntityFinderUtil$LimitRange is Serializable; consider declaring a serialVersionUID

      This class implements the Serializable interface, but does not define a serialVersionUID field. A change as simple as adding a reference to a .class object will add synthetic fields to the class, which will unfortunately change the implicit serialVersionUID (e.g., adding a reference to String.class will generate a static field class$java$lang$String). Also, different source code to bytecode compilers may use different naming conventions for synthetic variables generated for references to class objects or inner classes. To ensure interoperability of Serializable across versions, consider adding an explicit serialVersionUID.

      • EntityFinderUtil.java:402, SE_NO_SERIALVERSIONID
        SnVI: org.apache.ofbiz.entity.finder.EntityFinderUtil$LimitView is Serializable; consider declaring a serialVersionUID

      This class implements the Serializable interface, but does not define a serialVersionUID field. A change as simple as adding a reference to a .class object will add synthetic fields to the class, which will unfortunately change the implicit serialVersionUID (e.g., adding a reference to String.class will generate a static field class$java$lang$String). Also, different source code to bytecode compilers may use different naming conventions for synthetic variables generated for references to class objects or inner classes. To ensure interoperability of Serializable across versions, consider adding an explicit serialVersionUID.

      • EntityFinderUtil.java:462, SE_NO_SERIALVERSIONID
        SnVI: org.apache.ofbiz.entity.finder.EntityFinderUtil$UseIterator is Serializable; consider declaring a serialVersionUID

      This class implements the Serializable interface, but does not define a serialVersionUID field. A change as simple as adding a reference to a .class object will add synthetic fields to the class, which will unfortunately change the implicit serialVersionUID (e.g., adding a reference to String.class will generate a static field class$java$lang$String). Also, different source code to bytecode compilers may use different naming conventions for synthetic variables generated for references to class objects or inner classes. To ensure interoperability of Serializable across versions, consider adding an explicit serialVersionUID.

      • EntityFinderUtil.java:476, SE_NO_SERIALVERSIONID
        SnVI: org.apache.ofbiz.entity.finder.EntityFinderUtil$GetAll is Serializable; consider declaring a serialVersionUID

      This class implements the Serializable interface, but does not define a serialVersionUID field. A change as simple as adding a reference to a .class object will add synthetic fields to the class, which will unfortunately change the implicit serialVersionUID (e.g., adding a reference to String.class will generate a static field class$java$lang$String). Also, different source code to bytecode compilers may use different naming conventions for synthetic variables generated for references to class objects or inner classes. To ensure interoperability of Serializable across versions, consider adding an explicit serialVersionUID.

      • PrimaryKeyFinder.java:47, SE_NO_SERIALVERSIONID
        SnVI: org.apache.ofbiz.entity.finder.PrimaryKeyFinder is Serializable; consider declaring a serialVersionUID

      This class implements the Serializable interface, but does not define a serialVersionUID field. A change as simple as adding a reference to a .class object will add synthetic fields to the class, which will unfortunately change the implicit serialVersionUID (e.g., adding a reference to String.class will generate a static field class$java$lang$String). Also, different source code to bytecode compilers may use different naming conventions for synthetic variables generated for references to class objects or inner classes. To ensure interoperability of Serializable across versions, consider adding an explicit serialVersionUID.

        Activity

        Hide
        Dennis Balkir Dennis Balkir added a comment -
        • Diamond Operators fixed

        class ByAndFinder:

        • Line 37: it’s not necessary for the class to implement serialVerisonUID

        class ByConditionFinder:

        • Line 39: it’s not necessary for the class to implement serialVerisonUID

        class EntityFinderUtil:

        • removed unnecessary else
        • Line 166: it’s not necessary for the class to implement serialVerisonUID
        • Line 212: changed the String „|“ to ‚|‘ because it is more efficient
        • Line 214: changed the String „,“ to ‚,‘ because it is more efficient
        • Line 262: it’s not necessary for the class to implement serialVerisonUID
        • Line 314: it’s not necessary for the class to implement serialVerisonUID
        • Line 337: it’s not necessary for the class to implement serialVerisonUID
        • Line 399: it’s not necessary for the class to implement serialVerisonUID
        • Line 459: it’s not necessary for the class to implement serialVerisonUID
        • Line 473: it’s not necessary for the class to implement serialVerisonUID

        class PrimaryKeyFinder:

        • Line 47: it’s not necessary for the class to implement serialVerisonUID
        Show
        Dennis Balkir Dennis Balkir added a comment - Diamond Operators fixed class ByAndFinder: Line 37: it’s not necessary for the class to implement serialVerisonUID class ByConditionFinder: Line 39: it’s not necessary for the class to implement serialVerisonUID class EntityFinderUtil: removed unnecessary else Line 166: it’s not necessary for the class to implement serialVerisonUID Line 212: changed the String „|“ to ‚|‘ because it is more efficient Line 214: changed the String „,“ to ‚,‘ because it is more efficient Line 262: it’s not necessary for the class to implement serialVerisonUID Line 314: it’s not necessary for the class to implement serialVerisonUID Line 337: it’s not necessary for the class to implement serialVerisonUID Line 399: it’s not necessary for the class to implement serialVerisonUID Line 459: it’s not necessary for the class to implement serialVerisonUID Line 473: it’s not necessary for the class to implement serialVerisonUID class PrimaryKeyFinder: Line 47: it’s not necessary for the class to implement serialVerisonUID
        Hide
        mbrohl Michael Brohl added a comment -

        Thanks Dennis,

        your patch is in trunk r1813632.

        Show
        mbrohl Michael Brohl added a comment - Thanks Dennis, your patch is in trunk r1813632.

          People

          • Assignee:
            mbrohl Michael Brohl
            Reporter:
            Dennis Balkir Dennis Balkir
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development