[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Rob Stryker resolved JBIDE-4156.
--------------------------------
Fix Version/s: (was: 3.0.2.GA)
Resolution: Done
I think I've figured it out. Not sure about windows, but for linux, this is the case,
and it makes sense if it applies to windows.
The application.xml file *is* coppied over new, but it's timestamp is not adjusted.
Here in linux that means the new file copy keeps the timestamp of the old file (?) which I
find a bit shocking but whatever.
Looking in my code, I copy all the files I can, logging errors, but do not stop copying
files even if there are errors. So it's not that a copy or delete error is blowing
everythign up... not directly.
Instead, it seems I'm returning without touching timestamps. I'll make a quick
patch and commit this to trunk.
Since I'm fairly confident this was the problem, I'm gonna resolve this issue and
let QA give it a whirl.
Let me know. =] (since I'm in China I'm not sure when the nightly builds run
exactly... so... you may have to wait a day or two)
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL:
https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Fix For: 3.1.0.M1
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
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