December 2006 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: Excessive [could not destroy component] 1.1B1 to 1.1CR1

by gavin.king＠jboss.com

anonymous wrote : No, my session scoped SFSB are not sitting around idle. I don't believe you. If they were not sitting around idle, you would not be getting EJBNoSuchObjectExceptions. Please consider the possibility that this is your problem, instead of fixating that it is mine. anonymous wrote : What I'm trying to explain in both the ticket (and apologies for diverging here) is that I believe it is Seam's responsibility to handle this better, and agnostic to the JEE container. Is it also Seam's responsibility to solve the AIDS epidemic in Africa and help America bring democracy and stability to Iraq? It's all very well to wish for impossible things, but I have to actually write some code at some stage. There is no platform-neutral way to implement this, since the metadata to control SFSB timeout is not defined by the Java EE spec. End of story. Nor are there any exposed APIs that Seam could call. anonymous wrote : as of 1.1CR1, Seam is no longer destroying these components successfully (above error). I have @CacheConfig set at 35 minutes. It was previously at 30 minutes and worked FINE on 1.1b1 and below. Seam had no problems destroying these components. You are the only one who has experienced this (so far). You have given us no way to reproduce the problem. You have given no real information other than a stack trace. And you are ranting and telling us that we have a responsibility to deliver impossible things. If you can produce a very, very simple test case that demonstrates this happening, we can continue this discussion. If not, I have many other things to do. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990310#3990310 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990310

17 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: JBossSeam & Quartz: how?

by gavin.king＠jboss.com

anonymous wrote : Gavin, I've been looking for an example or something to look how to use the connecto. Do you have an URL? Ask in EJB3 forum. anonymous wrote : Another question. Since Seam is integrated with JBPM, can I create a JBPM schedulled-task?? No, not yet. This is slated for 1.2. anonymous wrote : (I need a task that executes forever with gaps of 10 minutes) | If thats all you need why not just use a Seam 1.1 asynchronous method? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990309#3990309 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990309

17 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: Excessive [could not destroy component] 1.1B1 to 1.1CR1

by rdewell

Alright, it's my fault, but this thread has gotten off topic. No, my session scoped SFSB are not sitting around idle. They're being used almost constantly throughout the app session. What I'm trying to explain in both the ticket (and apologies for diverging here) is that I believe it is Seam's responsibility to handle this better, and agnostic to the JEE container. Regardless of that perspective I have, back to topic, as of 1.1CR1, Seam is no longer destroying these components successfully (above error). I have @CacheConfig set at 35 minutes. It was previously at 30 minutes and worked FINE on 1.1b1 and below. Seam had no problems destroying these components. So, I don't know what's changed. I guess I'll have to dig more info up. I find the whole thing strange myself. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990308#3990308 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990308

17 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: No page context active - ICEFACES

by gavin.king＠jboss.com

Try CR2. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990307#3990307 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990307

17 years, 8 months

1
0
0 / 0

[EJB 3.0] - How to get CallerPrincipal in EJB3 session bean

by enazareno

Hi, How do I get a reference of the callerprincipal in a session in EJB3? In EJB2, we can get the caller principal in the context of the session bean, but now session beans are just pojos. I've just started working with EJB3. I don't know if this has been answered already, if it is, please direct me to that post or any wikis for that matter. Would appreciate any help. Thanks. Regards, Elmo View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990304#3990304 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990304

17 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: Injection and disinjection control

by gavin.king＠jboss.com

anonymous wrote : Could you please elaborate a bit why injection is happening for every method call instead of only 1 time on the 1st call. Because the value of a contextual variable can change b/w calls. anonymous wrote : I'm asking because I thought that configuration with xml or with annotations leads to the same result. It definitely does not, and the docs make this very clear. Stop pre-optimizing! The FIRST rule of performance is don't make assumptions about performance before you actually have a real application which has a performance problem. This is a basic rule that all good programmers follow. Seam's bijection is NOT going to make your fast application slow! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990303#3990303 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990303

17 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: EntityManager: For newbies or to close gaps in your know

by gavin.king＠jboss.com

anonymous wrote : One of the disatvantages of using an extended persistent context is that the transaction lasts for a long time, which is maybe not what you want. This is DEFINITELY not true. Persistence context != transaction context. That is why there are two different things. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990302#3990302 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990302

17 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: Bidirectional OneToMany removal of related entities

by gavin.king＠jboss.com

No. You would need to add the (Hibernate-specific) annotation for orphan delete. Also check your understanding of persist(), it is NOT used in the way you are trying to use it here! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990301#3990301 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990301

17 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: Null EntityManager

by gavin.king＠jboss.com

Seam JavaBean components do not support the @PersistenceContext annotation, which is only for EJB3 components. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990300#3990300 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990300

17 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: Excessive [could not destroy component] 1.1B1 to 1.1CR1

by gavin.king＠jboss.com

I mean, frankly, if you think about it, this is exposing a real flaw in your application design. What you have is state sitting on the server that is not even being used, for an entire login session! This is a waste of server resources. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990299#3990299 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990299

17 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user December 2006