Opening caveat: trying to manually manage the Hibernate 2nd level cache sounds like asking for problems.
The session.evict() call in Hibernate works on the session cache, not the 2nd level cache; that's why it has no effect. Check the Hibernate docs to see if there is an equivalent operation user's are meant to perform on the 2nd level cache; if so use that instead of manipulating TreeCache directly.
If you decide you still want to manipulate the tree cache directly, do you want to call evict() or remove()?
The log message you quoted is debug logging from the background eviction process that you're manually overriding; why are you concerned about it? It's not telling you that your remove() call didn't work.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978261#3978261
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978261
I found my problem.
In web.xml I had
| <context-param>
| <param-name>javax.faces.CONFIG_FILES</param-name>
| <param-value>
| /WEB-INF/faces-config.xml
| </param-value>
| </context-param>
|
Since faces-config.xml is read by default, this meant that my faces-config.xml file was read twice. Once I changed this to
| <context-param>
| <param-name>javax.faces.CONFIG_FILES</param-name>
| <param-value>
| </param-value>
| </context-param>
|
my problem went away. This configuration parameter is for extra configuration files and should not include the default faces-config.xml.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978258#3978258
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978258
Hmm... why then do I get "detached object passed to persist" when I try to persist a newly created entity with collection mapping?
I can persist anything just fine, but when I create an entity that holds a List of other entities (even when the list is still empty), that fails.
I have already tried to merge() the entit instead of persisting it, but then em.find will return null for it while still in the same transaction. I would expect to see and use the entity later on to fill that collection...
I am confused,
Phil
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978257#3978257
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978257
anonymous wrote : I was using an earlier build (jboss-seam-CVS.20061004) that has only the raiseEvent method and there are differences between the implementation of the two version.
There are??!
anonymous wrote : no such setter method: org.jboss.seam.core.ResourceBundle.bundle
| Name
The property is now called "bundleNames" plural, since we now support cascaded resource bundles.
Probably I should re-add the singular form for backward compatibility.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978255#3978255
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978255