On Thu, Dec 17, 2009 at 2:04 AM, Keean Schupke <[email protected] > wrote:
> Is this something that might get fixed? Is there a reason why this is > specifically not allowed? > The fact that it needs to be in your manifest? Because it keeps applications self-describing rather than relying on runtime behavior that can introduce lots of unintended broken behavior. > For example I can get to the meta-data via the PackageManager, and > getting the info associated with the service. This appears to be a > public Bundle, which I can put new values in. I can create a > BroadcastReceiver at runtime with the correct IntentFilter, so why can > I not use these two techinques together to do this? > Because for anything it will launch in your app the system needs to have it published in your manifest. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
