ZeroTurnaround Support Forum » JRebel Support

enum

(2 posts)
  • Started 7 months ago by GregTomkins
  • Latest reply from lauri

  1. Hi,

    I'm running the most recent JRebel with Tomcat 6.0 and for the most part it's like a dream come true.

    I blew a chunk of time today though, and it seems to be due to JRebel not dealing with the recompilation of a .class where the only change was to add a new value to an enum. The client class compiled OK and JRebel picked it up, but other classes saw the enum value as 'null'. Finally I tried stopping & restarting Tomcat, and suddenly, everything worked again.

    I could try to repeat this problem more accurately if it would help. Or, if this is just a known limitation, that's OK too, but I couldn't find evidence that this is the case, and I would like to understand this better.

    It's also possible that I am completely misunderstanding something here as I do not claim to be a Java or Tomcat wizard. It does seem clear, though, that restarting Tomcat fixed things, and I think the main point of JRebel is to avoid needing to do that.

    Thanks,
    Greg

    Posted 7 months ago #
  2. lauri

    Member
    Posts: 482

    If you add new fields to enums you'll see a warning in console that jrebel has reloaded a class that contains a new static filed and that field will not be initialized. Initializing new static fields has been implemented in the nightly builds http://www.zeroturnaround.com/nightly-build/jrebel-nightly-dev.zip

    Posted 7 months ago #

RSS feed for this topic

Reply

(required)

(required)

(optional)

(required)

Allowed markup: a blockquote code em strong ul ol li.
Put code in between `backticks`.

Olark Livehelp