enda wrote :
| There were some issues why it got deprecated and note from Gavin King was
to use pages.xml for it. So if it is undeprecated then it is ok.
|
Actually it's not undeprecated yet but I couldn't find a way to do the same
thing in pages.xml.
enda wrote :
| here you would
Hi Erik,
I would have two note for your solution.
1.
I do not know if Seam 2.1.0A1 undeprecated id in @Begin.
As you have
| @Begin(join = true, id =
#{facesContext.externalContext.requestParameterMap.forsendelseId})
|
There were some issues why it got deprecated and note from
I'm struggling with similar issues regarding natural conversations, can't get
them to join existing ones in a decent way.
+1 for better example in the docs.
Regards, Eirik
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4129082#4129082
Reply to the post :
In my application I keep getting Conversation id is already in use when I try
to use the same link twice to start the natural conversation. I thought I
should have a look at the seam-bay example to figure out what I did wrong, but
it turns out the same problem exists there. Please try for
Hi Erik this is my working solution (I am handling conversation on my own)
entityManager that inherits generalManager
|
| @Begin(flushMode = FlushModeType.MANUAL, join = true, pageflow =
teamHomeFlow)
| public String select(Team team) {
| // set conversation
|
Hi Tomas,
I was thinking about manually handling it, but since I only needed one type of
conversation and wanted that one named, I ended up with this:
components.xml:
core:manager conversation-id-parameter=forsendelseId /
view.xhtml:
h:dataTable id=forsendelser value=#{forsendelser}
1) I think I see the problem. Can you not use s:conversationPropagation
type=join / in your page? I agree, it would be nicer to specify this in
pages.xml, but unfortunately this isn't possible (this was the original design,
but pages.xml isn't processed until much later in the lifecycle).
2)
I also thank you for the feedback so I tried this:
| h:commandLink
|styleClass=left clearBoth
|action=#{teamManager.select(teamItem)}
value=select
|s:conversationName
No join should either join the existing conversation, or start a new one. If
this doesn't work, its a bug - please report it in JIRA.
I see the problem with problem 2 and I'll think about how to best help with
it.
View the original post :
Ok. Explain this one again (it sounds interesting, but I'm tired, and I got
lost ;)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4125935#4125935
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4125935
So imagine a scenario that you have one entity lets say people. You will
provide a table of all people. You can edit people and add new people.
Now you want to use jPDL and natural conversations (mix jPDL and pages.xml
because jPDL does not offer you to specify conversation name).
(note: I
11 matches
Mail list logo
