GeoTools
  1. GeoTools
  2. GEOT-3310

app-schema feature chaining requests nonexistent properties

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: app-schema plugin
    • Labels:
      None

      Description

      -------- Original Message --------
      Subject: [Geoserver-users] App schema feature chaining issue
      Date: Wed, 3 Nov 2010 05:46:22 +0800
      From: Ryan Zoerb
      To: geoserver-users@lists.sourceforge.net

      Hi everyone. I'm trying to get application schema with feature chaining working, but I'm running into an issue. I've attached the two mapping files I'm using. WaterWell is the top level element, which can have several nested logElement's. I've been able to successfully get GeoServer to return a correct response without feature chaining, but when I added the chaining, I get this Oracle error: 'ORA-00904: "TIMES": invalid identifier'. Here's the query that GeoServer is doing that returns the error:

      SELECT GW_LEV_PK,AGENCY_CD,SITE_NO,DATES,VALUE,REMARK,REMARK_DS,SOURCE_CD,METHOD_CD,METHOD_DS,QW_ACCURACY,QW_ACCURACY_NM,HOST,DBNUM,DWH_INSERT,LEV_CN,LEV_CR,LEV_MN,LEV_MD,MP_LEV_VA,SL_LEV_VA,LEV_ENT_CD,LEV_STATISTICS_CD,LEV_STATISTICS_NM,DATE_ACY_CD,SL_DATUM_CD,LEV_PARTY_TX,LEV_WEB_CD,LEV_AGENCY_CD,LEV_MPNT_SEQ_NU,LEV_RMK_TX,LEV_EQPID_TX,DWH_SITE_ID,PARAMETER_CODE,SOURCE,VALUE_ALL,AGENCY_CD,SITE_NO,DATES,VALUE,STATUS_CD,STATUS_DS,SOURCE_CD,METHOD_CD,METHOD_DS,QW_ACCURACY,QW_ACCURACY_NM,HOST,DBNUM,DWH_INSERT,LEV_CN,LEV_CR,LEV_MN,LEV_MD,TIMES,MP_LEV_VA,SL_LEV_VA,LEV_ENT_CD,LEV_STATISTICS_CD,LEV_STATISTICS_NM,DATE_ACY_CD,SL_DATUM_CD,LEV_PARTY_TX,LEV_WEB_CD,LEV_AGENCY_CD,LEV_MPNT_SEQ_NU,LEV_RMK_TX,LEV_EQPID_TX,DWH_SITE_ID FROM GWSI_LEVELS WHERE SITE_NO = ?

      The problem is that the GWSI_LEVELS table doesn't have a column called TIMES. All of the other columns are correct (even though most of them are in that list twice). The pattern I see is that the primary key, GW_LEV_PK, is first in the list, then all of the columns are listed in the same order they are in the db (except for GW_LEV_PK). Then, all the columns except the last three are listed again, but TIMES is put in GW_LEV_PK's column position. Can anyone see what could be causing this, or is it a bug?

      Thanks for any help,
      Ryan

      1. gsml_MappedInterval.xml
        3 kB
        Ben Caradoc-Davies
      2. gwml_WaterWell.xml
        5 kB
        Ben Caradoc-Davies

        Activity

        Hide
        Ben Caradoc-Davies added a comment -
        Ryan Z is not a watcher. Victor, please email him your question. (Even better, ask him to watch this issue.)
        Show
        Ben Caradoc-Davies added a comment - Ryan Z is not a watcher. Victor, please email him your question. (Even better, ask him to watch this issue.)
        Hide
        Victor Tey added a comment -
        I have emailed him already :)
        Show
        Victor Tey added a comment - I have emailed him already :)
        Hide
        Ben Caradoc-Davies added a comment -
        Great! (I often paste emails [with addresses removed] into Jira issues to make this even more obvious.)
        Show
        Ben Caradoc-Davies added a comment - Great! (I often paste emails [with addresses removed] into Jira issues to make this even more obvious.)
        Hide
        Victor Tey added a comment -
        No reply from ryan and i was unable to reproduce the same error with the data he had provided therefore I am closing this issue
        Show
        Victor Tey added a comment - No reply from ryan and i was unable to reproduce the same error with the data he had provided therefore I am closing this issue
        Hide
        Andrea Aime added a comment -
        Mass closing all issues in resolved state that have not been reopened nor commented over in the last month
        Show
        Andrea Aime added a comment - Mass closing all issues in resolved state that have not been reopened nor commented over in the last month

          People

          • Assignee:
            Victor Tey
            Reporter:
            Ben Caradoc-Davies
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: