[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1467) Fail to deploy EJB3 ear that uses a security-domain

Fri Sep 12 14:06:20 EDT 2008

    [ https://jira.jboss.org/jira/browse/EJBTHREE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12429405#action_12429405 ] 

Anil Saldhana commented on EJBTHREE-1467:
-----------------------------------------

It is not a question of security domain.  The question is ejb3 starts looking for a JBoss security manager by doing java:jaas/sometthing.  But the security bean that binds the java:jaas context is coming later in deployment. 

Something like: JBAS-5700

> 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