[Security & JAAS/JBoss] - Re: How to implement Federated SSO using our own custom logo
by njw
Ok... after several hours I think I've finally answered my own question
The two versions of the SSO package (source and binary-only) are DIFFERENT - the version of jboss-sso-tomcat5.jar in the binary download doesnt have PlainAutoSSOLogout.class but the version in the older, source does (as do the the versions in the Seam hotels and DVD demos).
I'm now using the version from the source download and have now gone past the stage of this classloader error.
The binary version is
JBoss Federated SSO - 1.0.0.Beta-Update 1 size 10 MB dated 12/7/06
|
| jar file - 01/11/2006 06:18 10,589 jboss-sso-tomcat5.jar
|
| jar contents
| META-INF/
| META-INF/MANIFEST.MF
| org/
| org/jboss/
| org/jboss/security/
| org/jboss/security/valve/
| org/jboss/security/valve/SSOAutoLogin.class
| org/jboss/security/valve/SSOAutoLogout.class
| org/jboss/security/valve/SSOSession.class
| org/jboss/security/valve/SSOTokenManager.class
|
and the source is
| JBoss Federated SSO - 1.0.0.Beta-Update 1 size 44 MB dated 11/20/06
|
| jar file - 21/11/2006 00:05 19,028 jboss-sso-tomcat5.jar
|
| jar contents
| META-INF/
| META-INF/MANIFEST.MF
| org/
| org/jboss/
| org/jboss/security/
| org/jboss/security/valve/
| org/jboss/security/valve/PlainSSOAutoLogin.class
| org/jboss/security/valve/PlainSSOAutoLogout.class
| org/jboss/security/valve/PlainSSOTokenManager.class
| org/jboss/security/valve/SSOAutoLogin.class
| org/jboss/security/valve/SSOAutoLogout.class
| org/jboss/security/valve/SSOSession.class
| org/jboss/security/valve/SSOTokenManager.class
|
Just to make things 'interesting', there are a number of differences in the two versions where it appears that the binary version is more up-to-date. e.g
from the binary download public LDAPIdentityProvider(String id, Properties properties)
| source download public LDAPIdentityProvider()
[rant mode]Ok, I know this is still in beta but it would be nice if the distributions were consistent with each other rather than me wasting hours of my time debugging them[/rant mode] :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992810#3992810
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992810
19 years, 4 months
[JBoss Seam] - Re: @Asynchronous / Dispatcher not bound
by m_hess
Hmmm.... OK. So maybe anybody else also experienced this errormessage?
| [17:24:37] [admin1] [ERROR] [...erceptors.ExceptionInterceptor:370 ] >> redirecting to debug page
| javax.ejb.EJBTransactionRolledbackException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.core.dispatcher
| at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:93)
| at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
| at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:201)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
| [...]
|
| Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.core.dispatcher
| at org.jboss.seam.Component.newInstance(Component.java:1724)
| at org.jboss.seam.Component.getInstance(Component.java:1627)
| at org.jboss.seam.Component.getInstance(Component.java:1594)
| at org.jboss.seam.Component.getInstance(Component.java:1573)
| at org.jboss.seam.Component.getInstance(Component.java:1568)
| at org.jboss.seam.core.Dispatcher.instance(Dispatcher.java:237)
| at org.jboss.seam.interceptors.AsynchronousInterceptor.invokeAsynchronouslyIfNecessary(AsynchronousInterceptor.java:24)
| 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)
| [...]
|
| Caused by: javax.naming.NameNotFoundException: Dispatcher not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
| at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
| at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:626)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:588)
| at javax.naming.InitialContext.lookup(InitialContext.java:351)
| at org.jboss.seam.Component.instantiateSessionBean(Component.java:1029)
| at org.jboss.seam.Component.instantiate(Component.java:1015)
| at org.jboss.seam.Component.newInstance(Component.java:1720)
| ... 170 more
| [...]
|
The Dispatcher components gets installed on startup:
| [16:55:06] [] [INFO ] [...org.jboss.seam.Component :245 ] >> Component: org.jboss.seam.core.dispatcher, scope: STATELESS, type: STATELESS_SESSION_BEAN, class: org.jboss.seam.core.Dispatcher, JNDI: Dispatcher/local
And we do have the local interface annotated (not the implementing classes method).
Any ideas or insights?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992809#3992809
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992809
19 years, 4 months