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
openwebbeans.propert
are parallel calls to
> the same proxy
> > instance, this means that parallel calls to same
> scoped instances. For
> > example, Seam defines some conditions for handling
> multi-threaded session or
> > application scoped instances.
> >
> > --Gurkan
> >
&
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 invocat
[
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 b
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)
> To: openwe
[
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 b
y, but I will look at your test
> class after you check in.
>
> Thanks ;
>
> --Gurkan
>
>
>
>
>
> From: Mark Struberg
> To: openwebbeans-dev@incubator.apache.org
> Sent: Mon, December 21, 2009 6:14:51 PM
> Subject: Proxy only
ill look at your test
> class after you check in.
>
> Thanks ;
>
> --Gurkan
>
>
>
>
>
> From: Mark Struberg
> To: openwebbeans-dev@incubator.apache.org
> Sent: Mon, December 21, 2009 6:14:51 PM
> Subject: Proxy only gets resol
y, you must not
> use Context interface
> > directly 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
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? Y
Reporter: Mark Struberg
Assignee: Mark Struberg
Priority: Blocker
Fix For: M4
I think I've hit a big problem!
If I inject a bean twice, I get no interceptor for the 2nd instance!
The problem seems caused in AbstractContext#getInstance()
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 schrieb am So, 20.12.2009:
> Von: Gurkan Erdogdu
> Betreff: OpenJPA Maven Plugin
> An: openwebbeans-dev@incubator.apache.
[
https://issues.apache.org/jira/browse/OWB-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792929#action_12792929
]
Mark Struberg commented on OWB-171:
---
sven, can you please merge again and attach the p
[
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 fo
Type: Improvement
Components: Java EE Integration
Affects Versions: M3
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: M4
currently if someone tries to inject a @PersistenceUnit("myUnitName") we inject
null without logging som
[
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-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-202.
---
Resolution: Fixed
we now use MyFaces-2.0.0-alpha
> upgrade webbeans-jsf to JS
[
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
: 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-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
[
https://issues.apache.org/jira/browse/OWB-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg reopened OWB-191:
---
WebBeansLogger crashes for Locale=de_AT because Resource.getBundle doesn't find
anything.
>
> >> Was there any 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
&
[
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 w
[
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 miss
[
https://issues.apache.org/jira/browse/OWB-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-135.
---
Resolution: Fixed
> implement API changes from spec version P
Hi!
I have a lot of half-done work lying around but I'm currently really short of
time :(
The good thing is, I'm now using OWB as CDI part of a new big project, so I
will find out what doesn't work sooner or later ;)
I hope I can commit OWB-190 today.
LieGrue,
strub
--- Gurkan Erdogdu schri
calls
> An: openwebbeans-dev@incubator.apache.org
> Datum: Freitag, 18. Dezember 2009, 13:38
> I also thought about migrating all
> JSF compile time depend classes from
> webbeans-impl to webbeans-jsf for a clearer seperation.
> wdyt?
>
> br, Sven
>
> 2009/12/17 Ma
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 supp
e to
> JSF 1.2 then it will be
> > reasonable to define new JSF2 project but we did not.
> Actually it is
> > meaningless for me to separate JSF 1.2 and JSF 2.
> >
> > We must not think of such a backward compatibility
> with JSF 1.2 etc because
> > we have
into package webbeans-jsf.
> There is no need to
> create extra project modules that confuses developers
> minds.
>
> Thnks;
>
> --Gurkan
>
> 2009/12/17 Mark Struberg
>
> > > JSF2 is backward compatible
> >
> > Not when it comes to the details!
> >
rt JSF2 and JSF2 is backward compatible.
> 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
>
> >
cool!
Id favour a webbeans-jsf2, I think that's more future proof.
And as Gurkan already said: please attach the patch as owb-171-patch.rfc in
Jira.
txs and LieGrue,
strub
--- Sven Linstaedt schrieb am Do, 17.12.2009:
> Von: Sven Linstaedt
> Betreff: Integration of JSF2 specific API calls
>
: 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 in
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 E
>
> Besides, would you like to be release guy for M4 :)?
>
> In the mean time, I will be marrying at next week, all of
> you are welcome to my wedding ceremony :)
>
> Thnks;
>
> --Gurkan
>
>
>
>
> From: Mark Struberg
&g
Hi!
Wdyt about releaseing a milestone M4 now?
I think OWB has become pretty stable and since the spec is not moving anymore,
it would be a good idea to get more users on board right now.
txs and LieGrue,
strub
__
Do You Yahoo!?
Sie sind Spam lei
code from webbeans-geronimo to
> webbeans-ejb
> 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, Ope
row
> out trashed code.
>
> We sure that all examples still work :)
>
> --Gurkan
>
> 2009/12/11 Mark Struberg (JIRA)
>
> >
> > [
> > https://issues.apache.org/jira/browse/OWB-188?page=com.atlassian.jira.plu
[
https://issues.apache.org/jira/browse/OWB-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-188.
---
Resolution: Fixed
> remove webbeans-jpa and cleanup webbeans-resou
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
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
___
[
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 s
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 to this
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 EJ
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
+1, looks fine :)
btw, I hope that the bugs in the TCK get fixed soon ;)
LieGrue,
strub
--- Matthias Wessendorf schrieb am Mi, 9.12.2009:
> Von: Matthias Wessendorf
> Betreff: Re: December Report
> An: openwebbeans-dev@incubator.apache.org
> Datum: Mittwoch, 9. Dezember 2009, 11:10
> looks go
[
https://issues.apache.org/jira/browse/OWB-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-184.
---
Resolution: Fixed
The problem which caused a lot TCKs to got skipped was that the BeanManager
got only
[
https://issues.apache.org/jira/browse/OWB-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784817#action_12784817
]
Mark Struberg commented on OWB-184:
---
after further debugging it turned out that we alr
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
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
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 e
[
https://issues.apache.org/jira/browse/OWB-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-127.
---
Resolution: Fixed
This fix was necessary to successfully handle the TCKs PassivatingContextTest
[
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
[
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
> InvoicationContex
[
https://issues.apache.org/jira/browse/OWB-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784742#action_12784742
]
Mark Struberg commented on OWB-182:
---
oki, command return ;)
After a long discussion on
ary
> responsibility for management of the projects within the
> scope of responsibility
> of the Apache OpenWebBeans PMC; and be it further
>
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed
> to serve as the initial members of the Apache OpenW
looks pretty fine!
LieGrue,
strub
--- Jean-Louis MONTEIRO schrieb am Di, 1.12.2009:
> Von: Jean-Louis MONTEIRO
> Betreff: Re: Documentation: first draft
> An: openwebbeans-dev@incubator.apache.org
> Datum: Dienstag, 1. Dezember 2009, 13:20
> Done https://issues.apache.org/jira/browse/OWB-183
>
it seems that our list drops the attachment.
LieGrue,
strub
--- Monteiro Jean-Louis schrieb am Di,
1.12.2009:
> Von: Monteiro Jean-Louis
> Betreff: RE: Documentation: first draft
> An: "openwebbeans-dev@incubator.apache.org"
>
> Datum: Dienstag, 1. Dezember 2009, 10:31
> No, but here is aga
ainer mode.
>
>
> >>>ad 2)Still it is not really clear 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, curr
EJB in Tomcat. So
> dependency:copy adds all necessary jar 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:
ou look at Interceptors
> specification, you can see that if you have @PreDestroy in
> interceptor class, it must take "InvocationContext" as a
> parameter. I think that our old impl. was correct. Seems
> that TCK tests are wrong!
>
>
> --Gurkan
>
>
>
> _
[
https://issues.apache.org/jira/browse/OWB-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-181.
---
Resolution: Fixed
> TCK requires to create newInstance of hidden construct
[
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
B-182
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 generat
: 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
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.
[
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 t
Components: Core
Affects Versions: M3
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: M4
PluginLoader need to call startUp() on each plugin while starting up
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a
Hi!
I'm playing around with the TCK suite for a few days and almost all tests got
skipped. I tried this with tomcat and also as standalone, and both give similar
results.
Let's stick with the standalone container for now:
1.) The webbeans-ejb plugin (which we should rename to webbeans-openejb
Imho it should.
And it must also work for AJAX requests and partial submits.
LieGrue,
strub
--- Gurkan Erdogdu schrieb am Mo, 23.11.2009:
> Von: Gurkan Erdogdu
> Betreff: Re: Review of WebBeansPhaseListener
> An: openwebbeans-dev@incubator.apache.org
> Datum: Montag, 23. November 2009, 8:04
>
[
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#getDeploymentT
[
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 s
: 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 to this
: 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 to be a
Struberg
Assignee: Mark Struberg
Fix For: M4
AROUND_TIMEOUT must be added
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
dev@incubator.apache.org"
>
> Datum: Samstag, 21. November 2009, 1:15
> Are the tests fired in multiple
> threads? If I remember correct, surefire introduced
> multithreaded thread execution in some version.
>
> br, Sven
>
>
> -- sent by phone
>
> Am 20.11.2
[
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
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
called. It's up to initB() to subsequently
call initA() itself (initA() must not be called at all for B instances).
LieGrue,
strub
--- Mark Struberg schrieb am Fr, 20.11.2009:
> Von: Mark Struberg
> Betreff: Re: Inheritance of class local interception and lifecyle invocation?
> An
Hi folks!
This should be working. At least that was exactly the reason why we have a
'CreationalContext' in our interfaces ;) It's only purpose is to make cyclic
bean references work.
LieGrue,
strub
--- Eric Covener schrieb am Fr, 20.11.2009:
> Von: Eric Covener
> Betreff: Re: Inheritance o
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
[
https://issues.apache.org/jira/browse/OWB-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-140.
---
Resolution: Fixed
> Remove javax.enterprise.event.Obser
[
https://issues.apache.org/jira/browse/OWB-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778826#action_12778826
]
Mark Struberg commented on OWB-168:
---
attaching patches we can apply to OWB is even
Txs David!
We discussed the pros and conns pretty lengthy a few months ago.
OpenEJB has a great community and is well established. Plus, I think we have to
work together pretty tight together with the OpenEJB community.
Otoh, OWB is so much more than 'just' EJB support, which justifies being a T
[
https://issues.apache.org/jira/browse/OWB-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-169.
---
Resolution: Fixed
Fixed by doing the PluginLoader#startUp() in the TestContext constructor
instead of
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
+1
LieGrue,
strub
--- Gurkan Erdogdu schrieb am Mo, 16.11.2009:
> Von: Gurkan Erdogdu
> Betreff: [VOTE] Gradutation
> An: openwebbeans-dev@incubator.apache.org
> Datum: Montag, 16. November 2009, 21:50
> Hi folks,
>
> There were some discussions related with graduation of the
> OpenWebBeans p
[
https://issues.apache.org/jira/browse/OWB-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-141.
---
Resolution: Fixed
I already implemented this.
> Conversation.isLongRunning() was removed in favor
What do we have to do in order to get OWB graduated?
LieGrue,
strub
- Ursprüngliche Mail
> Von: Kevan Miller
> 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 community has discu
Hi!
Gavin today released the final draft of the CDI specification:
http://in.relation.to/Bloggers/JSR299FinalDraftSubmitted
LieGrue,
strub
[
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 s
[
https://issues.apache.org/jira/browse/OWB-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772044#action_12772044
]
Mark Struberg commented on OWB-156:
---
after discussing the problem with Gavin, he
: Bug
Affects Versions: M3
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: M4
currently is:
{noformat}
public interface ProcessSessionBean extends ProcessBean
{
public AnnotatedType getAnnotatedBeanClass();
...
{noformat}
and spec defines
[
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 isTransi
: 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 if it is
[
https://issues.apache.org/jira/browse/OWB-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771930#action_12771930
]
Mark Struberg commented on OWB-154:
---
Gurkan, I saw this is still pretty often used in
remove Bean#getDeploymentType()
---
Key: OWB-154
URL: https://issues.apache.org/jira/browse/OWB-154
Project: OpenWebBeans
Issue Type: Bug
Reporter: Mark Struberg
Assignee: Gurkan Erdogdu
[
https://issues.apache.org/jira/browse/OWB-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OWB-154:
--
Component/s: Simple Web Beans
Affects Version/s: M3
Fix Version/s: M4
> remove B
[
https://issues.apache.org/jira/browse/OWB-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-153.
---
Resolution: Fixed
> javax.enterprise.inject.spi.Decorator#getDelegateBindings() must be renamed
&
/browse/OWB-153
Project: OpenWebBeans
Issue Type: Bug
Reporter: Mark Struberg
Assignee: Gurkan Erdogdu
the interface from the spec:
{noformat}
public interface Decorator extends Bean {
public Set getDecoratedTypes();
public Type getDelegateType
1 - 100 of 517 matches
Mail list logo
