[jboss-user] [JBoss Seam] - Re: Save conversation state in client
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 conversation context and the old window still has its conversation context stored. That way the user can start a new conversation by opening a new window. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4081186#4081186 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4081186 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Save conversation state in client
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 handled, new data is set in the context and the view is rendered to the new browser tab. If the old tab sends a different request (for example without opening a new tab), the server handles the old context without knowing that it was the same as the previous context. The context data is just set during the application phase, and the response is sendt back to the browser. In effect that means that we have split one conversation in two... I thought i could accomplish this with client side conversations (core:init client-side-conversations=true), but i suspect the conversation id parameter that always is appended somehow makes seam set the different conversation contexts as part of the same conversation (which is of course the expected behavior) Maybe one could turn the conversation id parameter off? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4081261#4081261 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4081261 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Save conversation state in client
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 : http://www.jboss.com/index.html?module=bbop=viewtopicp=4081272#4081272 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4081272 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Made it, but...
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 thought of (of course). All objects my action classes are referencing must be sent back to the browser. If i reduce the state to the minimum, the benefits of actually having a conversation are vanishing. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4081339#4081339 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4081339 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Save conversation state in client
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, but is this sufficient? I have tried this by setting the appropriate parameter in components.xml on the init component, but it seems to me that the state is still stored on the server side. Are there any other ways of achieving the functionality i am after? Could i save some conversation id in the page context and manually assign a conversation to a browser window? any suggestions would be appreciated. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4080992#4080992 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4080992 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: [OT] Trinidad 1.0.0-incubating
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 can combine them somehow...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4038721#4038721
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038721
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: End conversation and redirect problem
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 link to newBlogEntry? If the table of entries must be part of a conversation try to nest the conversations... View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038749#4038749 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038749 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: End conversation and redirect problem
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 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam Conversation Should Be Flexible but NOT
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 conversation running at a time, giving you the option to have a long timeout period. If the user enters a tab with a form, and the exits the form by clicking another tab, the conversation will be closed again. And if the user opens a new window, the users could fill out two forms concurrently (which is one of the big benefits of the conversation) Alas its not possible to restart a conversation with one action (correct me if i am wrong here), so you would have to redesign parts of the tabbing Of course it all depends on your requirements View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038268#4038268 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038268 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam Conversation Should Be Flexible but NOT
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 user interaction as a candidate for a conversation. In the end i solved by just having one conversation, possibly nesting if needed. (The users just love really long conversations ;) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038391#4038391 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038391 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: [OT] Trinidad 1.0.0-incubating
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 realize that whatever I do which i think might be smart, you guys are making it faster and better than me. Maybe i should just lean back and wait a bit longer. Chances are that you build the while application i am developing before me ;) - keep up the good work ) Any hints on where we can find the Seam Wiki? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038599#4038599 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038599 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Yeah!
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, leaving it to create the
components. The inject tag works just as a normal UI:include: It includes a
facelet with the same name as the macro, but it additionaly calls a factory
method on a seam component named 'wiki.', which creates a java bean that is
then passed to the included facelet. That way i can have a different bean for
each macro, based on the params the user supplies. (The params are supplied to
the factory as strings)
My approach has several obvious downsides:
Compiling the text every time is time consuming
No form submits, since the components disappear after they have been rendered
(i think)
The pros: I can back every macro with a bean, which is created based on macro
parameters.
Next i am thinking of implementing markers, that can give text some semantic
meaning that is a bit more advanced than the normal tags.
The beauty of seam is that it just makes it so easy to implement!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4038636#4038636
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038636
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
