[Design of Messaging on JBoss (Messaging/JBoss)] - Re: ClassLoader behaviour on remote clustering tests
by flavia.rainone@jboss.com
Clebert,
I am seeing 348 calls to the joinpoint class generation code during the execution of your tests. The weird is that there are only 28 entry points (method wrappers) that call this code.
8 of those 28 entry points are called thousands times each. The other 20 are called only a few times each, and if we sum up all the times they are called, we will get to 339 calls.
Thanks to the cache of generated classes, only 205 of the 348 calls to the generation of classes actually result in a class generation. The other calls just retrieve classes from the cache.
Anyway, I don't see why would the class generation ocurr so many times if you told me that those tests don't perform any dynamic addition/removal of aspects. My initial thought is that we should see one class generation call for each one of those 28 methods, and this should occur the first time those methods are called.
Probably I'm missing something here... I'll continue looking for what is causing this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143758#4143758
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143758
17 years, 12 months
[Design of JBoss Portal] - Re: JBoss Portlet Container integration into 2.7
by julien@jboss.com
I have adapted the content provider framework for rendering to use public render parameters as it was planned.
In order to be content driven a portlet needs to declare and manage the public render parameter "uri" with the namespace "urn:jboss:portal:content".
At runtime the portal will set the declared parameter with the window contained URI.
What is remaining to be done in that area is :
1/ update of the faces portlet component to handle a portlet generated event as a JSF event
2/ implement a special event that signals the end of the configuration activity during content edition using the same "urn:jboss:portal:content" namespace with an appropriate name. When this event is received it should tells the JSF admin portlet that content is configured. Today that already exists but relies on a special action parameter which is the previous way to communicate.
I experienced the impossibility to use the portlet content editor in the admin due to stack traces, so that should be solved asap.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143747#4143747
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143747
17 years, 12 months