Hi Gavin,
I'm using the jboss seam skeleton app, and I'm coming across that
switchableOutcome you referenced. Code example looks like this:
| ...
| return conversation.switchableOutcome( editTableOne, getDescription());
|
| return conversation.switchableOutcome(doneOutcome,
This stuff is no longer the way to do it. There is a much more elegant way now
(pages.xml). Hibernate Tools has been updated in CVS to no longer generate this
code.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3918784#3918784
Reply to the post :
OK, so, at least for conversation descriptions and timeouts, I've taken a whole
new tack now. I hated seeing conversation.switchableOutcome() everywhere in the
example apps, and I could not quite figure out why. It just *felt* ugly and
wrong.
Now I've decided that this stuff is really
By the way, it's becoming clear to me how much more pwerful jPDL navigation is
than JSF navigation :-)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3915718#3915718
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3915718
If I want to provide a more dynamic page title is that still possible ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3915737#3915737
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3915737
Oh. Hehe.
I should mention that the #{} stuff is not a reference to resource bundle-y
stuff.
They are EL expressions that are evaluated at runtime against the Seam
components.
Cool or what? :-)
View the original post :
..and i guess these seam components can evaluate/reason on to what view-id that
is relevant - then yes, its cool ;)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3915748#3915748
Reply to the post :
Great, thanks, no more questions. (on this thread, anyway ;-)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3914975#3914975
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3914975
[EMAIL PROTECTED] wrote : anonymous wrote : First, it looks like the
transition object is only @In, not @In @Out. But it's pretty clear that
myActionListener is trying to communicate some state outwards to the
conversation. So why not @Out also? Or is @Out only for cases where new
contextual
OK, slow down. Take a deep breath.
Now forget everything you know about dependency injection.
We are not doing dependency injection here. These are *stateful* components
with *identity*. Think about Seam in terms of contextual variables.
@In and @Out alias contextual variables to instance
[EMAIL PROTECTED] wrote : The difference with @In @Out is that you are able
to modify the value of the variable itself. ie. change the reference. With @In
alone, you can only change the state of the referent.
This is very clear and makes sense. I see where LoginAction.login() does this
on a
Uniqueness is predicated on the ordered pair of (Scope, context variable name).
Just like in EJB3, the default name of the contextual variable is the field
name. But you can always specify it explicitly if you like:
@In(foo) Foo bar;
Transition is new in CVS. I have not yet documented Seam
Hm. The second version confuses me in two ways. First, you have this:
@In Transition transition;
|
| @EndTask
| public String myActionListener() {
|transition.setName(approved);
|return success;
| }
First, it looks like the transition object is only @In, not @In @Out. But
anonymous wrote : First, it looks like the transition object is only @In, not
@In @Out. But it's pretty clear that myActionListener is trying to communicate
some state outwards to the conversation. So why not @Out also? Or is @Out only
for cases where new contextual objects might be outjected
Regarding conversations, JBPM, workflow annotations, etc..
While appreciate that Seam is (hopefully just initially) standardizing on JBPM
for most workflow functionality, what I would LOVE to see is Seam also support
a more lightweight workflow engine that is geared towards a non-persistent
Actually we are already working on this stuff. (It was part of the original
vision of Seam that we mapped out almost a year ago. Christian Bauer was
especially keen on this stuff, for several years.)
jBPM already runs in pure in-memory mode, all we really need to do is write the
JSF navigation
16 matches
Mail list logo
