Sorry, I didn't want to bore you with this whole pattern stuff (which
you probably know too):
- single responsibility,
- facade,
- object (thread) pool,
- active object,
- DI,
- yada yada yada.
I fail to see how the original implementation of ProcessExecutorPanel
confirms to any of these points. It's just a class which does to much
and now someone is asking for a method in Wicket to keep this mess running.
There might be good reasons for changes but IMHO this use case is not.
Sven
On 05/28/2010 08:31 PM, Douglas Ferguson wrote:
I know all this, I was just hoping you would explain what you were trying to
say.
On May 28, 2010, at 12:18 PM, Sven Meier wrote:
http://en.wikipedia.org/wiki/Multitier_architecture
On 05/28/2010 06:04 PM, Douglas Ferguson wrote:
What is the "service layer" that you speak of?
Is this built into wicket?
D/
On May 28, 2010, at 9:06 AM, Sven Meier wrote:
Why so much trouble inside your UI layer? Normally Wicket components are
single-threaded, but with your solution you may introduce race conditions.
Move the ExecutorService into your service layer:
http://pastebin.com/NN58fiZx
new ProcessExecutorPanel("associatedFilesMigration") {
@Override
protected Future<?> start() {
return injectedSpringBean.startMigration();
}
};
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/PROPOSAL-Application-runAs-Method-tp2230030p2234624.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
