OpenSAML user discussion

[Kenny Pearce <>]

In the meantime, can you briefly tell me what is supposed to happen
instead? Is the no-arg constructor fine? Do concrete implementations
still need to have (String, String) constructors?

Thanks.

On Thu, 2008-04-24 at 21:47 +0200, Chad La Joie wrote:
> The documentation is out of date, again.  That method was removed 
> because the functionality that used that causes issues and ends up 
> providing little value.  I didn't realize, or rather didn't remember, 
> that our documentation had people extending those classes.  File a bug 
> and I'll add them back in during the next release (which is probably 
> about a 1-2 weeks away).
> 
> Kenny Pearce wrote:
> > Hi,
> >     I just downloaded this version of OpenSAML, and it appears to be
> > lacking the constructor AbstractSAMLObjectMarshaller(String, String),
> > and the same for AbstractSAMLObjectUnmarshaller. The latest SVN has
> > these constructors, and the docs on the web-site still say to call them
> > if you create a subclass
> > (https://spaces.internet2.edu/display/OpenSAML/OSTwoDevManJavaNewMarshaller).
> >  Anyone know what's going on?
> >     Thanks,
> > 
> > On Mon, 2008-04-21 at 08:51 +0200, Chad La Joie wrote:
> >> OpenSAML/J 2.1.0 is now up on the site.
> >>
> >> This release incorporates the EGEE XACML code contributions and the 
> >> WS-Federation contributions from Naveen Sankar.  Additionally it fixes a 
> >> couple bugs: JOST-29, JOST-30, JOST-31
> >>
> >> Download Location:
> >> http://shibboleth.internet2.edu/downloads/opensaml/java/
> >>
> >> Documentation:
> >> http://www.opensaml.org/docs/
> >>
> >> Notes:
> >> This release is 2.1.0 (instead of 2.0.1) because it contains new 
> >> functionality.  It is a drop in replacement for 2.0.0.  A more formal 
> >> definition of our versioning policy should follow shortly.
> >>
> >> This is the first time I've used Maven on a project so if anything is 
> >> messed up please let me know.  I'll be creating an aggregate project 
> >> next time so that things like the report (javadocs, checkstyle, etc.) 
> >> are properly aggregated from the various projects into a single unit.
> >>
>