Re: Adding Java EE Security 1.0 Spec to geronimo-specs
Hi Roberto I would like to have a more stable implementation before moving this over > to Geronimo Personally, I prefer to develop (continue to develop) it on Geronimo Specs side and the all community can contribute together. Regards. Gurkan On Mon, Jan 14, 2019 at 2:19 PM Roberto Cortez wrote: > Sure. > > On 14 Jan 2019, at 11:03, Jean-Louis MONTEIRO wrote: > > Please open up a PR or I'll create a project on Geronimo side, so you can > push to it. > > Le lun. 14 janv. 2019 à 11:32, Roberto Cortez a > écrit : > >> Yes, these need to be moved to Geronimo, but I think not at this time. >> >> I would like to have a more stable implementation before moving this over >> to Geronimo. There are still a lot of things missing, including in the API >> (I didn’t app the full API, I added the source in a need basis) and is just >> easier to get this done in a single project. >> >> I’ll keep working on this to add the remaining things and once that is >> done we can move it over. >> >> On 12 Jan 2019, at 08:32, Jean-Louis Monteiro >> wrote: >> >> +1 of course. Thanks Gurkan. >> >> If needed, lemme know I can help on this >> -- >> Jean-Louis Monteiro >> http://twitter.com/jlouismonteiro >> http://www.tomitribe.com >> >> >> On Fri, Jan 11, 2019 at 8:29 PM Gurkan Erdogdu >> wrote: >> >>> Hi folks >>> Regarding TomEE, we need to add Java EE Security, JSR-375 spec to >>> geronimo-specs and needs a release. I have committer access to >>> geronimo-specs and added to code (implemented by Roberto Cortez in >>> tomee-security) into my local. Can I commit to code to the >>> geronimo-specs? >>> Any objection? >>> Regards. >>> Gurkan >>> >> >> > > -- > Jean-Louis > > >
Adding Java EE Security 1.0 Spec to geronimo-specs
Hi folks Regarding TomEE, we need to add Java EE Security, JSR-375 spec to geronimo-specs and needs a release. I have committer access to geronimo-specs and added to code (implemented by Roberto Cortez in tomee-security) into my local. Can I commit to code to the geronimo-specs? Any objection? Regards. Gurkan
Re: Yet another proxy/weaving problem
another day another problem Integration is always hard thing :) but this is going to involve making the list of ignored interfaces configurable and may not be acceptable to OWB. David, this is an acceptable. Explains why SPI module is there. --Gurkan From: David Jencks david_jen...@yahoo.com To: d...@aries.apache.org Cc: d...@openwebbeans.apache.org; Geronimo Dev List (JIRA) dev@geronimo.apache.org Sent: Fri, June 3, 2011 9:53:20 AM Subject: Yet another proxy/weaving problem another day another problem org.apache.webbeans.exception.WebBeansConfigurationException: Decorator : Name:null, WebBeans Type:DECORATOR, API Types:[org.jboss.jsr299.tck.tests.context.dependent.InteriorDecorator,org.apache.aries.proxy.weaving.WovenProxy,org.jboss.jsr299.tck.tests.context.dependent.Interior,java.lang.Object], Qualifiers:[javax.enterprise.inject.Any,javax.enterprise.inject.Default] delegate attribute must implement all of the decorator decorated types, but decorator type interface org.apache.aries.proxy.weaving.WovenProxy is not assignable from delegate type of interface org.jboss.jsr299.tck.tests.context.dependent.Interior I believe the story here is that decorator classes must not implement interfaces that the delegate doesn't implement, but aries is adding the org.apache.aries.proxy.weaving.WovenProxy to the decorator class. OWB is already excluding Serializable and I can modify the code to also exclude org.apache.aries.proxy.weaving.WovenProxy and the jcdi tests pass but this is going to involve making the list of ignored interfaces configurable and may not be acceptable to OWB. Is there any way to make the weaving/proxying code not add this interface? I don't think the jdk proxying code needs to add interfaces thanks david jencks
Happy Holiday session to everyone!
Gurkan Erdogdu PMC Chair, Apache OpenWebBeans
Yan:: geronimo/owb cdi tck status
Pete has closed cditck-199 issue. He will release final version as corrected tomorrow. We need to revert latest commit again :) Çar, 15 Ara 2010 10:10 EET tarihinde David Jencks şöyle yazdı: The cdi guys published a new release of the cdi tck on monday, 1.0.2.SP1. Geronimo/owb has 9 or 12 failures testNonexistentConversationExceptionThrown(org.jboss.jsr299.tck.tests.context.conversation.ClientConversationContextTest) This test was possibly inadvertently added from 1.1 (trunk) but with missing pieces. I've asked in CDITCK-191 what is intended. testGetAnnotatedMethod(org.jboss.jsr299.tck.tests.extensions.observer.ProcessObserverMethodEventTest) testProcessObserverMethodEventsSent(org.jboss.jsr299.tck.tests.extensions.observer.ProcessObserverMethodEventTest) testGetObserverMethod(org.jboss.jsr299.tck.tests.extensions.observer.ProcessObserverMethodEventTest) These are fixed currently per OWB-490 but there is a question whether the test is correct, Gurkan has opened CIDTCK-199 to try to find out what is intended. testProcessProducerMethodEvent(org.jboss.jsr299.tck.tests.extensions.processBean.ProcessBeanTest) testProcessProducerFieldEvent(org.jboss.jsr299.tck.tests.extensions.processBean.ProcessBeanTest) See OWB-493. I spent a few hours investigating this but got lost. I could use some help from OWB experts. testPassivationOfPersistenceUnit(org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest) testInjectionOfPersistenceContext(org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest) testInjectionOfPersistenceUnit(org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest) testBeanTypesAndBindingTypesOfPersistenceContext(org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest) testPassivationOfPersistenceContext(org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest) The immediate error here is that the persistence.xml uses a proprietary jndi name for jta-datasource. Pete says we should be able to replace the persistence.xml with one that works for us. I haven't tried yet. testInjectionIntoWebServiceEndpoint(org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.InjectionIntoWebServiceEndPointTest) I will raise a CDITCK jira asking why a web service test is run in web profile where web services are not supported. I have a little bit of evidence that there will be a problem when we run against the full server because I think the test harness is generating invalid ears: the war has a manifest class-path entry that is supposed to point to a jar with all the classes in it, but it appears to be wrong. thanks david jencks
TCK Access
Hello; FYI : I have sent ApacheNDA to secret...@a.o. 2 days ago to access Geronimo TCKs. --Gurkan
[jira] Commented: (GERONIMO-5282) JSR-299 section 10.4.4. Conditional observer methods uses receive=IF_EXISTS but Geronimo (from OWB) uses notifyObserver=IF_EXISTS
[ https://issues.apache.org/jira/browse/GERONIMO-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863182#action_12863182 ] Gurkan Erdogdu commented on GERONIMO-5282: -- I think that spec is not correct. RI and Java EE 6 API uses Observes#notifyObserver. See http://anonsvn.jboss.org/repos/weld/api/trunk/cdi/src/main/java/javax/enterprise/event/Observes.java See http://java.sun.com/javaee/6/docs/api/javax/enterprise/event/Observes.html JSR-299 section 10.4.4. Conditional observer methods uses receive=IF_EXISTS but Geronimo (from OWB) uses notifyObserver=IF_EXISTS --- Key: GERONIMO-5282 URL: https://issues.apache.org/jira/browse/GERONIMO-5282 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenWebBeans Environment: All Reporter: Paul J. Reder Attachments: observes.patch, receive.patch Original Estimate: 1h Remaining Estimate: 1h The copy of the 299 spec that I have, in section 10.4.4. Conditional observer methods, uses receive=IF_EXISTS but OWB uses notifyObserver=IF_EXISTS. The attached patch changes the Geronimo portion (definition of notifyObserver). There is a parallel patch being submitted to OpenWebBeans to change the references to receive. That patch is also attached here for reference. The patched file originated in OWB and was passed over to Geronimo (Observes.java) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5194) Patch for geronimo-jcdi spec
Patch for geronimo-jcdi spec Key: GERONIMO-5194 URL: https://issues.apache.org/jira/browse/GERONIMO-5194 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: specs Reporter: Gurkan Erdogdu Fix For: 3.0 Update geronimo-jcdi for updating AnnotationLiteral code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5194) Patch for geronimo-jcdi spec
[ https://issues.apache.org/jira/browse/GERONIMO-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gurkan Erdogdu updated GERONIMO-5194: - Attachment: jcdi.patch Patch for geronimo-jcdi spec Key: GERONIMO-5194 URL: https://issues.apache.org/jira/browse/GERONIMO-5194 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: specs Reporter: Gurkan Erdogdu Fix For: 3.0 Attachments: jcdi.patch Update geronimo-jcdi for updating AnnotationLiteral code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5121) Update geronimo-jcdi and geronimo-atinject to pass TCK Signature Tests
Update geronimo-jcdi and geronimo-atinject to pass TCK Signature Tests -- Key: GERONIMO-5121 URL: https://issues.apache.org/jira/browse/GERONIMO-5121 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: specs Reporter: Gurkan Erdogdu Update geronimo-jcdi and geronimo-atinject to pass TCK Signature Tests. This includes David Jencks comments about serialize ids and enumeration ordering. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5121) Update geronimo-jcdi and geronimo-atinject to pass TCK Signature Tests
[ https://issues.apache.org/jira/browse/GERONIMO-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gurkan Erdogdu updated GERONIMO-5121: - Attachment: atinject.patch jcdi.patch Update geronimo-jcdi and geronimo-atinject to pass TCK Signature Tests -- Key: GERONIMO-5121 URL: https://issues.apache.org/jira/browse/GERONIMO-5121 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: specs Reporter: Gurkan Erdogdu Attachments: atinject.patch, jcdi.patch Update geronimo-jcdi and geronimo-atinject to pass TCK Signature Tests. This includes David Jencks comments about serialize ids and enumeration ordering. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: milestone release of geronimo-jcdi_1.0_spec ?
Hi Donald; I have created a new jira issue and attached patches related with geronimo_jcdi and geronimo_atinject. Those patches satisfie David Jencks concerns. https://issues.apache.org/jira/browse/GERONIMO-5121 Thanks; --Gurkan From: Donald Woods dwo...@apache.org To: dev@geronimo.apache.org; d...@openwebbeans.apache.org Sent: Thu, February 4, 2010 3:31:59 PM Subject: Re: milestone release of geronimo-jcdi_1.0_spec ? Gurkan, if there are issues with the 1.0-beta code I just put up for a vote last night, then please open a new JIRA with the required patch and reply to that thread with the JIRA info. David, thus you can see why I am releasing all of these snapshot specs as 1.0-beta, since we have not run the full Java EE 6 TCK against them -Donald On 2/4/10 2:41 AM, David Jencks wrote: On Feb 3, 2010, at 10:49 PM, Gurkan Erdogdu wrote: Hi David; I have found some wrong ordering and wrong serialize id. I will correct those in the afternoon and patch it. Donald has already started a vote. Does this problem blocks the beta- release ? I'll certainly vote -1 on a non-snapshot with known problems, and I hope everyone else will too. I'm not that happy releasing specs until the implementaition (e.g. openWebBeans) passes its tck, since we have found subtle implementation problems in specs in the past. Many thanks for taking a look for these problems, better to look and fix now than on day 3 of the vote :-) thanks david jencks Thanks; --Gurkan 2010/2/4 David Jencks david_jen...@yahoo.com mailto:david_jen...@yahoo.com Gurkan, We've recently found a couple more gotchas to check beyond the tck could you check these by hand? Having them wrong obviously impedes interoperability :-) 1. all serializable classes have the serialVersionUID as specified in the javadoc 2. any enums are specified in the order in the javadoc Enum constant detail and NOT that in Enum constant summary thanks david jencks On Feb 3, 2010, at 9:09 AM, Gurkan Erdogdu wrote: That seems OK, It passed signature test. --Gurkan *From:* Donald Woods dwo...@apache.org mailto:dwo...@apache.org *To:* dev@geronimo.apache.org mailto:dev@geronimo.apache.org *Cc:* Gurkan Erdogdu gurkanerdo...@yahoo.com mailto:gurkanerdo...@yahoo.com; d...@openwebbeans.apache.org mailto:d...@openwebbeans.apache.org *Sent:* Wed, February 3, 2010 5:13:11 AM *Subject:* Re: milestone release of geronimo-jcdi_1.0_spec ? OK, the patch has been applied and new snapshots published. Can you (or Blevins) run the signature tests against the latest snapshots (jcdi, atinject and interceptor) and if everything passes (please post the confirmation to our TCK list at geronimo-...@geronimo.apache.org mailto:geronimo-...@geronimo.apache.org) I'll create release candidates for them tomorrow? Also, can you verify that the following are the correct dependencies, as we have a geronimo-el_2.2_spec for Java EE 6 - dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-interceptor_1.1_spec/artifactId version1.0.0-SNAPSHOT/version scopeprovided/scope /dependency dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-el_1.0_spec/artifactId version1.0.2-SNAPSHOT/version scopeprovided/scope /dependency dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-atinject_1.0_spec/artifactId version1.0-SNAPSHOT/version scopeprovided/scope /dependency -Donald On 2/2/10 2:11 PM, Gurkan Erdogdu wrote: Hi Donald; Thanks for the response. I have attached patch to https://issues.apache.org/jira/browse/GERONIMO-5101. We have a plan to release OpenWebBeans this week as soon as possible that you release geronimo-jcdi_1.0_spec and its dependents specs. Thanks --Gurkan *From:* Donald Woods dwo...@apache.org mailto:dwo...@apache.org *To:* dev@geronimo.apache.org mailto:dev@geronimo.apache.org *Cc:* Gurkan Erdogdu gurkanerdo...@yahoo.com mailto:gurkanerdo...@yahoo.com; d...@openwebbeans.apache.org mailto:d...@openwebbeans.apache.org *Sent:* Tue, February 2, 2010 3:56:38 PM *Subject:* Re: milestone release of geronimo-jcdi_1.0_spec ? For the geronimo spec api, if you open a JIRA and attach the patch, one of us will get it committed and built
Re: milestone release of geronimo-jcdi_1.0_spec ?
That seems OK, It passed signature test. --Gurkan From: Donald Woods dwo...@apache.org To: dev@geronimo.apache.org Cc: Gurkan Erdogdu gurkanerdo...@yahoo.com; d...@openwebbeans.apache.org Sent: Wed, February 3, 2010 5:13:11 AM Subject: Re: milestone release of geronimo-jcdi_1.0_spec ? OK, the patch has been applied and new snapshots published. Can you (or Blevins) run the signature tests against the latest snapshots (jcdi, atinject and interceptor) and if everything passes (please post the confirmation to our TCK list at geronimo-...@geronimo.apache.org) I'll create release candidates for them tomorrow? Also, can you verify that the following are the correct dependencies, as we have a geronimo-el_2.2_spec for Java EE 6 - dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-interceptor_1.1_spec/artifactId version1.0.0-SNAPSHOT/version scopeprovided/scope /dependency dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-el_1.0_spec/artifactId version1.0.2-SNAPSHOT/version scopeprovided/scope /dependency dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-atinject_1.0_spec/artifactId version1.0-SNAPSHOT/version scopeprovided/scope /dependency -Donald On 2/2/10 2:11 PM, Gurkan Erdogdu wrote: Hi Donald; Thanks for the response. I have attached patch to https://issues.apache.org/jira/browse/GERONIMO-5101. We have a plan to release OpenWebBeans this week as soon as possible that you release geronimo-jcdi_1.0_spec and its dependents specs. Thanks --Gurkan *From:* Donald Woods dwo...@apache.org *To:* dev@geronimo.apache.org *Cc:* Gurkan Erdogdu gurkanerdo...@yahoo.com; d...@openwebbeans.apache.org *Sent:* Tue, February 2, 2010 3:56:38 PM *Subject:* Re: milestone release of geronimo-jcdi_1.0_spec ? For the geronimo spec api, if you open a JIRA and attach the patch, one of us will get it committed and built for you. Once you verify that the new jar passes the signature tests, we'll start a release vote -Donald On 2/1/10 4:35 PM, Gurkan Erdogdu wrote: Moreover, I have to update API to pass CDI TCK signature tests. Currently it fails. Is it possible to give me a commit access to jcdi and atinject projects? --Gurkan *From:* Gurkan Erdogdu gurkanerdo...@yahoo.com mailto:gurkanerdo...@yahoo.com *To:* d...@openwebbeans.apache.org mailto:d...@openwebbeans.apache.org; dev@geronimo.apache.org mailto:dev@geronimo.apache.org *Cc:* d...@openwebbeans.apache.org mailto:d...@openwebbeans.apache.org *Sent:* Mon, February 1, 2010 11:05:10 PM *Subject:* Re: milestone release of geronimo-jcdi_1.0_spec ? Hello,.addInterceptorBinding(java.lang.Class? extends java.lang.annotation.Annotation) This is also required for geronimo-interceptor_1.1_spec, currently we use 1.0.0-EA1-SNAPSHOT --Gurkan From: Mark Struberg strub...@yahoo.de mailto:strub...@yahoo.de mailto:strub...@yahoo.de mailto:strub...@yahoo.de To: dev@geronimo.apache.org mailto:dev@geronimo.apache.org mailto:dev@geronimo.apache.org mailto:dev@geronimo.apache.org Cc: d...@openwebbeans.apache.org mailto:d...@openwebbeans.apache.org mailto:d...@openwebbeans.apache.org mailto:d...@openwebbeans.apache.org Sent: Mon, February 1, 2010 10:54:16 PM Subject: milestone release of geronimo-jcdi_1.0_spec ? Hi folks! We (most probably poor Gurkan ;) ) will do a release of OpenWebBeans Milestone 4 in the next days and need our API to be release also. Can anyone please be so kind and do the release of a milestone of the jcdi-spec-1.0 for us? txs in advance and LieGrue, strub ___ Yahoo! Türkiye açıldı! http://yahoo.com.tr İnternet üzerindeki en iyi içeriği Yahoo! Türkiye sizlere sunuyor! Yahoo! Türkiye açıldı! Haber, Ekonomi, Videolar, Oyunlar hepsi Yahoo! Türkiye'de! www.yahoo.com.tr http://www.yahoo.com.tr http://tr.yahoo.com/ Yahoo! Türkiye açıldı! Haber, Ekonomi, Videolar, Oyunlar hepsi Yahoo! Türkiye'de! www.yahoo.com.tr http://tr.yahoo.com/ ___ Yahoo! Türkiye açıldı! http://yahoo.com.tr İnternet üzerindeki en iyi içeriği Yahoo! Türkiye sizlere sunuyor!
Re: milestone release of geronimo-jcdi_1.0_spec ?
Hi David; I have found some wrong ordering and wrong serialize id. I will correct those in the afternoon and patch it. Donald has already started a vote. Does this problem blocks the beta- release ? Thanks; --Gurkan 2010/2/4 David Jencks david_jen...@yahoo.com Gurkan, We've recently found a couple more gotchas to check beyond the tck could you check these by hand? Having them wrong obviously impedes interoperability :-) 1. all serializable classes have the serialVersionUID as specified in the javadoc 2. any enums are specified in the order in the javadoc Enum constant detail and NOT that in Enum constant summary thanks david jencks On Feb 3, 2010, at 9:09 AM, Gurkan Erdogdu wrote: That seems OK, It passed signature test. --Gurkan -- *From:* Donald Woods dwo...@apache.org *To:* dev@geronimo.apache.org *Cc:* Gurkan Erdogdu gurkanerdo...@yahoo.com; d...@openwebbeans.apache.org *Sent:* Wed, February 3, 2010 5:13:11 AM *Subject:* Re: milestone release of geronimo-jcdi_1.0_spec ? OK, the patch has been applied and new snapshots published. Can you (or Blevins) run the signature tests against the latest snapshots (jcdi, atinject and interceptor) and if everything passes (please post the confirmation to our TCK list at geronimo-...@geronimo.apache.org) I'll create release candidates for them tomorrow? Also, can you verify that the following are the correct dependencies, as we have a geronimo-el_2.2_spec for Java EE 6 - dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-interceptor_1.1_spec/artifactId version1.0.0-SNAPSHOT/version scopeprovided/scope /dependency dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-el_1.0_spec/artifactId version1.0.2-SNAPSHOT/version scopeprovided/scope /dependency dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-atinject_1.0_spec/artifactId version1.0-SNAPSHOT/version scopeprovided/scope /dependency -Donald On 2/2/10 2:11 PM, Gurkan Erdogdu wrote: Hi Donald; Thanks for the response. I have attached patch to https://issues.apache.org/jira/browse/GERONIMO-5101. We have a plan to release OpenWebBeans this week as soon as possible that you release geronimo-jcdi_1.0_spec and its dependents specs. Thanks --Gurkan *From:* Donald Woods dwo...@apache.org *To:* dev@geronimo.apache.org *Cc:* Gurkan Erdogdu gurkanerdo...@yahoo.com; d...@openwebbeans.apache.org *Sent:* Tue, February 2, 2010 3:56:38 PM *Subject:* Re: milestone release of geronimo-jcdi_1.0_spec ? For the geronimo spec api, if you open a JIRA and attach the patch, one of us will get it committed and built for you. Once you verify that the new jar passes the signature tests, we'll start a release vote -Donald On 2/1/10 4:35 PM, Gurkan Erdogdu wrote: Moreover, I have to update API to pass CDI TCK signature tests. Currently it fails. Is it possible to give me a commit access to jcdi and atinject projects? --Gurkan *From:* Gurkan Erdogdu gurkanerdo...@yahoo.com mailto:gurkanerdo...@yahoo.com *To:* d...@openwebbeans.apache.org mailto:d...@openwebbeans.apache.org; dev@geronimo.apache.org mailto:dev@geronimo.apache.org *Cc:* d...@openwebbeans.apache.org mailto:d...@openwebbeans.apache.org *Sent:* Mon, February 1, 2010 11:05:10 PM *Subject:* Re: milestone release of geronimo-jcdi_1.0_spec ? Hello,.addInterceptorBinding(java.lang.Class? extends java.lang.annotation.Annotation) This is also required for geronimo-interceptor_1.1_spec, currently we use 1.0.0-EA1-SNAPSHOT --Gurkan From: Mark Struberg strub...@yahoo.de mailto:strub...@yahoo.de mailto:strub...@yahoo.de mailto:strub...@yahoo.de To: dev@geronimo.apache.org mailto:dev@geronimo.apache.org mailto:dev@geronimo.apache.org mailto:dev@geronimo.apache.org Cc: d...@openwebbeans.apache.org mailto:d...@openwebbeans.apache.org mailto:d...@openwebbeans.apache.org mailto:d...@openwebbeans.apache.org Sent: Mon, February 1, 2010 10:54:16 PM Subject: milestone release of geronimo-jcdi_1.0_spec ? Hi folks! We (most probably poor Gurkan ;) ) will do a release of OpenWebBeans Milestone 4 in the next days and need our API to be release also. Can anyone please be so kind and do the release of a milestone of the jcdi-spec-1.0 for us? txs in advance and LieGrue, strub ___ Yahoo! Türkiye açıldı! http://yahoo.com.tr İnternet üzerindeki en iyi içeriği
Re: milestone release of geronimo-jcdi_1.0_spec ?
I'm not that happy releasing specs until the implementaition (e.g. openWebBeans) passes its tck Then, how could we release our internal milestones without releasing spec. ? Thanks; --Gurkan 2010/2/4 David Jencks david_jen...@yahoo.com On Feb 3, 2010, at 10:49 PM, Gurkan Erdogdu wrote: Hi David; I have found some wrong ordering and wrong serialize id. I will correct those in the afternoon and patch it. Donald has already started a vote. Does this problem blocks the beta- release ? I'll certainly vote -1 on a non-snapshot with known problems, and I hope everyone else will too. I'm not that happy releasing specs until the implementaition (e.g. openWebBeans) passes its tck, since we have found subtle implementation problems in specs in the past. Many thanks for taking a look for these problems, better to look and fix now than on day 3 of the vote :-) thanks david jencks Thanks; --Gurkan 2010/2/4 David Jencks david_jen...@yahoo.com Gurkan, We've recently found a couple more gotchas to check beyond the tck could you check these by hand? Having them wrong obviously impedes interoperability :-) 1. all serializable classes have the serialVersionUID as specified in the javadoc 2. any enums are specified in the order in the javadoc Enum constant detail and NOT that in Enum constant summary thanks david jencks On Feb 3, 2010, at 9:09 AM, Gurkan Erdogdu wrote: That seems OK, It passed signature test. --Gurkan -- *From:* Donald Woods dwo...@apache.org *To:* dev@geronimo.apache.org *Cc:* Gurkan Erdogdu gurkanerdo...@yahoo.com; d...@openwebbeans.apache.org *Sent:* Wed, February 3, 2010 5:13:11 AM *Subject:* Re: milestone release of geronimo-jcdi_1.0_spec ? OK, the patch has been applied and new snapshots published. Can you (or Blevins) run the signature tests against the latest snapshots (jcdi, atinject and interceptor) and if everything passes (please post the confirmation to our TCK list at geronimo-...@geronimo.apache.org) I'll create release candidates for them tomorrow? Also, can you verify that the following are the correct dependencies, as we have a geronimo-el_2.2_spec for Java EE 6 - dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-interceptor_1.1_spec/artifactId version1.0.0-SNAPSHOT/version scopeprovided/scope /dependency dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-el_1.0_spec/artifactId version1.0.2-SNAPSHOT/version scopeprovided/scope /dependency dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-atinject_1.0_spec/artifactId version1.0-SNAPSHOT/version scopeprovided/scope /dependency -Donald On 2/2/10 2:11 PM, Gurkan Erdogdu wrote: Hi Donald; Thanks for the response. I have attached patch to https://issues.apache.org/jira/browse/GERONIMO-5101. We have a plan to release OpenWebBeans this week as soon as possible that you release geronimo-jcdi_1.0_spec and its dependents specs. Thanks --Gurkan *From:* Donald Woods dwo...@apache.org *To:* dev@geronimo.apache.org *Cc:* Gurkan Erdogdu gurkanerdo...@yahoo.com; d...@openwebbeans.apache.org *Sent:* Tue, February 2, 2010 3:56:38 PM *Subject:* Re: milestone release of geronimo-jcdi_1.0_spec ? For the geronimo spec api, if you open a JIRA and attach the patch, one of us will get it committed and built for you. Once you verify that the new jar passes the signature tests, we'll start a release vote -Donald On 2/1/10 4:35 PM, Gurkan Erdogdu wrote: Moreover, I have to update API to pass CDI TCK signature tests. Currently it fails. Is it possible to give me a commit access to jcdi and atinject projects? --Gurkan *From:* Gurkan Erdogdu gurkanerdo...@yahoo.com mailto:gurkanerdo...@yahoo.com *To:* d...@openwebbeans.apache.org mailto:d...@openwebbeans.apache.org; dev@geronimo.apache.org mailto:dev@geronimo.apache.org *Cc:* d...@openwebbeans.apache.org mailto:d...@openwebbeans.apache.org *Sent:* Mon, February 1, 2010 11:05:10 PM *Subject:* Re: milestone release of geronimo-jcdi_1.0_spec ? Hello,.addInterceptorBinding(java.lang.Class? extends java.lang.annotation.Annotation) This is also required for geronimo-interceptor_1.1_spec, currently we use 1.0.0-EA1-SNAPSHOT --Gurkan From: Mark Struberg strub...@yahoo.de mailto:strub...@yahoo.de mailto:strub...@yahoo.de mailto:strub...@yahoo.de To: dev@geronimo.apache.org mailto:dev@geronimo.apache.org mailto:dev@geronimo.apache.org mailto:dev
[jira] Created: (GERONIMO-5101) geronimo-jcdi_1_0_spec Update for Releasing
geronimo-jcdi_1_0_spec Update for Releasing --- Key: GERONIMO-5101 URL: https://issues.apache.org/jira/browse/GERONIMO-5101 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: specs Reporter: Gurkan Erdogdu Hi; This patch updates geronimo-jcdi_1.0_spec for passing TCK signature tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5101) geronimo-jcdi_1_0_spec Update for Releasing
[ https://issues.apache.org/jira/browse/GERONIMO-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gurkan Erdogdu updated GERONIMO-5101: - Attachment: jcdi.patch geronimo-jcdi_1_0_spec Update for Releasing --- Key: GERONIMO-5101 URL: https://issues.apache.org/jira/browse/GERONIMO-5101 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: specs Reporter: Gurkan Erdogdu Attachments: jcdi.patch Hi; This patch updates geronimo-jcdi_1.0_spec for passing TCK signature tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: milestone release of geronimo-jcdi_1.0_spec ?
Hi Donald; Thanks for the response. I have attached patch to https://issues.apache.org/jira/browse/GERONIMO-5101. We have a plan to release OpenWebBeans this week as soon as possible that you release geronimo-jcdi_1.0_spec and its dependents specs. Thanks --Gurkan From: Donald Woods dwo...@apache.org To: dev@geronimo.apache.org Cc: Gurkan Erdogdu gurkanerdo...@yahoo.com; d...@openwebbeans.apache.org Sent: Tue, February 2, 2010 3:56:38 PM Subject: Re: milestone release of geronimo-jcdi_1.0_spec ? For the geronimo spec api, if you open a JIRA and attach the patch, one of us will get it committed and built for you. Once you verify that the new jar passes the signature tests, we'll start a release vote -Donald On 2/1/10 4:35 PM, Gurkan Erdogdu wrote: Moreover, I have to update API to pass CDI TCK signature tests. Currently it fails. Is it possible to give me a commit access to jcdi and atinject projects? --Gurkan *From:* Gurkan Erdogdu gurkanerdo...@yahoo.com *To:* d...@openwebbeans.apache.org; dev@geronimo.apache.org *Cc:* d...@openwebbeans.apache.org *Sent:* Mon, February 1, 2010 11:05:10 PM *Subject:* Re: milestone release of geronimo-jcdi_1.0_spec ? Hello,.addInterceptorBinding(java.lang.Class? extends java.lang.annotation.Annotation) This is also required for geronimo-interceptor_1.1_spec, currently we use 1.0.0-EA1-SNAPSHOT --Gurkan From: Mark Struberg strub...@yahoo.de mailto:strub...@yahoo.de To: dev@geronimo.apache.org mailto:dev@geronimo.apache.org Cc: d...@openwebbeans.apache.org mailto:d...@openwebbeans.apache.org Sent: Mon, February 1, 2010 10:54:16 PM Subject: milestone release of geronimo-jcdi_1.0_spec ? Hi folks! We (most probably poor Gurkan ;) ) will do a release of OpenWebBeans Milestone 4 in the next days and need our API to be release also. Can anyone please be so kind and do the release of a milestone of the jcdi-spec-1.0 for us? txs in advance and LieGrue, strub ___ Yahoo! Türkiye açıldı! http://yahoo.com.tr İnternet üzerindeki en iyi içeriği Yahoo! Türkiye sizlere sunuyor! Yahoo! Türkiye açıldı! Haber, Ekonomi, Videolar, Oyunlar hepsi Yahoo! Türkiye'de! www.yahoo.com.tr http://tr.yahoo.com/ ___ Yahoo! Türkiye açıldı! http://yahoo.com.tr İnternet üzerindeki en iyi içeriği Yahoo! Türkiye sizlere sunuyor!
Re: milestone release of geronimo-jcdi_1.0_spec ?
Hello, This is also required for geronimo-interceptor_1.1_spec, currently we use 1.0.0-EA1-SNAPSHOT --Gurkan From: Mark Struberg strub...@yahoo.de To: dev@geronimo.apache.org Cc: d...@openwebbeans.apache.org Sent: Mon, February 1, 2010 10:54:16 PM Subject: milestone release of geronimo-jcdi_1.0_spec ? Hi folks! We (most probably poor Gurkan ;) ) will do a release of OpenWebBeans Milestone 4 in the next days and need our API to be release also. Can anyone please be so kind and do the release of a milestone of the jcdi-spec-1.0 for us? txs in advance and LieGrue, strub ___ Yahoo! Türkiye açıldı! http://yahoo.com.tr İnternet üzerindeki en iyi içeriği Yahoo! Türkiye sizlere sunuyor!
Re: milestone release of geronimo-jcdi_1.0_spec ?
Moreover, I have to update API to pass CDI TCK signature tests. Currently it fails. Is it possible to give me a commit access to jcdi and atinject projects? --Gurkan From: Gurkan Erdogdu gurkanerdo...@yahoo.com To: d...@openwebbeans.apache.org; dev@geronimo.apache.org Cc: d...@openwebbeans.apache.org Sent: Mon, February 1, 2010 11:05:10 PM Subject: Re: milestone release of geronimo-jcdi_1.0_spec ? Hello,.addInterceptorBinding(java.lang.Class? extends java.lang.annotation.Annotation) This is also required for geronimo-interceptor_1.1_spec, currently we use 1.0.0-EA1-SNAPSHOT --Gurkan From: Mark Struberg strub...@yahoo.de To: dev@geronimo.apache.org Cc: d...@openwebbeans.apache.org Sent: Mon, February 1, 2010 10:54:16 PM Subject: milestone release of geronimo-jcdi_1.0_spec ? Hi folks! We (most probably poor Gurkan ;) ) will do a release of OpenWebBeans Milestone 4 in the next days and need our API to be release also. Can anyone please be so kind and do the release of a milestone of the jcdi-spec-1.0 for us? txs in advance and LieGrue, strub ___ Yahoo! Türkiye açıldı! http://yahoo.com.tr İnternet üzerindeki en iyi içeriği Yahoo! Türkiye sizlere sunuyor! ___ Yahoo! Türkiye açıldı! http://yahoo.com.tr İnternet üzerindeki en iyi içeriği Yahoo! Türkiye sizlere sunuyor!
Re: G3.0 Plan and Status
Hi Jack; I would like to work with OpenWebBeans integration. Last time we discussed integration, David Blevins created some modules for openwebbeans integration. I am going to fill the blanks and see what other pieces are required. Could I/you write my name to it? Thanks; Gurkan Erdogdu OWB Chair 2010/1/22 Jack Cai greensi...@gmail.com Hi all, I had a discussion with Ivan, Shawn, Rex and Delos on all ongoing/TODO items and their status, and created a table here [1]. I hope this could be a starting point for us to put together the picture for G3.0. Note this is a very early version, and we must have missed or mis-interpreted something. Also, some areas are not detailed yet at all, e.g., documentation, sample, etc. So we urge everybody to take a look... The layout of the table is pretty straight forward. I tried to organize G3.0 release content into several categories, which consists of a number of components. Each component is further broken down into work items. The hope is that people can put their names to the work items that they are currently working on, describe the status (what's done, what's next, a brief estimation) and the dependencies. As a result, we can have a good overview of who's working on what and which parts need more love. All comments are welcome. -Jack [1] http://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+3.0+Release+Status -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com
Re: [jira] Created: (GERONIMO-5019) geronimo-cdi-1.0 spec needs to be using the JEE6 dependencies, not the JEE5 versions.
Hi; I also issued a JIRA issue https://issues.apache.org/jira/browse/GERONIMO-5007 Thks; --Gurkan 2010/1/7 Rick McGuire (JIRA) j...@apache.org geronimo-cdi-1.0 spec needs to be using the JEE6 dependencies, not the JEE5 versions. -- Key: GERONIMO-5019 URL: https://issues.apache.org/jira/browse/GERONIMO-5019 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Reporter: Rick McGuire The geronimo-cdi-1.0 spec jar is using the JEE5 versions of the interceptor and expression language spec jars rather than the JEE6 versions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com
[jira] Created: (GERONIMO-5007) Moving javax.interceptor.* from CDI Project to Interceptor_1.1 Project
Moving javax.interceptor.* from CDI Project to Interceptor_1.1 Project -- Key: GERONIMO-5007 URL: https://issues.apache.org/jira/browse/GERONIMO-5007 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: specs Reporter: Gurkan Erdogdu javax.interceptor.Interceptor and javax.interceptor.InterceptorBinding classes have moved from CDI Specification to Interceptor 1.1 Specification. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5007) Moving javax.interceptor.* from CDI Project to Interceptor_1.1 Project
[ https://issues.apache.org/jira/browse/GERONIMO-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gurkan Erdogdu updated GERONIMO-5007: - Attachment: interceptor.patch Moving javax.interceptor.* from CDI Project to Interceptor_1.1 Project -- Key: GERONIMO-5007 URL: https://issues.apache.org/jira/browse/GERONIMO-5007 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: specs Reporter: Gurkan Erdogdu Attachments: interceptor.patch javax.interceptor.Interceptor and javax.interceptor.InterceptorBinding classes have moved from CDI Specification to Interceptor 1.1 Specification. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5007) Moving javax.interceptor.* from CDI Project to Interceptor_1.1 Project
[ https://issues.apache.org/jira/browse/GERONIMO-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12795298#action_12795298 ] Gurkan Erdogdu commented on GERONIMO-5007: -- Could you permit me svn authorization to work on geronimo-specs-cdi and geronimo-specs-atinject projects? Moving javax.interceptor.* from CDI Project to Interceptor_1.1 Project -- Key: GERONIMO-5007 URL: https://issues.apache.org/jira/browse/GERONIMO-5007 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: specs Reporter: Gurkan Erdogdu Attachments: interceptor.patch javax.interceptor.Interceptor and javax.interceptor.InterceptorBinding classes have moved from CDI Specification to Interceptor 1.1 Specification. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4985) Adding JSR-330 and JSR-299 Spec. APIs
[ https://issues.apache.org/jira/browse/GERONIMO-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789874#action_12789874 ] Gurkan Erdogdu commented on GERONIMO-4985: -- https://svn.apache.org/repos/asf/incubator/openwebbeans/trunk/atinject-api https://svn.apache.org/repos/asf/incubator/openwebbeans/trunk/webbeans-api After that how will we continue to commit on those projects? Adding JSR-330 and JSR-299 Spec. APIs - Key: GERONIMO-4985 URL: https://issues.apache.org/jira/browse/GERONIMO-4985 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: specs Reporter: Gurkan Erdogdu Attachments: api.newerpatch, api.patch Adding JSR-330 and JSR-299 Spec. APIs -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4985) Adding JSR-330 and JSR-299 Spec. APIs
Adding JSR-330 and JSR-299 Spec. APIs - Key: GERONIMO-4985 URL: https://issues.apache.org/jira/browse/GERONIMO-4985 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: specs Reporter: Gurkan Erdogdu Adding JSR-330 and JSR-299 Spec. APIs -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4985) Adding JSR-330 and JSR-299 Spec. APIs
[ https://issues.apache.org/jira/browse/GERONIMO-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gurkan Erdogdu updated GERONIMO-4985: - Attachment: api.patch Adding patches for projects. As Kevan said, I only patched project and pom files. Adding JSR-330 and JSR-299 Spec. APIs - Key: GERONIMO-4985 URL: https://issues.apache.org/jira/browse/GERONIMO-4985 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: specs Reporter: Gurkan Erdogdu Attachments: api.patch Adding JSR-330 and JSR-299 Spec. APIs -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: About JSR-299 and JSR-330 API
Hi Kevan; I have created and patched issue. https://issues.apache.org/jira/browse/GERONIMO-4985. Thanks; --Gurkan 2009/12/9 Kevan Miller kevan.mil...@gmail.com On Dec 9, 2009, at 6:28 AM, Gurkan Erdogdu wrote: Hi folks; We would like to port our JSR-299 and JSR-330 related API projects into Geronimo spec. project. How could we start ? Hi Gurkan, Cool. Creating a Jira and patch for creating the projects in https://svn.apache.org/repos/asf/geronimo/specs/trunk would help a little bit. Patch shouldn't include the spec classes, themselves -- for that we'd want to use svn copy to maintain svn history. Guess we'd only be looking for the pom. I'll try and free up some time to look at this (next day or two). But if anybody else wants to have a go, please feel free! --kevan -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com
[jira] Updated: (GERONIMO-4985) Adding JSR-330 and JSR-299 Spec. APIs
[ https://issues.apache.org/jira/browse/GERONIMO-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gurkan Erdogdu updated GERONIMO-4985: - Attachment: api.newerpatch New patch , obsolete old patch! Adding JSR-330 and JSR-299 Spec. APIs - Key: GERONIMO-4985 URL: https://issues.apache.org/jira/browse/GERONIMO-4985 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: specs Reporter: Gurkan Erdogdu Attachments: api.newerpatch, api.patch Adding JSR-330 and JSR-299 Spec. APIs -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
About JSR-299 and JSR-330 API
Hi folks; We would like to port our JSR-299 and JSR-330 related API projects into Geronimo spec. project. How could we start ? Thanks; --Gurkan
Re: Webapp Annotation processing for 299
Thanks a lot david jencks. Actually, webbeans can be included in any ejb,war,ear,rar and library modules. But it is a good start with web builders. Let's see how it works. --Gurkan 2009/8/23 David Jencks david_jen...@yahoo.com Hi Gurkan, to get a ModuleBuilderExtension to do anything it has to be associated with a ModuleBuilder for a type of ee app which will call it at the appropriate points during deployment. I'm not sure what kinds of ee modules web beans can included in, but I added the OWBMBE to the jetty7 and tomcat6 builders in rev 806989. If this is not quite right you should be able to figure out what to do with other module builders. hope this is in the right direction :-) thanks david jencks On Aug 23, 2009, at 5:32 AM, Gurkan Erdogdu wrote: Hi David; I have deployed plugins(2 car ) into the server. Server calls OpenWebBeansModuleBuilderExtension while it starts. But it never calls createModule, addGBeans methods. Do I have to configure something for this? Thanks; --Gurkan 2009/8/22 Gurkan Erdogdu cgurkanerdo...@gmail.com Great help David! Thanks a lot. I will try to fill the blanks. --Gurkan 2009/8/22 David Blevins david.blev...@visi.com Great summary, thanks! So as I mentioned on the OpenEJB list and the reason I kicked the thread over here is that the ServletContextListener approach to scanning doesn't work as none of those things exist at deploy time. To try and move things forward I've created a basic plugin for OpenWebBeans that can serve as a starting point for the integration. This will help get us out of the abstract and right down to the nuts and bolts. DEPLOYMENT Long story short, the code that scans the managed bean classes for @Resource etc. goes here: http://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/openwebbeans/geronimo-openwebbeans-builder/src/main/java/org/apache/geronimo/openwebbeans/deployment/OpenWebBeansModuleBuilderExtension.java The code to do the @Resource scanning is actually in there already, it's the line like this: namingBuilders.buildNaming(webApp, jettyWebApp, webModule, buildingContext); What needs to happen in this class is we need to get a complete list of the managed bean classes so they can be scanned by the Geronimo naming builder. This class is an extension to the Geronimo deployment system, so no webapp objects exist yet. I know that the OpenWebBeans code doesn't currently work like this and relies on ServetContext and other things. We will have to find a way to get that to work without the use of any servet APIs. A bonus is that you can install any servlets or filters or listeners you like into the webapp so when it boots, anything you'd like to add will be there without the user having to add it. A pretty cool advantage to being part of the deployment system. I've got some code in there that adds a ServletContextListener -- I left the classname of the listener blank, you just need to fill it in. For a great example of what the JSF deployer extension looks like, see this class: https://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/myfaces/geronimo-myfaces-builder/src/main/java/org/apache/geronimo/myfaces/deployment/MyFacesModuleBuilderExtension.java RUNTIME Here's where you can add any startup and shutdown code you'd like: http://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/OpenWebBeansGBean.java This will be guaranteed to run just before the webapp starts up and stop just after the webapp stops. Great place for initialization code and taking care of getting any hooks into Geronimo that you might need/want for while the webapp is running. This doesn't tackle everything on the TODO list but is a step in the right direction. -David On Aug 20, 2009, at 8:01 AM, Gurkan Erdogdu wrote: I want to give brief introduction about current implementation in the view of integration points Brief Summary About Current Situation - Currently we bootstrap OpenWebBeans via ServletContextListener. It supports following containers - Java Web Containers like Jetty, Tomcat etc. - Tomcat Embeddable OpenEJB Container If developer wants to use OWB functionality in his application, it has to configure its web.xml to include some OWB specific classes. For EJB functionality, we use embeddable Tomcat OpenEJB container. To use EJB functionality, developer must annotate their EJB classes with OWB specific Interceptor class. How OWB Boots Currently(From integration point of view) --- 1* Web Container calls OWB specific context listener's application started method 2* OWB container scans related classes from the artifacts (if META-INF/beans.xml, or WEB-INF/beans.xml exists. beans.xml is a marker for deployment) 3* If developer
Re: Webapp Annotation processing for 299
Quick correction, rar modules are not eligible as far as I know. But it is defined in the specification. From the specification, defined in Chapter - 12.1 Bean Deployment Archives In an application deployed as an ear, the container searches every bean deployment archive belonging to the ear. The bean deployment archive may be library jars, ejb jars, rars or WEB-INF/classes directory. Thanks; --Gurkan 2009/8/25 David Blevins david.blev...@visi.com Quick correction, rar modules are not eligible as far as I know. Basically, anywhere you can use a persistence.xml you can have a beans.xml. -David On Aug 23, 2009, at 11:00 PM, Gurkan Erdogdu wrote: Thanks a lot david jencks. Actually, webbeans can be included in any ejb,war,ear,rar and library modules. But it is a good start with web builders. Let's see how it works. --Gurkan 2009/8/23 David Jencks david_jen...@yahoo.com Hi Gurkan, to get a ModuleBuilderExtension to do anything it has to be associated with a ModuleBuilder for a type of ee app which will call it at the appropriate points during deployment. I'm not sure what kinds of ee modules web beans can included in, but I added the OWBMBE to the jetty7 and tomcat6 builders in rev 806989. If this is not quite right you should be able to figure out what to do with other module builders. hope this is in the right direction :-) thanks david jencks On Aug 23, 2009, at 5:32 AM, Gurkan Erdogdu wrote: Hi David; I have deployed plugins(2 car ) into the server. Server calls OpenWebBeansModuleBuilderExtension while it starts. But it never calls createModule, addGBeans methods. Do I have to configure something for this? Thanks; --Gurkan 2009/8/22 Gurkan Erdogdu cgurkanerdo...@gmail.com Great help David! Thanks a lot. I will try to fill the blanks. --Gurkan 2009/8/22 David Blevins david.blev...@visi.com Great summary, thanks! So as I mentioned on the OpenEJB list and the reason I kicked the thread over here is that the ServletContextListener approach to scanning doesn't work as none of those things exist at deploy time. To try and move things forward I've created a basic plugin for OpenWebBeans that can serve as a starting point for the integration. This will help get us out of the abstract and right down to the nuts and bolts. DEPLOYMENT Long story short, the code that scans the managed bean classes for @Resource etc. goes here: http://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/openwebbeans/geronimo-openwebbeans-builder/src/main/java/org/apache/geronimo/openwebbeans/deployment/OpenWebBeansModuleBuilderExtension.java The code to do the @Resource scanning is actually in there already, it's the line like this: namingBuilders.buildNaming(webApp, jettyWebApp, webModule, buildingContext); What needs to happen in this class is we need to get a complete list of the managed bean classes so they can be scanned by the Geronimo naming builder. This class is an extension to the Geronimo deployment system, so no webapp objects exist yet. I know that the OpenWebBeans code doesn't currently work like this and relies on ServetContext and other things. We will have to find a way to get that to work without the use of any servet APIs. A bonus is that you can install any servlets or filters or listeners you like into the webapp so when it boots, anything you'd like to add will be there without the user having to add it. A pretty cool advantage to being part of the deployment system. I've got some code in there that adds a ServletContextListener -- I left the classname of the listener blank, you just need to fill it in. For a great example of what the JSF deployer extension looks like, see this class: https://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/myfaces/geronimo-myfaces-builder/src/main/java/org/apache/geronimo/myfaces/deployment/MyFacesModuleBuilderExtension.java RUNTIME Here's where you can add any startup and shutdown code you'd like: http://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/OpenWebBeansGBean.java This will be guaranteed to run just before the webapp starts up and stop just after the webapp stops. Great place for initialization code and taking care of getting any hooks into Geronimo that you might need/want for while the webapp is running. This doesn't tackle everything on the TODO list but is a step in the right direction. -David On Aug 20, 2009, at 8:01 AM, Gurkan Erdogdu wrote: I want to give brief introduction about current implementation in the view of integration points Brief Summary About Current Situation - Currently we bootstrap OpenWebBeans via ServletContextListener. It supports following containers - Java Web Containers like Jetty, Tomcat etc. - Tomcat Embeddable OpenEJB Container
Re: Webapp Annotation processing for 299
Hi David; I have deployed plugins(2 car ) into the server. Server calls OpenWebBeansModuleBuilderExtension while it starts. But it never calls createModule, addGBeans methods. Do I have to configure something for this? Thanks; --Gurkan 2009/8/22 Gurkan Erdogdu cgurkanerdo...@gmail.com Great help David! Thanks a lot. I will try to fill the blanks. --Gurkan 2009/8/22 David Blevins david.blev...@visi.com Great summary, thanks! So as I mentioned on the OpenEJB list and the reason I kicked the thread over here is that the ServletContextListener approach to scanning doesn't work as none of those things exist at deploy time. To try and move things forward I've created a basic plugin for OpenWebBeans that can serve as a starting point for the integration. This will help get us out of the abstract and right down to the nuts and bolts. DEPLOYMENT Long story short, the code that scans the managed bean classes for @Resource etc. goes here: http://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/openwebbeans/geronimo-openwebbeans-builder/src/main/java/org/apache/geronimo/openwebbeans/deployment/OpenWebBeansModuleBuilderExtension.java The code to do the @Resource scanning is actually in there already, it's the line like this: namingBuilders.buildNaming(webApp, jettyWebApp, webModule, buildingContext); What needs to happen in this class is we need to get a complete list of the managed bean classes so they can be scanned by the Geronimo naming builder. This class is an extension to the Geronimo deployment system, so no webapp objects exist yet. I know that the OpenWebBeans code doesn't currently work like this and relies on ServetContext and other things. We will have to find a way to get that to work without the use of any servet APIs. A bonus is that you can install any servlets or filters or listeners you like into the webapp so when it boots, anything you'd like to add will be there without the user having to add it. A pretty cool advantage to being part of the deployment system. I've got some code in there that adds a ServletContextListener -- I left the classname of the listener blank, you just need to fill it in. For a great example of what the JSF deployer extension looks like, see this class: https://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/myfaces/geronimo-myfaces-builder/src/main/java/org/apache/geronimo/myfaces/deployment/MyFacesModuleBuilderExtension.java RUNTIME Here's where you can add any startup and shutdown code you'd like: http://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/OpenWebBeansGBean.java This will be guaranteed to run just before the webapp starts up and stop just after the webapp stops. Great place for initialization code and taking care of getting any hooks into Geronimo that you might need/want for while the webapp is running. This doesn't tackle everything on the TODO list but is a step in the right direction. -David On Aug 20, 2009, at 8:01 AM, Gurkan Erdogdu wrote: I want to give brief introduction about current implementation in the view of integration points Brief Summary About Current Situation - Currently we bootstrap OpenWebBeans via ServletContextListener. It supports following containers - Java Web Containers like Jetty, Tomcat etc. - Tomcat Embeddable OpenEJB Container If developer wants to use OWB functionality in his application, it has to configure its web.xml to include some OWB specific classes. For EJB functionality, we use embeddable Tomcat OpenEJB container. To use EJB functionality, developer must annotate their EJB classes with OWB specific Interceptor class. How OWB Boots Currently(From integration point of view) --- 1* Web Container calls OWB specific context listener's application started method 2* OWB container scans related classes from the artifacts (if META-INF/beans.xml, or WEB-INF/beans.xml exists. beans.xml is a marker for deployment) 3* If developer configures OWB to use EJB functionality, for each scanned class, it asks OpenEJB to learn whether it is an EJB class or not (Using EJB Plugin that is written accroding to the OpenEJB) 4* If it is an EJB class, it creates EJB bean and register it with the OWB container otherwise if it is a Java EE defined Managed Bean Class, it creates a Managed Bean and register it with the OWB container. Developer Responsibility to Use OWB 1* Add servlet context listener to his web module's web.xml 2* Annotate EJB classes with OWB interceptor 3* Configure OWB container to use EJB functionality 4* Configure some OWB specific parameters (For example : if use JMS injections, specify ConnectionFactory JNDI name) Current Problems
Re: Webapp Annotation processing for 299
Great help David! Thanks a lot. I will try to fill the blanks. --Gurkan 2009/8/22 David Blevins david.blev...@visi.com Great summary, thanks! So as I mentioned on the OpenEJB list and the reason I kicked the thread over here is that the ServletContextListener approach to scanning doesn't work as none of those things exist at deploy time. To try and move things forward I've created a basic plugin for OpenWebBeans that can serve as a starting point for the integration. This will help get us out of the abstract and right down to the nuts and bolts. DEPLOYMENT Long story short, the code that scans the managed bean classes for @Resource etc. goes here: http://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/openwebbeans/geronimo-openwebbeans-builder/src/main/java/org/apache/geronimo/openwebbeans/deployment/OpenWebBeansModuleBuilderExtension.java The code to do the @Resource scanning is actually in there already, it's the line like this: namingBuilders.buildNaming(webApp, jettyWebApp, webModule, buildingContext); What needs to happen in this class is we need to get a complete list of the managed bean classes so they can be scanned by the Geronimo naming builder. This class is an extension to the Geronimo deployment system, so no webapp objects exist yet. I know that the OpenWebBeans code doesn't currently work like this and relies on ServetContext and other things. We will have to find a way to get that to work without the use of any servet APIs. A bonus is that you can install any servlets or filters or listeners you like into the webapp so when it boots, anything you'd like to add will be there without the user having to add it. A pretty cool advantage to being part of the deployment system. I've got some code in there that adds a ServletContextListener -- I left the classname of the listener blank, you just need to fill it in. For a great example of what the JSF deployer extension looks like, see this class: https://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/myfaces/geronimo-myfaces-builder/src/main/java/org/apache/geronimo/myfaces/deployment/MyFacesModuleBuilderExtension.java RUNTIME Here's where you can add any startup and shutdown code you'd like: http://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/OpenWebBeansGBean.java This will be guaranteed to run just before the webapp starts up and stop just after the webapp stops. Great place for initialization code and taking care of getting any hooks into Geronimo that you might need/want for while the webapp is running. This doesn't tackle everything on the TODO list but is a step in the right direction. -David On Aug 20, 2009, at 8:01 AM, Gurkan Erdogdu wrote: I want to give brief introduction about current implementation in the view of integration points Brief Summary About Current Situation - Currently we bootstrap OpenWebBeans via ServletContextListener. It supports following containers - Java Web Containers like Jetty, Tomcat etc. - Tomcat Embeddable OpenEJB Container If developer wants to use OWB functionality in his application, it has to configure its web.xml to include some OWB specific classes. For EJB functionality, we use embeddable Tomcat OpenEJB container. To use EJB functionality, developer must annotate their EJB classes with OWB specific Interceptor class. How OWB Boots Currently(From integration point of view) --- 1* Web Container calls OWB specific context listener's application started method 2* OWB container scans related classes from the artifacts (if META-INF/beans.xml, or WEB-INF/beans.xml exists. beans.xml is a marker for deployment) 3* If developer configures OWB to use EJB functionality, for each scanned class, it asks OpenEJB to learn whether it is an EJB class or not (Using EJB Plugin that is written accroding to the OpenEJB) 4* If it is an EJB class, it creates EJB bean and register it with the OWB container otherwise if it is a Java EE defined Managed Bean Class, it creates a Managed Bean and register it with the OWB container. Developer Responsibility to Use OWB 1* Add servlet context listener to his web module's web.xml 2* Annotate EJB classes with OWB interceptor 3* Configure OWB container to use EJB functionality 4* Configure some OWB specific parameters (For example : if use JMS injections, specify ConnectionFactory JNDI name) Current Problems - 1* Currently we just support WAR module with embeddable EJB. 2* Developer requires to update WAR/EJB module metadata files to use OWB. 3* Standalone EJB JAR,RAR, EAR not supported 4* Injections into Managed Beans class not well supported
Re: Webapp Annotation processing for 299
Hi; Thanks for kicking discussion David. As you may already know Java EE 6 will be planned to release on November. Do you have any plan or roadmap to integrate JSR-299 with Geronimo? We are working hard to implement full specification but it has some parts that requires to integrate with Java EE server tightly. Thanks; --Gurkan 2009/8/20 David Blevins david.blev...@visi.com I've been talking with Gurkan of OpenWebBeans over on the OpenEJB list and it seemed like a good idea to kick the thread over here as well. The long and short of it is that we'll need to scan 299 managed beans at deploy time exactly as we do for JSF. Wanted to point him at the JSF scanning code, but can't remember the details. Anyone remember? An svn link is fine. -David -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com
Re: Webapp Annotation processing for 299
We'd be interested in any details about what integration work might be needed to add this to Geronimo. It is a really fascinating thing that you support us to finish implementation and pass TCK :) We really need a help. Thanks; --Gurkan 2009/8/20 Rick McGuire rick...@gmail.com Gurkan Erdogdu wrote: Hi; Thanks for kicking discussion David. As you may already know Java EE 6 will be planned to release on November. Do you have any plan or roadmap to integrate JSR-299 with Geronimo? We have a tentative roadmap for implementing the Web Profile at: http://cwiki.apache.org/confluence/display/GMOxDEV/Road+map+for+JEE6+Web+Profile For the JEE6 plans, the web profile did not include JSR 299, which I guess has changed recently. We'd be interested in any details about what integration work might be needed to add this to Geronimo. Rick We are working hard to implement full specification but it has some parts that requires to integrate with Java EE server tightly. Thanks; --Gurkan 2009/8/20 David Blevins david.blev...@visi.com mailto: david.blev...@visi.com I've been talking with Gurkan of OpenWebBeans over on the OpenEJB list and it seemed like a good idea to kick the thread over here as well. The long and short of it is that we'll need to scan 299 managed beans at deploy time exactly as we do for JSF. Wanted to point him at the JSF scanning code, but can't remember the details. Anyone remember? An svn link is fine. -David -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com
Re: Webapp Annotation processing for 299
I want to give brief introduction about current implementation in the view of integration points Brief Summary About Current Situation - Currently we bootstrap OpenWebBeans via ServletContextListener. It supports following containers - Java Web Containers like Jetty, Tomcat etc. - Tomcat Embeddable OpenEJB Container If developer wants to use OWB functionality in his application, it has to configure its web.xml to include some OWB specific classes. For EJB functionality, we use embeddable Tomcat OpenEJB container. To use EJB functionality, developer must annotate their EJB classes with OWB specific Interceptor class. How OWB Boots Currently(From integration point of view) --- 1* Web Container calls OWB specific context listener's application started method 2* OWB container scans related classes from the artifacts (if META-INF/beans.xml, or WEB-INF/beans.xml exists. beans.xml is a marker for deployment) 3* If developer configures OWB to use EJB functionality, for each scanned class, it asks OpenEJB to learn whether it is an EJB class or not (Using EJB Plugin that is written accroding to the OpenEJB) 4* If it is an EJB class, it creates EJB bean and register it with the OWB container otherwise if it is a Java EE defined Managed Bean Class, it creates a Managed Bean and register it with the OWB container. Developer Responsibility to Use OWB 1* Add servlet context listener to his web module's web.xml 2* Annotate EJB classes with OWB interceptor 3* Configure OWB container to use EJB functionality 4* Configure some OWB specific parameters (For example : if use JMS injections, specify ConnectionFactory JNDI name) Current Problems - 1* Currently we just support WAR module with embeddable EJB. 2* Developer requires to update WAR/EJB module metadata files to use OWB. 3* Standalone EJB JAR,RAR, EAR not supported 4* Injections into Managed Beans class not well supported. (For example : @Resource, @WebServiceRef, @EJB, @PersistenceUnit,@PersistenceContext.) How Could We Integrate with Geronimo - 1* Geronimo looks for deployment. If it contains beans.xml, it automatically registers OWB servlet context listener with WAR's web.xml at deployment time 2* Automatically registers OWB EJB interceptor with EJBs at deployment time (If module is EJB module or EAR module containing EJB modules) 3* Support EJB JAR, EAR, RAR modules 4* Write EJB Plugin for Geronimo 5* Supports injections for Managed Beans I hope this helps a bit more Thanks; --Gurkan 2009/8/20 Rick McGuire rick...@gmail.com Gurkan Erdogdu wrote: We'd be interested in any details about what integration work might be needed to add this to Geronimo. It is a really fascinating thing that you support us to finish implementation and pass TCK :) We really need a help. I think there is a great willingness to help you with this, but I was looking form something more specific, such as the actual areas/functions where integration assistance is needed. Rick Thanks; --Gurkan 2009/8/20 Rick McGuire rick...@gmail.com mailto:rick...@gmail.com Gurkan Erdogdu wrote: Hi; Thanks for kicking discussion David. As you may already know Java EE 6 will be planned to release on November. Do you have any plan or roadmap to integrate JSR-299 with Geronimo? We have a tentative roadmap for implementing the Web Profile at: http://cwiki.apache.org/confluence/display/GMOxDEV/Road+map+for+JEE6+Web+Profile For the JEE6 plans, the web profile did not include JSR 299, which I guess has changed recently. We'd be interested in any details about what integration work might be needed to add this to Geronimo. Rick We are working hard to implement full specification but it has some parts that requires to integrate with Java EE server tightly. Thanks; --Gurkan 2009/8/20 David Blevins david.blev...@visi.com mailto:david.blev...@visi.com mailto:david.blev...@visi.com mailto:david.blev...@visi.com I've been talking with Gurkan of OpenWebBeans over on the OpenEJB list and it seemed like a good idea to kick the thread over here as well. The long and short of it is that we'll need to scan 299 managed beans at deploy time exactly as we do for JSF. Wanted to point him at the JSF scanning code, but can't remember the details. Anyone remember? An svn link is fine. -David --Gurkan Erdogdu http://gurkanerdogdu.blogspot.com -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com
Re: Whence the geronimo kernel?
Hi Gianny, As a keen observer of the Geronimo dev List , I would like to ask question on this subject. Gianny, do you want to say that there is an UniversalClassLoader for all the server instance that contains the other class loaders. IOW, try to change hierarchical class loaders with the flat class loader repository? Do you mean that if jar is already loaded by the any class loader that is registered in the UniversalClassLoader, it will always load the same jar? Thanks; Gurkan From: Gianny Damour gianny.dam...@optusnet.com.au To: dev@geronimo.apache.org Sent: Thursday, March 12, 2009 12:25:34 PM Subject: Re: Whence the geronimo kernel? On 12/03/2009, at 4:29 AM, David Jencks wrote: On Mar 11, 2009, at 1:46 AM, Gianny Damour wrote: Hi, So let's agree to disagree for now. This may be related to my personal way of comparing stuff which is pretty much limited to: 1. understand what the requirements are. 2. understand how the technologies support these requirements. I do not need all the bells and whistles that a technology offers to fulfill the requirements. Moreover comparing stuff based on technology differentiators not clearly linked to the requirements is pointless. 3. assess best way forward based on above scoring. Key steps are 1 and 2 where stuff offering all the bells and whistles may well be scored as good as other stuff (I clearly do not support over-bloated stuff...). Obviously, I am keen to be proven wrong and adjust accordingly. So far, I am still saying that the main challenge is to properly tune export/import of dependency declarations. For me, the technology is not the core issue and switching is not going to resolve problems. I agree. I doubt Guillaume has seen your additions to classloading in trunk which allow you to not export packages from a classloader. I haven't tried to prove it mathematically but I think that with this feature the classloading models for geronimo and osgi are equivalent in that you can express the same ability to access classes with either of them. Of course, the notation you use to express this and the specific information included in the configuration is different. I think I probably have the most experience with classloading problems in geronimo and the only real problem that arises is loading a jar in two different classloaders. This can be solved by a classloader-per-jar model which offers no theoretical problems to set up in geronimo but practically would take a lot of work (and maven projects to build a plugin per jar). So I think we'll have to see what kind of problems we get with trying to actually use OSGI. Hi, Thinking more about this, I believe we can expedite the implementation of a classloader-per-jar model. Under the hood of a MultiParentClassLoader we can replace the current implementation of find class and resources contracts by an implementation which delegates to a bunch of URLClassLoaders (one per jar). These bunch of URLClassLoaders are global classloaders, i.e. shared across all the configs/MultiParentClassLoaders. The core challenge is to create them in a hierarchy respecting the maven dependency declarations. So, we could install the pom of the dependencies in the repo and lazily parse them when MultiParentClassLoader are created to build this global and share tree of URLClassLoaders. I just started to work on it and I will post back my findings (i should be able to complete this over the week-end). Even if we switch to an OSGi kernel, part of this work may hopefully still be useful. Thanks, Gianny One thing I'd really like actual user data on is how people actually specify osgi classloading info in real life. I'm very aware that in theory you are supposed to specify the package imports and exports for your bundle but I've been told that in real life everyone with a serious osgi project actually specifies the jar dependencies they want using require-bundle. thanks david jencks Thanks, Gianny On 11/03/2009, at 7:11 PM, Guillaume Nodet wrote: On Wed, Mar 11, 2009 at 08:57, Gianny Damour gianny.dam...@optusnet.com.au wrote: Hi, FWIW, I believe that improving the configuration style to simplify the means of creating a bunch of objects in the kernel has more benefits than swapping the classloading infra. On paper OSGi may appear as superior from a classloading isolation perspective; however, I believe the current CLing design is nearly up to par with the OSGi one and that the main challenge is to properly tune export/import dependency declarations. I have to disagree with that. The CLing mechanism is very different in Geronimo (from what I recall) and OSGi. Geronimo uses a multi-parent classloader style with some nice features to be able to hide / never override + parent or self-first delegation. OSGi CLind is very different: the first one is that
[About WebBeans Integration]
Hi folks, We are developing the implementation of the JSR-299 WebBeans specification as an incubator, OpenWebBeans. In the last specification, it says that this functionality must be integrated into the Java EE 6.0 Servers. Currently, OpenWebBeans is working as a plugin (i.e configure in the web.xml via ServletCotnextListener, Filter etc.). Do you have any plan to integrate this stuff into the Geronimo runtime? If so, how could we collaborate on this to start rolling the ball? /Gurkan Incubator OpenWebBeans Project Lead
