[JCA/JBoss] - Re: No suitable driver found for java:PostgresDS
by chewbacca
Hi Vicky,
AFAIK, since I have configured the DataSource using the postgres-ds.xml in the deploy dir of JBoss, it should not be needed for me to, once again, enter the connection information (like driver, url, user and password). I should only need to refer to it using its JNDI name.
And you can be sure I googled it more than a handful of times. AAMOF, I even found the answers, but they are just not working. That is why i'm posting here.
Anyway, thanks a lot, again, for your help.
Andre
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107783#4107783
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4107783
18 years, 5 months
[JBoss Seam] - Re: Why is Authenticator.authenticate() called twice if it r
by Toby451
The call stacks differ in the following ways!
First call to login-method:
| ...
| at org.jboss.seam.security.Identity.quietLogin(Identity.java:265)
| at org.jboss.seam.security.Identity.isLoggedIn(Identity.java:182)
| at org.jboss.seam.security.Identity.isLoggedIn(Identity.java:172)
| at sun.reflect.GeneratedMethodAccessor748.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
| at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
| at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
| at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31)
| at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
| at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42)
| at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
| at org.jboss.seam.core.SynchronizationInterceptor.aroundInvoke(SynchronizationInterceptor.java:32)
| at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
| at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106)
| at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:155)
| at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:91)
| at se.reco.security.RecoIdentity_$$_javassist_4.isLoggedIn(RecoIdentity_$$_javassist_4.java)
| ...
|
Second call to same method:
| ...
| at org.jboss.seam.security.Identity.login(Identity.java:237)
| 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.seam.util.Reflections.invoke(Reflections.java:21)
| at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
| at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
| at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31)
| at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
| at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42)
| at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
| at org.jboss.seam.core.SynchronizationInterceptor.aroundInvoke(SynchronizationInterceptor.java:32)
| at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
| at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106)
| at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:155)
| at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:91)
| at se.reco.security.RecoIdentity_$$_javassist_4.login(RecoIdentity_$$_javassist_4.java)
| ...
|
Seems the isLoggedIn (a deceiving name) is quietly trying to login further down (up in the listing) the stack.
Maybe a bug? Or is it a requirement to write side-effect free authenticate-methods on rejected logins?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107776#4107776
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4107776
18 years, 5 months
[JBoss Portal] - GWT and JBoss customized login module
by jdsignature
Here is my problem, Can you give me some suggestions on what I am
doing wrong.
1. the form based authentication implemented in the GWT application,
the login form is a simple login form to collect the user name ,
passowrd;
2. The real authentication handled in the JBoss container by
customized login module;
3. The user logged out the application,then the session.invalidate();
4. The user attempted to revisit the GWT application to perform a
search after log out: What I am expecting is that the login page
should be repopulated and re-authenticate user, however, the GWT
either continue to allow the user to revisit the application or send
out the content of the HTML to the screen when the session closed.
What I am doing wrong here, per your point The GWT only sent back the
Object, so how GWT redirect the user to the login page?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107775#4107775
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4107775
18 years, 5 months