[Geoserver-devel] Community Module geoxacml commited to geoserver trunk

GeoServer GeoServer Developer
1

Hi all, I added a first GeoXACML implementation to the GeoServer trunk as a community module named "geoxacml"

---------------------
I need a mvn specialist to check my pom.xml.
"mvn clean compile" works fine.
"mvn test" runs only 2 test suites instead of 12 ?
"mvn install" runs fine

I assume there is problem with a dependency to the apache xpath implementation. Doing the tests within eclipse works fine.

What is in ?

I implemented all functions and datat ypes as described in the GeoXACML specification. (STANDARD compliant)
I also implemented the optional coordinate transformations.

I created the following test cases

For each of the needed GML Types (Point,Linestring,Linearring,Polygon,Multipoint,Multilinestring and Multipolygon)
parsing and encoding is tested. This is done for GML2 and GML3. GML encoding is used according to GM2 and GML3 binding specifications of GeoXACML.

For each GeoXACML function, there is policy file, a "good" and a "bad" request. Each functions has 2 test cases.
Coordinate transformation tests are also included.
Additonally, an XPath test is part of the test suite.

So far, we have a staring point.

christian

2

Christian Müller ha scritto:

Hi all, I added a first GeoXACML implementation to the GeoServer trunk as a community module named "geoxacml"

---------------------
I need a mvn specialist to check my pom.xml.
"mvn clean compile" works fine.
"mvn test" runs only 2 test suites instead of 12 ?
"mvn install" runs fine

Your classes are not following the expected name pattern,
they end in Tests instead of Test. That's why only the two
that end with Test are run. It's an easy fix :slight_smile:

What is in ?

I implemented all functions and datat ypes as described in the GeoXACML specification. (STANDARD compliant)
I also implemented the optional coordinate transformations.

Wow, already? Do you have any background documentation on what
you are doing, and the general design that you're trying to
implement?
A wiki page with references to existing official docs would
bd nice.

Also, I would like to know how (or, if) you plan to address the growing
number of vendor parameter, protocol extensions (WFS-versioning)
and RESTful APIs that would not be covered by the standard
GEOXACML proxy based approach. I know I already tried to discuss
this with you in private mail, but haven't seen feedback on the
topic so far.
I'll forward my mail on the topic separately.

I created the following test cases

For each of the needed GML Types (Point,Linestring,Linearring,Polygon,Multipoint,Multilinestring and Multipolygon)
parsing and encoding is tested. This is done for GML2 and GML3. GML encoding is used according to GM2 and GML3 binding specifications of GeoXACML.

Is this using the geotools gt-xsd module, did you roll your own,
or does Sun XACML provide any set of base classes.

For each GeoXACML function, there is policy file, a "good" and a "bad" request. Each functions has 2 test cases.
Coordinate transformation tests are also included.
Additonally, an XPath test is part of the test suite.

So far, we have a staring point.

A big one I'd say. I'm just a bit confused as what is implemented
in the module (still haven't had the time to read the GEOXACML
specification, did not know you were already this far in the
implementation). Can you elaborate?

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.