2009/9/30 Igor Vaynberg igor.vaynb...@gmail.com:
there is really no point in having your tasks be components. why not simply
repeatingview rv=..
for (task t:tasks) {
if (t.hasUIComponent()) {
rv.add(t.getUIComponent());
}
}
-igor
Although only one task panel is ever drawn at the
2009/9/30 Randy S. randypo...@gmail.com:
Have you thought about using Spring Web Flow for this? I'm not a SWF expert,
but it sounds like something well-tailored to your needs. For example, a
flow can have steps that don't have UIs.
Our group at work is looking into Wicket SWF integration. I
I tried JBoss JBPM and it worked for complex compound workflows. It also had
a eclipse designer plugin that could save the workflow image and provided a
class that visualised the current workflow state.
It had persistence module that was based on Hibernate. I had just to
implement simple UI to
We are also trying to find the right balance of how much we move to
declarative. It will depend on how well we get Web Flow to fit in. With
Wicket being Controller-less and wanting to launch right into the home
page, Web Flow is a clear candidate to do initial data load and logic to
determine the
Also, because we run in very large clusters, redirects
are out of the question due to the potential that the second request
hits
a different server before HTTP session has been properly
persisted/shared.
Can't you set up server affinity for the cluster to avoid that from
occurring?
We use server affinity but you can't guarantee same server and I can't go in
with a 100% plan. We have had funny routing in some cases where requests
from the same user even bounce from one data center to another... and back.
We've done a lot of work to prevent these things but in the end it's
If you're using Spring, the dependency injection issue for
non-component items can be solved by adding the following line to the
object's constructor:
InjectorHolder.getInjector().inject(this);
where InjectorHolder is org.apache.wicket.injection.web.InjectorHolder
. I'm afraid I don't have any
Phil,
Would an event-centric approach simplify things? I'm thinking that
you could then have multiple listeners for a given event and the
various listeners would not have to be aware of one another. This
might reduce the task/sub-task interactions. Adding errors, or
refreshing components could
2009/9/29 Scott Swank scott.sw...@gmail.com:
Phil,
Would an event-centric approach simplify things? I'm thinking that
you could then have multiple listeners for a given event and the
various listeners would not have to be aware of one another. This
might reduce the task/sub-task
there is really no point in having your tasks be components. why not simply
repeatingview rv=..
for (task t:tasks) {
if (t.hasUIComponent()) {
rv.add(t.getUIComponent());
}
}
-igor
On Tue, Sep 29, 2009 at 2:11 PM, Phil Housley undeconstruc...@gmail.com wrote:
Hello list,
I'm
Have you thought about using Spring Web Flow for this? I'm not a SWF expert,
but it sounds like something well-tailored to your needs. For example, a
flow can have steps that don't have UIs.
Our group at work is looking into Wicket SWF integration. I have a seen a
few comments on the web from
11 matches
Mail list logo
