nope, I don't think we made some archetypes yet :(
The main problem with archtetypes for OWB is that we'd need 6 of them ;)
We discussed about creating some pure pom modules which 'bundle' OWB parts
together for providing the right dependencies out of the box + preconfigured
Hi!
I've created OWB-206 and checked in a unit test which demonstrates the blocker!
I know that the build is currently broken therefore, but it's really important
that we fix this issue asap!
LieGrue,
strub
__
Do You Yahoo!?
Sie sind Spam leid?
to get instance that is specified in the
specification explicitly.
This is just a quick try, but I will look at your test
class after you
check in.
Thanks ;
--Gurkan
From: Mark Struberg strub...@yahoo.de
To: openwebbeans-dev
[
https://issues.apache.org/jira/browse/OWB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OWB-206:
--
Attachment: OWB-206-rfc.patch
proxies only get injected for the 1st instance of a bean
instance of a bean
An: openwebbeans-dev@incubator.apache.org
Datum: Montag, 21. Dezember 2009, 20:16
I added this section for some reasons
that I do not remember now!
I will look at it
From: Mark Struberg (JIRA) j...@apache.org
To: openwebbeans-dev
[
https://issues.apache.org/jira/browse/OWB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-206.
---
Resolution: Fixed
proxies only get injected for the 1st instance of a bean
Hi!
Just a short mail to ensure that we take care of a few things:
.) Are our proxies 100% thread safe? Because we currently only create one proxy
instance for all instances of a specific bean. Which means that parallel
requests coming through a web server may result in concurrent proxy
sorry, that slipped in.
I will release 1.1 in the next few weeks, but actually it should work with 1.0
too.
Will downgrade now.
txs and LieGrue,
strub
--- Gurkan Erdogdu gurkanerdo...@yahoo.com schrieb am So, 20.12.2009:
Von: Gurkan Erdogdu gurkanerdo...@yahoo.com
Betreff: OpenJPA Maven
agreement on the JSF2 topic? As far
as I remember two
solutions were mentioned:
1. Move completely to JSF2, JSF1 is not
supported any more
2. Create an additional project for JSF2
integration
br, Sven
2009/12/18 Mark Struberg strub...@yahoo.de
+1 big one :)
webbeans-impl
[
https://issues.apache.org/jira/browse/OWB-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-191.
---
Resolution: Fixed
i18n bundle moved from
* META-INF/Messages_en.properties
to
* openwebbeans
: OpenWebBeans
Issue Type: Improvement
Affects Versions: M3
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: M4
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/OWB-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OWB-202:
--
Component/s: Context and Scopes
Description:
*edit* saw that webbeans-impl already has been cleaned
[
https://issues.apache.org/jira/browse/OWB-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-190.
---
Resolution: Fixed
Moved the TestLifeCycle to a visible package.
A unittest in a project using
[
https://issues.apache.org/jira/browse/OWB-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-203.
---
Resolution: Fixed
Improve logging of webbeans-resource if a PersistenceUnit cannot be found
[
https://issues.apache.org/jira/browse/OWB-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792929#action_12792929
]
Mark Struberg commented on OWB-171:
---
sven, can you please merge again and attach the patch
[
https://issues.apache.org/jira/browse/OWB-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-176.
---
Resolution: Fixed
InterceptionType.AROUND_TIMEOUT is missing
[
https://issues.apache.org/jira/browse/OWB-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-144.
---
Resolution: Fixed
upgrade OWB TCK from webbeans to weld
.
But, if we really
emphasize that the code is related with JSF2, we can
create a package with
named jsf2 in webbeans-jsf project.
Thanks;
--Gurkan
2009/12/17 Mark Struberg strub...@yahoo.de
cool!
Id favour a webbeans-jsf2, I think that's more future
proof.
And as Gurkan
must not think of such a backward compatibility
with JSF 1.2 etc because
we have been implementing Java EE 6 defined JSR-299
specification.
--Gurkan
2009/12/17 Mark Struberg strub...@yahoo.de
Gurkan,
I was not talking about special products, I also
meant the API and I
Hi!
From the ASF board meeting report:
The following resolutions were passed unaminously:
...
B. Establish the Apache OpenWebBeans Project (Gurkan Erdogdu, VP)
Congratulations all for the hard and successful work!
I'd like to specially thank our Mentors Kevan and Matthias for their
: Lifecycle
Affects Versions: M3
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: M4
Currently the OpenWebBeansTestLifecycle is only available internally for the
tests and via the tests.jar.
This is not usable for running automated function tests
cool!
+1
How does the Release process and patching work?
Do we have commit rights for e.g. improving the JavaDoc in geronimo-specs?
How is the release process working? Are we obliged to release those 2 modules
or do we have to send a request to geronimo-dev?
txs and LieGrue,
strub
--- Gurkan
to throw
out trashed code.
We sure that all examples still work :)
--Gurkan
2009/12/11 Mark Struberg (JIRA) j...@apache.org
[
https://issues.apache.org/jira/browse/OWB-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
Mark Struberg resolved OWB-188
3* Remove webbeans-geronimo
In reality Geronimo integration code will be
implemented in the Geronimo
code base using its plugin architecture. This will use the
same technique
for what happened to MyFaces and OpenJPA, OpenEJB etc.
integration.
--Gurkan
2009/12/11 Mark Struberg
Hi!
I'm currently preparing the upgrade to JPA-2 since this is the version which is
defined in the EE6 Web profile.
I write this mail because there is a bit of confusion about the spec versions.
JPA1 was part of EJB3 and thus the artifact was called geronimo-jpa_3.0_spec.
So the '3.0' meant
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: M4
The EE6 Web profile defines JPA2 as persistence provider technologie. Thus we
shall upgrade to the jpa2-api and OpenJPA-2.0.
--
This message is automatically generated by JIRA.
-
You can reply
[
https://issues.apache.org/jira/browse/OWB-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-186.
---
Resolution: Fixed
implemented in Revision 889274
Upgrade OWB to the JPA-2 spec
Gurkan!
It seems you duplicated the jpa part to the resource plugin.
It seems there are a bunch of cleanup tasks left open.
I think we can drop the webbeans-jpa, and I will cleanup webbeans-resource and
webbeans-geronimo accordingly, ok?
LieGrue,
strub
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: M4
Most of the code from webbeans-jpa has been dupped over to webbeans-resource.
The whole plugin is now essentially obsolete and shall be removed.
We also have to cleanup webbeans-resource and webbeans
+1, looks fine :)
btw, I hope that the bugs in the TCK get fixed soon ;)
LieGrue,
strub
--- Matthias Wessendorf mat...@apache.org schrieb am Mi, 9.12.2009:
Von: Matthias Wessendorf mat...@apache.org
Betreff: Re: December Report
An: openwebbeans-dev@incubator.apache.org
Datum: Mittwoch, 9.
Just 2 make sure we all speak about the same:
We'd like to move over the atinject-api which only contains the annotations of
JSR-330. (This is similar to commons-annotations)
OpenWebBeans implements processing functionality for those annotations as part
of the JSR-299 implementation and passes
[
https://issues.apache.org/jira/browse/OWB-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12784742#action_12784742
]
Mark Struberg commented on OWB-182:
---
oki, command return ;)
After a long discussion
[
https://issues.apache.org/jira/browse/OWB-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed OWB-182.
-
Even if @PreDestroy is used in an Interceptor, it doesn't need an
InvoicationContext parameter
[
https://issues.apache.org/jira/browse/OWB-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg reopened OWB-127:
---
WebBeansUtil#checkPassivationScope still fails with a
WebBeansPassivationException while handling
Txs Matthias!
I just wonder about the @ManagedBean, because I still couldn't find anything in
the official JSF-2 spec (and also nothing about the JSF scopes!
Gerhard Petracek pointed me to the Mojarra where this is also implemented, but
it this 'official' now?
I'd like to implement a JSR-299
Hi folks!
I have tweaked the JSR-299 TCK and now a bit more tests pass.
I also found (and reported) a few bugs in the TCK, so for now, you should
checkout the TCK from
http://anonsvn.jboss.org/repos/weld/cdi-tck/trunk
and update the dependencyin openwebbeans-tck to 1.1.0-SNAPSHOT again.
Pete
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: M4
The BeanManager itself needs to be added as manages bean at the time we
bootstrap the lifecycle.
This needs to be done to be able to @Inject BeanManager bm; which a lot TCK
tests rely on.
--
This message
[
https://issues.apache.org/jira/browse/OWB-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12784817#action_12784817
]
Mark Struberg commented on OWB-184:
---
after further debugging it turned out that we already
it seems that our list drops the attachment.
LieGrue,
strub
--- Monteiro Jean-Louis jean-louis.monte...@atosorigin.com schrieb am Di,
1.12.2009:
Von: Monteiro Jean-Louis jean-louis.monte...@atosorigin.com
Betreff: RE: Documentation: first draft
An: openwebbeans-dev@incubator.apache.org
looks pretty fine!
LieGrue,
strub
--- Jean-Louis MONTEIRO jeano...@gmail.com schrieb am Di, 1.12.2009:
Von: Jean-Louis MONTEIRO jeano...@gmail.com
Betreff: Re: Documentation: first draft
An: openwebbeans-dev@incubator.apache.org
Datum: Dienstag, 1. Dezember 2009, 13:20
Done
to serve as the initial members of the Apache OpenWebBeans
PMC:
* Gurkan Erdogdu (gurkanerdogdu at yahoo dot com)
* Kevan Miller (kevan dot miller at gmail dot com)
* Mark Struberg (struberg at yahoo dot com)
* Joe Bergmark (bergmark at gmail dot com)
* Eric Covener (covener at gmail dot
into each test WAR
archive lib folder. I do not see any skipped test in my
environment. Maybe your Tomcat configuration is wrong.
--Gurkan
From: Mark Struberg strub...@yahoo.de
To: openwebbeans-dev@incubator.apache.org
Sent: Sat, November 28, 2009
to me how the
TCK suite works on your computer.
Will look at again.
For the unpacking vs dependency: the only thing
which matters is if the jars are on the classpath
Ok, then, current way for doing that is fine.
From: Mark Struberg strub...@yahoo.de
[
https://issues.apache.org/jira/browse/OWB-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-179.
---
Resolution: Fixed
PluginLoader need to actually startUp each plugin at load time
Versions: M3
Reporter: Mark Struberg
Assignee: Gurkan Erdogdu
Fix For: M4
Found in BeansDeployer
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
: Interceptor and Decorators
Affects Versions: M3
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: M4
The JSR-299 TCK defines a interceptors (e.g. MissileInterceptor) which have
only package scope.
This means we have to manually set the constructor
Project: OpenWebBeans
Issue Type: Bug
Affects Versions: M3
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: M4
thus we must disable the check in WebBeansUtils#configureInterceptorMethods
--
This message is automatically generated
[
https://issues.apache.org/jira/browse/OWB-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-182.
---
Resolution: Fixed
Even if @PreDestroy is used in an Interceptor, it doesn't need
Imho it should.
And it must also work for AJAX requests and partial submits.
LieGrue,
strub
--- Gurkan Erdogdu cgurkanerdo...@gmail.com schrieb am Mo, 23.11.2009:
Von: Gurkan Erdogdu cgurkanerdo...@gmail.com
Betreff: Re: Review of WebBeansPhaseListener
An:
: OpenWebBeans
Issue Type: Bug
Components: Interceptor and Decorators
Affects Versions: M3
Reporter: Mark Struberg
Fix For: M4
those interceptor types allow handling of the new ones defined in EJB-3.1.
Where do we handle them?
This turns out
[
https://issues.apache.org/jira/browse/OWB-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg reassigned OWB-178:
-
Assignee: Mark Struberg (was: Gurkan Erdogdu)
update Bean interface to fit the latest spec
: M4
Reporter: Mark Struberg
Assignee: Gurkan Erdogdu
Priority: Blocker
Fix For: M3
e.g. remove isSerialisable(),
We have to fix this in order to get the TCK running.
--
This message is automatically generated by JIRA.
-
You can reply
[
https://issues.apache.org/jira/browse/OWB-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-154.
---
Resolution: Fixed
remove Bean#getDeploymentType
Hi!
I think our atinject-api is pretty stable now.
Wdyt about adding a bit more documentation and finally moving it over to
geronimo-specs?
LieGrue,
strub
__
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz
any1 seen this before?
testGenericBeanInjection(org.apache.webbeans.test.unittests.inject.generic.GenericBeanTest)
Time elapsed: 0.004 sec ERROR!
javax.enterprise.context.ContextNotActiveException: WebBeans context with scope
type annotation @ApplicationScoped does not exist within current
[
https://issues.apache.org/jira/browse/OWB-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-150.
---
Resolution: Fixed
remove ActivityManager from OWB
+1
LieGrue,
strub
--- Gurkan Erdogdu gurkanerdo...@yahoo.com schrieb am Mo, 16.11.2009:
Von: Gurkan Erdogdu gurkanerdo...@yahoo.com
Betreff: [VOTE] Gradutation
An: openwebbeans-dev@incubator.apache.org
Datum: Montag, 16. November 2009, 21:50
Hi folks,
There were some discussions related
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: M4
testPrimitiveProducer(org.apache.webbeans.test.unittests.producer.primitive.PrimitiveProducerTest)
Time elapsed: 0.007 sec ERROR!
java.lang.NullPointerException
Hi!
Gavin today released the final draft of the CDI specification:
http://in.relation.to/Bloggers/JSR299FinalDraftSubmitted
LieGrue,
strub
What do we have to do in order to get OWB graduated?
LieGrue,
strub
- Ursprüngliche Mail
Von: Kevan Miller kevan.mil...@gmail.com
An: openwebbeans-dev@incubator.apache.org
Gesendet: Mittwoch, den 11. November 2009, 18:00:50 Uhr
Betreff: graduation
It's been a while since the
Versions: M3
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: M4
from a sample of the spec:
{noformat}
Produces @ConversationScoped
@Special Order getSpecialOrder(@New(Order.class) Order order)
{noformat}
--
This message is automatically generated
[
https://issues.apache.org/jira/browse/OWB-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OWB-153:
--
Affects Version/s: M3
Fix Version/s: M4
Assignee: Mark Struberg (was: Gurkan Erdogdu
[
https://issues.apache.org/jira/browse/OWB-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12771930#action_12771930
]
Mark Struberg commented on OWB-154:
---
Gurkan, I saw this is still pretty often used in our
: Bug
Components: Context and Scopes
Affects Versions: M3
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: M4
from the latest spec:
bq. Conversation#isTransient() returns true if the conversation is marked
transient, or false
[
https://issues.apache.org/jira/browse/OWB-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-155.
---
Resolution: Fixed
Conversation#isLongRunning() logic must be converted to isTransient
: Bug
Affects Versions: M3
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: M4
currently is:
{noformat}
public interface ProcessSessionBeanX extends ProcessBeanObject
{
public AnnotatedTypeX getAnnotatedBeanClass();
...
{noformat}
and spec
[
https://issues.apache.org/jira/browse/OWB-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-156.
---
Resolution: Fixed
ProcessSessionBean SPI interface needs to be updated to the latest spec
[
https://issues.apache.org/jira/browse/OWB-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12771325#action_12771325
]
Mark Struberg commented on OWB-148:
---
In fact currently only the ProcessAnnotatedBean event
uses
MetaDataDiscoveryStandard
We can implement whatever funtionality in TestLifecycle using
TestMetaDataDisceovery.
Thanks;
--Gurkan
From: Mark Struberg
To: openwebbeans-dev@incubator.apache.org
Sent: Thu, October 29, 2009 12:29:43 AM
Subject
: Mark Struberg
To: openwebbeans-dev@incubator.apache.org
Sent: Wed, October 28, 2009 11:23:24 PM
Subject: drop ActivityManager
Hi!
Activities have been dropped from the spec a long time ago.
We should finally also drop the ActivityManager from our code. This would
really
make
Versions: M3
Reporter: Mark Struberg
Assignee: Mark Struberg
It seems that the BeforeShutDown event doesn't get received, so we first have
to create a proper JUnit test case for it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add
[
https://issues.apache.org/jira/browse/OWB-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg reassigned OWB-149:
-
Assignee: Mark Struberg (was: Gurkan Erdogdu)
BeforeShutDown (in current code) should
[
https://issues.apache.org/jira/browse/OWB-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-149.
---
Resolution: Fixed
Fix Version/s: M4
I renamed it to BeforeShutdownImpl. txs!
BeforeShutDown
Hi!
Activities have been dropped from the spec a long time ago.
We should finally also drop the ActivityManager from our code. This would
really make the code much cleaner again.
Any reservations?
LieGrue,
strub
Hi!
Somehow those 2 functions cover pretty much of the same functionality, isn't?
Gurkan, do you think we can merge the functionalities somehow?
E.g. for the tests we could use BeansDeployer#deploy with a special
MetaDataDiscoveryService which only returns the one bean class under test.
we could simply use the api from MyFaces.
LieGrue,
strub
- Ursprüngliche Mail
Von: gerdo...@apache.org gerdo...@apache.org
An: openwebbeans-comm...@incubator.apache.org
Gesendet: Dienstag, den 27. Oktober 2009, 6:33:20 Uhr
Betreff: svn commit: r830063 -
Betreff: Re: svn commit: r830063 -
/incubator/openwebbeans/trunk/samples/pom.xml
More correclty, MyFaces supports JSF 2.0 specification?
-Gurkan
2009/10/27 Gurkan Erdogdu
Does MyFaces Api support JSF 2.0 Specification?
Thanks;
--Gurkan
2009/10/27 Mark Struberg
we could
/samples/pom.xml
That is why I include Sun specific maven artifacts.
Thanks;
--Gurkan
2009/10/27 Mark Struberg
gnah sorry, I was wrong.
Althouth the MyFaces team works on JSF-2 for over a year now (and being
pretty stable) they have still no final release. Their spec seems
Hi!
Haven't looked at it, but if you think it's a bug in the spec, then drop Gavin
or the weld-dev list a mail.
LieGrue,
strub
- Original Message
From: Sven Linstaedt sven.linsta...@googlemail.com
To: openwebbeans-dev@incubator.apache.org
Sent: Fri, October 23, 2009 5:53:28 PM
Hi!
I think we have a slight bug in
AnnotationUtil#checkQualifierConditions(Annotation...)
We currently only check for Annotation dupplications between 2 'neighbour'
qualifiers.
But dupplicated annotations like @Default @Special @Default will not be
detected correctly.
I fixed that by
[
https://issues.apache.org/jira/browse/OWB-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg reassigned OWB-140:
-
Assignee: Mark Struberg (was: Gurkan Erdogdu)
Remove javax.enterprise.event.Observer
Hiho!
Just a quick bid:
fn(Annotation... annotations) {...}
is not the most descriptive parameter naming ;)
Would also help if we write a quick JavaDoc for such functions.
I'm currently (still) reworking the whole Observer to ObserverMethod.
Sorry for taking so long, but I have not looked at
field injection at the very bottom of that section.
Sincerely,
Joe Bergmark
On Thu, Oct 15, 2009 at 4:37 PM, Mark Struberg wrote:
I hope we did take care that this rule must not be applied for field
InjectionPoints?
I know the spec is a bit cryptic for this case
If it helps, I think I enabled cobertura for the site plugin.
I will do a site deploy-staged to my peo...@ao in the afternoon.
The public site needs to be updated too I think.
LieGrue,
strub
- Original Message
From: David Blevins david.blev...@visi.com
To:
2009/10/14 Mark Struberg strub...@yahoo.de
Hi!
Bob and Jason today pushed the tagged v1 of the
atinject-api to mavens
central repository.
I will again check the license, but think it was
released under ASL2. So we
could now theoretically drop our atinject-api module
and use
detailed information
about licensing issues however.
Thanks;
--Gurkan
From: Mark Struberg strub...@yahoo.de
To: openwebbeans-dev@incubator.apache.org
Sent: Wed, October 14, 2009 12:27:13 PM
Subject: Re: atinject-api is available at maven-central
Hi
;
-Gurkan
2009/10/12 Mark Struberg (JIRA) j...@apache.org
[
https://issues.apache.org/jira/browse/OWB-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12764517#action_12764517]
Mark Struberg commented on OWB-140
[
https://issues.apache.org/jira/browse/OWB-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12764517#action_12764517
]
Mark Struberg commented on OWB-140:
---
only partly fixed!
I removed the Observer and a few
Hi!
I checked the latest spec against our implementation and found the following
differences:
* javax.enterprise.event.Observer got dropped from the Spec
* public T SetObserverT resolveObservers(T event, Annotation...
qualifiers);
got refactored to
public T SetObserverMethod? super T
and a post-vote +1 from me too.
Sorry, that I didn't find time earlier :(
LieGrue,
strub
--- On Wed, 9/23/09, Gurkan Erdogdu cgurkanerdo...@gmail.com wrote:
From: Gurkan Erdogdu cgurkanerdo...@gmail.com
Subject: [VOTE][RESULT] Release OpenWebBeans M3 (RC2)
To:
Congratulations, and thanks in advance for your highly welcome help :)
LieGrue,
strub
--- On Tue, 9/15/09, Kevan Miller kevan.mil...@gmail.com wrote:
From: Kevan Miller kevan.mil...@gmail.com
Subject: [ANNOOUNCE] Welcome David Blevins as a new OpenWebBeans Committer
To:
Hi!
Bob today announced that they will release a TCK for JSR-330.
My Question: I'm still not sure if JSR-299 is 100% 330 compliant or if we only
use the same annotations to have some 'basic' similarity.
So, should OWB (and other 299 containers) also comply with this TCK or only
with the 299er
, Mark Struberg strub...@yahoo.de
wrote:
Hi!
Bob today announced that they will release a TCK for
JSR-330.
My Question: I'm still not sure if JSR-299 is 100% 330
compliant or if we only use the same annotations to have
some 'basic' similarity.
So, should OWB (and other 299 containers
implementations should not also comply with jsr330's
TCK.
br, Sven
2009/9/14 Mark Struberg strub...@yahoo.de
Hi!
Bob today announced that they will release a TCK for
JSR-330.
My Question: I'm still not sure if JSR-299 is 100% 330
compliant or if we
only use the same
From: Mark Struberg strub...@yahoo.de
To: openwebbeans-dev@incubator.apache.org
Sent: Monday, September 14, 2009 12:55:07 PM
Subject: Re: jsr-330 TCK
But if the JSR-299 TCK implies that any
compatible
implementation must also pass the JSR-330 TCK
right, that's exactly what I'd like
heh, I just realised that this is actually the first time we didn't release an
already outdated implementation.
The last times, whenever we were going to release, the spec changed
dramatically ;)
LieGrue,
strub
--- On Thu, 9/10/09, Kevan Miller kevan.mil...@gmail.com wrote:
From: Kevan
Sorry for repeating myself: I think we should wait for the 330 and 299 specs to
settle, and THEN we can decide what to do. I feel uncomfortable with being
promoted from incubator without having the API pretty stable.
Once this point is reached, I look pretty confident that OWB will find a well
+1
looks good.
LieGrue,
strub
--- On Tue, 9/8/09, Gurkan Erdogdu gurkanerdo...@yahoo.com wrote:
From: Gurkan Erdogdu gurkanerdo...@yahoo.com
Subject: [VOTE][Third Try] Release OpenWebBeans 1.0.0-incubating-M3
To: openwebbeans-dev@incubator.apache.org
Date: Tuesday, September 8, 2009,
sorry for the delay, will look at it today in the night.
LieGrue,
strub
--- On Mon, 9/7/09, Gurkan Erdogdu cgurkanerdo...@gmail.com wrote:
From: Gurkan Erdogdu cgurkanerdo...@gmail.com
Subject: Re: [VOTE][Second Try] Release OpenWebBeans 1.0.0-incubating-M3
To:
[
https://issues.apache.org/jira/browse/OWB-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12751342#action_12751342
]
Mark Struberg commented on OWB-134:
---
yea cool patch - txs!
Hmm David, since OpenEjb
1 - 100 of 264 matches
Mail list logo
