[alesj]

"jaikiran" wrote:

The only additional thing that he had to do other than just building the AS 5_x branch was to update the profile.xml to include the cacheFilter:

This code in MetaDataStructureModificationChecker

 /**
 * Check filters.
 */
 public void start()
 {
 if (cacheFilter == null)
 {
 if (filter instanceof StructureCacheFilter)
 cacheFilter = (StructureCacheFilter) filter;
 else
 log.warn("No cache filter specified, possible non match on leaves.");
 }
 else if (cacheFilter != filter)
 {
 // not the same instance
 log.debug("VFS filter and structure cache filter are not the same instance, possible compatibility issue?");
 }
 }

should take care of this.

[banzeletti]

Dear jboss gurus,
Building JBoss 5.1.0.GA with the MetaDataStructureModificationChecker from the 5_x branch and deployers_2.0.8.GA seems to work very nicely in order to solve this problem. I just wanted to say "thank you".
Kind regards
Bernhard

[jeff.haynes1]

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

[gaboo]

Hi,

I've just spent the day trying to figure this out. Not an easy task

Background : I have a Seam 2.1.2 application working well with JBossAS 4.2.3. For various reasons (one of them being up to date and working RESTEasy support), I'd like to upgrade to Seam 2.2.0 or later. This needs JBossAS 5.1.0.

So, after a few obvious fixes and adjustments, I have my application almost completely working, that is great.

But, I can't get the explode feature to work correctly. When I try workarounds mentioned on seamframework.org, I get the redeploy infinite loop. When I try to fix redeploy infinite loop, I get other deployment errors. I've tried many things advised here and there : there is always something wrong. I guess the main reason is that there is no central place that states step by step how to deal with this : reading the various topics and faqs you're never sure what you're supposed to change at the same time.

What I've not tried is building JBossAS 5.x branch : not found in svn anymore. There is Branch_5_x_BootstrapLegacyRemoval or Branch_5_x_JBM2. Is one of them suitable ?

I've not tried JBossAS 6.M3 release either. Is this suitable for an already existing seam application ? (started with the early versions of Seam).

It's sad seing how frustrating and complicated this is to get something working, whereas it was as simple as download and deploy before.

I'm willing to spend time testing, helping, building to make this work, please advise and thank you for your time and work !

[alesj]

I've not tried JBossAS 6.M3 release either. Is this suitable for an already existing seam application ? (started with the early versions of Seam).

Sure, try AS6_M3 or the trunk (to be tagged M4 tomorrow).