[GeoNetwork-devel] Default Schemas and plugins

GeoNetwork GeoNetwork Developer
1

Hi,

I just updated and saw that the SchemaManager has been dramatically changed. At least for me it is not loading the “normal” schemas. It does seem to look in the schema plugins directory for existing schemas. Do I have to copy the schemas in xml/schemas to the schemasPlugin directory for them to be detected?

I personally liked the behaviour where both the default schemas and plugins would be detected. Is there a reason it was changed? Is it a bug?

Thanks,

Jesse

2

Hi Jesse,

You should put your all schemas in WEB-INF/data/config/schema_plugins (those that used to be in xml/schemas have been moved in there already) - they should be picked up from there as before. Any schema in that dir when GeoNetwork starts up will be loaded. Adding a schema using the schema functions in the admin page also puts it in that dir.

The change was done for at least two reasons:

- base schemas were built in because they were not supposed to be "removable" - but adding dependencies between schemas should prevent an admin from removing a base schemas inadvertently so the distinction between base and plugin schemas became a bit artificial
- having all schemas in one directory is simpler and should make sharing content between the schemas easier - in particular you can now include content from the base iso19139 schema by path name (eg ../iso19139/convert/functions.xsl) instead of having to code arcane url maps into the oasis catalogs

Apologies for catching you off guard with that - it had been discussed after Heikki filed a bug (enhancement request really) on the geobru plugin - but obviously not widely enough.

Cheers,
Simon
________________________________________
From: Jesse Eichar [jesse.eichar@anonymised.com]
Sent: Thursday, 12 April 2012 11:20 PM
To: Devel geonetwork-devel@lists.sourceforge.net; heikki doeleman; Francois Prunayre; Jose Garcia; Pigot, Simon (CMAR, Hobart)
Subject: Default Schemas and plugins

Hi,

I just updated and saw that the SchemaManager has been dramatically changed. At least for me it is not loading the "normal" schemas. It does seem to look in the schema plugins directory for existing schemas. Do I have to copy the schemas in xml/schemas to the schemasPlugin directory for them to be detected?

I personally liked the behaviour where both the default schemas and plugins would be detected. Is there a reason it was changed? Is it a bug?

Thanks,

Jesse

3

Thanks for the update. I saw some stuff going by about schema_plugins, but I didn’t watch that carefully so no worries. I appreciate the summary.

Jesse

On Thu, Apr 12, 2012 at 4:51 PM, Simon.Pigot@anonymised.com wrote:

Hi Jesse,

You should put your all schemas in WEB-INF/data/config/schema_plugins (those that used to be in xml/schemas have been moved in there already) - they should be picked up from there as before. Any schema in that dir when GeoNetwork starts up will be loaded. Adding a schema using the schema functions in the admin page also puts it in that dir.

The change was done for at least two reasons:

  • base schemas were built in because they were not supposed to be “removable” - but adding dependencies between schemas should prevent an admin from removing a base schemas inadvertently so the distinction between base and plugin schemas became a bit artificial
  • having all schemas in one directory is simpler and should make sharing content between the schemas easier - in particular you can now include content from the base iso19139 schema by path name (eg …/iso19139/convert/functions.xsl) instead of having to code arcane url maps into the oasis catalogs

Apologies for catching you off guard with that - it had been discussed after Heikki filed a bug (enhancement request really) on the geobru plugin - but obviously not widely enough.

Cheers,
Simon

From: Jesse Eichar [jesse.eichar@…189…]
Sent: Thursday, 12 April 2012 11:20 PM
To: Devel geonetwork-devel@lists.sourceforge.net; heikki doeleman; Francois Prunayre; Jose Garcia; Pigot, Simon (CMAR, Hobart)
Subject: Default Schemas and plugins

Hi,

I just updated and saw that the SchemaManager has been dramatically changed. At least for me it is not loading the “normal” schemas. It does seem to look in the schema plugins directory for existing schemas. Do I have to copy the schemas in xml/schemas to the schemasPlugin directory for them to be detected?

I personally liked the behaviour where both the default schemas and plugins would be detected. Is there a reason it was changed? Is it a bug?

Thanks,

Jesse

4

---------- Forwarded message ----------
From: Elgar Storm <elgarstorm@anonymised.com>
Date: 16 April 2012 13:24
Subject: Re: [GeoNetwork-devel] Default Schemas and plugins
To: Jesse Eichar <jesse.eichar@anonymised.com>

I just noticed that a clean checkout breaks when creating the
installation as a result of this move. installer-config.xml has a
reference to xml/schemas/iso19139/schematron-rules-inspire.xsl.disabled
which no longer exists since it lives in
WEB-INF/data/config/schema_plugins/iso19139/schematron-rules-inspire.xsl.disabled

Elgar Storm

On 13 April 2012 03:05, Jesse Eichar <jesse.eichar@anonymised.com> wrote:

Thanks for the update. I saw some stuff going by about schema_plugins, but
I didn't watch that carefully so no worries. I appreciate the summary.

Jesse

On Thu, Apr 12, 2012 at 4:51 PM, <Simon.Pigot@anonymised.com> wrote:

Hi Jesse,

You should put your all schemas in WEB-INF/data/config/schema_plugins
(those that used to be in xml/schemas have been moved in there already) -
they should be picked up from there as before. Any schema in that dir when
GeoNetwork starts up will be loaded. Adding a schema using the schema
functions in the admin page also puts it in that dir.

The change was done for at least two reasons:

- base schemas were built in because they were not supposed to be
"removable" - but adding dependencies between schemas should prevent an
admin from removing a base schemas inadvertently so the distinction between
base and plugin schemas became a bit artificial
- having all schemas in one directory is simpler and should make sharing
content between the schemas easier - in particular you can now include
content from the base iso19139 schema by path name (eg
../iso19139/convert/functions.xsl) instead of having to code arcane url maps
into the oasis catalogs

Apologies for catching you off guard with that - it had been discussed
after Heikki filed a bug (enhancement request really) on the geobru plugin -
but obviously not widely enough.

Cheers,
Simon
________________________________________
From: Jesse Eichar [jesse.eichar@anonymised.com]
Sent: Thursday, 12 April 2012 11:20 PM
To: Devel geonetwork-devel@lists.sourceforge.net; heikki doeleman;
Francois Prunayre; Jose Garcia; Pigot, Simon (CMAR, Hobart)
Subject: Default Schemas and plugins

Hi,

I just updated and saw that the SchemaManager has been dramatically
changed. At least for me it is not loading the "normal" schemas. It does
seem to look in the schema plugins directory for existing schemas. Do I
have to copy the schemas in xml/schemas to the schemasPlugin directory for
them to be detected?

I personally liked the behaviour where both the default schemas and
plugins would be detected. Is there a reason it was changed? Is it a bug?

Thanks,

Jesse

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork