November 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1969) updatedMessage, deletedMessage and createdMessage in framework.Home cause NPE if getEntityClass is overridden

by Damian Harvey (JIRA)

updatedMessage, deletedMessage and createdMessage in framework.Home cause NPE if getEntityClass is overridden ------------------------------------------------------------------------------------------------------------- Key: JBSEAM-1969 URL: http://jira.jboss.com/jira/browse/JBSEAM-1969 Project: JBoss Seam Issue Type: Bug Components: Framework Environment: Mac OSX 10.4.8, Jboss 4.2.1, Seam 1.3.0 Reporter: Damian Harvey Priority: Trivial I am extending an existing class (BookingHome) that extends EntityHome. My BookingHome class needs to override getEntityClass. Doing this then results in a NPE as updatedMessage, deletedMessage and createdMessage refer to entityClass rather than getEntityClass. -- 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, 9 months

3
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1927) wrong XSD schema URI in web.xml for seam-gen

by Dan Allen (JIRA)

wrong XSD schema URI in web.xml for seam-gen -------------------------------------------- Key: JBSEAM-1927 URL: http://jira.jboss.com/jira/browse/JBSEAM-1927 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.CR1 Reporter: Dan Allen Attachments: JBSEAM-1927-v1.txt The XSD schema URI in web.xml is still using the j2ee name rather than the javaee. This happened when migrating from 2.4 to 2.5, since more than just the version number needs to change. The correct line is: http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd basically, sed/j2ee/javaee/ Also, I feel that the servlet-api.jar file (stored in the lib directory of the root of the distribution) should be upgraded to 2.5. It is currently 2.4. You can grab the correct servlet jar from: http://repo1.maven.org/maven2/javax/servlet/servlet-api/2.5/servlet-api-2... -- 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, 9 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1933) WebRemoting in non-EJB environment anyway requires JMS library, even if JMS is not used.

by Dmitriy Lapko (JIRA)

WebRemoting in non-EJB environment anyway requires JMS library, even if JMS is not used. ---------------------------------------------------------------------------------------- Key: JBSEAM-1933 URL: http://jira.jboss.com/jira/browse/JBSEAM-1933 Project: JBoss Seam Issue Type: Patch Components: Remoting Affects Versions: 2.0.0.BETA1 Environment: Apache Tomcat 6.1, JBoss Seam 2.0.0.BETA1 nightly build 13.09.2007 Reporter: Dmitriy Lapko Assigned To: Shane Bryzak RequestHandlerFactory creates PollHandler even if JMS pooling is not used and not needed. In non-EJB environment it requires additional unused library with JMS classes. -- 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, 9 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1914) SEAM Example App: BLOG fails with XML Parser error

by Saeed Iqbal (JIRA)

SEAM Example App: BLOG fails with XML Parser error -------------------------------------------------- Key: JBSEAM-1914 URL: http://jira.jboss.com/jira/browse/JBSEAM-1914 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.0.BETA1 Environment: Windows XP Prof Reporter: Saeed Iqbal Priority: Critical Here is the string i put in a blog post to reproduce the error ------- lets see if we can test this thing. I(* D&23= ' ' '" /a sdrfd Okie dokke -------- Here is the error message XML Parsing Error: mismatched tag. Expected: </i>. Location: http://localhost:8080/seam-blog/seam/index.xhtml?conversationId=4 Line Number 37, Column 13:Okie dokke</p> ------------^ -- 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, 9 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1923) seam-gen does not generate "hibernate.dialect" in persistence.xml

by Simon Gunzenreiner (JIRA)

seam-gen does not generate "hibernate.dialect" in persistence.xml ----------------------------------------------------------------- Key: JBSEAM-1923 URL: http://jira.jboss.com/jira/browse/JBSEAM-1923 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.BETA1 Reporter: Simon Gunzenreiner seam-gen does not generate a "hibernate.dialect" propery in persistence.xml, although the hibernate.dialect property is collected and saved in hibernate-console.properties. Therefore some hibernate mappings and generated code can be incorrect. -- 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, 9 months

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1783) Add Hibernate Search support for JPA

by Emmanuel Bernard (JIRA)

Add Hibernate Search support for JPA ------------------------------------ Key: JBSEAM-1783 URL: http://jira.jboss.com/jira/browse/JBSEAM-1783 Project: JBoss Seam Issue Type: Feature Request Reporter: Emmanuel Bernard Assigned To: Emmanuel Bernard Priority: Minor Fix For: 2.0.0.CR1 -- 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, 9 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1851) Implement tags/topics for documents and topic plugin for blog view

by Christian Bauer (JIRA)

Implement tags/topics for documents and topic plugin for blog view ------------------------------------------------------------------ Key: JBSEAM-1851 URL: http://jira.jboss.com/jira/browse/JBSEAM-1851 Project: JBoss Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer -- 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, 9 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1853) Wiki diff is broken

by Christian Bauer (JIRA)

Wiki diff is broken ------------------- Key: JBSEAM-1853 URL: http://jira.jboss.com/jira/browse/JBSEAM-1853 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Some change broke the diff, the diff result looks wrong and there is one historical revision "too many" in the list. -- 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, 9 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1854) Context sensitive help system

by Christian Bauer (JIRA)

Context sensitive help system ----------------------------- Key: JBSEAM-1854 URL: http://jira.jboss.com/jira/browse/JBSEAM-1854 Project: JBoss Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Haven't decided yet if the help system is going to be based on separate data or if it's just some wiki documents in a specially named directory structure. -- 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, 9 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1857) ManagedEntityIdentityInterceptor nulls fields incorrectly in reentrant calls to conversation scoped components

by Kahli Burke (JIRA)

ManagedEntityIdentityInterceptor nulls fields incorrectly in reentrant calls to conversation scoped components -------------------------------------------------------------------------------------------------------------- Key: JBSEAM-1857 URL: http://jira.jboss.com/jira/browse/JBSEAM-1857 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Environment: Seam 2.0.0.BETA1, also jboss-seam-CVS.2007-08-22_00-49-47 Reporter: Kahli Burke Priority: Blocker When a conversation component method is called in a reentrant fashion, entity fields are nulled incorrectly. The scenario is as follows: I. Component A method is called A. entityIdsToRefs(). (reinject entity fields) B. Method invoked C. Component A calls method in object B D. Object B calls method in Component A. i. entityIdsToRefs() ii. Method invoked iii. entityRefsToIds(). (disinject entity fields, set to null, save in conversation) E. entityRefsToIds(). (fields are already null, so clearWrapper is called, and the objects are removed from the conversation) II. Component A method is called, values are null, and cannot be retrieved from the conversation context (they are in the removals map) The solution seems to be the same as what was done with the BijectionInterceptor in JBSEAM-631. I wonder if this also might be related to JBSEAM-1840? I've attached a patch that fixes the problem for me, please review. Thanks! -- 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, 9 months

5
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2007