I'm trying to set up the profiler for my jboss environment. I have no idea where to put the libjbossInspector.so. I'm working in linux. The profiler version is: jboss-profiler-1.0.CR4. The readme says this:
1. Once built, put jbossInspector.dll in your PATH (if you are using Windows)
or libjbossInspector.so in your LD_LIBRARY_PATH (if you are using Linux/Unix.)
Also when I look at the directories for the profiler I don't understand what jvmpi or jvmti actually mean. Which do I use?
Can someone help me with this?
Janel10
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217850#4217850
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217850
"alesj" wrote :
| I guess you need to update the jboss-classloading-1.0.xsd as well. ;-)
It already has capabilites as a top-level complex type, or do I also need it as a top-level element?
| $svn diff
| Index: jboss-classloading-1.0.xsd
| ===================================================================
| --- jboss-classloading-1.0.xsd (revision 85694)
| +++ jboss-classloading-1.0.xsd (working copy)
| @@ -25,6 +25,16 @@
| </xsd:annotation>
| </xsd:element>
|
| + <xsd:element name="capabilities" type="capabilities">
| + <xsd:annotation>
| + <xsd:documentation>
| + <![CDATA[
| + The capabilities for use in other schemas
| + ]]>
| + </xsd:documentation>
| + </xsd:annotation>
| + </xsd:element>
| +
| <xsd:complexType name="classloadingType">
| <xsd:annotation>
| <xsd:documentation>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217803#4217803
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217803
I evaluated both
1) current maven dependencies approach
2) and additionalClassPath approach
My conclusion:
Current 1) approach is better one according to the fact our tests framework is fully mavenized. It's because dependencies classpath specified in modules/testsuite/pom xml is also reused in modules/testsuite/*-tests/pom.xml submodules for invoking JBossWS tools. If we would want to remove current testing approach it would mean to antize it again (step back).
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217786#4217786
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217786