[
https://jira.jboss.org/jira/browse/EJBTHREE-1467?page=com.atlassian.jira....
]
jaikiran pai commented on EJBTHREE-1467:
----------------------------------------
Stefan,
The EAR attached in EJBTHREE-1485 fails consistently on a clean JBoss-5 CR1.
16:31:39,046 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.CR1 (build:
SVNTag=JBoss_5_0_0_CR1 date=200806301254)
Not sure if anything has changed on your CR1 setup. Let me know if you need more details
to reproduce this.
P.S: This comment was not meant to sidetrack Anil's comment dated 12/Sep/08 02:04 PM
Fail to deploy EJB3 ear that uses a security-domain
---------------------------------------------------
Key: EJBTHREE-1467
URL:
https://jira.jboss.org/jira/browse/EJBTHREE-1467
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: Ubuntu Linux, i386.
Sun Java 1.6.0_06
Reporter: Luis Fernando Planella Gonzalez
Assignee: Stefan Guilhen
When starting the JBoss server with a deployed ear which has on the jboss-app.xml a
security-domain, I always have an error on deploy, with a NameNotFoundException: jaas is
not bound.
However, when re-deploying the same ear after the server is initialized, the deploy runs
fine.
My guess is that for some reason the ejb deployer service is being run before the
security service...
The same ear can be deployed on JBoss 4.2.2 without problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira