[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1869) Example of Control Set for Quartz SEAM Interation

[Piergiuseppe Spinelli (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-1869?page=all ]

Piergiuseppe Spinelli updated JBSEAM-1869:
------------------------------------------

    Attachment: jarList.txt

The list of jars used in the project

> Example of Control Set for Quartz SEAM Interation
> -------------------------------------------------
>
>                 Key: JBSEAM-1869
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1869
>             Project: JBoss Seam
>          Issue Type: Task
>          Components: Examples
>    Affects Versions: 2.0.0.BETA1
>         Environment: Any OS. JBoss2_0B project.
>            Reporter: Piergiuseppe Spinelli
>            Priority: Optional
>         Attachments: jarList.txt
>
>   Original Estimate: 3 weeks
>  Remaining Estimate: 3 weeks
>
> The attached sample is an attept to create a control interface to SEAM asynchronous method using Quartz as scheduling engine.
> I was asked to do this in the related forum thread: I am not sure it is near to the desired functionalities, but it could be used as a starting point (or possibly as a negative sample).
> The sample is very raw and I have used SEAM  too short to be sure I did not make to stupid things, but if the idea is useful, I am sure other people will improve it.
> Notes:
> - The sample use quartz integrated in SEAM as it currently is: a support to asynchronous method
> - Quartz is used with its in-memory db, the persistent status is kept by the application usign custom Entities
> - Since I am a newby in SEAM, I preferred to make some custom classes for supporting CRUD operations since it was difficult to me to get the SEAM framework to do more that the simple things showed in the samples
> TODO:
> - it could be better to use some well known components library for the interface instead that my custom controls (i.e Trinidad)
> - the entities I made to keep the application status use a table schema very similar to the quartz schema: it could be a good idea in a future to be able to use some entity model over the quartz schema
> - it would be usefull to add the feature to upload the classes to be scheduler directly by the web interface, mayby using a classloader chain for supporting hot versioning.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira