> For now I've fixed the bug in CVS - probably best to not introduce
> anything majorly new until after 1.1.
Thanks much. I'm hoping to be able to ship the next Shibboleth/OpenSAML
releases with the 1.1 versions of both languages, this will give me
additional incentive. ;-)
-- Scott
Scott/Erwin,
For now I've fixed the bug in CVS - probably best to not introduce
anything majorly new until after 1.1.
Cheers,
Berin
Erwin van der Koogh wrote:
With the talk of a release, I'd note that the Java Base64 encoder in the
utility class is still adding an extra linefeed when th
+1 (non-binding) :)
--- Axl Mattheus <[EMAIL PROTECTED]> wrote:
> Erwin van der Koogh wrote:
>
> >> With the talk of a release, I'd note that the Java Base64 encoder in the
> >> utility class is still adding an extra linefeed when the encoded data
> >> ends
> >> up exactly on a line wrap boundar
Erwin van der Koogh wrote:
With the talk of a release, I'd note that the Java Base64 encoder in the
utility class is still adding an extra linefeed when the encoded data
ends
up exactly on a line wrap boundary (e.g. last line of 72 chars if wrap
length is 72).
This is treated as invalid by the X
With the talk of a release, I'd note that the Java Base64 encoder in the
utility class is still adding an extra linefeed when the encoded data ends
up exactly on a line wrap boundary (e.g. last line of 72 chars if wrap
length is 72).
This is treated as invalid by the Xerces C++ base64 data type val
