December 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Resolved: (SOLDER-43) enforce JavaBean property rules

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SOLDER-43?page=com.atlassian.jira.plugin.... ] Dan Allen resolved SOLDER-43. ----------------------------- Fix Version/s: 3.0.0.Beta1 (was: 1.0.0.Beta2) Resolution: Done Updating fix version. > enforce JavaBean property rules > ------------------------------- > > Key: SOLDER-43 > URL: https://issues.jboss.org/browse/SOLDER-43 > Project: Seam Solder > Issue Type: Feature Request > Reporter: Dan Allen > Assignee: Dan Allen > Fix For: 3.0.0.Beta1 > > > Currently, the create property from method functionality of the Properties class does very little checking against the JavaBean conventions. Add more checks that the method is actually going to produce a property, throwing an exception if any rule is violated. > http://www.oracle.com/technetwork/java/javase/documentation/spec-136004.html -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Reopened: (SOLDER-39) Weldx has a compile scoped dependency on jta, should be scope <test>

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SOLDER-39?page=com.atlassian.jira.plugin.... ] Dan Allen reopened SOLDER-39: ----------------------------- Assignee: Stuart Douglas > Weldx has a compile scoped dependency on jta, should be scope <test> > -------------------------------------------------------------------- > > Key: SOLDER-39 > URL: https://issues.jboss.org/browse/SOLDER-39 > Project: Seam Solder > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 3.0.0.Beta1 > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (SOLDER-40) Introduce @Qualified to have package name prepended to @Named value

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SOLDER-40?page=com.atlassian.jira.plugin.... ] Dan Allen resolved SOLDER-40. ----------------------------- Fix Version/s: 3.0.0.Beta1 (was: 1.0.0.Beta2) Resolution: Done > Introduce @Qualified to have package name prepended to @Named value > ------------------------------------------------------------------- > > Key: SOLDER-40 > URL: https://issues.jboss.org/browse/SOLDER-40 > Project: Seam Solder > Issue Type: Feature Request > Reporter: Dan Allen > Assignee: Dan Allen > Priority: Minor > Fix For: 3.0.0.Beta1 > > > @Named gives the bean a name equal to the annotation value property or, if one is not specified, the decapitalized simple name of the type. This behavior is precisely what the majority of developers will appreciate. However, framework writers should avoid stomping on the root bean namespace, instead assigning qualified names to their built-in components. The motivation is the same as qualifying Java types. > One way to accomplish this would be to include the package name in the name specified in the @Named annotation: > @Named("org.jboss.seam.security.Identity") > public class Identity ... { ... } > However, this is not in the spirit of type-safety. As an alternative, Weld X can introduce an annotation which indicates that the bean name be qualified to the package in which the type resides. > @Qualified @Named > public class Identity ... { ... } > This allows the bean name to be defaulted and keeps the package out of a string. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (SOLDER-40) Introduce @Qualified to have package name prepended to @Named value

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SOLDER-40?page=com.atlassian.jira.plugin.... ] Dan Allen closed SOLDER-40. --------------------------- Updating fix version. > Introduce @Qualified to have package name prepended to @Named value > ------------------------------------------------------------------- > > Key: SOLDER-40 > URL: https://issues.jboss.org/browse/SOLDER-40 > Project: Seam Solder > Issue Type: Feature Request > Reporter: Dan Allen > Assignee: Dan Allen > Priority: Minor > Fix For: 3.0.0.Beta1 > > > @Named gives the bean a name equal to the annotation value property or, if one is not specified, the decapitalized simple name of the type. This behavior is precisely what the majority of developers will appreciate. However, framework writers should avoid stomping on the root bean namespace, instead assigning qualified names to their built-in components. The motivation is the same as qualifying Java types. > One way to accomplish this would be to include the package name in the name specified in the @Named annotation: > @Named("org.jboss.seam.security.Identity") > public class Identity ... { ... } > However, this is not in the spirit of type-safety. As an alternative, Weld X can introduce an annotation which indicates that the bean name be qualified to the package in which the type resides. > @Qualified @Named > public class Identity ... { ... } > This allows the bean name to be defaulted and keeps the package out of a string. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Reopened: (SOLDER-40) Introduce @Qualified to have package name prepended to @Named value

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SOLDER-40?page=com.atlassian.jira.plugin.... ] Dan Allen reopened SOLDER-40: ----------------------------- Assignee: Dan Allen > Introduce @Qualified to have package name prepended to @Named value > ------------------------------------------------------------------- > > Key: SOLDER-40 > URL: https://issues.jboss.org/browse/SOLDER-40 > Project: Seam Solder > Issue Type: Feature Request > Reporter: Dan Allen > Assignee: Dan Allen > Priority: Minor > Fix For: 3.0.0.Beta1 > > > @Named gives the bean a name equal to the annotation value property or, if one is not specified, the decapitalized simple name of the type. This behavior is precisely what the majority of developers will appreciate. However, framework writers should avoid stomping on the root bean namespace, instead assigning qualified names to their built-in components. The motivation is the same as qualifying Java types. > One way to accomplish this would be to include the package name in the name specified in the @Named annotation: > @Named("org.jboss.seam.security.Identity") > public class Identity ... { ... } > However, this is not in the spirit of type-safety. As an alternative, Weld X can introduce an annotation which indicates that the bean name be qualified to the package in which the type resides. > @Qualified @Named > public class Identity ... { ... } > This allows the bean name to be defaulted and keeps the package out of a string. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (SOLDER-41) add getSingleResult() to PropertyQuery

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SOLDER-41?page=com.atlassian.jira.plugin.... ] Dan Allen closed SOLDER-41. --------------------------- Updating fix version. > add getSingleResult() to PropertyQuery > -------------------------------------- > > Key: SOLDER-41 > URL: https://issues.jboss.org/browse/SOLDER-41 > Project: Seam Solder > Issue Type: Feature Request > Reporter: Dan Allen > Assignee: Dan Allen > Fix For: 3.0.0.Beta1 > > > PropertyQuery should offer the method getSingleResult() for the same reason it exists in the JPA Query interface: to fetch a single result but also assert that there is only one result to be fetched. If more than one property is matched when getSingleResult() is called, an exception will result. > Using getFirstResult() to return exactly one result is inappropriate (and could lead to bugs) because it could hide the fact that multiple properties are being inadvertently matched. As a workaround, the developer would currently have to run getResultList() to ensure only one property matches. Offering a getSingleResult() would resolve these issues. > See http://download.oracle.com/javaee/6/api/javax/persistence/Query.html#getS... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (SOLDER-41) add getSingleResult() to PropertyQuery

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SOLDER-41?page=com.atlassian.jira.plugin.... ] Dan Allen resolved SOLDER-41. ----------------------------- Fix Version/s: 3.0.0.Beta1 (was: 1.0.0.Beta2) Resolution: Done > add getSingleResult() to PropertyQuery > -------------------------------------- > > Key: SOLDER-41 > URL: https://issues.jboss.org/browse/SOLDER-41 > Project: Seam Solder > Issue Type: Feature Request > Reporter: Dan Allen > Assignee: Dan Allen > Fix For: 3.0.0.Beta1 > > > PropertyQuery should offer the method getSingleResult() for the same reason it exists in the JPA Query interface: to fetch a single result but also assert that there is only one result to be fetched. If more than one property is matched when getSingleResult() is called, an exception will result. > Using getFirstResult() to return exactly one result is inappropriate (and could lead to bugs) because it could hide the fact that multiple properties are being inadvertently matched. As a workaround, the developer would currently have to run getResultList() to ensure only one property matches. Offering a getSingleResult() would resolve these issues. > See http://download.oracle.com/javaee/6/api/javax/persistence/Query.html#getS... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Reopened: (SOLDER-41) add getSingleResult() to PropertyQuery

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SOLDER-41?page=com.atlassian.jira.plugin.... ] Dan Allen reopened SOLDER-41: ----------------------------- Assignee: Dan Allen > add getSingleResult() to PropertyQuery > -------------------------------------- > > Key: SOLDER-41 > URL: https://issues.jboss.org/browse/SOLDER-41 > Project: Seam Solder > Issue Type: Feature Request > Reporter: Dan Allen > Assignee: Dan Allen > Fix For: 3.0.0.Beta1 > > > PropertyQuery should offer the method getSingleResult() for the same reason it exists in the JPA Query interface: to fetch a single result but also assert that there is only one result to be fetched. If more than one property is matched when getSingleResult() is called, an exception will result. > Using getFirstResult() to return exactly one result is inappropriate (and could lead to bugs) because it could hide the fact that multiple properties are being inadvertently matched. As a workaround, the developer would currently have to run getResultList() to ensure only one property matches. Offering a getSingleResult() would resolve these issues. > See http://download.oracle.com/javaee/6/api/javax/persistence/Query.html#getS... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (SOLDER-39) Weldx has a compile scoped dependency on jta, should be scope <test>

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SOLDER-39?page=com.atlassian.jira.plugin.... ] Dan Allen closed SOLDER-39. --------------------------- Fix Version/s: 3.0.0.Beta1 (was: 1.0.0.Beta2) Resolution: Done Updating fix version. > Weldx has a compile scoped dependency on jta, should be scope <test> > -------------------------------------------------------------------- > > Key: SOLDER-39 > URL: https://issues.jboss.org/browse/SOLDER-39 > Project: Seam Solder > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 3.0.0.Beta1 > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Reopened: (SOLDER-43) enforce JavaBean property rules

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SOLDER-43?page=com.atlassian.jira.plugin.... ] Dan Allen reopened SOLDER-43: ----------------------------- Assignee: Dan Allen > enforce JavaBean property rules > ------------------------------- > > Key: SOLDER-43 > URL: https://issues.jboss.org/browse/SOLDER-43 > Project: Seam Solder > Issue Type: Feature Request > Reporter: Dan Allen > Assignee: Dan Allen > Fix For: 3.0.0.Beta1 > > > Currently, the create property from method functionality of the Properties class does very little checking against the JavaBean conventions. Add more checks that the method is actually going to produce a property, throwing an exception if any rule is violated. > http://www.oracle.com/technetwork/java/javase/documentation/spec-136004.html -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 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 December 2010