Does the reference chain from the JOTM object lead through a javax.transaction.Synchronization implementation? For example, org.jboss.cache.interceptors.TxInterceptor$RemoteSynchronizationHandler (or TxInterceptor$LocalSynchronizationHandler)?
If not, please post the full reference chain.
If so, two possibilites:
1) JOTM is holding onto the ref to the Synchronization for a little while, but will eventually clean it up and your object will be gc'd.
2) JOTM is holding a ref to the Synchronization and won't ever release it. That would be a bug in JOTM.
See http://www.jboss.com/index.html?module=bb&op=viewforum&f=164 for a question I raised with our transaction gurus that deals with a strategy we could employ to aggressively cut the reference chain.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028039#4028039
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028039
First, it would help to know specifically what problem you have run into.
Second, since 2.6 is a beta, the documentation is also beta. Since you are just now learning the portal, it might be better to start with 2.4.1. The documentation for that is very good. Once yo understand the concepts, and have worked with portlets in 2.4.1, you can then try 2.6 again, many of the concepts are the same.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028032#4028032
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028032
It also works fine (I think to remember) without DTD listed in any page.xml, because then dom4j doesn't say it is false when in fact it isn't there.
One could say that's a bad library, that returns different results for an attribute value whether the DTD is mentioned in the XML or not. Though it is open for discussion what one expects. I think at least it should be optional to get the result one wants if one cares to code it so, and it seems dom4j doesn't let us do that here.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028022#4028022
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028022
You're not bugging me. Something not working the way I expect it to work bugging me. :)
anonymous wrote :
| but its barfing on startup now with error that seams needs to be configured before spring.
|
This is probably the heart of the problem. The Spring ContextLoaderListener needs to be loaded after the SeamListener. It may be a matter of simply changing the order in your web.xml. In the next release you will be able to use seam:context-loader to load the spring application context as a seam component. Anyway, give it a try if you want.
Mike
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028021#4028021
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028021