[EJB 3.0] - 5.0.0Beta1: ejb3-timer-service.xml with PostgreSQL fails
by Juergen.Zimmermann
In ejb3-timer-service.xml I made these changes:HSQLDBDelegate -> PostgreSQLDelegate
| qrtz_job_details: BINARY -> oid
| IS_VOLATILE VARCHAR(1) -> IS_VOLATILE boolean
| qrtz_triggers: BINARY -> oid
| IS_VOLATILE VARCHAR(1) -> IS_VOLATILE boolean
| qrtz_blob_triggers: BINARY -> oid
| qrtz_calendars: BINARY -> oid
| qrtz_fired_triggers: IS_VOLATILE VARCHAR(1) -> IS_VOLATILE boolean
| REQUESTS_RECOVERY VARCHAR(1) -> REQUESTS_RECOVERY boolean
When starting JBossAS I get this error message and stack trace although server/default/deploy/postgres-ds.xml defines DefaultDS:2006-12-21 18:22:27,853 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=jboss.ejb:persistencePolicy=database,service=EJBTimerService state=Create mode=Manual requiredState=Installed
| java.lang.IllegalStateException: Cannot find datasource meta data: jboss.jdbc:datasource=DefaultDS,service=metadata
| at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.init(GeneralPurposeDatabasePersistencePlugin.java:101)
| at org.jboss.ejb.txtimer.DatabasePersistencePolicy.startService(DatabasePersistencePolicy.java:92)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
| at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
| at org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
| at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:198)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:320)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190)
| at org.jboss.system.ServiceController.doChange(ServiceController.java:656)
| at org.jboss.system.ServiceController.start(ServiceController.java:431)
| at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:124)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:85)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:44)
| at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:53)
| at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
| at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:451)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
| at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
| at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
| at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
| at org.jboss.Main.boot(Main.java:210)
| at org.jboss.Main$1.run(Main.java:508)
| at java.lang.Thread.run(Thread.java:595)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995778#3995778
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995778
19 years, 4 months
[Security & JAAS/JBoss] - Re: SSO in JBoss 4.0.5
by sohil.shah＠jboss.com
anonymous wrote :
| 1. What are the limitations of this jBoss Federated SSO framework.
|
Currently, the integration point for the SSO Token Management functions is inside of Tomcat. Hence, currently Tomcat depedency is needed. JBoss ships with Tomcat out-of-the-box so, you should be ok on this.
anonymous wrote :
| 2. Does this support different apps in different domains.
|
Yes, the framework was designed with cross-domain integration from the ground up
anonymous wrote :
| 3. Any support for XACML (1.0, 2.0).
|
XACML is in the Authorization domain. SSO primarily is associated with the Authentication aspect of security. As such XACL is out of scope for SSO. But integration is possible.
Hence, if you have an Authorization framework based on XACML then, integration point for SSO would be to generate the Principal used by XACML to enforce Authorization decisions
anonymous wrote :
| 4. Can I get some reference implementations for federated SSO..other the one in the flash demo.
|
In its current form, the framework ships with the actual implementation of the two Seam apps that are featured in the flash demo.
It also has a test application that is used for testing scenarios during development
anonymous wrote :
| 5. Do we need a portal (customized or any product driven like Oracle portal, weblogic etc).
|
No. portal or any custom thirdparty product is not a requirement. The only requirement at this point is Tomcat
anonymous wrote :
| We have 5 applications using different login mechanisms like JAAS, Database etc running in different servers including jBoss, Tomcat, web logic.
|
| Can we use the beta Federated SSO beta for implementing SSO and SAML to support existing apps and also future apps..
|
Absolutely. Although I am not too familiar with WebLogic. As long as you run Tomcat you should be fine.
Also please refer here for more detailed documentation:
http://labs.jboss.com/portal/index.html?ctrl:cmd=render&ctrl:window=defau...
Thanks
Sohil
Project Lead, JBoss Federated SSO
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995774#3995774
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995774
19 years, 4 months
[JBoss Seam] - EL enhancement of parameters working?
by dandiodati
Hi was trying out the s:link tag and noticed that it did not support actionListener events(By the way will this be supported?) So I noticed that
you can pass parameters to methods since seam adds some enhancements to
EL. When trying it I end up getting a null parameter passed into my getAction method. Here is the code segment:
<c:forEach items="#{TopNavViewHelper.navBar}" var="item">
| <c:set var="navItemStyle" value=""/>
| <c:if test="#{item.name == TopNavViewHelper.selectedName}">
| <c:set var="navItemStyle" value="selected"/>
| </c:if>
|
| <li class="#{navItemStyle}" id="#{item.name}" >
| <s:link id="#{item.name}" title="#{item.descr}" action="#{TopNavViewHelper.getAction(item.name)}" actionListener="#{TopNavViewHelper.clicked}"><span>#{item.label}</span>
| </s:link>
| <div>
| <ul/>
| </div>
| </li>
| </c:forEach>
The item.name in the getAction method call ends up being null instead
of have the name of the item. Does this not work within forEach loops?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995767#3995767
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995767
19 years, 4 months