December 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-863) Remember-Me automatic authentication

by H T (JIRA)

Remember-Me automatic authentication ------------------------------------ Key: JBSEAM-863 URL: http://jira.jboss.com/jira/browse/JBSEAM-863 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: H T Fix For: 1.1.7.GA Extend the behaviour of Remember-Me to automatically authenticate the user after they have selected the "Remember Me" service rather than have him or her re-enter their password each time. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2039) selectManyListbox executePhase NullPointerException

by Przemyslaw Rudzki (JIRA)

selectManyListbox executePhase NullPointerException --------------------------------------------------- Key: JBSEAM-2039 URL: http://jira.jboss.com/jira/browse/JBSEAM-2039 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.1.GA Environment: JBoss AS 4.2.1GA, Sun Microsystems JavaServer Faces Implementation 1.2_04-b16-p02, Ubuntu 7.04 Reporter: Przemyslaw Rudzki Fix For: 1.2.1.GA I have simple model: class Book { @ManyToMany //unidirectional private List<DictionaryEntry> dictionaryEntryList; } In the JSF it is presented as: <h:selectManyListbox id="select2Status" value="#{bookHome.instance.dictionaryEntryList}" required="false"> <s:convertEntity /> <s:selectItems value="#{dictionaryEntryList.resultList}" var="item" label="#{item.value}" noSelectionLabel="---------" /> </h:selectManyListbox> 1. When I create entity with some elements selected everything works fine. 2. When I edit the selection and update everything works great. 3. The problem occurs when I deselect all the items and try to do an update. I get then: 00:46:49,840 WARN [lifecycle] executePhase(PROCESS_VALIDATIONS 3,com.sun.faces.context.FacesContextImpl@1625154) threw exception javax.faces.FacesException at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:108) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:307) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.NullPointerException at javax.faces.component.UISelectMany.matchValue(UISelectMany.java:496) at javax.faces.component.UISelectMany.validateValue(UISelectMany.java:454) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2226) Need Customer actionOutcome and actionMethod

by Danny Chen (JIRA)

Need Customer actionOutcome and actionMethod -------------------------------------------- Key: JBSEAM-2226 URL: http://jira.jboss.com/jira/browse/JBSEAM-2226 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.GA Reporter: Danny Chen For conversion id, JBoss Seam provide customize method, for example: <core:manager conversation-timeout="300000" conversation-id-parameter="cid" /> But for <s:link>, <s:button>'s actionOutcome and actionMethod, there isn't a way to change these id. I find it is hardcode in: UIAction: public String getName() { return isMethodBinding() ? "actionMethod" : "actionOutcome"; } Pages: private static boolean callAction(FacesContext facesContext) { //TODO: refactor with Pages.instance().callAction()!! boolean result = false; String outcome = facesContext.getExternalContext() .getRequestParameterMap().get("actionOutcome"); String fromAction = outcome; if (outcome==null) { String actionId = facesContext.getExternalContext() .getRequestParameterMap().get("actionMethod"); if (actionId!=null) { if ( !SafeActions.instance().isActionSafe(actionId) ) return result; String expression = SafeActions.toAction(actionId); result = true; MethodExpression actionExpression = Expressions.instance().createMethodExpression(expression); outcome = toString( actionExpression.invoke() ); fromAction = expression; handleOutcome(facesContext, outcome, fromAction); } } else { handleOutcome(facesContext, outcome, fromAction); } return result; } Can let us change them just like conversion id? Thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1491) Seam-managed persistence contexts and REQUIRES_NEW

by Gavin King (JIRA)

Seam-managed persistence contexts and REQUIRES_NEW -------------------------------------------------- Key: JBSEAM-1491 URL: http://jira.jboss.com/jira/browse/JBSEAM-1491 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.3.0.GA It's always wrong to try and propagate a PC across REQUIRES_NEW. But indeed that is exactly what Seam does with conversation scoped PCs. Of course, the correct thing to do is use @PersistenceContext in this case. But how many users know they are supposed to do this? Is there some way we can *detect* this problem? We should at the very least document it... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2270) Use jquery to support defaultAction on links

by Pete Muir (JIRA)

Use jquery to support defaultAction on links -------------------------------------------- Key: JBSEAM-2270 URL: http://jira.jboss.com/jira/browse/JBSEAM-2270 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.GA Reporter: Pete Muir Fix For: 2.0.x Consider using jquery, which supports simulating clicks on all elements, not just inputs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2225) Suppor for <action> inside a <rule> in pages.xml

by Adam Warski (JIRA)

Suppor for <action> inside a <rule> in pages.xml ------------------------------------------------ Key: JBSEAM-2225 URL: http://jira.jboss.com/jira/browse/JBSEAM-2225 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.GA Reporter: Adam Warski Sometimes (for example in my use case) it would be handy if there was a possibility to have a <action> inside a <rule> in pages.xml. Right now, a similar effect can be achieved, as you can fire an event from a rule - however just creating and defining an event in components.xml to simulate an action-in-rule seems unnecessary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1289) Conversation Propagation andTrinidad Dialogs

by Brian Smith (JIRA)

Conversation Propagation andTrinidad Dialogs -------------------------------------------- Key: JBSEAM-1289 URL: http://jira.jboss.com/jira/browse/JBSEAM-1289 Project: JBoss Seam Issue Type: Feature Request Environment: JBoss 4.0.4GA Reporter: Brian Smith Seam does not automatically support Trinidad's dialog feature in terms of propagating long running conversations to the dialog window. Forum User dajevtic has provided a custom phase listener and action listener to enable propagation but it requires a specific naming convention for the dialog page. It would be nice to enable support directly using standard Seam notation like the s:conversationPropagation tag or @Begin(join = true) Here are the relevant phase listener and action listener *Phase Listener* private static final String CONVERSATION_ID_SESSION_PARAMETER = "conversationId"; private Map createParameterMapForConversationRestore(String conversationId) { Map paramterMap = new Hashtable(); paramterMap.put(CONVERSATION_ID_SESSION_PARAMETER, conversationId); return paramterMap; } private void restoreConversation(Context context) { if (context.isSet(CONVERSATION_ID_SESSION_PARAMETER)) { String convId = context.get(CONVERSATION_ID_SESSION_PARAMETER).toString(); Manager.instance().restoreConversation(createParameterMapForConversationRestore(convId)); context.remove(CONVERSATION_ID_SESSION_PARAMETER); } } public void afterPhase(PhaseEvent event) { try { if (event.getPhaseId().equals(PhaseId.RESTORE_VIEW)) { UIViewRoot root = event.getFacesContext().getViewRoot(); if (root != null) { String viewId = root.getViewId(); if ((viewId != null) && viewId.endsWith("_dlg.jspx")) { restoreConversation(Contexts.getSessionContext()); } } } else { log.info("after " + event.getPhaseId()); } } catch (Exception e) { log.error("Could not restore Seam conversation", e); } } *Action Listener* public void processAction(ActionEvent actionEvent) throws AbortProcessingException { if (actionEvent.getComponent() instanceof CoreCommandLink) { CoreCommandLink link = (CoreCommandLink)actionEvent.getComponent(); if (link.isUseWindow()) { Contexts.getSessionContext().set("conversationId", Manager.instance().getCurrentConversationId()); } } super.processAction(actionEvent); } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

6
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1643) Complain when user tries to define the same view-id twice in pages.xml

by Matt Drees (JIRA)

Complain when user tries to define the same view-id twice in pages.xml ---------------------------------------------------------------------- Key: JBSEAM-1643 URL: http://jira.jboss.com/jira/browse/JBSEAM-1643 Project: JBoss Seam Issue Type: Feature Request Reporter: Matt Drees Priority: Minor Fix For: 2.0.0.CR1 If you define two page elements with the same view-id in pages.xml, Seam doesn't complain at all. This can be confusing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

6
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml

by Pete Muir (JIRA)

Hotdeployed components can't be configured through components.xml ----------------------------------------------------------------- Key: JBSEAM-2143 URL: http://jira.jboss.com/jira/browse/JBSEAM-2143 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Priority: Critical Fix For: 2.0.1.GA he hot deployment scanner is isolated, using a URLClassloader that is not available once that method comes to a close. The only way to make this work would be to keep that classloader alive during the rest of the startup process. I can direct you to the line of code that you need to look at if you are curious about it. Check out lines 540 and 541 or org.jboss.seam.init.Initialiation. The scanForHotDeployableComponents uses the following logic to create a component scanner: URL[] urls = { url }; classLoader = new URLClassLoader(urls, Thread.currentThread().getContextClassLoader()); paths = new File[] { directory }; Once it processes the classes, that classloader is discarded and obviously, since it is a URLclassloader, the classes aren't going to be found later on. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

4
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2381) EntityQuery to stop fetching maxResults + 1 rows

by Brian Kalbfus (JIRA)

EntityQuery to stop fetching maxResults + 1 rows ------------------------------------------------ Key: JBSEAM-2381 URL: http://jira.jboss.com/jira/browse/JBSEAM-2381 Project: JBoss Seam Issue Type: Feature Request Components: EJB3 Affects Versions: 2.0.1.CR1, 2.0.0.GA Reporter: Brian Kalbfus In using a hibernate interceptor to audit instantiating entities, I noticed one extra record in excess of getMaxResults() is instantiated that isn't used - thus rendering a false audit. This was because of the following code in EntityQuery (copied from CVS head): <code> protected javax.persistence.Query createQuery() { parseEjbql(); evaluateAllParameters(); joinTransaction(); javax.persistence.Query query = getEntityManager().createQuery( getRenderedEjbql() ); setParameters( query, getQueryParameterValues(), 0 ); setParameters( query, getRestrictionParameterValues(), getQueryParameterValues().size() ); if ( getFirstResult()!=null) query.setFirstResult( getFirstResult() ); if ( getMaxResults()!=null) query.setMaxResults( getMaxResults()+1 ); //add one, so we can tell if there is another page if ( getHints()!=null ) { for ( Map.Entry<String, String> me: getHints().entrySet() ) { query.setHint(me.getKey(), me.getValue()); } } return query; } </code> Specifically: if ( getMaxResults()!=null) query.setMaxResults( getMaxResults()+1 ); //add one, so we can tell if there is another page The code says it is adding one so that it knows if there is another page. I see its use here: <code> public boolean isNextExists() { return resultList!=null && resultList.size() > getMaxResults(); } </code> I propose this for isNextExists(): <code> public boolean isNextExists() { return getResultCount() > (getFirstResult()!=null?getFirstResult():0) + getMaxResults(); } </code> Then we can change that line in createQuery() to: if ( getMaxResults()!=null) query.setMaxResults( getMaxResults() ); I did this in my subclass by overriding these two methods for my project; I had to copy in some of the private members of EntityQuery to do this. Thanks, Brian Kalbfus -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2007