[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4156:
------------------------------------
I've added a delete call to the SingleFilePublisher, which should hopefully fix the
constant redeployment of the xml file.
As for the JST publisher i'll be looking into what's going on but again, I lack a
windows box to do this with. In case you're curious, the JSTPublisher also uses a file
PublishCopyUtil, which was originally a WTP class that was "liberated". If you
look at this class you'll see it's pretty much crafted to try to get around the
sun bug, constantly attempting to delete the file before doing the renameTo.
I can also try to look where I can improve the error reporting for JSTPublisher.
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
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