Found the solution. "jboss.security:name" became "jboss.security:service" from 3.0.0 to 3.0.3.
Thank you very much for posting your solution -- I wasted 3 hours this morning trying to migrate from a jboss 3.0.0 installation to a jboss 3.0.3 installation.
I can't tell you how much I hate these little changes that waste so much time.
Wouldn't it be possible to make newer releases of jboss backwards-compatible with deployments on earlier versions? I mean, most commercial applications are, aren't they? When you upgrade to a new version of Word or Oracle you can still work with the same stuff you worked with in the prior version.
Really great, Thax a lot