Exception while unmarshalling Integer with an element biggerthan 32-bit

[Brent Putman]

Ok, glad it worked. 

We can't literally change the existing provider's interface without a
major version bump, so presence and use of Integer is there until v3.  I
suppose we could add something in v2, like additional methods on
XSInteger that expose a String instead, or an alternative provider impl
like you did that the developer could optionally replace the registered
provider for xs:integer.  However, either would require a new minor
release, which we don't currently have plans to do.  If we do decide to
do a new minor release for other reasons, we could get it in there.  I
suppose we could also do a separate download or extension, it's only 5
very trivial classes.
 

On 6/15/12 10:36 AM, Maxime Gregoire wrote:
>
> Hello,
>
>  
>
> Thanks a lot Brent for the fix proposal. I implemented it on my side,
> XSIntegerCustom, using a Long instead of Integer and it works
> perfectly. Until a solution is integrated into the official release, I
> will use that custom version. After reading all your messages
> regarding this issue, is there a plan for a fix on the 2.x branch or
> are you waiting for 3.x release? Other than having to fix some unit
> tests, doing the fix was really trouble free.
>
>  
>
> Anyway, thanks again!
>
>  
>
> Maxime
>
>  
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20120615/57479ef8/attachment-0001.html