I'm using JBoss 4.2.3 with Hibernate and I have the following scenario.
Two entities, let's call them 'Parent' and 'Child'. A Parent has many Children.
The relationship in Parent is declared using javax.persistence annotation like
this:
@OneToMany(mappedBy = "parent", fetch = FetchType.LAZY, ca
I have the following declaration in my pages.xml
My page declaration is:
|
|
|
The componentLoader is a stateful session bean with conversation scope. My
desire is to instantiate only one such bean for any given oid. It almost
works...
The bean is created in the correct scope and
How about that. The preview of the post actually expands the html entities, not
just in the previewed text, but also in your entered text. Next preview (or
submit) is then corrupt. This time I used the back-button after my preview.
I meant to write "the undocumented element"
A re
Oops. Forgot to disable html. I meant to wrote "the undocumented element"
A related question. The element can be put in a file of its own, one for each
view. It seems to me like it would be desirable to perhaps have the option
declare the inline in a instead of referencing it using an attrib
I've made some attempts to use the undocumented element.
As far as I've understood, the attributes are:
name
The name of the conversation. You use this to reference the conversation from
the page clause and the name will also be prepended to the conversation id.
parameter-value
The conversatio
I'm managing my own conversation id's. After a conversation timeout has
occurred, I'm not able to reuse the same id again. I get the following message:
"sourceId=null[severity=(WARN 1), summary=(The conversation ended, timed out or
was processing another request)"
Is there any way I can make Se
I get the message "Exception calling stateful session bean default @Remove".
The cause is a null pointer exception when I try to access a @Logger injected
variable in an @Out annotated method.
As far as I can see, the @Out annotated method is called during the remove
phase at a time when all in
Assume the following:
public class X implements ISerializable
{
@Out
private String name;
...
}
What happens when I serialize this? Will the @Out annotation make the name
transient? I think it should since the name is not really part of the state of
X.
- thomas
View the original po
The "collection was processed twice bu flush" was there when we used the
2.0.0.BETA1 release so it is unlikely that it is related to changes made
yesterday.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065386#4065386
Reply to the post :
http://www.jboss.c
I'm running the same app as Henrik but on a faster machine with more memory. I
consistently get the "collection was processed twice by flush" exception.
- thomas
13:52:11,518 ERROR [AssertionFailure] an assertion failure occured (this may
indicate a bug in Hibernate, but is more likely due to u
And then you have the problem with us who are using your Update Site
(http://download.jboss.org/jbosside/updates/stable) from within the Eclipse
IDE. Why does it suggest that you download an incompatible version?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=
Perhaps you should add something on the downloads page as well? Why assume that
people go to the wiki before downloading?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001507#4001507
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&m
So, in essence there is no way to control the transaction timeout for an MDB
unless you change the global transaction timeout? If that's true, I would
consider it a fairly serious flaw in JBoss.
A work around involving new threads won't help me much since it's essential
that the popping of the
13 matches
Mail list logo
