January 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMPERSIST-20) @Transactional fails with weld 1.1.0.Final

by Stuart Douglas (JIRA)

@Transactional fails with weld 1.1.0.Final ------------------------------------------ Key: SEAMPERSIST-20 URL: https://issues.jboss.org/browse/SEAMPERSIST-20 Project: Seam Persistence Issue Type: Bug Affects Versions: 3.0.0.Beta1 Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 3.0.0.Beta2 The transaction interceptor is incorrectly looking at the proxy class instead of the bean class -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (SOLDER-69) Solder Messages are *extremely* slow in AnnotatedTypeBuilder, should not be used in such a performance sensitive place

by Lincoln Baxter III (JIRA)

Solder Messages are *extremely* slow in AnnotatedTypeBuilder, should not be used in such a performance sensitive place ---------------------------------------------------------------------------------------------------------------------- Key: SOLDER-69 URL: https://issues.jboss.org/browse/SOLDER-69 Project: Seam Solder Issue Type: Bug Components: Reflections Affects Versions: 3.0.0.Beta2 Reporter: Lincoln Baxter III Priority: Critical According to my YourKit profile of Seam Forge bootstrap, the following message bundle lookup is responsible for roughly 80% of boot-up time, just from all the instances of AnnotationBuilder and related classes that solder creates on EVERY Weld bootstrap. Obviously this could be simply removed and replaced with non-i18n messages, or these messages could be cached and loaded in a more performant manner... IMO, this is going to be a huge problem with messages. JBoss logging is slow, but message bundle lookup is much slower. The two offenders are the following methods - consider making them static, since this only needs to be done once per JVM: public class AnnotationBuilder { private transient static AnnotatedMessages messages = Messages.getBundle(AnnotatedMessages.class); ... } public class AnnotatedTypeBuilder<T> { private transient static AnnotatedMessages messages = Messages.getBundle(AnnotatedMessages.class); ... } -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
6
0 / 0

[JBoss JIRA] Updated: (SOLDER-34) Add validation of annotation retention and target to ServiceHandler

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/SOLDER-34?page=com.atlassian.jira.plugin.... ] Shane Bryzak updated SOLDER-34: ------------------------------- Fix Version/s: 3.0.0.Beta3 (was: 3.0.0.Beta2) > Add validation of annotation retention and target to ServiceHandler > ------------------------------------------------------------------- > > Key: SOLDER-34 > URL: https://issues.jboss.org/browse/SOLDER-34 > Project: Seam Solder > Issue Type: Feature Request > Components: Service Handler > Affects Versions: 3.0.0.Beta1 > Reporter: Pete Muir > Priority: Minor > Fix For: 3.0.0.Beta3 > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (SOLDER-26) Tighten validations on generic beans

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/SOLDER-26?page=com.atlassian.jira.plugin.... ] Shane Bryzak updated SOLDER-26: ------------------------------- Fix Version/s: 3.0.0.Beta3 (was: 3.0.0.Beta2) > Tighten validations on generic beans > ------------------------------------ > > Key: SOLDER-26 > URL: https://issues.jboss.org/browse/SOLDER-26 > Project: Seam Solder > Issue Type: Feature Request > Components: Generic Beans, Validation > Affects Versions: 3.0.0.Beta1 > Reporter: Pete Muir > Priority: Optional > Fix For: 3.0.0.Beta3 > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (SOLDER-23) Provide utility to extract type parameter from Instance

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/SOLDER-23?page=com.atlassian.jira.plugin.... ] Shane Bryzak updated SOLDER-23: ------------------------------- Fix Version/s: 3.0.0.Beta3 (was: 3.0.0.Beta2) > Provide utility to extract type parameter from Instance > ------------------------------------------------------- > > Key: SOLDER-23 > URL: https://issues.jboss.org/browse/SOLDER-23 > Project: Seam Solder > Issue Type: Feature Request > Components: Reflections > Affects Versions: 3.0.0.Beta1 > Reporter: Dan Allen > Assignee: Dan Allen > Priority: Minor > Fix For: 3.0.0.Beta3 > > > When discovering injection points, a type of Instance<T> is effectively the same as discovering a type T. You don't want to create a producer method for an Instance, for instance, hence why you want to figure out what T is. Thus, it's common to want to extract the type parameter from Instance. Having a utility would be convenient. > Here's an example that collects the actual bean types (extracting from the Instance type parameter if necessary) > Set<Type> types = new HashSet<Type>(); > for (InjectionPoint ip : event.getInjectionTarget().getInjectionPoints()) > { > types.add(Reflections.getActualType(ip.Type())); > } > Here's the utility: > private static Type getActualType(Type t) > { > if (t instanceof ParameterizedType && ((ParameterizedType) t).getRawType().equals(Instance.class)) > { > return ((ParameterizedType) t).getActualTypeArguments()[0]; > } > return t; > } -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (SOLDER-22) Cause a definition error if a unwrapping producer method declares a scope

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/SOLDER-22?page=com.atlassian.jira.plugin.... ] Shane Bryzak updated SOLDER-22: ------------------------------- Fix Version/s: 3.0.0.Beta3 (was: 3.0.0.Beta2) > Cause a definition error if a unwrapping producer method declares a scope > ------------------------------------------------------------------------- > > Key: SOLDER-22 > URL: https://issues.jboss.org/browse/SOLDER-22 > Project: Seam Solder > Issue Type: Feature Request > Components: Unwraps > Affects Versions: 3.0.0.Beta1 > Reporter: Pete Muir > Fix For: 3.0.0.Beta3 > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (SOLDER-19) Better validation for @Unwraps

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/SOLDER-19?page=com.atlassian.jira.plugin.... ] Shane Bryzak updated SOLDER-19: ------------------------------- Fix Version/s: 3.0.0.Beta3 (was: 3.0.0.Beta2) > Better validation for @Unwraps > ------------------------------ > > Key: SOLDER-19 > URL: https://issues.jboss.org/browse/SOLDER-19 > Project: Seam Solder > Issue Type: Feature Request > Components: Unwraps > Affects Versions: 3.0.0.Beta1 > Reporter: Stuart Douglas > Fix For: 3.0.0.Beta3 > > > - ensure type is proxiable > - ensure declaring bean is normal scoped -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (SOLDER-14) Provide utility to check if Type is assignable to another Type

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/SOLDER-14?page=com.atlassian.jira.plugin.... ] Shane Bryzak updated SOLDER-14: ------------------------------- Fix Version/s: 3.0.0.Beta3 (was: 3.0.0.Beta2) > Provide utility to check if Type is assignable to another Type > -------------------------------------------------------------- > > Key: SOLDER-14 > URL: https://issues.jboss.org/browse/SOLDER-14 > Project: Seam Solder > Issue Type: Feature Request > Components: Reflections > Affects Versions: 3.0.0.Beta1 > Reporter: Dan Allen > Assignee: Dan Allen > Priority: Minor > Fix For: 3.0.0.Beta3 > > > Often times when writing an extension, you need to know if one Type is assignable from another Type. This is a more sophisticated version of Class#isAssignableFrom(Class) which takes into account paramaterized types. > given > parameterized type Bean<N extends Number> > then > type Bean<Number> is assignable from type Bean<Integer> > One area where this is useful is when checking if a bean type is more specific than another bean type. It's not sufficient to assume the bean type is a simple class. > Something similar to what is provided by: http://google-gson.googlecode.com/svn-history/r442/trunk/gson/src/main/ja... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (SOLDER-13) Include type safe-properties extension

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/SOLDER-13?page=com.atlassian.jira.plugin.... ] Shane Bryzak updated SOLDER-13: ------------------------------- Fix Version/s: 3.0.0.Beta3 (was: 3.0.0.Beta2) > Include type safe-properties extension > -------------------------------------- > > Key: SOLDER-13 > URL: https://issues.jboss.org/browse/SOLDER-13 > Project: Seam Solder > Issue Type: Feature Request > Components: Core > Affects Versions: 3.0.0.Beta1 > Reporter: Pete Muir > Fix For: 3.0.0.Beta3 > > > See http://in.relation.to/Bloggers/AnotherNicePortableExtension -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (SOLDER-12) Add isMetadataChanged() accessor to AnnotatedTypeBuilder

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/SOLDER-12?page=com.atlassian.jira.plugin.... ] Shane Bryzak updated SOLDER-12: ------------------------------- Fix Version/s: 3.0.0.Beta3 (was: 3.0.0.Beta2) > Add isMetadataChanged() accessor to AnnotatedTypeBuilder > -------------------------------------------------------- > > Key: SOLDER-12 > URL: https://issues.jboss.org/browse/SOLDER-12 > Project: Seam Solder > Issue Type: Feature Request > Components: Builders > Affects Versions: 3.0.0.Beta1 > Reporter: Dan Allen > Assignee: Dan Allen > Priority: Minor > Fix For: 3.0.0.Beta3 > > > As an optimization, it makes sense to only create the AnnotatedType and assign it to ProcessAnnotatedType if the metadata has changed in anyway. Otherwise, you are wrapping the type just for the sake of wrapping it. > Therefore, I propose that any change to the state of the annotated type be tracked by a changed flag that is accessible by calling the AnnotatedTypeBuilder#isMetadataChanged() (or similarly named) method. It would be used as follows: > AnnotatedTypeBuilder b = AnnotatedTypeBuilder.readFromType(event.getAnnotatedType(), true); > // do extension logic > if (b.isMetadataChanged()) > { > event.setAnnotatedType(b.create()); > } -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2011