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

[Bernhard Hablesreiter (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463080#action_12463080 ] 

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?

> 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