2.0 GA tools bug on eclipse with jboss 4.2.2 : error add/rem

[wiggy]

I have jboss tools 2.0 GA installed ontop of callisto.



I create a valide EAR project and deploy to jboss AS - it all works okay and EJB intalls/can be called.

The server adapter puts exploded EAR file format into the deploy directory as required (the EAR file isnt copied - the directory structure itself is written in exploded format).


When i come to remove the EAR from the server - i get an error from the action to the effect that their is no META-INF/application.xml

16:39:06,542 ERROR [MainDeployer] Could not initialise deployment: file:/E:/jboss/jboss-4.2.2.GA/server/default/deploy/CustSiteEar.ear/
org.jboss.deployment.DeploymentException: No META-INF/application.xml found
at org.jboss.deployment.EARDeployer.init(EARDeployer.java:146)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)

If you look in the directory with explorer - the remove action has removed all the subdirectories including META-INF. It just leaves the .jar files top level in the EAR.

heres the error in the eclipse log.

!SUBENTRY 1 org.jboss.ide.eclipse.as.core 2 0 2008-01-27 16:39:03.918
!MESSAGE Unable to delete module from server. (CustSiteEar/CustSiteEAOProjectClient)
!STACK 0
java.lang.Exception: Some files were not removed from the server
at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.unpublish(JstPublisher.java:172)
at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.publishModule(JstPublisher.java:105)
at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:130)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:749)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:835)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:669)
at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887)
at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874)
at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:72)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

why cant it do this correctly - i can still add again and it will work - but the remove + error is somewhat annoying

[maxandersen]

the problem is that the classloader is still holding on the jar and thus under windows you will get such errors.

we are working on getting jboss to actually undeploy the app before we start removing the files - that should avoid this windows only issue.

[wiggy]

thanks mark

is that at next point release or next major release? At present I havent moved onto jboss as 5, as server support is limited to basic server.

is jboss tools next release to include jboss 5 as well as 4.2. Cant remeber seeing a timetable/roadmap for tools

[rob.stryker]

the fix is targeted to 2.1.0. The next release is 2.0.1, so it will not be in our very next release, but rather the one after that.

Hope that helps =]

For now, a workaround (crappy, I know) is to shut down the server, republish (clicking the publish icon), and restarting it. But, that kinda defeats the purpose of incremental deployment in the first place ;)

It's being worked on. I promise =D