[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4156:
------------------------------------
If you right-click on your server and select show in -> server log, you should see more
fine-grained deployment information.
The only reason the persistence unit would be republishing all the time is if someone or
something is touching it. The tools deployment checks timestamps to see if it should copy
a file over. Even if auto-publish is called every single second, if there's been no
change to the file, it should not be being touched (and thus not being republished). In
the server's view, what does it say next to the persistence unit module?
"synchronized" ? or "resync"
Unfortunately I don't have a windows vista machine to test this on. A full publish
deletes the entire deployment (yes physically deletes it) and then recopies each file
over. IMO it'd be very hard to see how the timestamp WOULDNT change unless the file
was never deleted.
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