Exploded Deployment from MyEclipse (trid 5.5 and 6.0M1) don'

tony.herstell1 Jul 19, 2007 7:15 PM

FOUND IT! - I think!

VERY frustrating.

This is do with MyEclipse Exploded deployment (not what seam calls exploded deployment)

Using
MyEclipse -> Add and Remove Project Deployments

and chosing exploded deployment (which maps out an exploded archive in JBoss deploy area) does NOT WORK.

choosing .ear form of deployment (which creates and ear file and pops that into the JBoss deploy area) does work.

Using JBoss Seam 2 B1 and JBoss 4.2.1GA

What gave me the clue was that in desperation I cracked open a Seam 2 booking example (that did work when build with ant) and laid out all the same files into MyEclipse EAR, EJB and War projects and tried to run that...

Cross post JBoss AS and MyEclipse & ICEfaces forums.

1. Re: Exploded Deployment from MyEclipse (trid 5.5 and 6.0M1)

patrickr Aug 23, 2007 3:44 PM (in response to tony.herstell1)

Today I encountered the same EL linkage error. It turned out to be (partly) a myeclipse issue. When you add JSF / Facelets support the facelets libary is automatically added to your web project. Myeclipse will copy the jars of this library into your WEB-INF/lib directory on deployment. And guess what: It contains el-ri library...

So, just remove the MyEclipse Faclets library from your web project and redeploy.
Actions
2. Re: Exploded Deployment from MyEclipse (trid 5.5 and 6.0M1)

tony.herstell1 Aug 23, 2007 3:47 PM (in response to tony.herstell1)

Oh yes, I found that too.
Worth pointing out.
Get some weired errors with that don't you and hard to find now that MyEclipse hides the jars you are including better.

:)
Actions

Go to original post