If you want one user deployment to have a dependency on another user deployment, you must name the deployment you depend on like this
This works in Beta2 but only if you deploy my-osgi-bundle through the AS7 deployment API. If you use BundleContext.installBundle() it is different and currently subject to change. You can monitor Make packages from OSGi deployments visible to EE for progress on this.
Generally it boils down to the question of how to derive the module identity for a bundle deployment. This should be identical accross all deployment channels. The module associated with a bundle deployment must then be managed by a ModuleLoader that is queried for EE dependencies. The obvious solution is to use the same ModuleLoader in the OSGi layer as AS uses for its deployments (i.e. ServiceModuleLoader)
Because the dependee is not known to the OSGi resolver we have the "human wiring dilemma" and there is no guaranty that you have class space consistency.