I'm having the problem I thought I had, second click on the command button
calling an action with @Begin(join=true) gets a new conversation id.
And I was wrong about the action not getting invoked with the seam ui
components, they just don't seem to go through the usual jsf lifecycle (don't
Hi
I just noticed that adding
| propagation=join
|
to the s:button, starts a conversation and I get a Beginning Conversation log
message.
But when clicking the s:button I notice that the dataSearch.pattern property is
not set on my backing bean.
Any ideas?
Cheers
View the original
s:button/s:link DO NOT SUBMIT THE FORM!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121754#4121754
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4121754
___
jboss-user mailing
Just re-read the docs and noticed the bit which says that the seam button
doesn't submit the form.
Also discovered the s:conversationPropagation tag.
It seems to work just fine when using it with a h:commandLink , but not with
h:commandButton.
Anyway, sorry for the rant.
Should the @Begin
hi all
Can someone see an error in the way I try and kick-off a long running
conversation?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121622#4121622
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4121622
[EMAIL PROTECTED] wrote : The last two buttons, executes the action but the
conversation Id is incremented.
This is because each request initializes a temporary conversation if a
long-running conversation is not resumed. This means that your first page
request resulted in a temporary
Hi Jacob
Not quite sure I understood.
For the last two buttons the cid is always incremented, which I thought meant
that the temporary conversation was never promoted in to a long running one.
Is this how it is suppose to be?
1. First page render, cid=1
2. Post back to @Begin(join=true) action
Ok,
so if I press the submit button again, then the cid should still be 2 right?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121654#4121654
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4121654
Yes, since the action is annotated with @Begin(join=true). If join=true was
not there you would get an exception.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121655#4121655
Reply to the post :
[EMAIL PROTECTED] wrote : Is this how it is suppose to be?
| 1. First page render, cid=1
Yes. This first rendering starts a temporary conversation which is cid=1.
Once the page is rendered that temporary conversation is destroyed.
[EMAIL PROTECTED] wrote : 2. Post back to @Begin(join=true)
Hi,
thanks for your patience :)
Here is where I have problems, the cid still gets incremented (and doing my
head in). Or at least I think so, pretty sure I tested this. Will make sure
again tomorrow at work.
I wonder what I've done wrong? And isn't it also a bit strange that the
s:button/link
the s:button/link does not call your action method if the form on the page
contains validation errors. I've been struggling with this for over a day once.
Maybe you have the same problem
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121666#4121666
Reply to
JBoss Tools is nice. I wish there was integration with NetBeans in addition to
Eclipse.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121464#4121464
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4121464
Tried your code in a JBoss Tools project? It is really straightforward and
assures that you don't struggle with some library conflict somewhere.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121432#4121432
Reply to the post :
Sorry, in a prev. message the code for page1.xhtml
should look like this (view attribute was missed by copy/paste):
| s:link value=start view=/page2.xhtml action=#{conversation.begin}/
|
View the original post :
This does not throw an exception due to the behavior of an s:link. An s:link
initiates a GET request which will only capture parameters passed in the query
string (nothing is posted). If you look at the URL generated by your s:link
you will see something like the following:
Thank you - I've got it.
Meantime I'm trying to explore org.jboss.seam.core.Manager sourcecode
in order to get an answer about how seam determines if long conversation
is active, but with no success (
Seems that restoreConversation() method looks at
conversationIsLongRunningParameter in
Which version of Seam are you using? conversation-is-long-running-parameter is
not included in latest (Seam 2.0.0.CR2) due to the addition of
conversation-required.
The key to understanding conversations is the conversationId sent with the
request. The conversationId is maintained along with
anonymous wrote :
| Which version of Seam are you using? conversation-is-long-running-parameter
is not included in latest (Seam 2.0.0.CR2) due to the addition of
conversation-required.
|
I'm using 1.2.1GA
anonymous wrote :
| The key to understanding conversations is the
amashtakov wrote : I'm using 1.2.1GA
Yes, 1.2.1.GA uses clr (conversation-long-running-parameter=clr).
There are essentially 2 scenarios:
- GET - conversation attributes passed in query string (the situation you are
referring to)
- POST - conversation attributes posted with the form not in the
Thank you,
I'm going to experiment tomorrow a bit more (do not have jboss/seam at home
yet) - will check back button feature.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4096220#4096220
Reply to the post :
Please, nobody has a solution?
Thanks :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4063826#4063826
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4063826
___
jboss-user
You called the setDescription(Class caller) from your @Factory method, so it
will be only called once. I guess the description is always your root
conversation
Please have a look here:
http://www.jboss.com/index.html?module=bbop=viewtopicp=4061563
If you'd like you can try the @Unwrap
Thank you I will consider this option :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4063944#4063944
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4063944
___
jboss-user mailing
Seam 1.2.1.GA
public class Conversation implements Serializable
| ..
|public void beginNested()
|{
| if ( Manager.instance().isLongRunningConversation() )
| {
| Manager.instance().beginNestedConversation(
Seam.getComponentName(Conversation.class) );
is this thread related to your problem?
http://www.jboss.com/index.html?module=bbop=viewtopict=112414
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4063859#4063859
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4063859
I've read that post, it is quite related but I am not working with seam 2.0,
but my question is a bit more basic, since I'm not quite sure about the fact
that conversations can be nested at more levels...
Did you understand my scenario and do you have any alternatives to nested
conversations?
The @Factory(DatamodelName) method is called when the associated DataModel is
null. Since I nullify my DataModel anytime I need to reload data the @Factory
method gets called when I want.
I read the Debug and conversation names are correctly set.
If you annotate with @Unwrap a method that
Never mind - it looks like (after reviewing in detail the documentation) that
conversation is not really a good scope for entities. Instead, it looks like a
solution based on private state in an SFSB and using the manager pattern
(@Unwrap) may be a better way of doing this.
Thanks,
Brad Smith
I wouldn't advise exposing entities as Seam components. I find it much neater
to manage through a CONVERSATION scoped bean (be it a Seam JavaBean or a SFSB)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4054168#4054168
Reply to the post :
Yeah I checked that. It is conversationId. Has anyone used frames in this
way?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4053313#4053313
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4053313
This is the error I get when I manually set the jsp in the frame:
16:13:34,571 ERROR [SeamPhaseListener] uncaught exception
| java.lang.IllegalStateException: No active conversation context
| at org.jboss.seam.core.Conversation.instance(Conversation.java:104)
| at
Are you sure that conversationId is the name of the parameter? You can
configure this in components.xml:
| core:manager concurrent-request-timeout=2000
| conversation-timeout=18
| conversation-id-parameter=cid/
|
View the original post :
I have forgot:
Conversation.pop();
before
| Pageflow.instance.reposition(detail);
|
to reposition parent pageflow.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4049189#4049189
Reply to the post :
Hi,
my solution isn't best but it works: with component Conversation I end up
nested conversation, then Redirect to required view a then define transitions
for previous node, or reposition pageflow to new view (node):
| public void endAndRedir() {
|
Did you find solutions for your questions?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4048899#4048899
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4048899
___
jboss-user
Seam provides a stack of your conversations.
@In List conversationStack;
Methods of interests are conversationEntry.destroy() and
conversationEntry.select()
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4048912#4048912
Reply to the post :
| @In ListConversationEntry conversationStack;
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4048913#4048913
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4048913
___
YOu can also do
|
| @In Conversation conversation;
|
| conversation.redirectToParent();
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4048915#4048915
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4048915
Another question:
It is possible to acquire parent conversation (within nested conversation) and
set viewID?
Something like this:
Conversation c = Conversation.instance();
| c.getParent().setViewId(/detail.jsp);
I don't know how to get parent conversation.
I need to return from nested
Another question:)
How to acquire parent conversations pageflow, seam component:
Pageflow.instance();
returns pageflow for actual conversation.
Need to reposition for parent pageflow.
Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4037072#4037072
Additional question:
When updating elements in a long-running conversation, is one big update sent
to the database when the conversation is explicitly ended?
Or are updates being sent to the database throughout the long-running
conversation (i.e. every time a page gets submitted), but if the
lightbulb432 wrote : Additional question:
|
| When updating elements in a long-running conversation, is one big update
sent to the database when the conversation is explicitly ended?
|
no.
Data is updated when a transaction starts and commits.
Read
So if it's not sent as one big update, is it sent as I guessed in the second
paragraph in my previous post?
If you specify flushMode=MANUAL, the docs say you explicitly have to call
flush(). What happens if you end a conversation that has pending updates to it
without calling flush()...aren't
This is basic Hibernate. The FlushMode controls when changes are sync'd to the
database, and if you look at the documentation on the FlushMode class, you will
see a precise definition of each mode. By default, all changes are flushed
before the end of a transaction, which usually means that
Thanks, that description cleared that up.
Let's say you have a conversation with several methods (one method called per
request) and I use FlushMode.COMMIT/AUTO. If the first few requests in the
conversation access a NEVER or NOT_SUPPORTED action method, and the next
request accesses a
anonymous wrote : Let's say you have a conversation with several methods (one
method called per request) and I use FlushMode.COMMIT/AUTO. If the first few
requests in the conversation access a NEVER or NOT_SUPPORTED action method, and
the next request accesses a REQUIRES (or similar) action
I use a conversation-scope entity component as the value of a
@DataModelSelection. Every time I select a row from the dataTable, the cid
keeps incrementing! I do see why this is happening, but I'd like it not
to...how would I get around this?
I tried changing the scope of the entity to EVENT
Is is possible to start a new conversation with @Begin and leave the current
one untouched? As result there will be two sibling conversations.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4003849#4003849
Reply to the post :
no.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4003983#4003983
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4003983
___
jboss-user mailing list
jboss-user@lists.jboss.org
As far as I know every faces request is conversation scoped by default, so if
you haven't configured other scopetypes...
And @Begin and @End will start and end a longrunning conversation which can
exist over multiple request-response cycles.
See chapter for conversations in seam-reference...
There is always a temporary conversation context. And this context spans
redirects. Hence the cid parameter.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4003516#4003516
Reply to the post :
No, no really good way at present. I suppose I could probably add a setting in
pages.xml to disable propagation of the temp conversation to a view id. Try
adding a feature request to JIRA, but note that this is not a high priority for
me right now.
View the original post :
Is there a way to disable that behavior? Is that what propagation=none or
end is for in the pages.xml?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4003540#4003540
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4003540
Never mind, I was confused. Sorry if you spent any time on this.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3966163#3966163
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3966163
55 matches
Mail list logo
