Content Object Properties defined either as xs:int or xs:integer are treated as equivalent (definition wise). They are saved as jcr properties of type Long and are rendered as Longs inside java objects. However the betacms web-ui forms present different input components for each of the two definitions.

This may mean that:
Either the repository module while interpreting as equal the two definitions it renders different java types for each one.
Or there is some problem in the web-ui module when it generates the appropriate form ui components according to each property type.