Timeline for Java client side bean container?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Sep 26, 2022 at 7:43 | history | suggested | James Risner | CC BY-SA 4.0 |
Made title a questions, fixed capitalization issues, spelling errors fixed, minor formatting changes.
|
| Sep 25, 2022 at 13:51 | review | Suggested edits | |||
| S Sep 26, 2022 at 7:43 | |||||
| Apr 5, 2014 at 13:34 | answer | added | Nicolas Raoul♦ | timeline score: 0 | |
| Apr 5, 2014 at 12:42 | answer | added | jwells131313 | timeline score: 2 | |
| Apr 5, 2014 at 1:52 | comment | added | Ezequiel | I dont need persistence, I just need a framework or library to help me in not to duplicate instances when they are rehydrated in client side. | |
| Apr 4, 2014 at 11:06 | history | tweeted | twitter.com/#!/StackSoftRecs/status/452039574551019520 | ||
| Apr 4, 2014 at 9:43 | comment | added | Nicolas Raoul♦ | Do you need persistency or not? Should the objects remain on the local side even after quitting your app? | |
| Apr 4, 2014 at 9:26 | comment | added | Ezequiel | In my case there are "domain objects". But any instance could be used for my problem. Instances that are Objects.equals(instanceA, instanceB); | |
| Apr 4, 2014 at 9:14 | comment | added | Nicolas Raoul♦ | Could you please use a more specific word than "bean"? Any serializable Java object with a default constructor and getters/setters is a bean. Spring is a good way to handle such beans on client-side. Do you actually mean something more specific? | |
| Apr 4, 2014 at 8:14 | review | First posts | |||
| Apr 4, 2014 at 13:02 | |||||
| Apr 4, 2014 at 7:54 | history | asked | Ezequiel | CC BY-SA 3.0 |