it may have been a type but do you mean
yeah ofcouse itz Manifest.mf.
The thing is I've just coppied the working version of the EAR file under jboss2.4 to jboss3. It is working under 2.4 and itz say the above mentioned exception with jboss3. The problem is tomcat was not able to see the classes. What am looking for is what is the additional change one has to incorporate while migrating from jboss2.4 to jboss3.0.
I am having the exact same problem.
It's been mentioned by myself and a few other
people here in the last month.
No solution or explanation yet.
I've put up an example, really to show how JBoss.NET is integrated, but it might also show what you're missing (*maybe the application.xml changes?), so have a look at this page:
Alternatively, go through the Quick Start guide on the Sourceforge files page at: