February 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2683) QueueSession is null when injected in classes with methods annotated as @Asynchronous

by Vassilis Petropoulos (JIRA)

QueueSession is null when injected in classes with methods annotated as @Asynchronous ------------------------------------------------------------------------------------- Key: JBSEAM-2683 URL: http://jira.jboss.com/jira/browse/JBSEAM-2683 Project: JBoss Seam Issue Type: Bug Components: Async Affects Versions: 2.0.0.GA Environment: win xp, jboss 4.2.2, Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-241) Reporter: Vassilis Petropoulos a) components.xml <jms:managed-queue-sender name="processSMSQueueSender" auto-create="true" queue-jndi-name="queue/processSMS" /> b) SmsHandlerBean.java @Stateless @Name("smsHandler") public class SmsHandlerBean implements SmsHandler { @In(create=true) SMSScheduler smsScheduler; public void test(Sms sms) throws Exception { QuartzTriggerHandle quartzTriggerHandle = smsScheduler.schedule( sms.getId(), sms.getStartDate(), sms.getEndDate(), sms.getCronExpression()); } } c) SMSScheduler.java @Name("smsScheduler") public class SMSScheduler { @In QueueSender processSMSQueueSender; @In QueueSession queueSession; @Asynchronous @Transactional public QuartzTriggerHandle schedule(int smsId, @Expiration Date when, @FinalExpiration Date endDate, @IntervalCron String cron) { try { processSMSQueueSender.send(queueSession.createObjectMessage(smsId)); } catch (Exception e) { e.printStackTrace(); } return null; } } when scheduler fires queueSession, processSMSQueueSender are null. This also happens if use create=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

16 years, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2659) more friendly documentation

by Sebastian Hennebrueder (JIRA)

more friendly documentation --------------------------- Key: JBSEAM-2659 URL: http://jira.jboss.com/jira/browse/JBSEAM-2659 Project: JBoss Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.0.1.GA, 2.0.0.GA Environment: any Reporter: Sebastian Hennebrueder Priority: Minor I would propose a more friendly formulation in the documentation. See my mail on the developer mailinglist http://lists.jboss.org/pipermail/seam-dev/2008-February/000021.html ------- existing formulation In almost all enterprise applications, the database is the primary bottleneck, and the least scalable tier of the runtime environment. People from a PHP/Ruby environment will try to tell you that so-called "shared nothing" architectures scale well. While that may be literally true, I don't know of many interesting multi-user applica- tions which can be implemented with no sharing of resources between different nodes of the cluster. What these silly people are really thinking of is a "share nothing except for the database" architecture. Of course, sharing the database is the primary problem with scaling a multi-user application—so the claim that this architecture is highly scalable is absurd, and tells you a lot about the kind of applications that these folks spend most of their time working on. ------------- alternative formulation: In almost all enterprise applications, the database is the primary bottleneck, and the least scalable tier of the runtime environment. People from a PHP/Ruby environment state that their lightweigth architecture - which is not sharing resources - scales well. We do not agree here. A PHP/Ruby will share the database which is in large scale application normally already the bottleneck. Lightweight can be fast in smaller applications but is not scalable. This chapter explains how Seam uses caching to provide a architecture which is fast and scalable at the same 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2663) ResourceLoader context problem

by Pierre Ingmansson (JIRA)

ResourceLoader context problem ------------------------------ Key: JBSEAM-2663 URL: http://jira.jboss.com/jira/browse/JBSEAM-2663 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.GA Environment: Windows XP, Eclipse, Seam running in a Tomcat 5.5.25 Reporter: Pierre Ingmansson Priority: Minor The ResourceLoader, a core component of Seam, is hard-coded in the ResourceLoader's instance()-method, to be in the stateless context. Some of the core components in Seam use this static instance()-method to fetch the ResourceLoader. Therefore you can not overload the ResourcLoader with your own component that want to be in another context than stateless. The ResourceLoader is accessed frequently during the JSF page rendering, and because of the stateless context setting of the ResourceLoader, a new instance of ResourceLoader is instantiated and initlialized everytime it is accessed. My opinion is that it is unnecessary to create a new instance of the ResourceLoader everytime it is accessed, it's just bad for performance. Also if you want to override the ResourceLoader with your own component, it is only possible to do so in the stateless-context. There is (right now) no way of creating a MyResourceLoader with @Scope(ScopeType.APPLICATION) for example. This problem is somewhat related to JIRA issue JBSEAM-2364. I bumped in to the ResourceLoader-overloading-problem when trying to find a workaround for this other problem. -- 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2648) SeamTest running inside the IDE

by Rodrigo Yoshima (JIRA)

SeamTest running inside the IDE ------------------------------- Key: JBSEAM-2648 URL: http://jira.jboss.com/jira/browse/JBSEAM-2648 Project: JBoss Seam Issue Type: Bug Components: Test Harness Affects Versions: 1.2.1.GA Environment: Jboss 4.0.5 / Seam 1.2.1.GA / Jboss IDE for Eclipse / Windows XP Reporter: Rodrigo Yoshima Priority: Minor My current 1.2.1 project based on seam-gen runs OK on 'test' ant target, but doesn't run via right-click on the IDE because Jboss MC doesn't find (deploy) the components on the IDE classpath. -- 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2630) Pageflow event type="node-enter" on start-page

by Krunoslav Samardzic (JIRA)

Pageflow event type="node-enter" on start-page ---------------------------------------------- Key: JBSEAM-2630 URL: http://jira.jboss.com/jira/browse/JBSEAM-2630 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.1.GA Reporter: Krunoslav Samardzic The problem is that actions in side event type="node-enter" on node start-page do not get called. but pageflow-2.0.xsd allows this on start-page. <?xml version="1.0"?> <pageflow-definition xmlns="http://jboss.com/products/seam/pageflow" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.com/products/seam/pageflow http://jboss.com/products/seam/pageflow-2.0.xsd" name="kruno"> <start-page view-id="/Kruno.jsp" name="kruno"> <redirect/> <description> Kruno </description> <event type="node-enter"> <action name="start" expression="#{kruno.odradi}"></action> </event> -- 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2577) pageflow.hasTransition(...) throws NPE if not in process

by Matthew Lieder (JIRA)

pageflow.hasTransition(...) throws NPE if not in process -------------------------------------------------------- Key: JBSEAM-2577 URL: http://jira.jboss.com/jira/browse/JBSEAM-2577 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 2.0.1.GA Reporter: Matthew Lieder Priority: Minor I use pageflow.hasTransition(...) to determine which buttons to show on various pages. Some pages however may be gotten to outside of a pageflow, and in those cases merely calling that one method throws a NPE because getNode() returns null. Hence I'm having to check pageflow.isInProcess() at the beginning of those EL expressions. It would be nice if hasTransition(...) (and probably hasDefaultTransition() ) could be modified to just return false if processInstance is null. -- 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2362) from-action "equals" requires a textual match not a semantical

by koen handekyn (JIRA)

from-action "equals" requires a textual match not a semantical --------------------------------------------------------------- Key: JBSEAM-2362 URL: http://jira.jboss.com/jira/browse/JBSEAM-2362 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: koen handekyn in my facelets page i'm referring to an action as " backinBean['persist'] " ( where backingBean is a facelet tag parameter that has the value accountHome ) in pages.xml one needs to use the same litteral string within example from-action, ie DOES NOT WORK <navigation from-action="#{accountHome.persist}"> <end-conversation /> <redirect view-id="/up/admin/accountList.xhtml" /> </navigation> DOES WORK <navigation from-action="#{backingBean['persist']}"> <end-conversation /> <redirect view-id="/up/admin/accountList.xhtml" /> </navigation> this is very weird to understand from within the pages.xml as this backingBean variable does not have any specific meaning in the context. i propose that the "EQUALS" for from-action should be performed on ' evaluated EL expressions ' ( the actual method pointer on the class ). -- 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, 10 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2314) Provide non-event triggering Context for use in MethodContextInterceptor as the method context

by Kahli Burke (JIRA)

Provide non-event triggering Context for use in MethodContextInterceptor as the method context ---------------------------------------------------------------------------------------------- Key: JBSEAM-2314 URL: http://jira.jboss.com/jira/browse/JBSEAM-2314 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.GA Reporter: Kahli Burke Some profiling has shown that in some cases Event triggering/handling can represent a significant chunk of page processing time. I found that Event triggering from the MethodContextInterceptor results in 10 events per method call, due to its use of the BasicContext which has pre and post set and remove events. Would a non-event triggering base class for BasicContext make sense for use as the method context? -- 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2307) Provide an integrated rich text editor control

by Shane Bryzak (JIRA)

Provide an integrated rich text editor control ---------------------------------------------- Key: JBSEAM-2307 URL: http://jira.jboss.com/jira/browse/JBSEAM-2307 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.GA Reporter: Shane Bryzak Assigned To: Shane Bryzak Priority: Minor Currently we don't have one of these (and it seems that RichFaces doesn't either). We should be able to provide this easily by wrapping one of the many popular rich text editors - probably fckeditor as it supports inline image uploads (the only rich editor that does), and is available under LGPL. -- 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, 10 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2263) Page-scoped components not accessible in jPDL page initial actions

by Matthew Lieder (JIRA)

Page-scoped components not accessible in jPDL page initial actions ------------------------------------------------------------------ Key: JBSEAM-2263 URL: http://jira.jboss.com/jira/browse/JBSEAM-2263 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 2.0.0.GA Reporter: Matthew Lieder See the following page declaration (selectEmployeePageBean is scoped to the page): <page name="selectEmployee" view-id="/selectEmployee.xhtml"> <action expression="#{selectEmployeePageBean.setShowDetails(true)}" /> <transition to="somewhere" /> </page> The problem is that when selectEmployee.xhtml is being rendered, selectEmployeePageBean.showDetails is false -- the bean is actually created twice, once for the action expression and again when accessed from the page renderer, and thus loses its state. I would think that the page scope should begin before the action expressions for that page are evaluated. That would allow me to easily customize pages from the pageflow definition (useful if in some places I want a "Next" button instead of "Finish", or want details to be shown in only one place, etc.) without having to make page-specific beans conversation-scoped. -- 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, 10 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2008