[seam-dev] Really *weird* problem in Seam 2.x

Max Rydahl Andersen max.andersen at redhat.com
Wed May 21 16:26:30 EDT 2008


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




More information about the seam-dev mailing list