December 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3663) @Begin can annotate constructors in wicket

by Clint Popetz (JIRA)

@Begin can annotate constructors in wicket ------------------------------------------ Key: JBSEAM-3663 URL: https://jira.jboss.org/jira/browse/JBSEAM-3663 Project: Seam Issue Type: Patch Reporter: Clint Popetz Constructors are frequently the only method in a component, and are the logical place to begin conversations for wicket apps. The current Begin annotation doesn't allow placement on constructors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3678) RedirectFilter should only act during a faces request

by Clint Popetz (JIRA)

RedirectFilter should only act during a faces request ----------------------------------------------------- Key: JBSEAM-3678 URL: https://jira.jboss.org/jira/browse/JBSEAM-3678 Project: Seam Issue Type: Patch Reporter: Clint Popetz This is broken out from https://jira.jboss.org/jira/browse/JBSEAM-3645 The redirect filter, which is jsf-specific, should only act when jsf is active, so that it can live in deployments where other view layers are sometimes used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3859) Wicket shouldn't instrument classes annotated with @Name

by Clint Popetz (JIRA)

Wicket shouldn't instrument classes annotated with @Name -------------------------------------------------------- Key: JBSEAM-3859 URL: https://jira.jboss.org/jira/browse/JBSEAM-3859 Project: Seam Issue Type: Bug Reporter: Clint Popetz Assignee: Clint Popetz Priority: Minor Attachments: JavassistInstrumentor.java.patch If a @Named component ends up being scanned by the instrumentation code, the result will be mangled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3679) WicketRedirectFilter should only be active on wicket requests

by Clint Popetz (JIRA)

WicketRedirectFilter should only be active on wicket requests ------------------------------------------------------------- Key: JBSEAM-3679 URL: https://jira.jboss.org/jira/browse/JBSEAM-3679 Project: Seam Issue Type: Patch Reporter: Clint Popetz Attachments: WicketRedirectFilter.patch This is broken out of https://jira.jboss.org/jira/browse/JBSEAM-3645. WicketRedirectFilter should check with Wicket to see if it has decided the request is a wicket request, and do nothing otherwise. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3807) Transactional Attribute doesn't allow override at method level

by Clint Popetz (JIRA)

Transactional Attribute doesn't allow override at method level -------------------------------------------------------------- Key: JBSEAM-3807 URL: https://jira.jboss.org/jira/browse/JBSEAM-3807 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.CR1 Reporter: Clint Popetz Assignee: Shane Bryzak Priority: Critical Attachments: tx-annotation.patch Shane, the fix to http://jira.jboss.org/jira/browse/JBSEAM-3519, and in particular part of this change: http://fisheye.jboss.com/browse/Seam/trunk/src/main/org/jboss/seam/transa... private boolean isNewTransactionRequired(Method method, Class beanClass, boolean transactionActive) 50 105 { - return isTransactionAnnotationPresent(method) ? 52 - isNewTransactionRequired(method, transactionActive) : 53 - isTransactionAnnotationPresent(beanClass) && isNewTransactionRequired(beanClass, transactionActive); 106 + TransactionMetadata metadata = lookupTransactionMetadata(method); 107 + if (metadata.isNewTransactionRequired(transactionActive)) 108 + { 109 + return true; 110 + } 111 + else 112 + { 113 + metadata = lookupTransactionMetadata(beanClass); 114 + return metadata.isNewTransactionRequired(transactionActive); 115 + } 54 116 breaks the use case of applying @Transactional to a method in order to override the behavior at the class level: @Transactional public class foo { @Transactional(SUPPORTS) public method shouldntTryToStartANewMethod() { } } I''ll attach a patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3863) Rerender is stronger than the pages.xml

by joe Koch (JIRA)

Rerender is stronger than the pages.xml --------------------------------------- Key: JBSEAM-3863 URL: https://jira.jboss.org/jira/browse/JBSEAM-3863 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.GA Reporter: joe Koch Priority: Trivial hi, we had a bit a strange thing on one of our pages after we added a a4j thing. as it used to work correctly: we entered a value in a field, the browser gave us some values we entered before (auto completion). when we left the focus on the input field, the "drop down list" was still there, and we pressed a button that did a action and left the page via an return code via pages.xml as we liked the input field to be formatted nicely we added a <a4j:support event="onchange" reRender="selectUnderlyingForm"/> so now the imput field was renderd as wished when we left the field. But when we left the page (with the action button) and had the values on the auto completion on the input field, the action from the button was called and exited correctly but the page reload it self an did not redirect as told on the pages.xml => we never left the original page. we searched for days, till we found out that the render of the "onchange" was stronger than the pages.xml, without the a4j everything is working correctly. we did some test with the "live http headers" and saw that first the rerender goes to the server and than the button click. what is correct. as i had not enough knowledge i was not able to see the responds for that page. may that came synchronous back after the button action? i guess seam should stop comunication with the page as soon as it comes to the pages.xml. i guess this is the problem. this is not an important issue but someting hard to find! if you need any more information i am glad to help you. best regards <td class="prodTableCell"> <s:decorate id="issueSizeDecorator"> <h:inputText label="#{messages['issueSize']}" styleClass="numberInput" id="issueSize" required="true" value="#{product.issueSize}"> <f:convertNumber integerOnly="true" pattern="###,###,###" locale="de_CH"/> <a4j:support event="onchange" reRender="selectUnderlyingForm"/> <xxx:productRangeValidator/> <f:attribute name="product" value="#{product}"/> <f:attribute name="fieldName" value="issueSize"/> </h:inputText> </s:decorate> </td> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3862) http://www.seamframework.org/Community/SeamGenToolBug

by huix jan (JIRA)

http://www.seamframework.org/Community/SeamGenToolBug ----------------------------------------------------- Key: JBSEAM-3862 URL: https://jira.jboss.org/jira/browse/JBSEAM-3862 Project: Seam Issue Type: Bug Components: EL Environment: all version Reporter: huix jan http://www.seamframework.org/Community/SeamGenToolBug -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3861) support more detailed TransactionSuccessEvent when update,persist,remove entity

by zhou yanming (JIRA)

support more detailed TransactionSuccessEvent when update,persist,remove entity ------------------------------------------------------------------------------- Key: JBSEAM-3861 URL: https://jira.jboss.org/jira/browse/JBSEAM-3861 Project: Seam Issue Type: Feature Request Components: Framework Affects Versions: 2.1.0.GA Reporter: zhou yanming sometimes we want to synchronize particular entity to other seam compenont,so need to raise event with this entity and transaction type. org.jboss.seam.framework.Home: change protected void raiseAfterTransactionSuccessEvent() { raiseTransactionSuccessEvent("org.jboss.seam.afterTransactionSuccess"); String simpleEntityName = getSimpleEntityName(); if (simpleEntityName != null) { raiseTransactionSuccessEvent("org.jboss.seam.afterTransactionSuccess." + simpleEntityName); } } to protected void raiseAfterTransactionSuccessEvent(Ojbect... params) { raiseTransactionSuccessEvent("org.jboss.seam.afterTransactionSuccess"); String simpleEntityName = getSimpleEntityName(); if (simpleEntityName != null) { raiseTransactionSuccessEvent("org.jboss.seam.afterTransactionSuccess." + simpleEntityName); } if (simpleEntityName != null && params.length==1) { raiseTransactionSuccessEvent("org.jboss.seam.afterTransactionSuccess." + simpleEntityName+"."+params[0]); } if (simpleEntityName != null && params.length==2) { raiseTransactionSuccessEvent("org.jboss.seam.afterTransactionSuccess." + simpleEntityName+"."+params[0],params[1]); } } org.jboss.seam.framework.EntityHome{ change raiseAfterTransactionSuccessEvent(); to raiseAfterTransactionSuccessEvent("persisted",getInstance()); raiseAfterTransactionSuccessEvent("removed",getInstance()); raiseAfterTransactionSuccessEvent("updated",getInstance()); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3860) support @DataModel on javax.faces.model.DataModel type field

by zhou yanming (JIRA)

support @DataModel on javax.faces.model.DataModel type field ------------------------------------------------------------ Key: JBSEAM-3860 URL: https://jira.jboss.org/jira/browse/JBSEAM-3860 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.1.0.GA Reporter: zhou yanming add four lines to class org.jboss.seam.faces.DataModels if (value instanceof DataModel) { return (DataModel)value; } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3608) self-written DataModel as @DataModel

by Juergen Hartler (JIRA)

self-written DataModel as @DataModel ------------------------------------ Key: JBSEAM-3608 URL: https://jira.jboss.org/jira/browse/JBSEAM-3608 Project: Seam Issue Type: Feature Request Components: Framework Affects Versions: 2.0.2.SP1 Reporter: Juergen Hartler Priority: Minor Dear Seam-Team! I have self-written DataModel extending the org.richfaces.model.ExtendedTableDataModel to support true pagination via the database. The only problem is just that the @DataModel tag of seam does not support self-written DataModels. I added manually in the downloaded source code of jboss-seam-2.0.2.SP1 and added to the class org.jboss.seam.faces.DataModels.getDataModel(Object value) the lines: ... else if (value instanceof DataModel){ return (DataModel)value; }else{ ... Could you please mind to add this to your next release? Many thanks, Juergen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2008