"dlmiles" wrote : Hi Max thanks for the reply. | | Okay this is what I can tell you about things: | | I have an "EAR Project" called "EAREclipseManager", this has 2 artifacts added to it. These are 1 x "J2EE Utility project" called "TheLibrary" and 1 x "EJB Project" called "TheEJB". | | If I do a project properties on the "EAR Project" under "J2EE Dependancies" I has a tick for both of the other two projects set. The EAR Project has the Project Facet "EAR" set to "5.0", Project References also has a tick for both of the other two projects set, Seam Support is disabled (no tick in box), Targetted Runtime is : JBoss AS 4.2. | | Is is the encapsulating EAR project I am trying to publish. I don't think I need to do anything special with the project settings of the 2 contributing projects do I ? | I haven't had time to reproduce your scenario, but if WTP default adapters does not work with it then something else is missing. Check out the prjoects beta4 of jbosstools (announcing later today, but already available for download) generates for Seam EAR ...it is just using normal WTP funcitonallity. anonymous wrote : | /opt/jboss-4.2.1.GA/server/default/deploy/EAREclipseManager.ear/ | | | Yes - that is where our WTP adapter would put things by default if your chosen configuration is the one named "default" and your project is called EAREclipseManager. anonymous wrote : | Hmm... when I run a "clean" function from the server tooling with the WTP provider driver I get an error: | | [jar] Building jar: $HOME/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp2/EAREclipseManager.ear | | [move] Moving 1 file to /opt/jboss-4.2.1.GA/server/default/deploy | | | | BUILD FAILED | | /opt/eclipse/plugins/org.eclipse.jst.server.generic.jboss_1.5.105.v200709061325/buildfiles/jboss323.xml:33: Failed to copy $HOME/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp2/EAREclipseManager.ear to /opt/jboss-4.2.1.GA/server/default/deploy/EAREclipseManager.ear due to /opt/jboss-4.2.1.GA/server/default/deploy/EAREclipseManager.ear (Is a directory) | Yes - apparently default WTP adapter does not check if the project is already deployed (and possibly exploded) anonymous wrote : | * Which method of deployment does JBossTool-AS use, does it create an exploded EAR ? | Yes - that is the most efficient way of deploying/developing so that is what we do by default. anonymous wrote : | When it created that exploded EAR does it create a directory with a ".ear" extension in the deploy directory ? | Yes. anonymous wrote : | Does an exploded EAR need to have a .ear extension so its treated correctly by the correct deployer ? | that was at least the case when we starting doing the exploded development; that might have changed in JBoss 4.2, but I do not think so. anonymous wrote : | * Does it matter that my workspace and my JBoss runtime location are on different file system (different drives), since its not possible to rename files between my workspace and the JBoss runtime location. The IDE must perform a file copy. | I don't understand the question. Renames/Deletes/Creations in your workspace will automatically be reflected on to the deployment location incrementally. why should that be affected by them being on different drives ? anonymous wrote : | * When the files are copied are they copied atomically, i.e. each file is copied into tmp/filename.tmp first, then its last modified time is fixed to whatever it needs to be, then its renamed (i.e. moved) to the deploy/whatever/filename.foo. | As said earlier, we don't use any tmp location; it is copied from the original location to the deployment. The timestamp will be updated in that process too (if not it's a bug) anonymous wrote : | I cleaned things again and tried with the JBossTool-AS driver and it created a directory with .ear extension, the tree is just like I put in the CODE block above, with AREclipseManager.ear/TheLibrary.jar being the only file and the application.xml and the .class files are all missing. So the problem for me appears to be with the JBossTool-AS driver (which is my preferred choice). | please report a bug on this if this is how beta4 behaves (this is a bug that were present in beta3). I have tested the jbosstools as ear deployment extensively with our EAR structure (which is just WTP) and it works...so if you could attach a project to a jira that shows this error it would be great. anonymous wrote : | Would there be any call to allow JBoss to take a command line property to configure a 2nd and alternative deployment directory ? | The JBoss 4.2 runtime currently is fixed to the deploy dir in the configuration; there is an jira issue for allowing an alternate location. anonymous wrote : | The purpose of this would be to allow for a Tomcat like situation where the workspace area could be used for the deployment, when you just alter the driver to contribute the property to the launch configuration when it sets things up. Okay it would not be 100% compatible with tomcat since the work, tmp, log, etc.. directories would also need to be picked up based on the alternative path too. Just a thought, since it would seem difficult for "clean" to mean clean if the deploy directory was not empty to start with. there is also the option of using the "deploy only" runtime; where don't do anything but just maintaing a deployed directory. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092557#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...