- This topic has 3 replies, 2 voices, and was last updated 19 years, 11 months ago by Scott Anderson.
-
AuthorPosts
-
james_a_woodsMemberHi
I am having a curious deployment problem with JBoss.
I have an EAR file containing a single WAR. I then have a number of dependant Java Projects.I have the MyEclipse deployment settings so that the EAR and WAR are deployed to JBoss as an exploded archive with the the dependant Java Projects packaged up as Jars in the Ear deployment.
This deploys fine. Then when I make changes to a java file in one of the Java Projects, the JBoss hot-deploy picks it up straight away. But if I restart JBoss, all the changes are lost to JBoss and it runs the code that I originally deployed. I must do a manual re-deploy for JBoss to start with the latest version of the code.
On a similar note, I have noticed that if I add or move XML or properties files, these are not automatically deployed, I must deploy them manually.
I will be out of town for the next week, so if you have further questions I will get back to you in the new year.
Otherwise I am very impressed with your product.
Happy Holidays
James– Windows 2000
– Eclipse 3.0.1 [200409161125]; Fresh installation
– MyEclipse 3.8.3 [200412061200-3.8.3]
– Other Plugins: Oxygen XML editor
– JBoss [Zion] 4.0.0 (build: CVSTag=JBoss_4_0_0 date=200409200418)
– Java VM: Java HotSpot(TM) Client VM 1.4.2_05-b04,Sun Microsystems Inc.
Scott AndersonParticipantJames,
The issues you’re describing about deploying Java code in dependent Java projects is a known problem in 3.8.3. When you make changes to a Java file, it is compiled and the new code is injected directly into the remote JBoss JVM. However, right now the modified class file is not being copied out to the server deployment location, so the changes are lost at restart. So, the workaround is to redeploy after server shutdown, as you’ve seen. We’ll certainly take care of this issue maintenance release or possibly in the first quick fix for 3.8.3 in a few weeks.
james_a_woodsMemberCool, thanks for that.
Scott AndersonParticipantNo problem. Sorry a workaround is needed in the short term, but we’ll get it fixed.
-
AuthorPosts