![]() INFO: Created user preferences directory. JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m 4Stack=true =true -Drebel.remoting_plugin=true -agentpath:/opt/jboss/wildfly/libjrebel64.soĨ:37:30 PM $1 run Run the container as: docker run -it -p 8080:8080 javaee7-hol.Actually build the image as: docker build -t javaee7-hol.This WAR file is the same that was generated earlier. This will not work for you, and you’ll need to replace it with something like:ĬOPY $JBOSS_HOME/standalone/deployments/ Downloads the pre-built WAR file from GitHub.Configuring application server such that it knows about the “remote” mode and platform-specific library.Copying the JRebel agent and platform-specific library to the image.Using the official jboss/wildfly Docker image.RUN curl -L -o /opt/jboss/wildfly/standalone/deployments/ RUN echo "JAVA_OPTS=\"\$JAVA_OPTS -Drebel.remoting_plugin=true -agentpath:\$JBOSS_HOME/libjrebel64.so\"" > $JBOSS_HOME/bin/nfĬMD The exact name would very likely differ in your case.ĬOPY libjrebel64.so $JBOSS_HOME/libjrebel64.so ![]() #JREBEL JSP REMOTE SERVER MAC#On Mac these files are available in eclipse/mars/m5/eclipse/plugins/_6.1.1.RELEASE-201503121801/jr6/jrebel/ directory. Both of these files are available from Eclipse if JRebel was installed earlier. This will package rebel.xml and rebel-remote.xml in the WAR file.Īpplication server needs to know about JRebel agent and platform-specific library. Package your application as mvn package.This will ensure that the public key is generated appropriately. This needs to be done on the machine where JRebel will be used in the IDE. ![]() This generates rebel-remote.xml, in src/main/resources directory again, and will look like:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |