[webbeans-dev] standard name for conversation
by Dan Allen
It would seem very useful if certain components had standard names. For
instance, it is quite common to consult the conversation object in JSF via
the EL. I would hate for different implementations to use different names
making the reference to the conversation non-portable. Would it be
reasonable to make javax.context.conversation the standard name?
e.g. #{javax.context.conversation.longRunning}
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.
15 years, 7 months
[webbeans-dev] Fwd: Today's spec
by Gavin King
Latest
---------- Forwarded message ----------
From: Gavin King <gavin.king(a)gmail.com>
Date: Thu, May 14, 2009 at 7:13 PM
Subject: Today's spec
To: Java Community Process JSR #299 Expert List <JSR-299-EG(a)jcp.org>
This revision includes the following changes:
* use of META-INF/services in 10.5, 11.2
* 10.4.3. The ObserverMethod interface
* 10.5.7. ProcessObserver event
* support for @Decorates on any injection point in 8.1.2, 5.4.9.
* changes to Decorator and Interceptor interfaces 10.1.1./10.1.2
* changes to @New in 3.11
* improved support for parameterized types 5.1.1
* changes to Appendix C (packages) for discussion only
If it's OK with you guys I would like to circulate a draft of the spec
to the community next week, so please take a look at this draft and
let me know if there are any show stoppers here.
Thanks!
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
15 years, 7 months
[webbeans-dev] Supporting proxies with no no-arg constructors in RI
by Jason T. Greene
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()
--
Jason T. Greene
JBoss, a division of Red Hat
15 years, 7 months
[webbeans-dev] @New
by Pete Muir
Since the change in the spec defining that there is a new bean for
every bean, we lost the language that disallows:
@New @SomeOtherBinding Foo foo;
AFAICT it still makes sense to disallow this. So, should that language
be there?
We also lost the language that disallows specific declaration of a
Bean as having @New as a binding type.
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
15 years, 7 months
[webbeans-dev] Latest
by Gavin King
Here's the latest. Esp. check out:
* the redesign of Instance and Event: 5.5, 8.5
* the SPIs in 9.3, 9.4
* initialization events redesign 10.4
* JMS event mappings 8.7
* Injectable references 5.4.1
* Dependent objects 6.4.1-6.4.2
* Changes to Bean/BeanManager in 9.1,9.2
* Resource declarations 3.6.1, 3.7.2
And note the removal of almost all XML.
I really need feedback from you guys on all this stuff...
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
15 years, 7 months
[webbeans-dev] Fwd: Major new revision of the specification
by Gavin King
Folks, please take a look through this...
---------- Forwarded message ----------
From: Gavin King <gavin.king(a)gmail.com>
Date: Sat, May 9, 2009 at 7:34 PM
Subject: Re: Major new revision of the specification
To: Java Community Process JSR #299 Expert List <JSR-299-EG(a)jcp.org>
And here's the spec :-)
On Sat, May 9, 2009 at 7:32 PM, Gavin King <gavin.king(a)gmail.com> wrote:
> The attached spec draft aims to address the following criticisms made
> by Sun, IBM and others:
>
> * the the spec is difficult to read and understand
> * that the spec defines too many implementation details
>
> I've made the following major sets of changes:
>
> * redefinition of all semantics without reference to BeanManager
> * separation of material relating to the BeanManager, Bean and
> framework integration into a separate chapter
> * overall reorganization or material
>
> In order to make it possible to define all semantics in words instead
> of code, several new terms were defined:
>
> * injectable reference
> * contextual reference
> * contextual instance
>
> I've also partially written up several proposals from other threads:
>
> * annotation-based event mappings
> * new APIs to simplify implementation of the Bean interface
> * changes to the BeanManager interface
> * enhancement to the Instance interface
> * renamed @Initialized / @Deployed to @AfterBeanDiscovery /
> @AfterDependencyValidation
>
> Overall, I believe that this is a really major improvement, but it
> certainly needs a really thorough review, especially the following
> sections:
>
> * 6.5, 6.4.2
> * 5.4 - 5.6
> * 9.2 - 9.4
>
>
> --
> Gavin King
> gavin.king(a)gmail.com
> http://in.relation.to/Bloggers/Gavin
> http://hibernate.org
> http://seamframework.org
>
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
15 years, 7 months
