That it works on JBoss AS 4.2.2.GA and not on EAP 4.3 is also odd.
On 21 May 2008, at 21:26, Max Rydahl Andersen wrote:
Hi,
http://jira.jboss.com/jira/browse/JBIDE-2190 is one of those things
you just don't want to see before going GA.
We had QA reporting that they could not deploy and run an Ear
application since it would throw an "no application context"
exception.
I could not reproduce it and rejected it a couple of times - until
they kept saying new builds did not help etc. etc.
It turns out I can reproduce it, but *only* if the deployment starts
with a captial letter(!)
SeamEear breaks seamEar works. MyApp breaks myApp works.
You can "fix" it by removing jboss-seam.jar from the MANIFEST.MF but
that makes zero sense since that is actually required/legal by spec
since that is what defines the classpath.
Pete thinks it is something inside jbossAS that is causing this, but
what I don't understand is why it works fine with Seam 1.2, but
fails on Seam 2.0.1 and Seam 2.0.2.
Is there anyone who has an idea why seam suddenly starts failing
because the first letter is a captial letter ?
(note: all references inside descriptors is the exact same casing)
/max
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev