November 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3864) Document working with multiple seam-gen projects - JBSEAM-2338

by Jay Balunas (JIRA)

Document working with multiple seam-gen projects - JBSEAM-2338 -------------------------------------------------------------- Key: JBSEAM-3864 URL: https://jira.jboss.org/jira/browse/JBSEAM-3864 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.1.1.GA Reporter: Jay Balunas Assignee: Dan Allen Fix For: 2.1.2.CR1 Document how to use seam-gen to manage multiple projects - JBSEAM-2338 -- 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, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3205) Make it easier to get the delegate you want

by Pete Muir (JIRA)

Make it easier to get the delegate you want ------------------------------------------- Key: JBSEAM-3205 URL: https://jira.jboss.org/jira/browse/JBSEAM-3205 Project: Seam Issue Type: Feature Request Components: Core Reporter: Pete Muir Assignee: Christian Bauer Fix For: 2.1.0.BETA2 PersistenceProvider.instance.getDelegate(Class clazz) which returns the requested delegate (e.g. a FullTextSession) -- 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, 1 month

5
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1978) Minimize the performance cost of calling getter in JBoss EL

by Mikhail Grushinskiy (JIRA)

Minimize the performance cost of calling getter in JBoss EL ----------------------------------------------------------- Key: JBSEAM-1978 URL: http://jira.jboss.com/jira/browse/JBSEAM-1978 Project: JBoss Seam Issue Type: Feature Request Reporter: Mikhail Grushinskiy Minimize the performance cost of calling getter in JBoss EL bean.property is the most common EL construct used in all JSF applications. The cost of calling property getter in EL is more important to overall JSF application performance (specifically rendering phase) See also http://jira.jboss.com/jira/browse/JBSEAM-1977 -- 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, 1 month

6
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1875) Rework configuration chapter

by Pete Muir (JIRA)

Rework configuration chapter ---------------------------- Key: JBSEAM-1875 URL: http://jira.jboss.com/jira/browse/JBSEAM-1875 Project: JBoss Seam Issue Type: Task Components: Documentation Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir Fix For: 2.0.0.GA Rework configuration chapter to make it a generic discussion of configuring and packaging Seam applications. Move platform specific stuff to platform specific chapter. i.e. 25 Configuring & Packaging Seam Applications 25.1 Basic Seam Configuration 25.1.1 Integrating Seam with JSF and the Servlet Container 25.1.2 Using Facelets 25.1.3 Seam Resource Servlet 25.1.4 Seam Filter 25.1.5. Integrating Seam with your EJB container 25.2 Seam Applications in a JEE 5 environment 25.3 Seam Applications in a J2EE environment 25.4 Seam Applicaitons in a JSE environment * Move JBPM configuration to JBPM chapter * Move JBoss AS stuff to new JBoss AS chapter * Move JBoss Embedded stuff to new JBoss Embedded Chapter 26 Seam on JBoss AS 26.1 Seam on JBoss AS 4.0 * Includes stuff on install JSF 1.2 from Chapter 2 26.2 Seam on JBoss AS 4.2 27 Seam with JBoss Embedded 28 Seam on OC4J 29 Seam on Glassfish * Needs writing! -- 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, 1 month

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3159) Debug/development mode control

by Pete Muir (JIRA)

Debug/development mode control ------------------------------ Key: JBSEAM-3159 URL: http://jira.jboss.com/jira/browse/JBSEAM-3159 Project: Seam Issue Type: Task Components: Tools Reporter: Pete Muir Priority: Critical Fix For: 2.1.0.BETA2 Currently we have a very overloaded system which is hard to use: 1) debug flag is used to control parsing of hot-deploy (/dev) which is odd 2) to view the debug page at all you must both include jboss-seam-debug.jar and enable debug mode in components.xml. Further, if you do this, then the debug page handler is installed, which screws with the exception handling. I propose that by simply including jboss-seam-debug.jar you get 1) hot deployment enabled 2) use of the debug page by calling /debug.seam BUT not as a redirect off the exception handler and, further, by <exception:exceptions enable-debug-page="true" /> (better ideas for attribute name?) you can automagically redirect to the debug page when an exception occurs. The default for this is false, and this should be set in seam-gen (the seam-gen app should include a link to debug.seam in perhaps its footer) -- 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, 1 month

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4247) Seam managed @Provider not registered

by Matthew Bowman (JIRA)

Seam managed @Provider not registered ------------------------------------- Key: JBSEAM-4247 URL: https://jira.jboss.org/jira/browse/JBSEAM-4247 Project: Seam Issue Type: Bug Components: WS Affects Versions: 2.1.2.GA Reporter: Matthew Bowman Example: @Name("serviceExceptionMapper") @Scope(ScopeType.APPLICATION) @Provider public class ServiceExceptionMapper implements ExceptionMapper<ServiceException> { public Resposne toResponse(ServiceException ex) { return Response.noContent().build(); } } This custom ExceptionMapper provider will not be registered with ResteasyProviderFactory. If I remove the @Name + @Scope annotations, the provider is registered. -- 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, 1 month

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4388) Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state

by David Thompson (JIRA)

Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state -------------------------------------------------------------------------------------- Key: JBSEAM-4388 URL: https://jira.jboss.org/jira/browse/JBSEAM-4388 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Environment: JBoss 4.2.3 or JBoss 5.1, jboss-seam-2.2.0, JBoss set up to hot deploy. Reporter: David Thompson Priority: Blocker We currently write struts apps. One of the things we do is hot deploy these apps by setting up JBoss/Tomcat (jboss-web.deployer) to enable session persistence. This way when an app is deployed with "ant deploy", the session data can be stored out--app is torn down-- then when new app deploys the session data restores. If a component that is in ScopeType.CONVERSATION is instantiated and is currently in the Conversation Context when the app is deployed, then JBoss throws an error trying to reload the component and no SESSION data is restored. For example, all logged in users (data stored in Identity or Credentials) do not restore so all users get the boot. This doesn't happen if the scope on a component is EVENT or SESSION. For the way we deploy to our production system, this causes problems for us. The ideal solution, would be to have the conversations to come back to life, but we could also live with the conversations not being reestablished--but we really need the other session data (such as login credentials) to live through the deploy. AFAIK, I have looked all over the web and read the seam reference as well as Seam In Action and can't find any information about how Conversations can persist over a session (such as a redeploy this way) or over a cluster. -- 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, 1 month

2
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2057) Syntax highlighting

by Gavin King (JIRA)

Syntax highlighting ------------------- Key: JBSEAM-2057 URL: http://jira.jboss.com/jira/browse/JBSEAM-2057 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Gavin King Assigned To: Christian Bauer I would love some way to do syntax highlighting in code blocks. Would require some extra wiki syntax of some kind, maybe <pre highlight="java">...</pre> or something. RIFE has some code we can probably reuse. This will make our blogs and docs *so* much more readable. -- 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, 1 month

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4171) Wiki Forum:Deadlock found when trying to get lock

by Francisco Jose Peredo Noguez (JIRA)

Wiki Forum:Deadlock found when trying to get lock ------------------------------------------------- Key: JBSEAM-4171 URL: https://jira.jboss.org/jira/browse/JBSEAM-4171 Project: Seam Issue Type: Bug Components: Wiki Reporter: Francisco Jose Peredo Noguez Assignee: Christian Bauer A week ago I was writing a long answer to a forum thread... I previewed it, it was fine, I clicked to post it and got (and of course lost all my text): HTTP Status 400 - Request failed, please check the application log or contact the administrator (christian.bauer(a)gmail.com): 'com.mysql.jdbc.exceptions.MySQLTransactionRollbackException, Deadlock found when trying to get lock; try restarting transaction in com.mysql.jdbc.SQLError@1042' type Status report message Request failed, please check the application log or contact the administrator (christian.bauer(a)gmail.com): 'com.mysql.jdbc.exceptions.MySQLTransactionRollbackException, Deadlock found when trying to get lock; try restarting transaction in com.mysql.jdbc.SQLError@1042' description The request sent by the client was syntactically incorrect (Request failed, please check the application log or contact the administrator (christian.bauer(a)gmail.com): 'com.mysql.jdbc.exceptions.MySQLTransactionRollbackException, Deadlock found when trying to get lock; try restarting transaction in com.mysql.jdbc.SQLError@1042'). -- 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, 1 month

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4484) Wiki Forum: Give me a chance to hit the push button again... and again... and so on, and so forth

by Francisco Jose Peredo Noguez (JIRA)

Wiki Forum: Give me a chance to hit the push button again... and again... and so on, and so forth ------------------------------------------------------------------------------------------------- Key: JBSEAM-4484 URL: https://jira.jboss.org/jira/browse/JBSEAM-4484 Project: Seam Issue Type: Feature Request Components: Wiki Reporter: Francisco Jose Peredo Noguez Assignee: Christian Bauer Today, for the second time, I lost a post. I wrote medium sized a post (it took me around 15 minutes, it was an answer and it is hard to get the Wiki Text Markup correctly between the blockquotes). I click Save... And I am greeted with this error page: JBSEAM-4171 In old fashioned "written directly in Javascript" XMLHttpRequest based application, this would have been handled by a try/catch, and I wouldn't have lost my post... I am not asking here for fancy Google Gears like functionality, all I want is a chance to push the submit button again... Can it be done? -- 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, 1 month

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2009