[
https://issues.apache.org/jira/browse/GERONIMO-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627315#action_12627315
]
Ivan commented on GERONIMO-4140:
--------------------------------
I am looking at this JIRA now, and part of the migration work has been done, so
far, I have some questions, thanks for any comment.
a. I use the JAXB to support multi-triggers with one quartz job, my question is
that I use the xjc in the JDK's bin directory to generate some binding classes,
do we need to keep those generated message in the generated java file ? do we
need to add Apache license to the head of the file ? I found some source code
in geronimo does it, and some not.
b. The old quartz version uses a DeploymentWatcher to monitor the deployment
process, it will search the geronimo-quartz.xml file in the deployment process,
so that it will inject those ejb reference in the runtime. I wonder whether we
really need this feature ? And if does, could we have a better solution to
implement it, I just think importing a new schema file for this single plugin
is not a good way. I am a newbie to Geronimo, could anyone shed light on it ?
c. Currently, the quartz portlet is very simple, it only list all the running
job, I suggest that we open a new JIRA to enforce it, for example, we could add
new job dynamically, attach a new trigger ....
Thanks !
> Update quartz plugin to geronimo 2.1+
> -------------------------------------
>
> Key: GERONIMO-4140
> URL: https://issues.apache.org/jira/browse/GERONIMO-4140
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Plugins
> Affects Versions: 2.1.2, 2.2
> Reporter: David Jencks
>
> Aaron very kindly donated his quartz plugin, currently at
> sandbox/quartz-plugin. We should update it to a g. 2.1 plugin and release it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
