[jboss-dev-forums] [JBoss Microcontainer Development POJO Server] - Re: Seam deployments and hot deployments in AS 5.1.0

[jeff.haynes@q9.com]

I was experiencing the same problem as described in this thread, but I think there's a pretty simple workaround that I'm now using (until the 5.2 comes out with the new deployers code).  I'm also deploying my exploded war file using Eclipse and was seeing the *.jsfdia and *.spdia files being deployed to my WEB-INF directory along with everything else.  

The simple workaround?  Just put an exclude directive in your build.xml to make sure the *.jsfdia and *.spdia files are not being deployed with your exploded application.  I'm using an Eclipse project that I set up using seamgen, but for anyone else using something different, I'm sure you can use a similar approach.

Here's the appropriate portion of my build.xml file:


  | <target name="war" depends="compile"
  |         description="Build the WAR structure in a staging directory">
  | 
  |         . . .
  | 
  |         <copy todir="${war.dir}/WEB-INF">
  |             <fileset dir="${basedir}/resources/WEB-INF">
  |                 <include name="*.*"/>
  |             	<exclude name="*.*dia"/>
  |                 <include name="classes/**/*.*"/>
  |                 <exclude name="classes/**/*.class"/>
  |             </fileset>
  |         </copy>
  | 
  |         . . .
  | 
  | </target>
  | 



My environment:

jdk1.6.0_16
Eclipse 3.4.2
JBoss AS 5.1.0.GA
Seam 2.2.0.GA
RichFaces 3.3.1.GA




View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257985#4257985

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257985