November 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2299) Seam Generate Entities creates edit field for @Version annotated fields

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-2299?page=comments#action_12389069 ] Max Andersen commented on JBSEAM-2299: -------------------------------------- thorsten please state which version of seam you are having issues with. > Seam Generate Entities creates edit field for @Version annotated fields > ----------------------------------------------------------------------- > > Key: JBSEAM-2299 > URL: http://jira.jboss.com/jira/browse/JBSEAM-2299 > Project: JBoss Seam > Issue Type: Bug > Reporter: Thorsten Kunz > Priority: Minor > > When you have an entity with a @Version annotation present (which is the default if you create it with "Seam Entity") and then run "Seam Generate Entities" on the project and select "use existing entities" the resulting CRUD pages will allow the version field to be edited. So you won't be able to create entities because the set accessor for the version was declared private in the entity. This renders the CRUD pages useless. > I think this field should not be editable in the first place. > Cheers, Thorsten -- 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

18 years, 4 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2245) Custom validator disables hibernate default validator

by dapeng wang (JIRA)

Custom validator disables hibernate default validator ----------------------------------------------------- Key: JBSEAM-2245 URL: http://jira.jboss.com/jira/browse/JBSEAM-2245 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.GA Reporter: dapeng wang Fix For: 2.0.1.GA The default hibernate validator doesn't work anymore, as soon as a custom validator is added to the component, though the text field is put inside a validateAll tag. In the class ValidateAllRendererBase following code is found, which is buggy in my opinion: if ( evh.getValidators().length==0 && evh.getValidators().length == 0 ) { evh.addValidator( new ModelValidator() ); } First of all, I don't understand, why you check the same condition twice. Second, I have no clue, why you only add the ModelValidator, if here is no other validator. I would exactly like to combine the hibernate validator with my custom one. Pleas remove the if check. I would also like to help and fix this bug. -- 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

18 years, 4 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2297) standard-jaxws-endpoint-config.xml filename in webservice chapter has a dash too much

by Paul Bakker (JIRA)

standard-jaxws-endpoint-config.xml filename in webservice chapter has a dash too much ------------------------------------------------------------------------------------- Key: JBSEAM-2297 URL: http://jira.jboss.com/jira/browse/JBSEAM-2297 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 2.0.0.GA Reporter: Paul Bakker Priority: Minor In the PDF reference documentation, in the webservice chapter, the standard-jaxws-endpoint-config.xml is described. Because of a line-wrap however, there is a dash added between jaxws, which makes the the filename like this: standard-jax-ws-endpoint-config.xml. Because this does not look wrong it's easy to think that the line-wrap dash is part of the filename. If the file is named like that, the webservice will throw "no application context available" exeptions when accessing a Seam component. -- 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

18 years, 4 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2200) Create events for successful login and failed login

by Shane Bryzak (JIRA)

Create events for successful login and failed login --------------------------------------------------- Key: JBSEAM-2200 URL: http://jira.jboss.com/jira/browse/JBSEAM-2200 Project: JBoss Seam Issue Type: Feature Request Components: Security Affects Versions: 2.0.0.GA Reporter: Shane Bryzak Assigned To: Shane Bryzak Fix For: 2.0.1.GA Identity should raise events for a successful login and a failed login, and the JSF-specific code in Identity should be refactored into a separate component (SecurityMessage ?), which is based on these new event types. -- 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

18 years, 4 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1257) default equals() on javabean components is not reflexive

by Matt Drees (JIRA)

default equals() on javabean components is not reflexive -------------------------------------------------------- Key: JBSEAM-1257 URL: http://jira.jboss.com/jira/browse/JBSEAM-1257 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Reporter: Matt Drees If a javabean component doesn't override equals(), the javassist proxy generated for it has a nonreflexive equals method. I.e., component.equals(component) returns false. -- 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

18 years, 4 months

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1081) s:enumItem should support itemLabel and itemValue attributes

by Pete Muir (JIRA)

s:enumItem should support itemLabel and itemValue attributes ------------------------------------------------------------ Key: JBSEAM-1081 URL: http://jira.jboss.com/jira/browse/JBSEAM-1081 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.0.GA Reporter: Pete Muir Priority: Optional This is what an f:selectItem supports, so we should at least support them, if not make them the default. -- 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

18 years, 4 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1099) s:button does not show both image and text

by Alex Narinsky (JIRA)

s:button does not show both image and text ------------------------------------------ Key: JBSEAM-1099 URL: http://jira.jboss.com/jira/browse/JBSEAM-1099 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.0.GA Reporter: Alex Narinsky I need to create a button that shows both text and image. I found that if I use s:button then after image specification the text does not show up. -- 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

18 years, 4 months

4
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1912) Incorrect graphicImage attribute in validation.xml

by Ali Sadik Kumlali (JIRA)

Incorrect graphicImage attribute in validation.xml -------------------------------------------------- Key: JBSEAM-1912 URL: http://jira.jboss.com/jira/browse/JBSEAM-1912 Project: JBoss Seam Issue Type: Patch Components: Documentation Affects Versions: 2.0.0.BETA1 Environment: Does not matter Reporter: Ali Sadik Kumlali Priority: Trivial Hi, <h:graphicImage/> does not have "src" attribute as shown in http://docs.jboss.com/seam/2.0.0.B1/reference/en/html/validation.html and it must be replaced by "value". Incorrect: <h:graphicImage src="img/error.gif" rendered="#{invalid}"/> Correct: <h:graphicImage value="/img/error.gif" rendered="#{invalid}"/> Please also note that "/" character preceding "img". An extra information that explains where to put "img" folder would be useful, as well. Regards, Ali Sadik Kumlali -- 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

18 years, 4 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1385) Use ELResolver instead of Namespace extends Map for namespaces

by Gavin King (JIRA)

Use ELResolver instead of Namespace extends Map for namespaces -------------------------------------------------------------- Key: JBSEAM-1385 URL: http://jira.jboss.com/jira/browse/JBSEAM-1385 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Minor Fix For: 1.3.0.ALPHA That's more elegant. -- 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

18 years, 4 months

1
3
0 / 0

[jbossseam-issues] Accessing entities outside of injection

by David Radunz

Hey, Not sure if this is the correct list to be posting to, if it isn't please advise the appropriate place. I have a web application that does not use persistence (hibernate) as we have a non-database data source and a custom mediation layer between that and Seam. I have a need to get a new (or existing) instance of a named entity (or what ever: action/controller as well) by code. The reason I am posting a request to the mailing list is because we are using the @Install annotation and as such I cannot instantiate the class directly because I of course want the "installed" version. Something like the following would be great.. --------------------------- package test.product; @Name("person") @Install(1) public class Person { } --------------------------- --------------------------- package test.site; @Name("person") @Install(2) public class Person extends test.product.Person { } --------------------------- And then in code somewhere use "person" to obtain a new or existing instance of "test.site.Person" (being the installed version). Perhaps some sort of EL resolving code? Any ideas? David -- David Radunz Senior Developer Utiba Pty Ltd ph: +613 9606 0444 ad: Level 6, 190 Queen St, Melbourne, VIC, 3000, Australia

18 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2007