Re: ChildActivityManager
Hi Mark; tw, I have no clue how we should implement Manager#setCurrent, any suggestions? I understand from the spec is that, we have to register context related with the given scope with the current (this) activity. Whenever we get the Manager instance, we have to find the current activity. I have implemented the setCurrentMethod. Please see the ActivityManager class how to get/set the current activity. Another thing which I was not sure: A bunch of TCK tests fail due to the fact that DependingContext is not active for them! Which tests that are failed! When I was running the TCK, I have excluded the some tests that are not implemented yet in the OWB, like enterprise, jms, etc. >Have we forgotten this, or was this intentionally? Intentional. Because, dependent context is activated based on some conditions. You can see try--finally blocks in the code that are related with activating and passivating the dependent context. From: Mark Struberg To: openwebbeans-dev@incubator.apache.org Sent: Wednesday, April 22, 2009 7:24:15 PM Subject: ChildActivityManager Hiho! Today I tried to implement section 11.6 of the Spec by introducing a ChildActivityManager. Please read the JavaDocs and tell me if it is not clear enough. Please review my changes, maybe you have a better idea how this may be implemented? There are a lot of open //X TODO in the code. Basically all things which needs to be reviewed ;) Btw, I have no clue how we should implement Manager#setCurrent, any suggestions? Another thing which I was not sure: A bunch of TCK tests fail due to the fact that DependingContext is not active for them! For the TCKs we have the org.apache.webbeans.test.tck.ManagersImpl#getManager() where something like ContextFactory.initApplicationContext(null); is being called for all other default contexts but not for DependingContext. Have we forgotten this, or was this intentionally? LieGrue, strub
ChildActivityManager
Hiho! Today I tried to implement section 11.6 of the Spec by introducing a ChildActivityManager. Please read the JavaDocs and tell me if it is not clear enough. Please review my changes, maybe you have a better idea how this may be implemented? There are a lot of open //X TODO in the code. Basically all things which needs to be reviewed ;) Btw, I have no clue how we should implement Manager#setCurrent, any suggestions? Another thing which I was not sure: A bunch of TCK tests fail due to the fact that DependingContext is not active for them! For the TCKs we have the org.apache.webbeans.test.tck.ManagersImpl#getManager() where something like ContextFactory.initApplicationContext(null); is being called for all other default contexts but not for DependingContext. Have we forgotten this, or was this intentionally? LieGrue, strub
Sending mails to jsr-299-comme...@jcp.org, How ?
Hi All... How to send jsr-299-comme...@jcp.org, just send mails or I have to subscribe first ? -- Thanks - Mohammad Nour - LinkedIn: http://www.linkedin.com/in/mnour "Life is like riding a bicycle. To keep your balance you must keep moving" - Albert Einstein
[jira] Created: (OWB-94) Spec requires CreationalContext instead of in Manager#getInstanceToInject
Spec requires CreationalContext instead of in Manager#getInstanceToInject Key: OWB-94 URL: https://issues.apache.org/jira/browse/OWB-94 Project: OpenWebBeans Issue Type: Bug Components: Core Affects Versions: M1 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: M2 the spec defines the getInstanceToInject function in the Manager interface as public T getInstanceToInject(InjectionPoint injectionPoint, CreationalContext context); and we have public T getInstanceToInject(InjectionPoint injectionPoint, CreationalContext context); Must be fixed! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OWB-68) Support for Child Managers
[ https://issues.apache.org/jira/browse/OWB-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned OWB-68: Assignee: Mark Struberg (was: Gurkan Erdogdu) > Support for Child Managers > -- > > Key: OWB-68 > URL: https://issues.apache.org/jira/browse/OWB-68 > Project: OpenWebBeans > Issue Type: Task > Components: Injection and Lookup >Reporter: Gurkan Erdogdu >Assignee: Mark Struberg > Fix For: M2 > > > Support for the Current Manager (Activity) and Child Managers (Activities). > See chapter 11.6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (OWB-68) Support for Child Managers
[ https://issues.apache.org/jira/browse/OWB-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reopened OWB-68: -- Why has this been closed? As far as I've seen it is still in the spec, isn't? > Support for Child Managers > -- > > Key: OWB-68 > URL: https://issues.apache.org/jira/browse/OWB-68 > Project: OpenWebBeans > Issue Type: Task > Components: Injection and Lookup >Reporter: Gurkan Erdogdu >Assignee: Gurkan Erdogdu > Fix For: M2 > > > Support for the Current Manager (Activity) and Child Managers (Activities). > See chapter 11.6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: JSR 299 / WebBeans -> Expert Group
sounds good. I'll do the rest. PS: I don't expect this is a fast process, so bear with me ;-) -M On Tue, Apr 21, 2009 at 9:56 PM, Gurkan Erdogdu wrote: > > Hi Matthias; > > I have done step 1. > > Thanks; > > Gurkan > > > > > > From: Matthias Wessendorf > To: openwebbeans-dev@incubator.apache.org > Cc: Gurkan Erdogdu ; James Carman > > Sent: Tuesday, April 21, 2009 1:04:48 PM > Subject: Re: JSR 299 / WebBeans -> Expert Group > > Gurkan and James, > > the process for this is like the following: > > 1) Have the person nominate themselves for the EG at jcp.org > http://jcp.org/en/jsr/egnom?id=299 > 2) Email the PMO p...@jcp.org and ask them to process > 3) Email Gavin to ensure he accepts > > Once you have done step 1), let me know. > I'll take care of 2) and 3) > > Thanks! > Matthias > > > On Thu, Apr 16, 2009 at 10:35 AM, Matthias Wessendorf > wrote: >> Hi, >> >> I am currently "representing" the ASF on the above JSR. >> However, I never really did much. Also I never really committed >> anything to this podling. I just try to help the community growing >> whenever I have some free time. >> >> I want to step back from the Expert Group. Question is now: >> Does one of you want to be on that EG ? This community would >> make most sense to have an active OWB committer being part >> of the spec/EG. >> >> Thanks! >> Matthias >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Resolved: (OWB-93) OWB TCKs should switch to released jsr-299 TCK artifacts
[ https://issues.apache.org/jira/browse/OWB-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-93. -- Resolution: Fixed Assignee: Mark Struberg (was: Gurkan Erdogdu) fixed. upgraded webbeans-tck/pom.xml > OWB TCKs should switch to released jsr-299 TCK artifacts > > > Key: OWB-93 > URL: https://issues.apache.org/jira/browse/OWB-93 > Project: OpenWebBeans > Issue Type: Improvement >Affects Versions: M1 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: M2 > > > we should change the dependencies for our TCK integration to the officially > released ones (1.0.0.BETA2 currently) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OWB-93) OWB TCKs should switch to released jsr-299 TCK artifacts
OWB TCKs should switch to released jsr-299 TCK artifacts Key: OWB-93 URL: https://issues.apache.org/jira/browse/OWB-93 Project: OpenWebBeans Issue Type: Improvement Affects Versions: M1 Reporter: Mark Struberg Assignee: Gurkan Erdogdu Fix For: M2 we should change the dependencies for our TCK integration to the officially released ones (1.0.0.BETA2 currently) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
