Uploaded image for project: 'OFBiz'
  1. OFBiz
  2. OFBIZ-6523

service findOrders set viewSize and viewIndex to optional

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: Trunk
    • Fix Version/s: 16.11.01
    • Component/s: order
    • Labels:
      None

      Description

      The findOrder service force the value viewSize and viewIndex. Set them as optionnal and if they aren't present resolve it from widgets.properties

        Issue Links

          Activity

          Hide
          jacques.le.roux Jacques Le Roux added a comment -

          Created at OFBIZ-6712

          Show
          jacques.le.roux Jacques Le Roux added a comment - Created at OFBIZ-6712
          Hide
          jacques.le.roux Jacques Le Roux added a comment -

          This indeed needs more work in EntityUtilProperties, but a new Jira should be created, so I close here and create a new Jira

          Show
          jacques.le.roux Jacques Le Roux added a comment - This indeed needs more work in EntityUtilProperties, but a new Jira should be created, so I close here and create a new Jira
          Hide
          soledad Nicolas Malin added a comment -

          Yes I can use EntityUtilProperties, just un element that I don't understand :

              public static Integer getPropertyAsInteger(String resource, String name, int defaultNumber) {
                  return UtilProperties.getPropertyAsInteger(resource, name, defaultNumber);
              }
          

          It's the same code.

          Show
          soledad Nicolas Malin added a comment - Yes I can use EntityUtilProperties, just un element that I don't understand : public static Integer getPropertyAsInteger( String resource, String name, int defaultNumber) { return UtilProperties.getPropertyAsInteger(resource, name, defaultNumber); } It's the same code.
          Hide
          pfm.smits Pierre Smits added a comment -

          Reopening.

          Don't use UtilProperties, as it only applies configuration aspects in .properties files. Use EntityUtilProperties. This will use values in the SystemProperty entity, and will fall back to the .properties file when no data is available in the SystemProperty record.

          This will make it more run time configurable for single instance and in multi-tenancy setups.

          Show
          pfm.smits Pierre Smits added a comment - Reopening. Don't use UtilProperties, as it only applies configuration aspects in .properties files. Use EntityUtilProperties. This will use values in the SystemProperty entity, and will fall back to the .properties file when no data is available in the SystemProperty record. This will make it more run time configurable for single instance and in multi-tenancy setups.
          Hide
          soledad Nicolas Malin added a comment -

          done on trunk at revision 1686691

          Show
          soledad Nicolas Malin added a comment - done on trunk at revision 1686691

            People

            • Assignee:
              soledad Nicolas Malin
              Reporter:
              soledad Nicolas Malin
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development