Trace:
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
jvx:common:util:classes [2018/02/02 10:44] admin [Other classes] |
jvx:common:util:classes [2020/06/15 14:42] cduncan [Working With Arrays] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ~~NOTRANS~~ | ||
~~Title: Utility Classes~~ | ~~Title: Utility Classes~~ | ||
Line 24: | Line 23: | ||
</file> | </file> | ||
- | ==== Working with Arrays ==== | + | More Details about [[jvx:common:util:xml|XML Handling]]. |
+ | ==== Working With Arrays ==== | ||
Array operations are always tedious coding work, and every developer could easily do without it. Removing a single element from an array is not rocket science, but there is no standard function available for this task. And who would not like to search an array for an element without coding a loop? | Array operations are always tedious coding work, and every developer could easily do without it. Removing a single element from an array is not rocket science, but there is no standard function available for this task. And who would not like to search an array for an element without coding a loop? | ||
Line 34: | Line 34: | ||
From time to time objects have to be cached and exchanged between various instances. Parameters and public methods are very useful for this purpose, but we do not always want to pass an object on across countless instances to the target. Also, the required objects are not always located in the same scope. | From time to time objects have to be cached and exchanged between various instances. Parameters and public methods are very useful for this purpose, but we do not always want to pass an object on across countless instances to the target. Also, the required objects are not always located in the same scope. | ||
- | This is what the ObjectCacheis for, which handles objects statically, for certain time periods or permanently, within a VM. | + | This is what the ObjectCache is for, which handles objects statically, for certain time periods or permanently, within a VM. |
This can be compared to a static hash table, complement by a timeout. | This can be compared to a static hash table, complement by a timeout. | ||
Line 50: | Line 50: | ||
The KeyValueList handles the administration of lists and leaves the developer time for more important tasks. | The KeyValueList handles the administration of lists and leaves the developer time for more important tasks. | ||
- | ==== Other classes ==== | + | ==== Reflective === |
- | There are many other interesting utility classes, such asStringUtil, BeanUtil, DateUtil, FileUtil, ImageUtil, ... | + | The Reflective class allows you to create class instances or call methods via reflection but without directly using ''java.lang.reflect''. |
+ | |||
+ | More details, see [[jvx:common:util:reflective|here]]. | ||
+ | |||
+ | ==== More classes ==== | ||
+ | |||
+ | There are many other interesting utility classes, such as StringUtil, BeanUtil, DateUtil, FileUtil, ImageUtil, ... | ||
Additional information can be found in [[https://www.sibvisions.com/files/jvx/current/api/|javadoc]]. | Additional information can be found in [[https://www.sibvisions.com/files/jvx/current/api/|javadoc]]. |