March 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Commented: (WELD-56) Supporting proxies with no no-arg constructors

by Nicklas Karlsson (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-56?page=com.atlassian.jira.plugin... ] Nicklas Karlsson commented on WELD-56: -------------------------------------- Where should this be done? Integrated into the core code or move instance construction behind the SPI? > Supporting proxies with no no-arg constructors > ---------------------------------------------- > > Key: WELD-56 > URL: https://jira.jboss.org/jira/browse/WELD-56 > Project: Weld > Issue Type: Feature Request > Components: Scopes & Contexts > Reporter: Pete Muir > Fix For: 1.1.0.BETA1 > > > On Tue, May 12, 2009 at 1:11 AM, Jason T. Greene > <jason.greene(a)redhat.com> wrote: > Hi Everyone, > As a non-standard extension, I was thinking that we could support generation > proxies of classes not containing no-arg constructors by using various > techniques that are supported by most JDKs. > This would involve generating a proxy with a constructor call passing bogus > parameters. Then a JDK specific approach would be used to instantiate the > proxy class: > Sun, IcedTea, Mac: Unsafe.allocateInstance() - The most efficient > Above + IBM, JRockit: ReflectionFactory.newConstructorForSerialization() -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Assigned: (WELD-56) Supporting proxies with no no-arg constructors

by Nicklas Karlsson (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-56?page=com.atlassian.jira.plugin... ] Nicklas Karlsson reassigned WELD-56: ------------------------------------ Assignee: Nicklas Karlsson > Supporting proxies with no no-arg constructors > ---------------------------------------------- > > Key: WELD-56 > URL: https://jira.jboss.org/jira/browse/WELD-56 > Project: Weld > Issue Type: Feature Request > Components: Scopes & Contexts > Reporter: Pete Muir > Assignee: Nicklas Karlsson > Fix For: 1.1.0.BETA1 > > > On Tue, May 12, 2009 at 1:11 AM, Jason T. Greene > <jason.greene(a)redhat.com> wrote: > Hi Everyone, > As a non-standard extension, I was thinking that we could support generation > proxies of classes not containing no-arg constructors by using various > techniques that are supported by most JDKs. > This would involve generating a proxy with a constructor call passing bogus > parameters. Then a JDK specific approach would be used to instantiate the > proxy class: > Sun, IcedTea, Mac: Unsafe.allocateInstance() - The most efficient > Above + IBM, JRockit: ReflectionFactory.newConstructorForSerialization() -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Closed: (WELD-58) Move conversation lifecycle methods into ContextLifecycle

by Nicklas Karlsson (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-58?page=com.atlassian.jira.plugin... ] Nicklas Karlsson closed WELD-58. -------------------------------- Fix Version/s: 1.0.2.CR1 (was: 1.1.0.BETA1) Resolution: Done Accidently done when applying the ConversationManager interface ;-) > Move conversation lifecycle methods into ContextLifecycle > --------------------------------------------------------- > > Key: WELD-58 > URL: https://jira.jboss.org/jira/browse/WELD-58 > Project: Weld > Issue Type: Feature Request > Components: Scopes & Contexts > Reporter: Pete Muir > Fix For: 1.0.2.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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (WELD-331) Stop using exceptions for flow control in DefaultServiceLoader, it is a mess

by Pete Muir (JIRA)

Stop using exceptions for flow control in DefaultServiceLoader, it is a mess ---------------------------------------------------------------------------- Key: WELD-331 URL: https://jira.jboss.org/jira/browse/WELD-331 Project: Weld Issue Type: Feature Request Components: Reflection layer Reporter: Pete Muir Fix For: 1.0.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, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (WELD-457) 4.11. The InjectionPoint object example is non-functional

by Matthieu Chase Heimer (JIRA)

4.11. The InjectionPoint object example is non-functional --------------------------------------------------------- Key: WELD-457 URL: https://jira.jboss.org/jira/browse/WELD-457 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.0.1.Final Reporter: Matthieu Chase Heimer http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html_single/index.... There are 3 code blocks dealing with an HTTP param example (after the logger example) In the first block @BindingType should be @Qualifier In the second block each line should start with @Inject In the third example the producer method uses parameter injection to get a ServletRequest object. ServletRequest is not a valid object to inject which kind of kills the whole example. In fact the note under section "15.1. Built-in beans" says that it may not work and even if it did it would be a bad idea. -- 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, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (WELD-456) Example of transactional observer won't compile

by Matthieu Chase Heimer (JIRA)

Example of transactional observer won't compile ----------------------------------------------- Key: WELD-456 URL: https://jira.jboss.org/jira/browse/WELD-456 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.0.1.Final Reporter: Matthieu Chase Heimer Priority: Minor >From the last code example in section 11.7: http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html_single/#d0e4211 I think you meant for that second addProduct method to be named something else. @ApplicationScoped @Singleton public class Catalog { void addProduct(@Observes(during = AFTER_SUCCESS) @Created Product product) { products.add(product); } void addProduct(@Observes(during = AFTER_SUCCESS) @Deleted Product product) { products.remove(product); } } -- 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, 1 month

3
2
0 / 0

[JBoss JIRA] Commented: (WELD-26) Add database support to login example

by Rob van den Bogaard (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-26?page=com.atlassian.jira.plugin... ] Rob van den Bogaard commented on WELD-26: ----------------------------------------- Thanks for your reply! I checked out the examples trunk from anonsvn and incorporated my (few) additions. I still have the problem though that nothing seems to be written to the database, and my head is spinning a bit, because from the book it seems that I have to add a lot more than just a call to userDatabase.persist(newUser)... (Probably I mix contexts and should let the register action have its own class instead of taking advantage of the login class - as in login.register().) > Add database support to login example > ------------------------------------- > > Key: WELD-26 > URL: https://jira.jboss.org/jira/browse/WELD-26 > Project: Weld > Issue Type: Feature Request > Components: Examples > Reporter: Pete Muir > Fix For: 1.0.2.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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (WELD-468) Weld should give better error message about why it can't proxy a class

by Pete Muir (JIRA)

Weld should give better error message about why it can't proxy a class ---------------------------------------------------------------------- Key: WELD-468 URL: https://jira.jboss.org/jira/browse/WELD-468 Project: Weld Issue Type: Bug Components: Class Beans (Managed and Session), Producers (Methods, Fields and Disposers) Affects Versions: 1.0.1.Final Reporter: Pete Muir Priority: Minor Fix For: 1.0.2.CR1 For a bean like @Entity @Named @RequestScoped public class Plot extends RObject { ... } we get an error like Caused by: javax.enterprise.inject.UnproxyableResolutionException: Normal scoped bean org.jboss.weld.bean-/home/ss141213/NetBeansProjects/ear1/dist/gfdeploy/ear1/ear1-ejb_jar/-ManagedBean-class org.vgcowa.dm.Plot is not proxyable which was caused by a final method. Not a useful error message! -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Assigned: (WELD-4) Bean validation needs to be more verbose/exact

by Nicklas Karlsson (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-4?page=com.atlassian.jira.plugin.... ] Nicklas Karlsson reassigned WELD-4: ----------------------------------- Assignee: Nicklas Karlsson (was: David Allen) > Bean validation needs to be more verbose/exact > ---------------------------------------------- > > Key: WELD-4 > URL: https://jira.jboss.org/jira/browse/WELD-4 > Project: Weld > Issue Type: Feature Request > Components: Bootstrap and Metamodel API > Affects Versions: 1.0.0.ALPHA2 > Reporter: Nicklas Karlsson > Assignee: Nicklas Karlsson > Priority: Critical > Fix For: 1.0.2.CR1 > > > e.g. the checks for unproxyable dependencies all go through Proxies.isTypeProxyable, returning a boolean for several conditions that result in failures, making tracking down the true cause difficult -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (WELDX-23) Support servlet injection on Jetty

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELDX-23?page=com.atlassian.jira.plugi... ] Pete Muir commented on WELDX-23: -------------------------------- Excellent work. I am on vacation until early April, but I will review when I am back for sure! If we can do the same for Tomcat, then we are in great shape. > Support servlet injection on Jetty > ---------------------------------- > > Key: WELDX-23 > URL: https://jira.jboss.org/jira/browse/WELDX-23 > Project: Weld Extensions > Issue Type: Feature Request > Components: Servlet Containers > Reporter: Pete Muir > Assignee: Matija Mazi > Attachments: jetty-injection.patch, jetty-injection.patch, jetty-injection.patch, jetty-injection.patch, jetty-web.xml, myapp-context.xml > > -- 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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues March 2010