You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2008/06/19 23:49:45 UTC

[jira] Created: (GERONIMO-4140) Update quartz plugin to geronimo 2.1+

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.


Re: [jira] Commented: (GERONIMO-4140) Update quartz plugin to geronimo 2.1+

Posted by xu haihong <xh...@gmail.com>.
Thanks very much, David,
    In the previous quartz plugin implementation, the plugin defined a new
xml configuration file schema, and it uses xmlbeans to generate the mapping
bean objects. While the user deploys a file, it uses a DeploymentWatcher
implementation to  search the geronimo-quartz.xml file in the META-INF
directory, if the file is found, it will do the injection works.
    Currently in Geronimo, we usually deploy some services by provding a
geronimo-services.xml, I mean if we adopt the old solution, while we deploy
a quartz job service with EJB injection, we must provide an extra service
file. I wonder shall we have a solution that we only need to use the
geronimo-services.xml file ?


2008/9/3 David Jencks (JIRA) <ji...@apache.org>

>
>    [
> https://issues.apache.org/jira/browse/GERONIMO-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627841#action_12627841]
>
> David Jencks commented on GERONIMO-4140:
> ----------------------------------------
>
> Hi Ivan,
>
> (a) My current preference is to generate the jaxb classes once and check
> them into svn somewhere under src/main/java.  If we do this then the classes
> should be changed to include the standard apache header.  Doing this lets
> you customize the code and for instance use sxc more easily.  It's also
> possible to generate the code during the build into
> target/generated-sources/ using one of the maven xjc plugins.  I think this
> method is used in framework/modules/geronimo-system.
>
> (b) I don't know how the current plugin works. If we have ejb injection
> into the quartz task that seems to me to be a very good feature.  Could you
> explain in more detail what you are thinking?
>
> (c) Better console support would be wonderful!  Getting the plugin to work
> at all would be great!
>
> You might get more response by discussing these ideas on the dev list.
>
> > 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.
>
>


-- 
Haihong Xu ( Ivan )

[jira] Commented: (GERONIMO-4140) Update quartz plugin to geronimo 2.1+

Posted by "David Jencks (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/GERONIMO-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627841#action_12627841 ] 

David Jencks commented on GERONIMO-4140:
----------------------------------------

Hi Ivan,

(a) My current preference is to generate the jaxb classes once and check them into svn somewhere under src/main/java.  If we do this then the classes should be changed to include the standard apache header.  Doing this lets you customize the code and for instance use sxc more easily.  It's also possible to generate the code during the build into target/generated-sources/ using one of the maven xjc plugins.  I think this method is used in framework/modules/geronimo-system.

(b) I don't know how the current plugin works. If we have ejb injection into the quartz task that seems to me to be a very good feature.  Could you explain in more detail what you are thinking?

(c) Better console support would be wonderful!  Getting the plugin to work at all would be great!

You might get more response by discussing these ideas on the dev list.

> 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.


[jira] Commented: (GERONIMO-4140) Update quartz plugin to geronimo 2.1+

Posted by "Ivan (JIRA)" <ji...@apache.org>.
    [ 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.