[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction

[ https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu... ] Bernhard Hablesreiter commented on JBIDE-4156: ---------------------------------------------- Ok, now we have more information. Forgive me, but I've never used the Server Log View before. To answer your first question, the "testapp-ear" module switches to "Synchronized" after a full-publish, but the "testapp-ds.xml" remains in "Republish" state (see below). The publishing of a single xhtml-file shows 2 log-entries: - The module cannot be published - 1 files modified in module testapp The auto-publish seems to recognize the "testapp-ds.xml" as changed an copies it over to the "jbosstoolsTemp" directory. However, it remains there and cannot be copied over to the deploy directory (which probably causes this module to stay in "Republish" state - ?). The server-log shows the following stack-trace: java.lang.Exception: Move from C:\jboss\jboss-4.2.2.GA\server\default\tmp\jbosstoolsTemp\testapp-ds.xml to C:\jboss\jboss-4.2.2.GA\server\default\deploy\testapp-ds.xml failed. at org.jboss.ide.eclipse.as.core.publishers.SingleFilePublisher.publish(SingleFilePublisher.java:79) at org.jboss.ide.eclipse.as.core.publishers.SingleFilePublisher.publishModule(SingleFilePublisher.java:56) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:86) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:947) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1037) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:871) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:707) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2492) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:270) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) This happens everytime (!) I safe a file in eclipse, which explains the rebuilding of the persistence-unit I guess. The same error appears when using the .metadata-deploy directory... The full-publishing shows 6 log-entries: - The module cannot be published (same error and stacktrace as above) - Full Publish Failed for module testapp-ear (no stacktrace) - 8 files modified in module testapp-ejb - Full Publish Failed for module testapp (no stacktrace) - 1 files modified in module lib/testapp-ear/EarContent/jboss-seam.jar - 1 files modified in module lib/testapp-ear/EarContent/mvel14.jar So the log-entries show the failure of the full-publishing. Unfortunately I don't get any stack-trace or detailed error information. Is there any other place to look for detailed error-information? -- 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