I downloaded the latest Seam 2.0.1.GA release and I still have issues with
Authenticator method being invoked twice.
Based on the solution here, the authenticate() method is invoked with
isLoggedIn(false), but then when there is a navigation rule like this
|
|
|
please refer to
[url]
http://jira.jboss.com/jira/secure/ReleaseNote.jspa?version=12311437&styleName=Html&projectId=10071&Create=Create
[/url]
anonymous wrote :
| * [JBSEAM-2165] - Authenticator method invoked twice when login fails
|
View the original post :
http://www.jboss.com/inde
Hi,
I downloaded Seam 2.0.1 CR1 to test the Authenticator method being called twice
when the login method returns false and it looks like this issue is still
there.
Could anyone please provide some insight.
Thanks !
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewt
Thanks for the replies,
I finally got that ruleset working by configuring
|
|
|
|
|
|
|
Is there any drawback in implementing it this way.
Thanks !
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114734#4114734
R
Sorry my mistake. I read it as 2.0.0.CR1.
Thanks !
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113599#4113599
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113599
___
jbo
Isn't this referring to
http://jira.jboss.org/jira/browse/JBSEAM-2165
and it says it is fixed in CVS. Is it out in 2.0.0.GA? I am still having this
issue in 2.0.0.GA.
Could anyone please clarify.
Thanks !
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113
Thank you for the answers.
anonymous wrote :
| Not yet implemented. This is the best way to do what you are AFAICS.
|
Does this mean that there are plans for adding this to future release?
anonymous wrote :
| Null in JSF means stay on the same page.
|
But I am getting the page naviga
Hello !
| 1. Is there a way we can map identity.loggedIn to a method to keep checking
against some criteria. For eg: If I want to redirect the user to login page
when the session expires, can I configure identity.loggedIn =
loginBean.sessionExpired.
|
| 2. Or, I found in the forum that
On further research I found this.
http://jira.jboss.org/jira/browse/JBSEAM-2165
It has been fixed in the new release.
Thanks !!!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111045#4111045
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=
I think I put it the wrong way.
What I meant to say is i have mapped
|
|
and the loginBean.login method is something like
| public boolean login(){
| boolean succeeded = loginAction.login();
| return succeeded;
| }
|
so this method is called twice when succeeded = fals
Thanks Shane.
I see one more behavior
When i provide the wrong username or password, my configured login method is
being called twice. On debugging I see that the method authenticate of Identity
class
| public void authenticate()
| throws LoginException
|{
| // If we'r
Thanks, it worked. I had another question too...
I am configuring my identity.login to loginBean.login and my loginBean class is
like
| import org.jboss.seam.annotations.In;
| import org.jboss.seam.annotations.Name;
|
| @Name("loginBean")
| public class LoginBean {
|
| @In
Is there a way to map identity.logout to some component method if there is
something to be done while logging out.
Just as we map identity.login="authenticator.authenticate", can we map
identity.logout="authenticator.logout" also? Or overriding identity.logout?
Thanks in Advance !
View the orig
Thank you for the briefing... it really helped.
Is it possible to annotate just the super interface and its concrete
implementations will be intercepted. (I dont want to annotate all my classes
for logging interception)
|
| Is there any drawbacks in using this kind of interception for logg
Thank you Jacob for the solution.
I tired implementing the method-level annotation as explained in your blog. It
totally works.
But still it needs to be configured from the component perspective.
I dont have EJB's in my application. So using the EJB interceptor for
configuring the pattern ma
Hi Jacob,
Thanks for the reply. I tried it that way and it worked.
I had few doubts too.
1. Is there a way to intercept just the methods and not the class.
2. Is there any way to collectively configure a set of classes or pattern in
the interceptor as we do with Spring. (So that we dont have to
I am working on a Seam project with Facelets and Spring on Tomcat. Enviroment
is Seam 2.0.0.CR2, Tomcat 6.0.10, Facelets 1.2, Spring 2.0.
Could anyone please tell me if there is a way to do intercepting on Seam
components using AspectJ just as we do with Spring beans? Is there a way to
create
My Environment now is
Seam : 2.0.0.CR2
Woodstock : 4.1
JSF : 1.2
Java : 5.0
Tomcat : 6.0.10
These are the files that I have
Employee.java
| package test.injection;
|
| import java.io.Serializable;
|
| import org.jboss.seam.ScopeType;
| import org.jboss.seam.annotations.In;
| imp
Seems like this should be of high priority. I have an application with
Woodstock + Seam +Spring in the stack. I get any 2 of these working together
but not the 3.
For example: I have a seam bean having Spring bean injected into it. When i try
to set any input field into this Seam bean, it is no
This issue is resolved. I didn't have jboss-seam-ioc.jar file in my classpath
(not mentioned in the document). Here is the resolution.
Seam-Spring integration :- Spring framework integration module of Seam requires
the jboss-seam-ioc.jar file to be in the classpath. The Spring bean injection
wo
Seam : 1.2.1
JDK : 5
Woodstock : 4.1
Server : Tomcat 6.0.10
I just had the seam built-in component "conversationList" in one of my pages
and accessing the page throws UnsupportedOperationException. When i remove the
Woodstock jar files from the classpath,
Could anyone please reply to this thread. Seam-Woodstock stack issue!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097260#4097260
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097260
_
I am using Woodstock component library and its because of the Woodstock
UIComponentELResolver, that the seam built-in components are not working.
Is there any way this can be resolved so that we can use Woodstock and Seam
together?
Thanks !
View the original post :
http://www.jboss.com/index
I found that Seam built-in components wont work if you have Woodstock libraries
in your classpath.
I tried removing the Woodstock libraries and everything works fine.
These are the jar files that i have
1. dataprovider.jar
| 2. dojo-0.4.3-ajax.jar
| 3. json.jar
| 4. prototype-1.5.0.jar
Sure, I will send over my project environment to you.
Thanks...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096756#4096756
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096756
___
Yes it is.
I am getting all my components installed on running the test case. And the test
case works for components testing also. Its just the Spring bean is not
resolved. ELResolver throws the exception.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=40966
Seam version is 1.2.1 and JSF version is 1.2.
I am getting UnsupportedOperationException while accessing several built-in
Seam components.
1. conversationList
2. localeSelector
3. messages
Any ideas would be really helpful.
Thanks.
View the original post :
http://www.jboss.com/index.html?modu
ok, so maybe that ELResolver is not resolving the Spring bean names.
I was trying to test a user interaction scenario, trying to set the bean values
and add it to the DB. But the injection is not working as the ELResolver cannot
resolve the Spring bean identifiers. Totally stuck at this point. :
I am getting the same exception when i try to access "localeSelector" or
"org.jboss.seam.core.localeSelector" in my pages. Could anyone please reply.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096266#4096266
Reply to the post :
http://www.jboss.com/index
Could it be possible that the DelegatingVariableResolver is not getting loaded?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096264#4096264
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096264
___
Could anyone please reply with some ideas as to why this exception is
happening.
The Spring beans are not resolved in integration testing when invoked through
EL. I have the DelegatingVariableResolver in place.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=
I tried to see if the Spring Bean is resolved.
|
| package test.testNG;
|
| import org.jboss.seam.mock.SeamTest;
| import org.testng.annotations.Test;
|
| public class InjectionTestNG extends SeamTest{
|
| @Test
| public void testInjection() throws Exception {
Here it is
| http://jboss.com/products/seam/components";
| xmlns:core="http://jboss.com/products/seam/core";
| xmlns:web="http://jboss.com/products/seam/web";
| xmlns:spring="http://jboss.com/products/seam/spring";
| xmlns:xsi="http://www.w
These are the classes that I have
Employee.java
| package test.injection;
|
| import org.jboss.seam.ScopeType;
| import org.jboss.seam.annotations.In;
| import org.jboss.seam.annotations.Name;
| import org.jboss.seam.annotations.Scope;
|
| @Name("employeeBean")
| @Scope(Scope
Frankly speaking I tried to upgrade to 2.0 CR1 and had to struggle with lots of
issues. I couldn't even get a lrc working. So i reverted back to 1.2.1.
And I have been facing issues with EL in 1.2.1
| 1. Not getting the #{conversationList} component.
| 2. Not getting the #{localeSelector} com
Seam 1.2.1 with Tomcat 6.0.10.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095818#4095818
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095818
___
jboss-user mailing list
1. Yes my application works fine in a web container.
2. Yes, I removed the ContextLoaderListener from web.xml.
3. Yes, I have the @In (value="#searchService") specified in the searchBean.
But no required=false.
Is there any other configuration required?
One more thing i found is this is not just
My Seam application has Spring beans injected into some of the components. When
i try to do an integration testing, I get this exception
| Error writing 'searchTerm' on type
com.test.seam.ui.backing.SearchBean_$$_javassist_0
| at javax.el.BeanELResolver.setValue(BeanELResolver.java:112)
On debugging I found that, when #{conversationEntries} is called the key coming
in to Namespace.getChild(String key) is "conversationEntries" but for
#{conversationList} , the key is always "org" and this is throwing the
UnSupportedOperationException. Can anyone please help me with this??? Any h
I am using Seam 1.2.1 with Tomcat 6.0.10, JSF 1.2, Facelets 1.1.12.
But then how #{conversationEntries} in conversations.xhtml doesn't throw this
exception.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090394#4090394
Reply to the post :
http://www.jboss.c
I am using Seam 1.2.1 with Tomcat 6.0.10, JSF 1.2, Facelets 1.1.12.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090392#4090392
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090392
___
Could anyone please help me with this situation. Why am i getting this
exception? conversationList being empty is understandable but this exception, i
cannot figure out what is happening here.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090374#4090374
Rep
This is the conversations.xhtml page
| http://www.w3.org/1999/xhtml";
| xmlns:c="http://java.sun.com/jstl/core";
| xmlns:ui="http://java.sun.com/jsf/facelets";
| xmlns:f="http://java.sun.com/jsf/core";
| xmlns:h="http://java.sun.com/jsf/html";
| xmlns:s="http:/
I tried printing the conversationEntries
| ConversationEntries convEntries = ConversationEntries.instance();
| Collection entryCollection =
convEntries.getConversationEntries();
| if(!entryCollection.isEmpty()){
| System.out.println("--Conversation Entries
Desc--
I am facing a similar problem. I can see the conversationEntries displayed
properly with the descriptions, when i print them in the console.
But, I am getting an UnsupportedOperationException when I include
#{conversationList} or #{org.jboss.seam.core.conversationList} in my page.
Could anyone
I was trying to implement a simple non-EJB appliaction using Seam and JSF.
Multiple conversation is working fine for me. But, when i try to check for the
workspace management, I am getting unsupportedOperationException at
conversationList variable.
I have the view-ids and descriptions inside my
46 matches
Mail list logo
