Details to be flushed out. Keep in mind the use case has been for EARs/WARs, which are not done through the normal package deployment but rather through the create resource workflow.
Feature requested on forums: http://forums.rhq-project.org/viewtopic.php?f=4&t=58&sid=8d19012741f0ae8b5c0f07eb33cc35b6
i think this is important enough to shoot for 1.1, and we already most of the back- and front-end infrastructure for it. back-end: just gotta create a new class (the quartz job) and a new method on the content manager (to gather job data and insert into the quartz table). the job will call into existing content interfaces to carry out the work. front-end: we have a reusable JSF scheduler component that interacts with the quartz API. the only substantial UI piece that needs to be written is the "create new" page (that embedded the scheduler component), and the "view schedules" page to display the list of current content schedules.
This is a bit too large for this release.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-547
This is still not possible with content or bundles. Probably still useful.