We will advertise it more next week when people are back from holidays but we released the 2.4.1.SP1 (2.4.1 had a minor bug immediatly corrected in 2.4.1.SP1) of portal last week and it is available on sourceforge for those who are working with portal at the moment during the holidays, you can see that as a Christmas gift brougth to you by the portal team.
That release has a rock solid portlet cache implementation based on the render parameters, portlet mode and window state. More robust caching was requested by a couple of persons recently and we did listen to them.
Actually our caching layer did not have strong testing before simply because writing unit test case for that feature is certainly harded than writing the code itself (http://anonsvn.jboss.org/repos/portal/tags/JBoss_Portal_2_4_1_SP1/portlet...).
Now it is properly tested and we implement everything that is in the jsr168 specification.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996220#3996220
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996220
"pshankar" wrote : I have tried the same in my friend's PC and found that the problem lies in the JDK.
|
| JBoss cluster option reboot the XP when used in conjunction with JDK[1.5._06 and above]. I checked my friend's jboss log and found his JUDDI never failed. The system started rebooting after it joined the Cluster/GMS/JGroup channel.
|
| I will get the details of the log after I get to work. I am pretty sure the probjem lies in JDK. I downgraded my JDK and everything seem to be running fine. But in reality regarding the DST fix in Java I have to use JDK 1.5.0_06 and above at some point.
| As of now the development server is our machine where we can upgrade/downgrade at our will.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996219#3996219
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996219
