I am in the process of documenting some of the primary structures in the production profiler and their constituent cardinalities.
One issue I have run into is the cardinality and identification of Nodes. I had originally thought that a Node would be unqiuely identified as a Category Name and an Operation Name.
For example, consider an EJB Method "OrderEJB.processOrder". We might assign it an identifier as follows:
Category Name: Stateless Session Bean
Operation Name: OrderEJB.processOrder
Unique Identifer: "Stateless Session Bean:OrderEJB.processOrder"
However, what this does not take into account is the potential for different execution paths within that operation.
OrderEJB.processOrder-->Op A --> Op B --> Op C
OrderEJB.processOrder-->Op C --> Op X --> Op Y
In this instance, I would think these two code paths should be represented by two different nodes, but the naming and tracking will now get substantially more complex.
Any thoguhts ?
//Nicholas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955543#3955543
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955543
|
