Community
Participate
Working Groups
BeanArrayHolder is itself serializable. However, it only accepts generics of type serializable for beans it wraps. This limitation is not optimal, since it often makes sense to use the bean array holder as a transport wrapping tool only. Without serialiazation. Solution: Release the limitation and allow for any object.
Created attachment 203733 [details] Patch to solve issue
Applied patch.
shipped with 3.7.1
The patch for this ticket makes the BeanArrayHolder itself non-Serializable (removes Serializable from the implements clause). This effectively breaks our code, as we are using BeanArrayHolder as the return type of a service call. Letting BeanArrayHolder implement Serializable, but not imposing this restriction on the wrapped type would be consistent with the Holder<T> class and would fix the issue. I think this was the intended fix in this ticket anyway? Affected is Eclipse Scout branch 3.7.1 and Eclipse Scout trunk.
29.11.2011 dwi/imo Bugzilla: 358369 (bug-fix) Problem: BeanArrayHolder should implement Serializable to be used as transfer object in client-server communication. However, the wrapped type must not necessarily be serializable to also be used as holder for any beans (e.g. beans of a webservice stub) Solution: Changed BeanArrayHolder to implement Serializable. This only applies to the holder, not the wrapped type. Migration: None Release: 3.7.1
(In reply to comment #5) > 29.11.2011 dwi/imo > Bugzilla: 358369 (bug-fix) > Problem: BeanArrayHolder should implement Serializable to be used as transfer > object in client-server communication. > However, the wrapped type must not necessarily be serializable to also be used > as holder for any beans (e.g. beans of a webservice stub) > Solution: Changed BeanArrayHolder to implement Serializable. This only applies > to the holder, not the wrapped type. > Migration: None > Release: 3.7.1 Fixed on Eclipse Scout branch 3.7.1 and Eclipse Scout trunk.
Thank you very much for the fast reaction! Successfully tested on Eclipse Scout branch 3.7.1.
assigned correct target milestone (3.7.2 instaed of 3.7.1). will update status to resolved verified
just trying to set proper status ...
shipped with eclipse scout 3.7.2 (indigo sr2)