Since XINS-2.1 a class cast exception is raised when trying to get the input parameters from a session.
In XINS 2.0 the object returned from a _api.getSessionManager().getProperty("_inputs") was of type Map and this could be succesfully casted to a HashMap.
In XINS 2.1 the object returned from a _api.getSessionManager().getProperty("_inputs") was of type ChainedMap and this is causing a class cast exception.
Was there a specific reason to make this change, if no can we rollback this change?
Logged In: YES
user_id=987589
Originator: NO
The idea is to have is to have the parameters in the same order that you received them instead of random. For example it's easier to debug (e.g. firstname, lastname, address, postcode, city).
Why do you want to cast to HashMap instead of Map? I don't any technical reason why.