Thank you for the reply, i realize that my question was unclear at best. What i
want is to store the onversation context at the client, so if the user clicks
a link the conversation continues, but if the user clicks a link and opens the
response in a new window, the new window has its own
Yes, the server will not be able to detect if the view is rendered to a new
window. But if the conversation context is stored in the client, the server
does not need to know.
If a user opens a view in a new window the context is sendt to the server along
with the request, the request is
How stupid of me. The s:link produces a GET request with parameters, which
means that the conversation context cannot posted to the server. If i use
normal JSF postback, i can't open in new tab. I have to think of another
solution...
View the original post :
I managed to make the application behave like i wanted. I replaced all the
s:link components with the normal h:commandLink component. But i am pretty sure
it's not a very good idea to send the whole state back and forth all the time.
The conversation contexts state is a lot larger than i first
I would like one conversation per open browser window. If the user opens a link
in a new tab, i would like the new tab run in a new conversation, and the old
tab to continue running in the old conversation.
I believe that this could be achieved by saving the conversation state in the
client,
Yes, i replace all text that looks like [:param_1;...;param_n] into
wiki:include name= factory=wiki.('param_1',...,'param_n')/
The text is then compiled by the facelet compiler and finally rendered.
I'll try to understand your approach a bit better, it seems more elegant :),
and then see if i
I don't think its possible to end and start a new conversation in a single
request (yet). I am not 100% sure of the seam lifecycle, but i believe i have
read in this forum that its not possible, but might be implemented in some
future version. Why not start the conversation when you click the
Or you could just try to redirect the page? (In pages.xml) It might do the
trick...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4038764#4038764
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038764
If you set the conversation id manually, you can control the number of
conversations created. (The side effect is that you might rejoin the
conversation even if you don't want to.)
You could also be sure to end conversations whenever a new treenode or tab is
clicked. That way you only have one
Just a short comment: i had the similar issues you mentioned, as I also was
risking an huge growth of un-ended conversations. (But my application requires
multiple parallell windows.)
I was overwhelmed by the possibilites that the conversation context gave me
that i started to see almost every
Pete: I read your blogpost about facelets-plugins which seems very interesting.
But i cant seem to locate the Seam Wiki you refer to. (I tried the CVS ROOT of
Seam)
( I have just made a small site with wiki functionality using seam and
facelets, following the first strategy you mention. But I
This looks excellent!
I used a different approach. I modified the seam antlr grammer so it would
recognize the macros, and replaced it with a home made injection tag
(wiki:inject name=macroname factory=wiki.macroname('param1','param2') /)
I then run the facelet compiler over the content,
12 matches
Mail list logo
