[
https://jira.jboss.org/browse/JBSEAM-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane Bryzak reassigned JBSEAM-1869:
------------------------------------
Assignee: (was: Michael Yuan)
> Example of Control Set for Quartz SEAM Interation
> -------------------------------------------------
>
> Key: JBSEAM-1869
> URL: https://jira.jboss.org/browse/JBSEAM-1869
> Project: 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, scheduler.zip, scheduler_v2.zip
>
> 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:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
