I've followed up with Binod and confirmed that AMF does not need to
manage standalone appclient module. :-) Nandini, so please update the
one-pager by removing the requirement on appclient under jsr77
implementation section.
It seems the AMF does need to manage the resource adapter module, so
that item will remain on the list.
I also did some investigation on why the JSR77 start did not load the
previously deployed (with disabled state) ear application during server
start up. It seems in the enable path we have a few places checking
for "enable" attribute before actually loading the application, and the
"enabled=false" prevent the application from being loaded. So we might
have to loosen the checks in those places for this to happen.
- Hong