July 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1878) Validation for Hibernate Class Level Validators

by Martin Hoffmann (JIRA)

Validation for Hibernate Class Level Validators ----------------------------------------------- Key: JBSEAM-1878 URL: http://jira.jboss.com/jira/browse/JBSEAM-1878 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.2.1.GA Reporter: Martin Hoffmann Priority: Optional A JSF Component for Validation of Hibernate Class Validators. This Component should be used like s:validateAll Tag. Currently SEAM throws an exception in case of a not validating class validator. -- 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

14 years, 11 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4186) HTTP caching for SeamResourceServlet resources

by Christian Bauer (JIRA)

HTTP caching for SeamResourceServlet resources ---------------------------------------------- Key: JBSEAM-4186 URL: https://jira.jboss.org/jira/browse/JBSEAM-4186 Project: Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assignee: Christian Bauer Priority: Minor This affects built-in Seam stuff like the remote.js that is always delivered with 200 OK and can be quite large. We need to explore how/when we can send 304. I've assigned this to the 'wiki' component because I want to try different solutions there first. -- 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

14 years, 11 months

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2761) Verify other JPA providers can used by seam applications.

by Jay Balunas (JIRA)

Verify other JPA providers can used by seam applications. --------------------------------------------------------- Key: JBSEAM-2761 URL: http://jira.jboss.com/jira/browse/JBSEAM-2761 Project: JBoss Seam Issue Type: Task Components: Examples, Test Harness Reporter: Jay Balunas Assigned To: Jay Balunas Priority: Minor This would entail replacing Hibernate JPA with another JPA implementation such as OpenJPA. A subset of examples should be modified, tested and if appropriate documented so work with alternate JPA providers. Examples: Booking DVD TBD -- 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

14 years, 11 months

3
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4312) Exception while checking out transaction causing infinite loop trying to render error page

by Matthew Lieder (JIRA)

Exception while checking out transaction causing infinite loop trying to render error page ------------------------------------------------------------------------------------------ Key: JBSEAM-4312 URL: https://jira.jboss.org/jira/browse/JBSEAM-4312 Project: Seam Issue Type: Bug Components: Exception Handling Affects Versions: 2.2.0.CR1 Environment: java 6, Tomcat 6, c3p0 0.9.2 Reporter: Matthew Lieder We have the following pretty typical exception config in our pages.xml: <exception> <end-conversation /> <redirect view-id="/seam/error.xhtml"> <message severity="error">#{org.jboss.seam.handledException}</message> </redirect> </exception> That works great, except when our database server is down. In that case a com.mchange.v2.resourcepool.TimeoutException is thrown and the exception handler is properly called, but Seam then tries to access the database again when rendering the error page and thus the cycle repeats ad infinitum. I don't believe this is specific to the TimeoutException exception or even to c3p0; this seems to be a pretty general problem. There needs to be some way to prevent Seam from trying to start a transaction while rendering the error page, either always or maybe by an attribute on the <exception> tag. -- 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

14 years, 11 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3525) Analyse JNDI lookups in an EJB app (Booking) and a EntityHome based app (seam-gen)

by Pete Muir (JIRA)

Analyse JNDI lookups in an EJB app (Booking) and a EntityHome based app (seam-gen) ---------------------------------------------------------------------------------- Key: JBSEAM-3525 URL: https://jira.jboss.org/jira/browse/JBSEAM-3525 Project: Seam Issue Type: Task Affects Versions: 2.1.0.BETA1 Reporter: Pete Muir Assignee: Jay Balunas Fix For: 2.1.1.CR1 -- 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

14 years, 11 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3712) Seam performance regression from 2.1.0.SP1 to 2.1.1.CR1

by Jay Balunas (JIRA)

Seam performance regression from 2.1.0.SP1 to 2.1.1.CR1 ------------------------------------------------------- Key: JBSEAM-3712 URL: https://jira.jboss.org/jira/browse/JBSEAM-3712 Project: Seam Issue Type: Bug Components: Core, Platform interoperability Affects Versions: 2.1.0.SP1 Environment: Fedora 8 JDK 5 Reporter: Jay Balunas Priority: Blocker Fix For: 2.1.1.CR2 Working with the latest trunk (r9557) and testing the performance changes that were made. Previous tests were done with (r9017). Just as a refresher my baseline test uses the wiki example with all of the sfwk.org data up to July 31st 2008. For these tests I use JBoss AS 4.2.3 with JDK5 on my linux machine. Jmeter is used to load test and calculate the results and graphs. I then use JProfiler to to identify either blocking threads, call graphs, and CPU usage. I was using a mixture of 25 and 50 users - hitting the server 25 times each. As before they were accessing the first page of the user forum. With r9017 the 25 user x 25 requests averaged 3 seconds a request. With trunk they were 100+ seconds. Thinking something was wrong with the system I replaced the 9557 wiki.war with the 9017 and reran with all other variables the same. Again the 9017 saw about 3 seconds for the average over the 625 requests. I then profiled the server under load as I did before. The methods below appear to be the primary offenders although as with most blocking threads there are some others waiting on the same monitor. ----------------------------------- 1) com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate.findLock(..) - This appears to be the biggest issue. Every requests are generating many of these calls. - http://viewvc.jboss.org/cgi-bin/viewvc.cgi/labs/labs/jbosstm/branches/JBO... - It looks like every interaction with any transaction causing synchronization issues with this call. - We'll need to find a way to limit these calls. - I'm guessing some of the changes made for JBSEAM-3519 may be the cause although I have not had time to look deeper. - See : http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/transa... http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/util/W... ----------------------------------- 2) org.jboss.naming.ENCFactory.getObjectInstance() javax.naming.Context.lookup(java.lang.String) This appears to be the second biggest offender and it looks like we are no longer blocking on retrieving the InitialContext, but now blocking on performing the lookups using the context. ----------------------------------- 3) org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection() org.jboss.resource.connectionmanager.CachedConnectionManager.registerConnection() This is the third biggest issue, but much less than the others. 1 or 2 dozen blocks on 60 requests. These are all related to hibernate calls and database access from what I've seen so far. ----------------------------------- -- 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

14 years, 11 months

5
16
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4279) RendererRequest does not respect the user's locales

by Dan Allen (JIRA)

RendererRequest does not respect the user's locales ---------------------------------------------------- Key: JBSEAM-4279 URL: https://jira.jboss.org/jira/browse/JBSEAM-4279 Project: Seam Issue Type: Bug Components: JSF Controls, Mail, PDF Affects Versions: 2.2.0.CR1 Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.2.1.CR1 When Seam sets up the Renderer component, it replaces the FacesContext with a mock FacesContext specifically for rendering a template (such as a mail or PDF template). That mock infrastructure does not respect the user's locales. If the ExternalContext is available, the result of getRequestLocales() should be transferred to the mock infrastructure. -- 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

14 years, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3856) seam-gen projects on windows "ant validate" fails

by Jay Balunas (JIRA)

seam-gen projects on windows "ant validate" fails ------------------------------------------------- Key: JBSEAM-3856 URL: https://jira.jboss.org/jira/browse/JBSEAM-3856 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Environment: Windows XP JDK 5 Reporter: Jay Balunas Assignee: Dan Allen Fix For: 2.1.2.CR1 Create a seam-gen EAR project on a windows machine. Within the projects directory execute "ant validate" and on a windows machine you will see the exception below. I did not see this on OS X. Note that this is seen with a space in the path, and without. Also the output is ugly, but this is how it was displayed. validate: [mkdir] Created dir: C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar\exploded-archives\schemas [unjar] Expanding: C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar\lib\jboss-seam.jar into C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar\exploded-archives\schemas validateConfiguration: [validateConfiguration] C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar\exploded-archives\seamGenEar.ear\META-INF\application.xml:1:1: http://www.w3.org/TR/xml-schema-1#SchemaLocation? http://jboss.com/products/seam/async C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/schemas/org/jboss/seam/async-2.1.xsd http://jboss.com/products/seam/bpm C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/schemas/org/jboss/seam/bpm-2.1.xsd http://jboss.com/products/se am/components C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/schemas/org/jboss/seam/components-2.1.xsd http://jboss.com/products/seam/core C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/schemas/org/jboss/seam/core-2.1.xsd http://jboss.com/products/seam/drools C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/schemas/org/jboss/seam/drools-2.1.xsd http://jboss.com/products/seam/framework C:\dev\projects\seam\2.1.1.GA\seam gen\seamGe nEar/exploded-archives/schemas/org/jboss/seam/framework-2.1.xsd http://jboss.com/products/seam/international C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/schemas/org/jboss/seam/international-2.1.xsd http://jboss.com/products/seam/jms C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/schemas/org/jboss/seam/jms-2.1.xsd http://jboss.com/products/seam/mail C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/schemas/org/jboss/seam/mail-2. 1.xsd http://jboss.com/products/seam/navigation C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/schemas/org/jboss/seam/navigation-2.1.xsd http://jboss.com/products/seam/pageflow C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/schemas/org/jboss/seam/pageflow-2.1.xsd http://jboss.com/products/seam/pages C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/schemas/org/jboss/seam/pages-2.1.xsd http://jboss.com/products/seam/pdf C:\dev\pr ojects\seam\2.1.1.GA\seam gen\seamGenEar/src/pdf/org/jboss/seam/pdf/pdf-2.1.xsd http://jboss.com/products/seam/persistence C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/schemas/org/jboss/seam/persistence-2.1.xsd http://jboss.com/products/seam/remoting C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/schemas/org/jboss/seam/remoting-2.1.xsd http://jboss.com/products/seam/security C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/sche mas/org/jboss/seam/security-2.1.xsd http://jboss.com/products/seam/theme C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/schemas/org/jboss/seam/theme-2.1.xsd http://jboss.com/products/seam/transaction C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/schemas/org/jboss/seam/transaction-2.1.xsd http://jboss.com/products/seam/web C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar/exploded-archives/schemas/org/jboss/seam/web-2.1.xsd [validateConfiguration] http://java.sun.com/xml/ns/javaee/javaee_5.xsd:83:57: schema_reference.4: Failed to read schema document 'http://www.w3.org/2001/xml.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. [validateConfiguration] http://java.sun.com/xml/ns/javaee/javaee_5.xsd:141:33: src-resolve: Cannot resolve the name 'xml:lang' to a(n) 'attribute declaration' component. [validateConfiguration] http://java.sun.com/xml/ns/javaee/javaee_5.xsd:141:33: s4s-elt-invalid-content.1: The content of 'descriptionType' is invalid. Element 'attribute' is invalid, misplaced, or occurs too often. [validateConfiguration] http://java.sun.com/xml/ns/javaee/javaee_5.xsd:188:33: s4s-elt-invalid-content.1: The content of 'display-nameType' is invalid. Element 'attribute' is invalid, misplaced, or occurs too often. [validateConfiguration] http://java.sun.com/xml/ns/javaee/javaee_5.xsd:689:36: s4s-elt-invalid-content.1: The content of 'iconType' is invalid. Element 'attribute' is invalid, misplaced, or occurs too often. BUILD FAILED C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar\build.xml:444: The following error occurred while executing this line: C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar\validate.xml:51: C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar\exploded-archives\seamGenEar.ear\META-INF\application.xml is not a valid XML document. Total time: 24 seconds C:\dev\projects\seam\2.1.1.GA\seam gen\seamGenEar> -- 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

14 years, 11 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3636) UTF8 quoted-printable encoding bug with seam mail

by Daniel Wachter (JIRA)

UTF8 quoted-printable encoding bug with seam mail ------------------------------------------------- Key: JBSEAM-3636 URL: https://jira.jboss.org/jira/browse/JBSEAM-3636 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.0.3.CR1 Environment: Debian Linux (Lenny), JBoss AS 4.2 Reporter: Daniel Wachter Assignee: Pete Muir All umlauts passed to the view (which actually is an email template), get a wrong encoded in the wrong charset (iso8859-1) as soon as they are encoded as quoted-printable. Example: können is converted to k=C3=B6nnen It looks, as if the input is wrongly treated as iso8859-1 while it actually is utf8. -- 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

14 years, 11 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3818) Wicket example - confirmation message is not displayed after succesful booking on JDK6

by Jozef Hartinger (JIRA)

Wicket example - confirmation message is not displayed after succesful booking on JDK6 -------------------------------------------------------------------------------------- Key: JBSEAM-3818 URL: https://jira.jboss.org/jira/browse/JBSEAM-3818 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.1.CR2 Environment: JBoss AS 5.0.0.GA JDK 6 update 10 Reporter: Jozef Hartinger Fix For: 2.1.2.CR1 Message appears normally on JDK5. -- 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

14 years, 11 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2009