April 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-808) StatckOverflowError if factory specifies it's component

by John Ray (JIRA)

StatckOverflowError if factory specifies it's component ------------------------------------------------------- Key: JBSEAM-808 URL: http://jira.jboss.com/jira/browse/JBSEAM-808 Project: JBoss Seam Issue Type: Bug Environment: Latest from CVS Reporter: John Ray I accidently specified the name of my component instead of a context variable and this resulted in a StatckOverflowError. For example @Stateful @Name("foo") @Scope(ScopeType.EVENT) public class FooAction implements Foo { @Out("bar") private String bar; @Factory("foo") public void initBar() { ... } } I'd sugest changing the code in org.jboss.seam.Component at line 490 to include an if/throw. I highlighted the 2 new lines with an asterisk if ( method.isAnnotationPresent(org.jboss.seam.annotations.Factory.class) ) { Init init = (Init) applicationContext.get( Seam.getComponentName(Init.class) ); //can't use Init.instance() here 'cos of unit tests String contextVariable = toName( method.getAnnotation(org.jboss.seam.annotations.Factory.class).value(), method ); * if (contextVariable.equals(name)) * throw new IllegalStateException("@Factory method can not be for it's own component: " + name); init.addFactoryMethod(contextVariable, method, this); } -- 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

15 years, 8 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1183) Allow custom ExceptionHandler implementations to be inserted

by Mike Quilleash (JIRA)

Allow custom ExceptionHandler implementations to be inserted ------------------------------------------------------------ Key: JBSEAM-1183 URL: http://jira.jboss.com/jira/browse/JBSEAM-1183 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash Currently you can only configure a small subset of actions to occur on an exception (redirect, http-error etc). Enhancing the exception configuration xml to allow pluggable ExceptionHandler implementations would make this a lot more flexible. e.g. pages.xml <pages>  <exception class="javax.persistence.EntityNotFoundException"> <http-error error-code="404"/> </exception>  <exception handlerClass="com.xxx.seam.CustomExceptionHandler"/> </pages> These should probably have higher precedence than standard configure-by-exception-class handlers. -- 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

15 years, 9 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1146) Include optional Ant build-${profile}.xml in seam-gen/build-scripts

by Stephan Heffner (JIRA)

Include optional Ant build-${profile}.xml in seam-gen/build-scripts ------------------------------------------------------------------- Key: JBSEAM-1146 URL: http://jira.jboss.com/jira/browse/JBSEAM-1146 Project: JBoss Seam Issue Type: Patch Affects Versions: 1.2.1.GA Reporter: Stephan Heffner Attachments: build.xml  <import file="build-${profile}.xml" optional="true"/> -- 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

15 years, 10 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1228) Add sort option to <s:selectItems>

by Stephan Bublava (JIRA)

Add sort option to <s:selectItems> ---------------------------------- Key: JBSEAM-1228 URL: http://jira.jboss.com/jira/browse/JBSEAM-1228 Project: JBoss Seam Issue Type: Patch Components: JSF Affects Versions: 1.2.1.GA Reporter: Stephan Bublava Attachments: sort-selectitems-patch.txt The attached patch adds a sort option to <s:selectItems>, that allows the entries to be sorted by their label. Example: <h:selectOneMenu value="#{person.honorific}"> <s:selectItems value="#{honorifics}" var="honorific" label="#{honorific.label}" noSelectionLabel="Please select" sort="ascending" /> <s:convertEnum /> </h:selectOneMenu> This version has not been tested in depth (especially interactions with "noSelectionLabel"), but I've been using similar code in our project (based upon Seam SelectItems 1.1.1beta1) for some time now and not encountered any problems. -- 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

15 years, 10 months

4
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-905) Using the debug page without exceptions

by Christian Bauer (JIRA)

Using the debug page without exceptions --------------------------------------- Key: JBSEAM-905 URL: http://jira.jboss.com/jira/browse/JBSEAM-905 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Christian Bauer Priority: Minor I'd like to call /debug.seam manually to look into my conversations. I usually don't enable it because I don't like being redirected to it from an exception. Why? It hides the URL that caused the exception and it fills my log with hundreds of lines after the exception stacktrace. -- 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

15 years, 10 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1000) Propagation of conversations with pageflow in testing environment.

by Denis Karpov (JIRA)

Propagation of conversations with pageflow in testing environment. ------------------------------------------------------------------ Key: JBSEAM-1000 URL: http://jira.jboss.com/jira/browse/JBSEAM-1000 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.0.GA Environment: windows 2000 jboss-4.0.5.GA Reporter: Denis Karpov I think there is bug in testing environment (propagation of conversations with pageflow does not work) In this test there is 2 requests . In the first I start conversation and pageflow In the second conversation is lost. If I do not start pageflow then conversation propagates. Code: public class TOrdTest extends SeamTest{ private static final Log log = LogFactory.getLog( TOrdTest.class ); @Test public void Test1() throws Exception { String id = new FacesRequest(){ @Override protected void invokeApplication() throws Exception { Conversation.instance().begin(); Pageflow.instance().begin("val_buy"); // uses start-state setOutcome("browse"); log.info("##### 1 Conversation_ID "+ Conversation.instance().getId()); assert isLongRunningConversation(); } @Override protected void renderResponse() throws Exception { } }.run(); id = new FacesRequest("/exchange/buy_readonly.xhtml",id){ @Override protected void beforeRequest() { log.info("#####beforeRequest Conversation_ID "+ getConversationId()); } @Override protected void applyRequestValues() throws Exception { log.info("##### 2 Conversation_ID "+ Conversation.instance().getId()+" "+getConversationId()); } @Override protected void invokeApplication() throws Exception { //Conversation.instance().beginNested(); log.info("##### 3 Conversation_ID "+ Conversation.instance().getId()+" "+getConversationId()); assert isLongRunningConversation(); } }.run(); } } -- 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

15 years, 10 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1173) HibernateSessionProxy ClassCastException

by dazhu tang (JIRA)

HibernateSessionProxy ClassCastException ---------------------------------------- Key: JBSEAM-1173 URL: http://jira.jboss.com/jira/browse/JBSEAM-1173 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 1.2.0.GA Reporter: dazhu tang Priority: Critical 1. i want to inject the hibernate session in seam,so i config the component.xml as follows: <core:hibernate-session-factory name="hibernateSessionFactory" /> <core:managed-hibernate-session name="session" auto-create="true" session-factory-jndi-name="java:/HibernateSessionFactory" /> 2. Inside managed Bean , i use @in to inject the Hibernate Session, but when i am using DetachedCriteria in my application DetachedCriteria criteria = DetachedCriteria.forClass(Smartform.class); criteria.getExecutableCriteria(session) i got the HibernateSessionProxy ClassCastException,i debug the application and found that seam injected HibernateSessionProxy not the real HibernateSession object . So DetachedCriteria can't work. -- 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

15 years, 10 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-796) Seam does not recognise the @Role annotation when the component is loaded via xml rather than scanning

by Mike Quilleash (JIRA)

Seam does not recognise the @Role annotation when the component is loaded via xml rather than scanning ------------------------------------------------------------------------------------------------------ Key: JBSEAM-796 URL: http://jira.jboss.com/jira/browse/JBSEAM-796 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.0.GA Environment: Any Reporter: Mike Quilleash The @Role and @Roles annotations are checked in Initialization.installScannedComponentAndRoles() which is not called when components are specified in components.xml. -- 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

15 years, 10 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1226) Ability to upload ZIP/JAR archives with automatic unarchiving

by Christian Bauer (JIRA)

Ability to upload ZIP/JAR archives with automatic unarchiving ------------------------------------------------------------- Key: JBSEAM-1226 URL: http://jira.jboss.com/jira/browse/JBSEAM-1226 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Minor I'd like to be able to upload a ZIP with pictures and have it uncompressed and unarchived into a new directory with the name of the archive. Or a bunch of docbook.xml files that are rendered as documents in a new directory. This feature probably needs some abstraction of file handling (better than the little hashmap we have right now). -- 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

15 years, 10 months

1
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1052) seam-dev.properties, seam-prod.properties

by Pete Muir (JIRA)

seam-dev.properties, seam-prod.properties ----------------------------------------- Key: JBSEAM-1052 URL: http://jira.jboss.com/jira/browse/JBSEAM-1052 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 1.2.0.GA Reporter: Pete Muir Priority: Optional In the same way you have persistence-dev.xml, there should be seam-dev.properties to allow you to configure your application differently when in dev/prod (e.g. disable random password generation). AFAICS seam.properties must be in WEB-INF/classes/seam.properties for it to be read (it isn't read in ejb-jar/seam.properties as it's not in the classloader) -- 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

15 years, 10 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2007