uCosminexus Application Server, Common Container Functionality Guide
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
(1) Common notes
- You cannot obtain operation information related to the resource adapters conforming to the Connector 1.5 specifications even if you use the management portal or the mngsvrutil command.
- If you use the management portal or the mngsvrutil command to obtain status information of the resource adapters conforming to the Connector 1.5 specifications, information indicating that the resource adapter is stopped is returned even if the resource adapter is running.
- If you execute the cmx_stop_resource command for the resource adapters conforming to the Connector 1.5 specifications, the resource adapter is not stopped even if the command is always successful.
(2) When you deploy and use the resource adapter as a J2EE resource adapter (when the resource adapter is not included in the J2EE application)
When you specify an Administered object in an annotation, you must add the Administered object interface in the container extension library.
For details on the container extension library, see 14. Container Extension Library.
(3) When you include and use the resource adapter in the J2EE application
- When you use the reload functionality, you must add the following classes (interfaces) in the container extension library:
- Implementation class of the javax.resource.spi.ActivationSpec interface
- Message listener interface supported by the resource adapter
- When you specify an Administered object in an annotation, you must add the Administered object interface in the container extension library.
- The global transaction is not available when you use the Inbound resource adapter.
For details on the container extension library, see 14. Container Extension Library.
All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd.