[ http://jira.jboss.com/jira/browse/JBAS-1457?page=comments#action_12315423 ] Andrew Oliver commented on JBAS-1457: -------------------------------------
confirmed. Sorry about that. > Datasources require JAAS > ------------------------ > > Key: JBAS-1457 > URL: http://jira.jboss.com/jira/browse/JBAS-1457 > Project: JBoss Application Server > Type: Bug > Components: EJBs > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-3.2.6 Final > Reporter: Andrew Oliver > Priority: Minor > > > do this: > vi server/slim/jboss-service.xml > <!-- ==================================================================== > --> > <!-- Security > --> > <!-- ==================================================================== > --> > <!-- > <mbean code="org.jboss.security.plugins.SecurityConfig" > name="jboss.security:service=SecurityConfig"> > <attribute > name="LoginConfig">jboss.security:service=XMLLoginConfig</attribute> > </mbean> > <mbean code="org.jboss.security.auth.login.XMLLoginConfig" > name="jboss.security:service=XMLLoginConfig"> > <attribute name="ConfigResource">login-config.xml</attribute> > </mbean> > --> > <!-- JAAS security manager and realm mapping --> > <!-- <mbean code="org.jboss.security.plugins.JaasSecurityManagerService" > name="jboss.security:service=JaasSecurityManager"> > <attribute name="SecurityManagerClassName"> > org.jboss.security.plugins.JaasSecurityManager > </attribute> > <attribute name="DefaultCacheTimeout">1800</attribute> > <attribute name="DefaultCacheResolution">60</attribute> > </mbean> > --> > and this > vi server/slim/deploy/jbossweb-tomcat50.sar/META-INF/jboss-service.xml > <!-- The JAAS security domain to use in the absense of an explicit > security-domain specification in the war WEB-INF/jboss-web.xml > --> > <!-- <attribute > name="DefaultSecurityDomain">java:/jaas/other</attribute>--> > <!-- <depends optional-attribute-name="SecurityManagerService" > proxy-type="attribute">jboss.security:service=JaasSecurityManager > </depends>--> > you get this: > 17:51:23,961 ERROR [URLDeploymentScanner] Incomplete Deployment listing: > MBeans waiting for other MBeans: > ObjectName: jboss.jca:service=LocalTxCM,name=DefaultDS > state: CONFIGURED > I Depend On: jboss.jca:service=ManagedConnectionPool,name=DefaultDS > jboss.jca:service=CachedConnectionManager > jboss.security:service=JaasSecurityManager > jboss:service=TransactionManager > Depends On Me: > MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM: > ObjectName: jboss.security:service=JaasSecurityManager > state: NOTYETINSTALLED > I Depend On: > Depends On Me: jboss.jca:service=LocalTxCM,name=DefaultDS > even with the default hsql-db.xml. However if you remove the (incorrect?) > dependence on the CachedConnectionManager from the jboss-jca.rar's stylesheet > it still depends on JAAS. If you comment out the JAAS section (not sure why > the condition gets triggered anyhow since I have no domain specified) then > you get a NPE while it tried to look for JAAS. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
