[jboss-dev-forums] [Design the new POJO MicroContainer] - Controller's execution env
alesj
do-not-reply at jboss.com
Mon Aug 4 08:58:09 EDT 2008
In order to implement concurrent deployments handling (https://jira.jboss.org/jira/browse/JBMICROCONT-265)
we need some sort of execution environment to be passed to Controller:
- https://jira.jboss.org/jira/browse/JBMICROCONT-323
The question is, what how should this interface look like?
Should we take the run operations from our ThreadPool:
| /**
| * Run a task wrapper
| *
| * @param wrapper the task wrapper
| */
| public void runTaskWrapper(TaskWrapper wrapper);
|
| /**
| * Run a task
| *
| * @param task the task
| * @throws IllegalArgumentException for a null task
| */
| public void runTask(Task task);
|
| /**
| * Run a runnable
| *
| * @param runnable the runnable
| * @throws IllegalArgumentException for a null runnable
| */
| public void run(Runnable runnable);
|
| /**
| *
| * @param runnable
| * @param startTimeout
| * @param completeTimeout
| */
| public void run(Runnable runnable, long startTimeout, long completeTimeout);
|
Or perhaps just the last two, making EE not depend on JBoss Common-core?
But since we already do depend on Common core, we can probably leave the Task and TaskWrapper there as well.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168434#4168434
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168434
More information about the jboss-dev-forums
mailing list