[
https://jira.jboss.org/jira/browse/JBIDE-4608?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4608:
------------------------------------
Interesting. Because you're using all JEE code (as opposed to J2EE) you have no
descriptors. The way we used to ensure restart of a module was by touching the
descriptors. Since there aren't any, this isn't happening. Simply changing byte
code does not tell the jboss AS to re-scan the folder for changes (no hot-deploy there on
a runtime level so nothing the tooling can do).
This is being tested on the JBoss 5.0.x stream. JBoss 5.0.x does *not* have JMX suspend /
resume deployment scanner, so that's not an issue here and cannot be complicating the
matter. As you mentioned, doing a full publish does not cause the runtime to republish.
Not only has the changed class been modified (which should not honestly restart the app on
the server), but the entire ear folder was removed and a new one coppied in with a new
timestamp.
[rob@localhost deploy]$ ls -l | grep "clear"
drwxrwxr-x 3 rob rob 4096 2009-07-14 14:06 clear-ear.ear
:: perform full publish inside eclipse ::
[rob@localhost deploy]$ ls -l | grep "clear"
drwxrwxr-x 3 rob rob 4096 2009-07-14 14:09 clear-ear.ear
So the timestamp of both the folder and all files changes, but the underlying JBoss AS
runtime does not redeploy the application. I feel this is a problem with the runtime and
not hte tooling. For completeness, the file tree of this application is as follows:
[rob@localhost deploy]$ du -a clear-ear.ear/
8 clear-ear.ear/clear-ejb.jar/EJBRem.class
8 clear-ear.ear/clear-ejb.jar/EJB01.class
8 clear-ear.ear/clear-ejb.jar/META-INF/MANIFEST.MF
16 clear-ear.ear/clear-ejb.jar/META-INF
8 clear-ear.ear/clear-ejb.jar/jndi.properties
8 clear-ear.ear/clear-ejb.jar/EJBTest.class
56 clear-ear.ear/clear-ejb.jar
64 clear-ear.ear/
Effectively, the entire clear-ear.ear folder is removed and a new one put in its place
with a new timestamp, however possibly very quickly. It seems the deployment scanner does
not recognize this redeployment.
Hot deployment woks incorrectly with JBossAS Tools
--------------------------------------------------
Key: JBIDE-4608
URL:
https://jira.jboss.org/jira/browse/JBIDE-4608
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.1.GA
Environment: Windows XP SP3
Eclipse 3.5: eclipse-jee-galileo-win32.zip
JBossTools : 3.0.1.GA JBossTools-ALL-win32-3.0.1.GA-R200905070146-H18.zip
JBoss AS: 5.0.1.GA
Reporter: Alexander Lengson
Assignee: Rob Stryker
Fix For: 3.0.2.GA
Attachments: clear-prj.zip
Original Estimate: 3 days
Remaining Estimate: 3 days
Hot deployment does not work as expected with the above configuration.
* Two eclipse projects are created: one EJB Project containing single EJB, and one EAR
project containing that EJB.
* EAR Project is deployed to JBoss thru JBoss Server View.
* JBoss started and recognized EJB:
clear-ear/EJB01/remote - EJB3.x Default Remote Business Interface
clear-ear/EJB01/remote-EJBRem - EJB3.x Remote Business Interface
* When source code of EJB is changed, it is recompiled and "Republish" note
appeared
* After pressing "Full publish" code is actually copied to the deploy folder on
the server (byte code is verified manually), but JBoss does not detect hot deployment and
does not redeploy EJB
When trying to make deployment thru Project Archives View on the same configuration, the
following happening:
* Archives are created within eclipse project folder.
* After pressing "Publish to Server" in Project Archives View, item appears in
JBoss Server View, but archive is not copied into JBoss deploy folder and JBoss does not
detect that new EJB is deployed.
JBoss' properties are:
Use the JBoss deploy folder
Tested on two separate machines. Results are the same.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira