It looks like your exception is defined to be a RuntimeException. Is your
PaService a stateful session bean? RuntimeExceptions cause the component
instance to be removed from the conversation by the RemoveInterceptor, if you
are using a SFSB. I believe this is to stay consistent with the J2EE
OK, thanks for the update on status. Unfortunately I didn't track down the
root cause or I'd post a patch for you. If I do end up figuring it out I'll be
sure to attach something to JIRA.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119875#4119875
Reply
I have been experiencing thread safety problems with the Pages component (this
is Seam 2.0.0 GA). This has been occurring when running load tests against our
application. The basic symptom is that Page actions are not executed and a
quick look shows that the Page object does not have any Actio
Yeah, I think that the issue you linked to is the same underlying problem.
I'll add a note to that issue that this affects more than the noSelectionLabel
functionality.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112794#4112794
Reply to the post :
http:
Hi,
We found a problem that started occurring in our application when we upgraded
to Seam 2.0.0GA. This occurs when using a List to back and
using an (or listbox).
for example using this component:
| @Name("testComp")
| @Scope(ScopeType.CONVERSATION)
| public class TestComp {
|
http://jira.jboss.org/jira/browse/JBSEAM-2314
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108738#4108738
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108738
___
jboss-use
Pete, thanks for the response.
I don't have the profiler results any more, but I believe the page time was
around 3-4 seconds. This was a bit of an expensive page due to the amount of
data being output in a table form, and that probably also explains why the
event notification was becoming n
I would note that similar issues also affect methods called from asynchronous
event handlers.
I had 'read' rules on entities that caused them to be unavailable when loaded
in an asynchronous method, because the rules still fire but there is no
established session and nothing in the working memo
I've been doing some profiling of our application, and finding in some cases
that a considerable amount of time per request (> 500 ms) is being taken up by
event triggering and handling.
When I look at the main source of the events, they appear to come from the
MethodContextInterceptor, which s
Seam is trying to create your session component by looking up the bean in JNDI.
Seam will try to use a pattern for the name as specified by the jndi-name
initialization parameter. This is usually something like
myEarName/#{ejbName}/local. So, seam will use the name of your component as
spe
Could it be that you don't have the SeamRedirectFilter in your web.xml?
|
| Seam Redirect Filter
|
org.jboss.seam.servlet.SeamRedirectFilter
|
|
|
| Seam Redirect Filter
| *.seam
|
|
Note that I am using *.seam as the URL
I believe you need to specify a Faces converter for the string:
|
|
This is in the documentation, Section 5.1.1
Hope it helps.
Kahli
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003089#4003089
Reply to the post :
http://www.jboss.com/index.html?m
Thank you for the information on the Hibernate bug. I had not searched on the
Atlassian JIRA, just on the JBoss one. I'll keep that in mind in the future.
I downloaded the 3.2.1 release of Hibernate Core and copied that library into
my JBoss installation. That error does not occur and more an
OK, here we go with a first post to the JBoss forums...
I've searched through the forums and JIRA and can't find anything about this.
Forgive me if this problem is due to my own lack of understanding. This may be
more appropriate for the EJB 3 forum, just let me know.
I am using the following
14 matches
Mail list logo
