uCosminexus Service Platform, Basic Development Guide
This section describes nodes when designing UOC class.
- As UOC class operates as extension of the container extended library of J2EE server, there are limitations of the available functions.
For details, see "14.6 Limitations when using container extended library and server start/stop hook function" in the "Application Server Common Container Functionality Guide".
UOC class is read in the system class loader and hence if you can read and write the external file with full path specification, if not in scope of limitations, mentioned above.
- When you crate UOC class, specify public in access settings modifier of the class.
When it is not public(not writing the access settings modifier=package private), IllegalAccessException occurs and you cannot send UOC data.
- Perform process considering the multi-thread access.
UOC class is invoked from multiple threads and hence you must implement thread safe. You must release the appropriate resources as well, considering the cases of insufficient memory.
- In UOC class of standard reception (SessionBean), you must consider the input of null in the message at the time of request processing.
When you re-execute the business process, standard reception (SessionBean) is invoked, with message is null status.
- You must add cscmsg.jar to class path, when compiling. Interface used is included in cscmsg.jar.
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.