November 2006 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: EntityManger-per-user-session...

by iradix

It does seem that we aren't quite understanding each other. Let me clarify a few points that I think might help you. 1) So I don't confuse things (including myself) I'm going to pretend that Persistence Context and Entity Manager mean the same thing. @PersistenceContext(type=EXTENDED) does not provide an EM scoped to the conversation, because it is not aware that conversations exist. This confused me at first too because there is a lot of new information to take in. First you have the EJB3 spec and the EM propagation rules there, and then you have your Seam Managed EM with it's own rules. What you get by using @PersistenceContext(type=EXTENDED) is an EM that will survive from call to call on the session bean where it's defined, even if those calls span requests. It will also be propagated through to other session beans called by the original. That might be an oversimplification but I think you get the gist. What you get with a seam managed persistence context is a single EM per conversation which can be injected using @In. 2) Once you've got your Seam Managed EM set up it will act as an object cache over the course of the conversation, only hitting the database for object retrieval when it has to. So if you retrieve a User as soon as the conversation is started, every time you call em.find(User.class, userId) afterwards you get the cached user back. No extraneous queries. The EM will also check to see which objects have been updated and generated the appropriate sql once it is flushed. 3) I see 2 reasons off the top of my head not to use a session scoped EM. The first is that you are caching data that the user has accessed throughout their session when much of it is quite possibly no longer relevant. Why take up the extra memory? I see no real benefits to this approach and even if your app is small enough that it doesn't make a difference now, it's not going to be very scalable. The second is a matter of providing accurate data. In my opinion it's a good thing to drop your entity manager at a well defined point (when the data in it is no longer being used) so that if the user chooses another operation that relies on that data a fresh, up to date version of it will be retrieved. If you use the same entity manager throughout a user's session they will only see any changes that they have made (which are retrieved from their EM cache). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984165#3984165 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984165

19 years, 6 months

1
0
0 / 0

[JBoss Seam] - Re: hibernate-ALL.jar

by gavin.king＠jboss.com

You can use your own hibernate jars if you like, just make sure you get versions that are compatible with your version of E-EJB3. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984164#3984164 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984164

19 years, 6 months

1
0
0 / 0

[JBoss Seam] - Re: UPDATED: SelectItems (the one with the EntityConverter)

by petemuir

In the example the EntityManager is a Seam Managed Persistence Context so is injected using @In. If you look at the getting started guide, you'll see that it tells you to use JBoss 4.0.4.GA not 4.0.4.CR2. I'm not going to waste my time sorting out why the code doesn't work a unsupported platform. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984163#3984163 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984163

19 years, 6 months

1
0
0 / 0

[JBoss Messaging] - Re: Messages delivery stops after a while

by timfox

Also bear in mind that each consumer by default will prefetch 150 messages, so this is probably what is happening: 1) Create consumer. 2) 150 messages get prefetched. 3) Receive one of the messages 4) Forget about the consumer 5) Go to step 1 So in 20 iterations, probably, 20 * 150 = 3000 messages will be in the consumers. If you can provide some valid JMS code that demonstrates a problem will be happy to investigate further. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984162#3984162 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984162

19 years, 6 months

1
0
0 / 0

[Security & JAAS/JBoss] - Jboss Portal Integration with OpenSSO

by bmathew06

I have OpenSSO doing the authentication, post authentication the userid is sent to JBoss Portal, I have a servlet filter which takes this and does a redirect. String url = "j_security_check?j_username=" + username + "&j_password=" + password; String redirectUrl = response.encodeRedirectURL(url); response.sendRedirect(redirectUrl); I was expecting the login to happen and user taken to the portal home page. This does not work. Any inputs on how to get this done? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984161#3984161 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984161

19 years, 6 months

1
0
0 / 0

[JBoss Seam] - Re: Problems with application-like behaviour project

by gavin.king＠jboss.com

I have a release (1.1.BETA2) this week and have not had time. It is marked todo in my email client. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984160#3984160 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984160

19 years, 6 months

1
0
0 / 0

[JBoss Seam] - Re: PAGE-scoped data dropped on validation errors

by gavin.king＠jboss.com

It was by design, but that design has been changed in Seam 1.1. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984159#3984159 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984159

19 years, 6 months

1
0
0 / 0

[JBoss Getting Started Documentation] - PluggableInstrumentor

by l_richy007

I use "jboss-4.0.5.GA" I follow the tutorial on "http://docs.jboss.com/jbosside/tutorial/build/en/html/index.html" when I start jboss I have an error 15:19:27,828 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml | 15:19:33,562 WARN [ServiceController] Problem creating service jboss.aop:service=AspectManager | java.lang.NoClassDefFoundError: org/jboss/aop/standalone/PluggableInstrumentor | at org.jboss.aop.deployment.AspectManagerServiceJDK5.attachTranslator(AspectManagerServiceJDK5.java:42) | at org.jboss.aop.deployment.AspectManagerService.createService(AspectManagerService.java:121) | Can anybody tell me why ? When Jboss loads my FiboApp.ear I have that error 15:20:13,406 INFO [EARDeployer] Init J2EE application: file:/C:/java/jboss-4.0.5.GA/jboss-4.0.5.GA/server/default/deploy/FiboApp.ear | 15:20:13,500 INFO [EARDeployer] Started J2EE application: file:/C:/java/jboss-4.0.5.GA/jboss-4.0.5.GA/server/default/deploy/FiboApp.ear | 15:20:13,515 ERROR [URLDeploymentScanner] Incomplete Deployment listing: | | --- MBeans waiting for other MBeans --- | ObjectName: jboss.aop:service=AspectManager | State: FAILED | Reason: java.lang.NoClassDefFoundError: org/jboss/aop/standalone/PluggableInstrumentor | | --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- | ObjectName: jboss.aop:service=AspectManager | State: FAILED | Reason: java.lang.NoClassDefFoundError: org/jboss/aop/standalone/PluggableInstrumentor Can you help me to find what's wrong View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984158#3984158 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984158

19 years, 6 months

1
0
0 / 0

[JBoss Seam] - Re: Mixing @PersistenceContext with Seam Managed Persistence

by gavin.king＠jboss.com

An EM holds stale data until you close() o clear() it. This is just basic JPA. I recommend you spend some time with Hibernate in action or jpwh, to properly understand the semantics of a persistence context. This question is not seam-related. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984157#3984157 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984157

19 years, 6 months

1
0
0 / 0

[EJB/JBoss] - Upgrading to Remoting 2.0.0GA in JBoss 4.0.5

by alexg79

I would like to upgrade JBoss Remoting to 2.0.0GA on JBoss 4.0.5 to work around a bug that causes some EJB3 remote calls to fail on JDK 6 beta 2. Is it just a drop-in replacement, or is there something else I should consider? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984155#3984155 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984155

19 years, 6 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 November 2006