Loading Profile...
Twitter, 
Facebook, or email.
Currently it seems impossible to use Chronon with the server types from JBoss Tools (just nothing happens when record is pushed). It only works for the simple (basic-)server types that are part of the Eclipse WTP distribution. But I think a lot of people are using JBoss Tools for this purpose.
So, are you planning to support JBoss Tools in the future?
Support for Eclipse JBoss Tools
Official Response
-
EMPLOYEE
I’m happy
Chronon 3.6.5 released today adds support for JBoss tools 4.0.
You should now be able to record jboss from within eclipse.
-
soon :)Comment
-
-
Ok, got it somehow running as a standard 'JBoss v5.0' server for now.
But I the recordings are almost empty an do not show much useful information. Seems that most information is lost somewhere in the "Unrecorded Methods" when I start it with the default settings. It seems that I can only see the outermost (EJB) interceptor call.
So I tried the pattern '' to find out why, but in this case the startup takes forever or is interrupted by the server's respective timeout.
On the server I currently use JBoss 5.1 with Seam 2.2.2.
My projects in Eclipse are maven projects that are integrated by the JBoss Tool's maven integration support.
So are there any issues regarding the usage of maven projects or Seam (or AOP interceptors in general)? -
-
chronon operates at the jvm level, so maven or not, shouldnt be a problem.
* is an invalid pattern.... -
-
I’m frustrated
That's clear, but I thought it might have a problem with complex maven project setups...
I just saw that I get a lot of this messages on startup:
"Chronon: java.lang.instrument.UnmodifiableClassException" -
-
is a class name listed next to it?
-
-
No, just the text I mentioned and a message that something with Log4J seem not to be ok...
Please have a look at the attached console output:
-
-
can you tell me your include/exclude patterns please?
-
-
Thanks, I think the problem was caused by the pattern *.** which I added since I was not able to record the interesting classes in my application.
So since I now use de.logsolut.* the shown exception has disappeared but I'm still not able to record the interesting parts of my applications:
1.) First I have a server component on top of JBoss 5.1 using Seam and want to debug the calls to Seam components and Session beans which match the mentioned pattern but nevertheless don't get recorded.
2.) On the other side there is are some WebStart/Swing clients on which it shows up an abnormally thread termination for the EDT if it gets a litte bit delayed or if a SwingWorker is used. -
-
you do realize that de.logsolut.* just records thing in de.logsolut package.
Any subpackages like de.logsolut.abcd, etc wont be recorded. For that you need to use a double start at the end(not single star). -
-
EMPLOYEE
I’m happy
Chronon 3.6.5 released today adds support for JBoss tools 4.0.
You should now be able to record jboss from within eclipse. -
