Shibboleth Developers

["Rod Widdowson" <>]

Good idea I'd say.

This raises a couple of related questions:

Firstly, what is happening to org.opensaml.xml.util.DatatypeHelper and 
friends?  Is it moving over (or has it and I hadn't noticed).

Secondly, and related, is there any value in building a special version of 
the "temp" dependenies (like xmltooling-1.3-jar &c) and
mark all the "ported forward" interfaces as deprecated.  I keep on finding 
that things like  

import org.opensaml.xml.util.LazySet;

...rather than...

import org.opensaml.util.collections.LazySet;

ending up in my code by accident because eclipse finds the old version 
first...

R


> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of
> Chad La Joie
> Sent: 16 May 2011 16:22
> To: Shib Dev
> Subject: [Shib-Dev] Java helper/support/tool projects
> 
> This is mostly for the dev's themselves but if anyone else using our
> code has strong feelings they can reply too...
> 
> I've noticed that I have various bits of code within some of our
> projects that are really what I would call toolbox classes.  That is,
> they are just generic helper/support classes or certain pattern
> implementations that are actually used by numerous Shib products.  I'm
> thinking of splitting these out in to separate small projects that we
> can just import as needed.
> 
> Off the top of my head I can think of the following such items (I know
> there are others but I can't think of them off the top of my head):
> - everything in the OpenSAML 3 opensaml-util module (I'd probably
> split this up in to at least two projects, one focused on XML and on
> with everything else in it)
> - metadata aggregator's pipeline interfaces and some implementation
> classes (these actually have nothing that's metadata specific)
> 
> Does anyone have any objections to doing this?  I think the projects
> would go in to the /utilities repo.
> 
> --
> Chad La Joie
> www.itumi.biz
> trusted identities, delivered