You're right about the standalone RAR. Admin can configure that RAR with various properties, in preparation for an EAR file which is going to be deployed at some time in the future, which will use that resource. The EAR is deployed, and as soon as the application is fully deployed it may use the RAR. Now take the embedded RAR. If there are no configuration properties, then when the EAR is deployed, there is no problem. If the EAR deployer gets it right, the RAR gets deployed in time for the rest of the application components to start using it. Also, if the application components could be kept inactive and not using the resource, then one could go to the Admin GUI wire up the RAR, configure it etc, then activate the components which then access the configured RAR. I just wanted to set up the configuration properties for the embedded RAR beforehand, if that makes sense and is possible. And just in case there is some overall better way of achieving what I want, it's a RAR that can only be accessed by a chosen application deployed in the application server, yet still configurable via the application server...hence embedded RAR seems to do the job in terms of access to it, but not in terms of configuring it.
Thanks
Joe
[Message sent by forum member 'teknomad' (joe.isaac_at_tolven.org)]
http://forums.java.net/jive/thread.jspa?messageID=392307