[webbeans-dev] May we ditch the ScopeType annotation?
by Mark Struberg
Hi!
Just a few thoughts.
If we need our applications to use the @ScopeType annotation instead of the @Scope which is defined in JSR-330, we will never get apps for JSR-330 running on our System.
Since Bob planes to introduce a portable SPI (as we currently have) for context implementations, it is imho increasingly important that we have to fully support @Scope. I think Bobs idea with the SPI is rubbish for JSR-330 as he will end up with the full blown complexity like we have, but being able to handle @Scope and only having to rewrite the Context implementations for it without touching the other parts of the app would be a huge improvement.
So why do we need the ScopeType instead of only using javax.inject.Scope?
a) normal scope vs pseudo scope
b) marking passivation capable scopes
anything missing?
Imho all the information currently residing in @ScopeType may easily be moved to the Context! So I think it does make no difference if the annotations knows about if a scope is a normal scope or if the Context of that very scope knows about it as long as the info is there at the time the actual contextual instance gets created.
So my proposal is as following:
.) ditch ScopeType
.) ditch NormalScope
.) add isNormalScope() and isPassivating() to the Context interface or somewhere else in that area
Wdyt?
txs and LieGrue,
strub
14 years, 8 months
Re: [webbeans-dev] Web Beans Trunk Compilation Errors
by Roger Kitain
Roger Kitain wrote:
> CCing Dan Allen as well..
>
> Roger Kitain wrote:
>> Hi Pete -
>>
>> Just did the following on my copy of the trunk:
>>
>> svn update
>> mvn clean
>> mvn -U install
>>
>> and I'm getting a bunch of compilation errors:
>>
>> [INFO] Building Web Beans Service Provider Interfaces
>> [INFO] task-segment: [install]
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [enforcer:enforce {execution: enforce}]
>> [INFO] [resources:resources]
>> [INFO] Using default encoding to copy filtered resources.
>> [INFO] [compiler:compile]
>> [INFO] Compiling 46 source files to
>> /Users/rogerk/webbeans/integration/webbeans-source/trunk/spi/target/classes
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Compilation failure
>>
>> /Users/rogerk/webbeans/integration/webbeans-source/trunk/spi/src/main/java/org/jboss/webbeans/bootstrap/api/Environments.java:[26,49]
>> cannot find symbol
>> symbol : class JSFServices
>> location: package org.jboss.webbeans.persistence.spi.helpers
>>
>> /Users/rogerk/webbeans/integration/webbeans-source/trunk/spi/src/main/java/org/jboss/webbeans/bootstrap/api/Environments.java:[30,37]
>> cannot find symbol
>> symbol : class ServletServices
>> location: package org.jboss.webbeans.servlet.api
>>
>> /Users/rogerk/webbeans/integration/webbeans-source/trunk/spi/src/main/java/org/jboss/webbeans/bootstrap/api/Environments.java:[46,185]
>> cannot find symbol
>> symbol : class ServletServices
>> location: class org.jboss.webbeans.bootstrap.api.Environments
>>
>> /Users/rogerk/webbeans/integration/webbeans-source/trunk/spi/src/main/java/org/jboss/webbeans/bootstrap/api/Environments.java:[46,208]
>> cannot find symbol
>> symbol : class JSFServices
>> location: class org.jboss.webbeans.bootstrap.api.Environments
>>
>> /Users/rogerk/webbeans/integration/webbeans-source/trunk/spi/src/main/java/org/jboss/webbeans/bootstrap/api/Environments.java:[51,197]
>> cannot find symbol
>> symbol : class ServletServices
>> location: class org.jboss.webbeans.bootstrap.api.Environments
>>
>> /Users/rogerk/webbeans/integration/webbeans-source/trunk/spi/src/main/java/org/jboss/webbeans/bootstrap/api/Environments.java:[51,220]
>> cannot find symbol
>> symbol : class JSFServices
>> location: class org.jboss.webbeans.bootstrap.api.Environments
>>
>> /Users/rogerk/webbeans/integration/webbeans-source/trunk/spi/src/main/java/org/jboss/webbeans/bootstrap/api/Environments.java:[56,51]
>> cannot find symbol
>> symbol : class ServletServices
>> location: class org.jboss.webbeans.bootstrap.api.Environments
>>
>> Pete Muir wrote:
>>> Ok, good feedback. If Roger is able to help out by doing the Maven
>>> portion of the release (as he did for the fixes he needed for
>>> PREVIEW2) then that would be great! Especially as I am travelling
>>> that week for JBoss World, me doing the release is unlikely to work
>>> well.
>>>
>>> As I wrote below, I think we can have 330 integration within 10 days
>>> (so basically a week on Monday) assuming Gavin can get the PFD2 out
>>> by middle of next week.
>>>
>>> On 20 Aug 2009, at 18:47, Barbara Louis wrote:
>>>
>>>> Hi Pete,
>>>>
>>>> Talked to Ken - he would like to get his hands on preview3. But as
>>>> discussed earlier it need not be a release but needs to be a stable
>>>> build.
>>>>
>>>> Will wait for Roger to return on Mon to see how we can work this
>>>> out to use preview3 build/ tag etc. We can decide then.
>>>>
>>>> We are definitely looking forward to a first integration of 330 as
>>>> soon as possible. Timeline for this will be useful for us.
>>>>
>>>> Steve will answer your question on TCK.
>>>>
>>>> Thanks,
>>>> Barbara
>>>>
>>>> Pete Muir wrote:
>>>>> Hi
>>>>>
>>>>> After Gavin having published the preview draft of PFD2, I have no
>>>>> real reason now to release PREVIEW3, but instead would prefer to
>>>>> push on the FCS release. Doing a full release is both time
>>>>> consuming and a distraction from the real goal of the FCS.
>>>>> Therefore I propose that I branch trunk once 330 integration is in
>>>>> (probably in about 10 days), but still not at CR1. This would then
>>>>> give the GF team a stable base to make a release against, and do
>>>>> another integration round.
>>>>>
>>>>> Then we would release the FCS in about 3-4 weeks (TCK in about 3
>>>>> weeks) from now.
>>>>>
>>>>> Whilst we are talking about schedules, I am interested as to how
>>>>> far you (Sun) have got running the TCK inside GlassFish, as this
>>>>> will really give the integration a good workout - especially the
>>>>> deployment structure work I'm currently working on for the RI, and
>>>>> will add to the TCK tests in the next week or so.
>>>>>
>>>>> Thanks,
>>>
>>
>
14 years, 8 months
[webbeans-dev] @NormalScope and @Singleton
by Mark Struberg
Hi!
I'm a bit confused about the description of the pseudo scopes in the latest spec (but it's really late here, so I might missed the point)
a) ch 6.3:
> Any scope that is not a normal scope is called a pseudo-scope.
-> @Singleton [1] is per se only @Scope but not @NormalScope,
> The concept of a current instance is not well-defined in the case of a pseudo-scope.
-> but instances of @Singleton are pretty well defined, isn't?
Maybe we should introduce @Passivating and @PseudoScope instead of @NormalScope and invert the logic?
b) ch 6.3
> All pseudo-scopes must be explicitly declared @NormalScope,
> to indicate to the container that no client proxy is required.
vs ch 5.5
> A contextual reference to a bean with a normal scope ...
> ..not a direct reference...
> Instead, the contextual reference is a client proxy object.
I'd say pseudo scopes must _not_ declare @NormalScope?
txs and LieGrue,
strub
[1] http://atinject.googlecode.com/svn/trunk/javadoc/javax/inject/Singleton.html
14 years, 8 months
[webbeans-dev] Java 6?
by Pete Muir
Hi all,
I want to gather some feedback on whether everyone is happy if we make
Java 6 a requirement for Web Beans. This will simplify the build
slightly.
JBoss 5.2 will require Java 6 (AFAIK), and I assume GlassFish will do
as well.
Anyone got strong opinions either way?
Pete
14 years, 8 months
[webbeans-dev] Spec draft with 330 annotations
by Sven Linstaedt
Hello,
sorry for not being able to answer to the original mail. I was not
subscribed until now.
Correct me, if I am wrong, but as I am reading through the updated specs it
seems the @Initializer becomes obsolete. Instead @Inject should be used. If
this is the case, there is another small issue in the document with still
using the term "@Initializer" at page 78.
Best regards,
Sven
14 years, 8 months
[webbeans-dev] Copyright headers
by Pete Muir
Hi all,
We have been informed that the standard copyright headers which we
apply to source files are in error. They currently read "Copyright
<Year>, Red Hat Middleware LLC," when in fact they should read
"Copyright <Year>, Red Hat, Inc. and/or its
affiliates,". Please change your templates going forward; there is no
need to retroactively apply this change immediately. In the not-to-
distant future I will run a tool over all files in the Web Beans
project to update them.
I've also updated the website and the docs.
Pete
14 years, 8 months
