Configuration might be different on each node. Thus having it Serializable is simply counter-productive.
It will be very easy to just add an @ApplicationScopedproducer later. But this is not part of our SE core but later for EE integration. Spring can do the same as can do guice. WE don't need to support that. LieGrue, strub > On Saturday, 27 December 2014, 10:52, Romain Manni-Bucau > <[email protected]> wrote: > > Well it should be but it shouldnt be serialized to let it be injectable. > Having AppScope or equivalent sounds the main constraint when we ll > integrate it with IoCs. > > Le 27 déc. 2014 10:45, "Mark Struberg" <[email protected]> a > écrit : > >> What is the benefit of having all the things Serializable? >> >> >> Usually the configuration will be rebuilt on every node and if something >> needs to be serializable then only the configured values. The configuration >> system itself imo doesn't need to be Serializable. And sometimes > it's even >> impossible/counter-productive to do so. E.g. sometimes the configuration >> differs depending on the cluster node you are on... >> >> LieGrue, >> strub >> >
