Regarding your first question, this happens only in dev mode when your plugin is deployed from Eclipse/STS, the work-around is covered in the SDK doc (see the doc on the actions-ui sample in docs/samples-doc/actions.html#ui)
I don't understand your 2nd question, can you clarify?