On Thu, May 26, 2011 at 12:43 AM, Andrea Aime
<[email protected]>wrote:
> On Thu, May 26, 2011 at 8:00 AM, <[email protected]> wrote:
> > XML would be the best. I added some samples to
> > http://jira.codehaus.org/browse/GEOS-4554
> > for further discussion.
> >
> > @Justin, perhaps you should watch this issue.
> >
> > I would strongly vote for 2 xml files, one for role management and one
> for
> > user/group management.
> >
> > I created 2 xml schemes and 2 demo files and tried to keep it simple.
> > Using an XML schema has a lot of advantages. The user can edit with a
> tool
> > and validate, I can use JAXB for serializing/deserializing (if this is
> ok).
>
> Time ago we noticed that adding jaxb jars in the path would break GML
> handling due to some Eclipse XSD incompatibilities (as far as I
> remember, Justin,
> any help there?).
> If you design your in memory classes carefully I believe you can just
> use XStream, that is known to work.
>
Yeah afaik there were some issues with multiple versions of xerces required.
Sounds like we are going xstream though.
>
> > I would implement the access logic using XPath. I looked at the
> > possibilities of DB2 and you can store even large xml files, access them
> via
> > XPath, create indices on nodes and so on. I think this is possible with
> > other products too.
>
> Ok, good for alternative implementations, though we're mainly interested
> in having a file system based solution now (and possibly a hibernate
> based solution later if we go dbconfig).
>
> > The roles can be hierarchical if something is wondering about the
> "parent"
> > attribute in roles.xml.
>
> Do we really need hierarchy? Can't the same be obtained by composition
> of roles in a user group?
>
> Anyways, better than 6 files already, but I would go down to one if
> possible, less cross referencing among the files and everything
> just one one place that's easier to look up for the writer.
> Adding a space for roles and groups in a user definition should
> be easy
>
> Ah, I appreciated the usage of attributes when possible to reduce
> the xml boilerplate.
>
> I was wondering whether to use a gml:ordinates like approach
> for lists such as the roles ones:
>
> <gsv:userroles username="user1">ROLE_WFS ROLE_WMS</gsv:userroles>
>
> Though I guess I might be pushing the "simplify thy xml" thing a little
> too far now
>
> Cheers
> Andrea
>
> --
> -------------------------------------------------------
> Ing. Andrea Aime
> GeoSolutions S.A.S.
> Tech lead
>
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
>
> phone: +39 0584 962313
> fax: +39 0584 962313
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.youtube.com/user/GeoSolutionsIT
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
> -------------------------------------------------------
>
>
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery,
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now.
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
