Autodeploy and naming conventions about entity links etc.
Note that the autodeployer was assuming some hard coded naming convention about ResourceAdaptorEntity name. There is no such default name in the slee spec and such assumptions make it brittle and subject to failure. That was at least part of the problem we uncovered today. We changed the entity link name and could not deploy the SIP resource adaptor. It took a lot of searching and precious time to discover the root cause of the problem.
The steps for installing the resource adaptor are
1. Create the Entity
2. Activate it
3. Give it an entity link name.
This is how the application ( sip proxy in this case ) binds to the RA.
I think it would be a good thing to move in the direction of the 1.1 Spec for the ResourceManagement Mbean. Autodeploy seems to have some dependency issues that I had not previously thought of. I can see several hairy problems being introduced without some explicit way of defining dependencies. Moving in the direction of the ResourceManagementMBean from the 1.1 spec may be a better use of reseources.
All: Please do an end to end test of the specific component you are working on before commit. I am going to use the sip tester from cafesip.org ( which works on jain-sip) to do a simple proxy auto test. These hiccups take a long time to fix.