[Geoserver-users] App-schema and CharacterString Type

snuffy · October 11, 2013, 12:58am

Hello All,

I am trying to use the following constructs from the GMD namespace: CI_Contact / CI_Telephone + CI_Address

It uses the ‘CharacterString_PropertyType’ which when i look at:
http://www.isotc211.org/2005/gco/basicTypes.xsd

States:

<xs:element name="CharacterString" type="xs:string"/>
	
<xs:complexType name="CharacterString_PropertyType">
	<xs:sequence minOccurs="0">
		<xs:element ref="gco:CharacterString"/>
	</xs:sequence>
	<xs:attribute ref="gco:nilReason"/>
</xs:complexType>

So it appears it maps back to the general ‘string’ type, but it is not working when trying to populate the entry with a varchar from the DB.

Ideas? (Below is trace output from geoserver.log)

2013-10-11 11:11:11,192 TRACE [org.geotools.data.complex.filter] - ENTRY FeatureImpl:CI_Address<CI_Address_Type id=2>= gmd:city next city null null
2013-10-11 11:11:11,192 TRACE [org.geotools.data.complex.filter] - ENTRY FeatureImpl:CI_Address<CI_Address_Type id=2>=[ComplexAttributeImpl:city<CharacterString_PropertyType>=] gmd:postalCode null null null

Thanks in advance

Ben_Caradoc-Davies · October 14, 2013, 3:33am

Please provide your mapping file and a description of the problem (empty or missing element)?

Kind regards,
Ben.

On 11/10/13 08:58, snuffy wrote:

Hello All,

I am trying to use the following constructs from the GMD namespace:
CI_Contact / CI_Telephone + CI_Address

It uses the 'CharacterString_PropertyType' which when i look at:
http://www.isotc211.org/2005/gco/basicTypes.xsd

States:

<xs:element name="CharacterString" type="xs:string"/>

<xs:complexType name="CharacterString_PropertyType">
  <xs:sequence minOccurs="0">
    <xs:element ref="gco:CharacterString"/>
  </xs:sequence>
  <xs:attribute ref="gco:nilReason"/>
</xs:complexType>

So it appears it maps back to the general 'string' type, but it is not
working when trying to populate the entry with a varchar from the DB.

Ideas? (Below is trace output from geoserver.log)

2013-10-11 11:11:11,192 TRACE [org.geotools.data.complex.filter] - ENTRY
FeatureImpl:CI_Address<CI_Address_Type id=2>= gmd:city next city null null
2013-10-11 11:11:11,192 TRACE [org.geotools.data.complex.filter] - ENTRY
FeatureImpl:CI_Address<CI_Address_Type
id=2>=[ComplexAttributeImpl:city<CharacterString_PropertyType>=]
gmd:postalCode null null null

Thanks in advance

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk

_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

snuffy · October 14, 2013, 6:14am

Hello Ben,

I think my issue was I read it wrongly,

So CI_Contact and friends use ‘gco:CharacterString’ as their types which in turn is a string…

eg: http://www.schemacentral.com/sc/niem21/e-gmd_phone-1.html

Using a mapping like the following then worked correctly:

gmd:electronicMailAddress/gco:CharacterString fcon_email

The mapping below failed because it was expecting a ‘gco:CharacterString’ entry not a string.

gmd:electronicMailAddress fcon_email

···

On 14 October 2013 14:33, Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com> wrote:

Please provide your mapping file and a description of the problem (empty or missing element)?

Kind regards,
Ben.

On 11/10/13 08:58, snuffy wrote:

Hello All,

I am trying to use the following constructs from the GMD namespace:
CI_Contact / CI_Telephone + CI_Address

It uses the ‘CharacterString_PropertyType’ which when i look at:
http://www.isotc211.org/2005/gco/basicTypes.xsd

States:

<xs:element name=“CharacterString” type=“xs:string”/>

<xs:complexType name=“CharacterString_PropertyType”>
<xs:sequence minOccurs=“0”>
<xs:element ref=“gco:CharacterString”/>
</xs:sequence>
<xs:attribute ref=“gco:nilReason”/>
</xs:complexType>

So it appears it maps back to the general ‘string’ type, but it is not
working when trying to populate the entry with a varchar from the DB.

Ideas? (Below is trace output from geoserver.log)

2013-10-11 11:11:11,192 TRACE [org.geotools.data.complex.filter] - ENTRY
FeatureImpl:CI_Address<CI_Address_Type id=2>= gmd:city next city null null
2013-10-11 11:11:11,192 TRACE [org.geotools.data.complex.filter] - ENTRY
FeatureImpl:CI_Address<CI_Address_Type
id=2>=[ComplexAttributeImpl:city<CharacterString_PropertyType>=]
gmd:postalCode null null null

Thanks in advance

October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk

Geoserver-users mailing list
Geoserver-users@anonymised.comsourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–
Ben Caradoc-Davies Ben.Caradoc-Davies@anonymised.com
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

snuffy · October 14, 2013, 6:22am

As a minor follow up to this.

I’ve tried taking my ‘company’ schema and adding a CI_Contact entry.

I believe something is not right in my xsd/xml.

The error is listed below:

ows:ExceptionText
java.lang.RuntimeException: Error applying mapping with targetAttribute company:contactInfo Error applying mapping with targetAttribute company:contactInfo java.io.IOException null Schema ‘person’ does not exist.

Have attached zip with relevant files.

company-app-schema.zip (385 KB)

···

On 14 October 2013 17:14, snuffy <snuffy22@anonymised.com> wrote:

Hello Ben,

I think my issue was I read it wrongly,

So CI_Contact and friends use ‘gco:CharacterString’ as their types which in turn is a string…

eg: http://www.schemacentral.com/sc/niem21/e-gmd_phone-1.html

Using a mapping like the following then worked correctly:
gmd:electronicMailAddress/gco:CharacterString fcon_email
The mapping below failed because it was expecting a ‘gco:CharacterString’ entry not a string.
gmd:electronicMailAddress fcon_email

On 14 October 2013 14:33, Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com> wrote:

Please provide your mapping file and a description of the problem (empty or missing element)?

Kind regards,
Ben.

On 11/10/13 08:58, snuffy wrote:

Hello All,

I am trying to use the following constructs from the GMD namespace:
CI_Contact / CI_Telephone + CI_Address

It uses the ‘CharacterString_PropertyType’ which when i look at:
http://www.isotc211.org/2005/gco/basicTypes.xsd

States:

<xs:element name=“CharacterString” type=“xs:string”/>

<xs:complexType name=“CharacterString_PropertyType”>
<xs:sequence minOccurs=“0”>
<xs:element ref=“gco:CharacterString”/>
</xs:sequence>
<xs:attribute ref=“gco:nilReason”/>
</xs:complexType>

So it appears it maps back to the general ‘string’ type, but it is not
working when trying to populate the entry with a varchar from the DB.

Ideas? (Below is trace output from geoserver.log)

2013-10-11 11:11:11,192 TRACE [org.geotools.data.complex.filter] - ENTRY
FeatureImpl:CI_Address<CI_Address_Type id=2>= gmd:city next city null null
2013-10-11 11:11:11,192 TRACE [org.geotools.data.complex.filter] - ENTRY
FeatureImpl:CI_Address<CI_Address_Type
id=2>=[ComplexAttributeImpl:city<CharacterString_PropertyType>=]
gmd:postalCode null null null

Thanks in advance

October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk

Geoserver-users mailing list
Geoserver-users@anonymised.comsourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–
Ben Caradoc-Davies Ben.Caradoc-Davies@anonymised.com
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

Ben_Caradoc-Davies · October 14, 2013, 6:30am

I was also surprised by the use of string as the simple content of a complex property in this way; this encoding style differs from the use of gml:MeasureType and gml:CodeType. Good to hear you got it working.

Kind regards,
Ben.

On 14/10/13 14:14, snuffy wrote:

Hello Ben,

I think my issue was I read it wrongly,

So CI_Contact and friends use 'gco:CharacterString' as their types
which in turn is a string..

eg: http://www.schemacentral.com/sc/niem21/e-gmd_phone-1.html

Using a mapping like the following then worked correctly:

         <AttributeMapping>

<targetAttribute>gmd:electronicMailAddress/gco:CharacterString</targetAttribute>
           <sourceExpression>
             <OCQL>fcon_email</OCQL>
           </sourceExpression>
         </AttributeMapping>

The mapping below failed because it was expecting a
'gco:CharacterString' entry not a string.

         <AttributeMapping>
           <targetAttribute>gmd:electronicMailAddress</targetAttribute>
           <sourceExpression>
             <OCQL>fcon_email</OCQL>
           </sourceExpression>
         </AttributeMapping>

On 14 October 2013 14:33, Ben Caradoc-Davies
<Ben.Caradoc-Davies@anonymised.com <mailto:Ben.Caradoc-Davies@anonymised.com>> wrote:

    Please provide your mapping file and a description of the problem
    (empty or missing element)?

    Kind regards,
    Ben.

    On 11/10/13 08:58, snuffy wrote:

        Hello All,

        I am trying to use the following constructs from the GMD namespace:
        CI_Contact / CI_Telephone + CI_Address

        It uses the 'CharacterString_PropertyType' which when i look at:
        http://www.isotc211.org/2005/__gco/basicTypes.xsd
        <http://www.isotc211.org/2005/gco/basicTypes.xsd>

        States:

        <xs:element name="CharacterString" type="xs:string"/>

        <xs:complexType name="CharacterString___PropertyType">
                 <xs:sequence minOccurs="0">
                         <xs:element ref="gco:CharacterString"/>
                 </xs:sequence>
                 <xs:attribute ref="gco:nilReason"/>
        </xs:complexType>

        So it appears it maps back to the general 'string' type, but it
        is not
        working when trying to populate the entry with a varchar from
        the DB.

        Ideas? (Below is trace output from geoserver.log)

        2013-10-11 11:11:11,192 TRACE
        [org.geotools.data.complex.__filter] - ENTRY
        FeatureImpl:CI_Address<CI___Address_Type id=2>= gmd:city next
        city null null
        2013-10-11 11:11:11,192 TRACE
        [org.geotools.data.complex.__filter] - ENTRY
        FeatureImpl:CI_Address<CI___Address_Type
        id=2>=[ComplexAttributeImpl:__city<CharacterString___PropertyType>=]
        gmd:postalCode null null null

        Thanks in advance

        ------------------------------__------------------------------__------------------
        October Webinars: Code for Performance
        Free Intel webinars can help you accelerate application performance.
        Explore tips for MPI, OpenMP, advanced profiling, and more. Get
        the most from
        the latest Intel processors and coprocessors. See abstracts and
        register >
        http://pubads.g.doubleclick.__net/gampad/clk?id=60134071&iu=__/4140/ostg.clktrk
        <http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk>

        _________________________________________________
        Geoserver-users mailing list
        Geoserver-users@anonymised.com
        <mailto:Geoserver-users@lists.sourceforge.net>
        https://lists.sourceforge.net/__lists/listinfo/geoserver-users
        <https://lists.sourceforge.net/lists/listinfo/geoserver-users>

    --
    Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
    Software Engineer
    CSIRO Earth Science and Resource Engineering
    Australian Resources Research Centre

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

Ben_Caradoc-Davies · October 14, 2013, 6:34am

Do you have a full stack trace?

On 14/10/13 14:22, snuffy wrote:

As a minor follow up to this.

I've tried taking my 'company' schema and adding a CI_Contact entry.

I believe something is not right in my xsd/xml.

The error is listed below:

<ows:ExceptionText>
java.lang.RuntimeException: Error applying mapping with targetAttribute
company:contactInfo Error applying mapping with targetAttribute
company:contactInfo java.io.IOException null Schema 'person' does not exist.

Have attached zip with relevant files.

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

snuffy · October 14, 2013, 11:11pm

Attached is stack trace…

Appears to be having issue with sql…

I think I know where the issue might be… it is possible it is trying to join between two databases.

(It was)

I have two different databases and two different jdbc connections, each project uses their own… except…

An app-schema feature can only describe a single jdbc datasource, so even though each db has their own version of the ‘ci_contact’ and friends table, when app-schema does a query its locked into the one jdbc datasource.

I guess if I want to implement separate db’s which share another common featureType from an external namespace i’ll need to have separate geoservers or have it within a single database schema.

Thanks

stack-trace.txt (16.3 KB)

···

On 14 October 2013 17:34, Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com> wrote:

Do you have a full stack trace?

On 14/10/13 14:22, snuffy wrote:

As a minor follow up to this.

I’ve tried taking my ‘company’ schema and adding a CI_Contact entry.

I believe something is not right in my xsd/xml.

The error is listed below:

ows:ExceptionText
java.lang.RuntimeException: Error applying mapping with targetAttribute
company:contactInfo Error applying mapping with targetAttribute
company:contactInfo java.io.IOException null Schema ‘person’ does not exist.

Have attached zip with relevant files.

–
Ben Caradoc-Davies Ben.Caradoc-Davies@anonymised.com
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

Ben_Caradoc-Davies · October 15, 2013, 1:46am

Aha! Because app-schema can use separate connections for different feature types, it should work with chaining across different databases, but only if joining is turned off. It looks like you have found a use-case that does not automatically turn off joining; this is a bug. You can manually turn off joining in your app-schema.properties file:
http://docs.geoserver.org/latest/en/user/data/app-schema/joining.html#conditions

Kind regards,
Ben.

On 15/10/13 07:11, snuffy wrote:

Attached is stack trace..

Appears to be having issue with sql..

I think I know where the issue might be.. it is possible it is trying to
join between two databases.

(It was)

I have two different databases and two different jdbc connections, each
project uses their own.. except..

An app-schema feature can only describe a single jdbc datasource, so
even though each db has their own version of the 'ci_contact' and
friends table, when app-schema does a query its locked into the one jdbc
datasource.

I guess if I want to implement separate db's which share another common
featureType from an external namespace i'll need to have separate
geoservers or have it within a single database schema.

Thanks

On 14 October 2013 17:34, Ben Caradoc-Davies
<Ben.Caradoc-Davies@anonymised.com <mailto:Ben.Caradoc-Davies@anonymised.com>> wrote:

    Do you have a full stack trace?

    On 14/10/13 14:22, snuffy wrote:

        As a minor follow up to this.

        I've tried taking my 'company' schema and adding a CI_Contact entry.

        I believe something is not right in my xsd/xml.

        The error is listed below:

        <ows:ExceptionText>
        java.lang.RuntimeException: Error applying mapping with
        targetAttribute
        company:contactInfo Error applying mapping with targetAttribute
        company:contactInfo java.io.IOException null Schema 'person'
        does not exist.

        Have attached zip with relevant files.

    --
    Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
    Software Engineer
    CSIRO Earth Science and Resource Engineering
    Australian Resources Research Centre

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

Angreani_Rini_Minera · October 15, 2013, 3:44am

Perhaps we could improve the joining setting by applying it per feature type, instead of per GeoServer instance.
I raised this task, but I can't commit on working on it anytime soon.
https://jira.codehaus.org/browse/GEOT-4596

-----Original Message-----
From: Caradoc-Davies, Ben (CESRE, Kensington)
Sent: Tuesday, 15 October 2013 9:47 AM
To: snuffy
Cc: geoserver-users@lists.sourceforge.net; Angreani, Rini (CESRE, Kensington)
Subject: Re: [Geoserver-users] App-schema and CharacterString Type

Aha! Because app-schema can use separate connections for different feature types, it should work with chaining across different databases, but only if joining is turned off. It looks like you have found a use-case that does not automatically turn off joining; this is a bug.
You can manually turn off joining in your app-schema.properties file:
http://docs.geoserver.org/latest/en/user/data/app-schema/joining.html#conditions

Kind regards,
Ben.

On 15/10/13 07:11, snuffy wrote:

Attached is stack trace..

Appears to be having issue with sql..

I think I know where the issue might be.. it is possible it is trying
to join between two databases.

(It was)

I have two different databases and two different jdbc connections,
each project uses their own.. except..

An app-schema feature can only describe a single jdbc datasource, so
even though each db has their own version of the 'ci_contact' and
friends table, when app-schema does a query its locked into the one
jdbc datasource.

I guess if I want to implement separate db's which share another
common featureType from an external namespace i'll need to have
separate geoservers or have it within a single database schema.

Thanks

On 14 October 2013 17:34, Ben Caradoc-Davies
<Ben.Caradoc-Davies@...367... <mailto:Ben.Caradoc-Davies@…367…>> wrote:

    Do you have a full stack trace?

    On 14/10/13 14:22, snuffy wrote:

        As a minor follow up to this.

        I've tried taking my 'company' schema and adding a CI_Contact entry.

        I believe something is not right in my xsd/xml.

        The error is listed below:

        <ows:ExceptionText>
        java.lang.RuntimeException: Error applying mapping with
        targetAttribute
        company:contactInfo Error applying mapping with targetAttribute
        company:contactInfo java.io.IOException null Schema 'person'
        does not exist.

        Have attached zip with relevant files.

    --
    Ben Caradoc-Davies <Ben.Caradoc-Davies@...367...>
    Software Engineer
    CSIRO Earth Science and Resource Engineering
    Australian Resources Research Centre

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@...367...> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre

snuffy · October 15, 2013, 4:47am

Sounds good,

I’d almost like an ‘override’ parameter or similar attached to the datastore definition that I could then say:
true

Which when applied would use the JDBC connection of the feature requesting the linkage to this feature.
aka:
Person pulls in CI_Contact, therefore override the jndi connection specified by CI_Contact (if forceLinkJNDI = true) to be Person’s JNDI information.

I’m not sure how possible that is because I have not reviewed the code in that respect.

PS: i noticed some sorting related changes on the git tree for app-schema recently, does any of those changes remove the odd requirement of needing the idExpression table column in the feature being linked to (because of sorting)?

···

On 15 October 2013 14:44, <Rini.Angreani@anonymised.com> wrote:

Perhaps we could improve the joining setting by applying it per feature type, instead of per GeoServer instance.
I raised this task, but I can’t commit on working on it anytime soon.
https://jira.codehaus.org/browse/GEOT-4596

-----Original Message-----
From: Caradoc-Davies, Ben (CESRE, Kensington)
Sent: Tuesday, 15 October 2013 9:47 AM
To: snuffy
Cc: geoserver-users@lists.sourceforge.net; Angreani, Rini (CESRE, Kensington)
Subject: Re: [Geoserver-users] App-schema and CharacterString Type

Aha! Because app-schema can use separate connections for different feature types, it should work with chaining across different databases, but only if joining is turned off. It looks like you have found a use-case that does not automatically turn off joining; this is a bug.
You can manually turn off joining in your app-schema.properties file:
http://docs.geoserver.org/latest/en/user/data/app-schema/joining.html#conditions

Kind regards,
Ben.

On 15/10/13 07:11, snuffy wrote:

Attached is stack trace…

Appears to be having issue with sql…

I think I know where the issue might be… it is possible it is trying
to join between two databases.

(It was)

I have two different databases and two different jdbc connections,
each project uses their own… except…

An app-schema feature can only describe a single jdbc datasource, so
even though each db has their own version of the ‘ci_contact’ and
friends table, when app-schema does a query its locked into the one
jdbc datasource.

I guess if I want to implement separate db’s which share another
common featureType from an external namespace i’ll need to have
separate geoservers or have it within a single database schema.

Thanks

On 14 October 2013 17:34, Ben Caradoc-Davies
<Ben.Caradoc-Davies@anonymised.com mailto:[Ben.Caradoc-Davies@anonymised.com](mailto:Ben.Caradoc-Davies@anonymised.com)> wrote:

Do you have a full stack trace?

On 14/10/13 14:22, snuffy wrote:

As a minor follow up to this.

I’ve tried taking my ‘company’ schema and adding a CI_Contact entry.

I believe something is not right in my xsd/xml.

The error is listed below:

ows:ExceptionText
java.lang.RuntimeException: Error applying mapping with
targetAttribute
company:contactInfo Error applying mapping with targetAttribute
company:contactInfo java.io.IOException null Schema ‘person’
does not exist.

Have attached zip with relevant files.

–
Ben Caradoc-Davies Ben.Caradoc-Davies@anonymised.com
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

–
Ben Caradoc-Davies Ben.Caradoc-Davies@anonymised.com Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre

Angreani_Rini_Minera · October 15, 2013, 5:07am

Hi,

That’s not possible with the current joining implementation, as it uses INNER JOIN between the linked tables – not possible across different databases.

It has to use the old implementation (without joining), which is painfully slow for large datasets.

It’s probably OK for demonstration purposes where there are only a few records, but for production, I would recommend using joining (with one database).

Re: sorting changes, it was to cater for database views where idExpression is not specified and the primary keys aren’t available.

If your table has primary keys, then it would sort by the primary key in absence of the idExpression. I also replied to your other thread regarding this.

Cheers

Rini

···

From: snuffy [mailto:snuffy22@anonymised.com]
Sent: Tuesday, 15 October 2013 12:47 PM
To: Angreani, Rini (CESRE, Kensington)
Cc: Caradoc-Davies, Ben (CESRE, Kensington); geoserver-users@anonymised.comourceforge.net
Subject: Re: [Geoserver-users] App-schema and CharacterString Type

Sounds good,

I’d almost like an ‘override’ parameter or similar attached to the datastore definition that I could then say:

true

Which when applied would use the JDBC connection of the feature requesting the linkage to this feature.

aka:

Person pulls in CI_Contact, therefore override the jndi connection specified by CI_Contact (if forceLinkJNDI = true) to be Person’s JNDI information.

I’m not sure how possible that is because I have not reviewed the code in that respect.

PS: i noticed some sorting related changes on the git tree for app-schema recently, does any of those changes remove the odd requirement of needing the idExpression table column in the feature being linked to (because of sorting)?

On 15 October 2013 14:44, <Rini.Angreani@anonymised.com> wrote:

Perhaps we could improve the joining setting by applying it per feature type, instead of per GeoServer instance.
I raised this task, but I can’t commit on working on it anytime soon.
https://jira.codehaus.org/browse/GEOT-4596

-----Original Message-----
From: Caradoc-Davies, Ben (CESRE, Kensington)
Sent: Tuesday, 15 October 2013 9:47 AM
To: snuffy
Cc: geoserver-users@lists.sourceforge.net; Angreani, Rini (CESRE, Kensington)
Subject: Re: [Geoserver-users] App-schema and CharacterString Type

Aha! Because app-schema can use separate connections for different feature types, it should work with chaining across different databases, but only if joining is turned off. It looks like you have found a use-case that does not automatically turn off joining; this is a bug.
You can manually turn off joining in your app-schema.properties file:
http://docs.geoserver.org/latest/en/user/data/app-schema/joining.html#conditions

Kind regards,
Ben.

On 15/10/13 07:11, snuffy wrote:

Attached is stack trace…

Appears to be having issue with sql…

I think I know where the issue might be… it is possible it is trying
to join between two databases.

(It was)

I have two different databases and two different jdbc connections,
each project uses their own… except…

An app-schema feature can only describe a single jdbc datasource, so
even though each db has their own version of the ‘ci_contact’ and
friends table, when app-schema does a query its locked into the one
jdbc datasource.

I guess if I want to implement separate db’s which share another
common featureType from an external namespace i’ll need to have
separate geoservers or have it within a single database schema.

Thanks

On 14 October 2013 17:34, Ben Caradoc-Davies
<Ben.Caradoc-Davies@anonymised.com mailto:[Ben.Caradoc-Davies@anonymised.com](mailto:Ben.Caradoc-Davies@anonymised.com)> wrote:

Do you have a full stack trace?

On 14/10/13 14:22, snuffy wrote:

As a minor follow up to this.

I’ve tried taking my ‘company’ schema and adding a CI_Contact entry.

I believe something is not right in my xsd/xml.

The error is listed below:

ows:ExceptionText
java.lang.RuntimeException: Error applying mapping with
targetAttribute
company:contactInfo Error applying mapping with targetAttribute
company:contactInfo java.io.IOException null Schema ‘person’
does not exist.

Have attached zip with relevant files.

–
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

–
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre

Andrea_Aime4 · October 15, 2013, 6:01am

On Tue, Oct 15, 2013 at 5:44 AM, <Rini.Angreani@anonymised.com> wrote:

Perhaps we could improve the joining setting by applying it per feature
type, instead of per GeoServer instance.
I raised this task, but I can't commit on working on it anytime soon.
https://jira.codehaus.org/browse/GEOT-4596

Ideally, the code should be able to do that on a per join basis: same
store, jdbc type, use joining, otherwise,
use the old strategy (inner loop?)

Cheers
Andrea

--

Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

Angreani_Rini_Minera · October 15, 2013, 6:16am

That’s a good idea, but that would make it more complicated to implement.

Will consider it when I have the time to do this.

Cheers

Rini

···

From: andrea.aime@anonymised.com [mailto:andrea.aime@anonymised.com] On Behalf Of Andrea Aime
Sent: Tuesday, 15 October 2013 2:01 PM
To: Angreani, Rini (CESRE, Kensington)
Cc: Caradoc-Davies, Ben (CESRE, Kensington); snuffy22@anonymised.com; GeoServer Mailing List List
Subject: Re: [Geoserver-users] App-schema and CharacterString Type

On Tue, Oct 15, 2013 at 5:44 AM, <Rini.Angreani@anonymised.com> wrote:

Perhaps we could improve the joining setting by applying it per feature type, instead of per GeoServer instance.
I raised this task, but I can’t commit on working on it anytime soon.
https://jira.codehaus.org/browse/GEOT-4596

Ideally, the code should be able to do that on a per join basis: same store, jdbc type, use joining, otherwise,

use the old strategy (inner loop?)

Cheers

Andrea

–

==

Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

==

Ing. Andrea Aime

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054 Massarosa (LU)

Italy

phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

http://www.geo-solutions.it

http://twitter.com/geosolutions_it