January 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: Seam-Managed Persistence Context

by lightbulb432

anonymous wrote : If you used another persistence context, your objects would become detached when the persistence context ended. But doesn't what you said above apply to all persistence contexts, including the SMPC? What still confuses me is when does an SMPC end in comparison to, say, a SFSB extended PC? What's so special about SMPC...when is it created, when does it end, what requirements does it have in terms of associating itself with transactions, etc? Will my code look any different (I don't mean @In vs @PersistenceContext) in terms of the way I deal with entities from using another PC to using SMPC? (e.g. will I never have to do a merge again, what?) What should I keep in mind while I code so that I can actually take advantage of the fact that I'm using an SMPC? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000675#4000675 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000675

19 years, 3 months

1
0
0 / 0

[JBoss Seam] - seam context

by james_027

Hi, I don't quite understand the seam context, as they are many and the documentation doesn't seem to be enough for a beginner. Could somebody explain this. Is the session context and seam and jsf have the same scope? what is then the equivalent of jsf's request scope in seam? is it page or event? how are they differ from one another? In the clickable list example. the message entity has a scope of event? I can't understand why it has a scope? isn't the messengermanagerbean is doing all the work? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000674#4000674 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000674

19 years, 3 months

1
0
0 / 0

[JBoss Seam] - Re: invoke a action method everytime a page is accessed FROM

by norman.richards＠jboss.com

If you need a very peculiar strategy, why not just look up the value as a request attribute directly? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000673#4000673 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000673

19 years, 3 months

1
0
0 / 0

[JBoss Seam] - Re: Seam-Managed Persistence Context

by norman.richards＠jboss.com

If you used another persistence context, your objects would become detached when the persistence context ended. (either at the end of the transaction or when the associated session bean is removed, depending on the persistence context type) When that happens, you can notice a couple of problems. First, you would no longer be able to save changes to the entity into the database without manually merging it back into the new persistence context. You might also get lazy instantiation errors if you try to access state/relations that had not yet been loaded. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000672#4000672 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000672

19 years, 3 months

1
0
0 / 0

[JBoss Seam] - Re: problem persisiting a processInstance save the transient

by norman.richards＠jboss.com

If you are using the normal jbpm APIs, you should probably inquire in the jbpm forums for more experienced jbpm users to see. The jbpm APIs can be tricky... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000671#4000671 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000671

19 years, 3 months

1
0
0 / 0

[JBoss Seam] - Re: Seam and URL rewriting

by norman.richards＠jboss.com

Oh - no idea how apache URL rewriting would affect things. In general, I would suggest that it is a bad practice, but that's just my opinion. :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000670#4000670 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000670

19 years, 3 months

1
0
0 / 0

[JBoss Seam] - Re: Seam and URL rewriting

by norman.richards＠jboss.com

The conversation id must go with the request. It can go in the URL or it can be transmitted with the view data in a normal JSF POST. It obviously can't be stored in the HTTP session, because then you could have only one conversation per session. In theory it could go in a cookie if web browsers implemented conversational cookies, but they don't. But, actually, that's not a bad idea. It would be nice if cookies could be marked as "conversational" and would be transmitted on subsequent requests only on clicks/requests from the page that originated the conversation. It would also solve the general cookie problem because users who are paranoid could turn of cookies completely. There would be no privacy harm in using conversation cookies, because they would never be persisted by the browser, could never be used to transfer data between websites and the user could be sure that when he closed a window that his "state" would be gone. (think public internet access, etc...) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000669#4000669 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000669

19 years, 3 months

1
0
0 / 0

[JBoss Seam] - Re: EntityHome

by norman.richards＠jboss.com

Dumb question, but can you inject usersDatabase in other places? Does usersDatabase.component show up in the application context on the debug page? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000665#4000665 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000665

19 years, 3 months

1
0
0 / 0

[JBoss Seam] - Check for session attributes through EL

by lightbulb432

If I want to see whether there's a user component in session scope, how in EL can I output the presence of a component in the session context? I tried the following but it gives an error saying the "user" property is not found: #{not empty sessionContext.user} #{not empty sessionContext['user']} I simply tried #{not empty user} but this always equals true (i.e. there is a user component existing somewhere) even though I don't know how the component is existing on the first access of the page. The JSF pages don't refer to any of the properties of "user" so it shouldn't be getting automatically instantiated... What's the proper way to check through EL if something's been added to session scope? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000662#4000662 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000662

19 years, 3 months

1
0
0 / 0

[JBoss jBPM] - Re: How to create a Timer on a task-node?

by dasriharsha

The scheduler thread is running and the exception is because of an older version of the Handler that was deployed. So i cleaned up the JBPM tables and deployed the handlers again. It worked. Thanks for all the help. Regards Harsha View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000656#4000656 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000656

19 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user January 2007