[JBoss Seam] - Upgrading from 1.1.5 to 1.2
by nekstrom
Is there a list of what changes need to be made in the security configuration when upgrading from 1.1.5 to 1.2? I tried to just do a library upgrade using seam-gen but when I tried to use my Authenticator it threw an error saying that it couldn't find the function. The stack trace is:
anonymous wrote : 23:53:43,396 ERROR [SeamLoginModule] Error invoking login method
| javax.faces.el.EvaluationException: Exception while invoking expression #{authenticator.authenticate}
| at org.apache.myfaces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:165)
| at org.jboss.seam.actionparam.ActionParamBindingHelper.invokeTheExpression(ActionParamBindingHelper.java:58)
| at
| ...
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:619)
| Caused by: java.lang.NoSuchMethodException: edu.byu.cs.csl.dogma.server.Authenticator$$EnhancerByCGLIB$$f577284d.authenticate()
| at java.lang.Class.getMethod(Class.java:1605)
| at org.apache.myfaces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:118)
| ... 58 more
|
| I remember seeing that there were some API changes between 1.5 and 1.6 but I didn't have the time to figure them out and now I can't find what they are. Thanks for you help. Also thanks for a great system. Any idea of when WS will be integrated?
|
| --nathan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024098#4024098
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024098
18Â years, 9Â months
[JNDI/Naming/Network] - Re: JNDI Problem
by gopinathb4u
I am using Jboss 3.2.7. It is not working.
I got the below error while lookup. Help me to resolve.
|
| javax.naming.NameNotFoundException: Detects not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:490)
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:498)
| at org.jnp.server.NamingServer.getObject(NamingServer.java:504)
| at org.jnp.server.NamingServer.lookup(NamingServer.java:277)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:606)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:568)
| at javax.naming.InitialContext.lookup(InitialContext.java:351)
| at com.ingenix.itg.framework.util.JNDIUtils.lookup(JNDIUtils.java:79)
| at com.ingenix.itg.framework.dao.JNDISessionFactoryProvider.getSession(JNDISessionFactoryProvider.java:83)
| at com.ingenix.itg.framework.dao.JNDISessionFactoryProvider.getSession(JNDISessionFactoryProvider.java:58)
| at com.ingenix.itg.detects.lookup.dao.LookupDAOImpl._findAllClients(LookupDAOImpl.java:386)
| at com.ingenix.itg.detects.lookup.dao.LookupDAOImpl.findAllClients(LookupDAOImpl.java:367)
| at com.ingenix.itg.detects.lookup.LookupManagerImpl.findAllClients(LookupManagerImpl.java:190)
| at example1.Test2.setupClass(Test2.java:30)
| 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.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:645)
| at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:385)
| at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:141)
| at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:79)
| at org.testng.TestRunner.beforeRun(TestRunner.java:504)
| at org.testng.TestRunner.run(TestRunner.java:472)
| at org.testng.SuiteRunner.runTest(SuiteRunner.java:278)
| at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:273)
| at org.testng.SuiteRunner.privateRun(SuiteRunner.java:253)
| at org.testng.SuiteRunner.run(SuiteRunner.java:168)
| at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:987)
| at org.testng.TestNG.runSuitesLocally(TestNG.java:951)
| at org.testng.TestNG.run(TestNG.java:719)
| at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73)
| at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:122)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024089#4024089
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024089
18Â years, 9Â months
[Remoting] - Re: SSLHandshakeException when connecting to JNDI
by ron.sigalï¼ jboss.com
Hi,
The detectors will periodically ping the servers they know about to see if they are still alive. The ping is an actual invocation on the server, so, for sslsocket, there will be an SSL handshake, for which the client will need a truststore. Note the line
| 2007-02-27 14:59:52,273 WARN [main] org.jboss.remoting.ConnectionValidator: ConnectionValidator could not successfully ping server (InvokerLocator [sslsocket://localhost:1101/]
|
in the client log, which corresponds in time to the line
| 2007-02-27 14:59:52,273 ERROR [SocketServerInvoker#0-1101] org.jboss.remoting.transport.sslsocket.SSLSocketServerInvoker: Failed to accept socket connection
in the server log. That looks like a handshake failure. See the client SimpleSSLDetectorClient in org.jboss.remoting.samples.detection.jndi.ssl for an example of a detector in the presence of servers using an ssl transport. Note that the server, SimpleSSLDetectorServer, must be configured to use sslsocket with a system arg like -Dargs=sslsocket-1101.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024073#4024073
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024073
18Â years, 9Â months