Re: About JSR-299 and JSR-330 API
On Wed, Dec 9, 2009 at 2:31 PM, Mark Struberg strub...@yahoo.de wrote: 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 the JSR-330 TCK. There is no separate JSR-330-container or something. So assumed we speak about only the api, then I'm d'accord we should release it as 1.0.0 yeah, that's my understanding as well :-) LieGrue, strub --- Matthias Wessendorf mat...@apache.org schrieb am Mi, 9.12.2009: Von: Matthias Wessendorf mat...@apache.org Betreff: Re: About JSR-299 and JSR-330 API An: d...@geronimo.apache.org CC: openwebbeans-dev@incubator.apache.org Datum: Mittwoch, 9. Dezember 2009, 14:16 IMO would be cool if there is a standalone release of that soon. As this passed the TCK, we even do not need to say alpha or so, on that... -Matthias On Wed, Dec 9, 2009 at 12:28 PM, Gurkan Erdogdu cgurkanerdo...@gmail.com 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 ? Thanks; --Gurkan -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: December Report
looks good so far... On Wed, Dec 9, 2009 at 10:35 AM, Gurkan Erdogdu cgurkanerdo...@gmail.com wrote: Hi folks; I have written our December Report http://wiki.apache.org/incubator/December2009. Today is the last day for sending reports. Thanks; --Gurkan -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
JSR-330
Hi, is there a plan to release these bit separately as well ? (sorry if I am ignorant and this has already been discussed :-) ) -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: About JSR-299 and JSR-330 API
IMO would be cool if there is a standalone release of that soon. As this passed the TCK, we even do not need to say alpha or so, on that... -Matthias On Wed, Dec 9, 2009 at 12:28 PM, Gurkan Erdogdu cgurkanerdo...@gmail.com 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 ? Thanks; --Gurkan -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Apache Web Profile Edition of the Java EE 6 standard ?
FYI http://markmail.org/message/kbnb2imqdohkra7f -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Documentation: first draft
nice!! On Tue, Dec 1, 2009 at 4:27 PM, Gurkan Erdogdu cgurkanerdo...@gmail.com wrote: I gonna add Apache headers to my XSL files and clean the whole. I guess i'll can submit a patch file by the end of this week. Cool, thanks. Do we also need to generate HTML (single and multi/chunk)? Yes, so we can attach HTMLs(single is enough I think) to our website. 2009/12/1 Jean-Louis MONTEIRO jeano...@gmail.com OK, no problem. I gonna add Apache headers to my XSL files and clean the whole. I guess i'll can submit a patch file by the end of this week. Do we also need to generate HTML (single and multi/chunk)? Jean-Louis 2009/12/1 Gurkan Erdogdu cgurkanerdo...@gmail.com Pretty cool. You are not able to assign it yourself because of not being committer currently. I think that we agree on the current format/template. Could you also add other patch/diff files ? Therefore, I can commit those into the webbeans-doc project. --Gurkan 2009/12/1 Jean-Louis MONTEIRO jeano...@gmail.com Done https://issues.apache.org/jira/browse/OWB-183 Gurkan, I was not able to assign it to me, so feel free to do it if you want. Jean-Louis 2009/12/1 Gurkan Erdogdu cgurkanerdo...@gmail.com Better is to create a JIRA issue and attach artifacts to it. You could create a issue here : http://issues.apache.org/jira/browse/OWB Thanks; --Gurkan 2009/12/1 Jean-Louis MONTEIRO jeano...@gmail.com Sorry for the spam it should work better with my gmail. Jean-Louis 2009/12/1 Monteiro Jean-Louis jean-louis.monte...@atosorigin.com *De :* Monteiro Jean-Louis *Envoyé :* mardi 1 décembre 2009 10:28 *À :* openwebbeans-dev@incubator.apache.org *Objet :* Documentation: first draft Hi all, I’ve been working on the documentation. I refactored a lot of things to make all more sexy and professional. Before submitting a patch, I’d like to have your opinion. I’m ready to change whatever you want. Any feedback is welcome. * * *Jean-Louis* -- Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Apache Web Profile Edition of the Java EE 6 standard ?
On Wed, Dec 2, 2009 at 12:39 PM, Mark Struberg strub...@yahoo.de wrote: 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? in my blog there is a link to these specs, the last entry is the managed bean spec. MyFaces implements this Managed Bean stuff as well! Not only Mojarra... I'd like to implement a JSR-299 extension which basically provides an alias between javax.faces.scopes.SessionScoped and javax.enterprise.context.SessionScoped and others. As well as a JSR-299 implementation of the FlashScoped and support for @ManagedBean of course. The goal is to be able to disable the whole DI part of MyFaces/Mojarra somehow (haven't looked at it) and use OWB instead if it is available. sounds pretty cool! txs and LieGrue, strub --- Gurkan Erdogdu cgurkanerdo...@gmail.com schrieb am Mi, 2.12.2009: Von: Gurkan Erdogdu cgurkanerdo...@gmail.com Betreff: Re: Apache Web Profile Edition of the Java EE 6 standard ? An: openwebbeans-dev@incubator.apache.org Datum: Mittwoch, 2. Dezember 2009, 12:29 Yeah, that will be awesome. --Gurkan 2009/12/2 Matthias Wessendorf mat...@apache.org FYI http://markmail.org/message/kbnb2imqdohkra7f -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [RESULT]Re: [VOTE] Gradutation
+1 (for TLP) sorry, was traveling :-) On Thu, Nov 19, 2009 at 8:40 PM, Gurkan Erdogdu gurkanerdo...@yahoo.com wrote: Hi folks; VOTE is now closed after more than 72 hours. OWB community would like to graduate as TLP. It is passed with the following +1's and no 0 or -1. Kevan Miller(PPMC) Gurkan Erdogdu(PPMC) Mark Struberg(PPMC) David Blevins(PPMC) Joe Bergmark Monteiro Jean-Louis I will prepare a draft resolution document and post it here for discussion. After that we can start a new VOTE for it. Thanks; --Gurkan From: Kevan Miller kevan.mil...@gmail.com To: openwebbeans-dev@incubator.apache.org Sent: Thu, November 19, 2009 12:59:34 AM Subject: Re: [VOTE] Gradutation On Nov 16, 2009, at 3:50 PM, Gurkan Erdogdu wrote: Hi folks, There were some discussions related with graduation of the OpenWebBeans podling from incubator. Last time we discussed graduation, main barrier is the lack of community around it. Over couple of weeks, we have diverted and increased our community around the project. Generally, it seems that community would like to graduate as a TLP. To do formal process, I would like to start a VOTE for graduating OWB as TLP. Please cast your VOTEs here. VOTE is open for 72 hours. [-1] Do not graduate as TLP [0 ] Do not care TLP or not [+1] Graduate as TLP This is my +1; Here's my +1. IIUC, this vote is intended to set the direction for graduation. The community will then prepare the community for graduation, determine who will be community members, PMC chair, and draft a resolution. We will then approve that via a vote. That resolution will then be taken to the Incubator PMC. Is that what we're working towards? --kevan -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [DISCUSSION] Draft Resolution Document
looks good to me On Sun, Nov 22, 2009 at 7:04 PM, Gurkan Erdogdu gurkanerdo...@yahoo.com wrote: Hi folks; Below is the draft resolution document for Apache Board? WDYT? All comments are lovely welcome! --Gurkan --- WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project, to be known as Apache OpenWebBeans, related to the implementation of the JSR-299,i.e Contexts and Dependency Injection for the Java EE platform, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC) is hereby established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache OpenWebBeans PMC be and hereby is charged with the creation and maintenance of Apache OpenWebBeans; and be it further RESOLVED, that the office of Vice President, Apache OpenWebBeans be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of Apache OpenWebBeans, and to have primary 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 OpenWebBeans PMC: * Gurkan Erdogdu * Kevan Miller * Mark Struberg * Joe Bergmark * Eric Covener * David Blevins NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gurkan Erdogdu be appointed to the office of Vice President, Apache OpenWebBeans, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that Apache OpenWebBeans be and hereby is tasked with the migration and rationalization of the Apache Incubator OpenWebBeans podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator OpenWebBeans podling encumbered upon the Apache Incubator PMC are hereafter discharged. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Time to move atinject-api over to geronimo?
+1, good point Kevan On Mon, Nov 23, 2009 at 11:01 PM, Kevan Miller kevan.mil...@gmail.com wrote: On Nov 20, 2009, at 8:22 AM, Gurkan Erdogdu wrote: +1. How could we integrate this into geronimo-specs? Kevan, David? Best to start with an email to the geronimo dev list. A Jira and optonally a patch, always helps... --kevan -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [PATCH] component-comp interceptor stack copy
Eric, the right way to provide a patch is by using the JIRA issue tracker. Doing so makes sure they aren't forgotten. Can you please upload your patch ? Thx, Matthias On Tue, Oct 27, 2009 at 1:16 PM, Eric Covener cove...@apache.org wrote: Typo in WebBeansUtil::createNewBean() copying interceptor stack from bean class to managed bean -- see attachment. Contributed By: Joe Bergmark, Eric Covener -- Eric Covener cove...@gmail.com -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: JSR 299 - being outside of JAvaEE 6 container
On Wed, Sep 16, 2009 at 9:49 PM, Gurkan Erdogdu gurkanerdo...@yahoo.com wrote: Actually we are more than this. We can use embeddable OpenEJB in Tomcat with OWB. which is cool. The more blog entries, the better ;-) Greetings, Matthias --Gurkan From: Matthias Wessendorf mat...@apache.org To: openwebbeans-dev@incubator.apache.org Sent: Wednesday, September 16, 2009 6:09:57 PM Subject: JSR 299 - being outside of JAvaEE 6 container Hi, WebBeans - the RI for 299 - has this: http://seamframework.org/Community/WebBeansAndTomcat we do have similar, but I didn't find a wiki or so, on it :-) (or a blog post) Is there some documentation on it ? -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
Re: [ANNOOUNCE] Welcome David Blevins as a new OpenWebBeans Committer
Welcome aboard, David! great to have you here- -M On Tue, Sep 15, 2009 at 10:07 PM, David Blevins david.blev...@visi.com wrote: Thanks All! Great little community here. -David On Sep 14, 2009, at 4:54 PM, Kevan Miller wrote: All, The Apache OpenWebBeans PMC is pleased to announce that David Blevins has accepted our invitation to become an OpenWebBeans committer. It's great to have David joining our project. Welcome David! --kevan -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: JSR 299 - being outside of JAvaEE 6 container
On Wed, Sep 16, 2009 at 5:37 PM, Mark Struberg strub...@yahoo.de wrote: You are right, we are actually pretty bad at selling our selfs ;) but you may run our guess sample with jetty + MyFaces (currently 1.2) with $ mvn -Pjetty clean package jetty:run I know. Used it already on a JSF2.0 talk :-) We could perhaps also move over to the JSF-2 branch of MyFaces. +1 :) LieGrue, strub --- On Wed, 9/16/09, Matthias Wessendorf mat...@apache.org wrote: From: Matthias Wessendorf mat...@apache.org Subject: JSR 299 - being outside of JAvaEE 6 container To: openwebbeans-dev@incubator.apache.org Date: Wednesday, September 16, 2009, 5:09 PM Hi, WebBeans - the RI for 299 - has this: http://seamframework.org/Community/WebBeansAndTomcat we do have similar, but I didn't find a wiki or so, on it :-) (or a blog post) Is there some documentation on it ? -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
Re: Graduation?
On Wed, Sep 9, 2009 at 7:54 PM, Kevan Miller kevan.mil...@gmail.com wrote: On Sep 9, 2009, at 12:26 PM, Mark Struberg wrote: Sorry for repeating myself: I think we should wait for the 330 and 299 specs to settle, and THEN we can decide what to do. I feel uncomfortable with being promoted from incubator without having the API pretty stable. Once this point is reached, I look pretty confident that OWB will find a well established place in the community. I understand that point. Personally, I think I've been guilty of allowing spec instabilities to affect my judgement on community readiness (or at least affecting how much I pushed the community to consider graduation). IMO, I think that was wrong. I should not be allowing external factors to be affecting my community evaluation. There is certainly an indirect effect of spec resolution -- as spec issues are resolved, hopefully we'll see an increase in users and more projects interested in participating. This could happen pre or post graduation... +1 --kevan -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Graduation?
+1 on the graduation - I agree with Kevan, that this (little) community is on the right way. Instead of being a sub-project, I'd vote to have OWB becoming a TLP. One reason is that by being standalone it is easier to ensure the project is tied to closely to Geronimo, which makes distribution on other containers easier. -Matthias On Wed, Sep 9, 2009 at 2:11 AM, Mohammad Nour El-Dinnour.moham...@gmail.com wrote: -1 Allow me to disagree with you Gurkan, IMHO I think OWN should be a TLP project. I know it is to some extent related to JEE but IMO it defines a generic and extensible model for dependency injection and contextual programming which is not restricted to JEE, so being a sub-project to Geronimo will give the community users the impression that we only support JEE. I think we should follow the model of Tomcat and OpenEJB, which is a separate TLP and being integrable with other ASF projects like Geronimo for example. And for the communit, being a separate TLP will not be affected and we could get more contributers and committers and a big example on that is DBlevins. On Tue, Sep 8, 2009 at 8:30 PM, Mark Strubergstrub...@yahoo.de wrote: +1 LieGrue, strub --- On Tue, 9/8/09, Gurkan Erdogdu gurkanerdo...@yahoo.com wrote: From: Gurkan Erdogdu gurkanerdo...@yahoo.com Subject: Re: Graduation? To: openwebbeans-dev@incubator.apache.org Date: Tuesday, September 8, 2009, 8:23 PM Hi Kevan; Firstly its very good news for us! I personally think that we can continue to implement OWB as a sub-project under Geronimo. Geronimo has a stable community so we can also benefit from its diverse community and its reputation. Moreover, it ease the integration OWB with other Geronimo modules like EJB, JSF etc. So this is my +1 as it is a sub-project under Geronimo. --Gurkan From: Kevan Miller kevan.mil...@gmail.com To: openwebbeans-dev@incubator.apache.org Sent: Tuesday, September 8, 2009 6:00:44 PM Subject: Graduation? All, I wanted to checkpoint with the community about their thoughts regarding Incubator Graduation. I don't want the community to be too focused on implementation issues and forget about an important goal -- getting you out of the Apache Incubator! IMO, this community displays nearly all of the characteristics that I would look for from a successful Incubator project: you've successfully created several releases while operating in a clear, open, and welcoming manner. All of this while facing some significant challenges as the JSR 299 spec has been an ever shifting target. I'd like to see us moving towards graduation. To start things off, is the community interested in becoming a top-level project? Or would you rather graduate as a sub-project of an existing TLP? --kevan -- 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 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
JSR 299 / 330
http://weblogs.java.net/blog/rogerk/archive/2009/09/04/contexts-and-dependency-injection-jsr-299-and-glassfish -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: JSR 299 / 330
+1 that would be cool! On Wed, Sep 9, 2009 at 12:58 PM, Gurkan Erdogducgurkanerdo...@gmail.com wrote: Actually we can also blogs/posts/examples. We got very good 2 examples related with JSF. --Gurkan 2009/9/9 Matthias Wessendorf mat...@apache.org http://weblogs.java.net/blog/rogerk/archive/2009/09/04/contexts-and-dependency-injection-jsr-299-and-glassfish -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
java.lang.NoClassDefFoundError: javax/interceptor/AroundInvoke
Hi, running TRUNK and JSF 2.0, I am getting this when accessing a XHTML page: java.lang.NoClassDefFoundError: javax/interceptor/AroundInvoke at org.apache.webbeans.intercept.InterceptorUtil.isWebBeansBusinessMethod(InterceptorUtil.java:60) at org.apache.webbeans.intercept.InterceptorHandler.invoke(InterceptorHandler.java:68) at org.apache.webbeans.conversation.ConversationImpl_$$_javassist_0.updateTimeOut(ConversationImpl_$$_javassist_0.java) at org.apache.webbeans.jsf.WebBeansPhaseListener.beforePhase(WebBeansPhaseListener.java:167) at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:212) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:311) this was working in June - Question is why is there no dependency bundled ? -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: java.lang.NoClassDefFoundError: javax/interceptor/AroundInvoke
it is my own application :) I added the dependency and set the scope to RUNTIME. So that seems to be the work-around for Jetty On Wed, Aug 26, 2009 at 11:42 AM, Gurkan Erdogdugurkanerdo...@yahoo.com wrote: Hi Matthias; We bundle jar via Jetty profile becuase of other Java EE servers contains this jar. So you can run samples via -Pjetty like this mvn jetty:run -Pjetty Hope,this works. Thanks; From: Matthias Wessendorf mat...@apache.org To: openwebbeans-dev@incubator.apache.org Sent: Wednesday, August 26, 2009 11:35:51 AM Subject: java.lang.NoClassDefFoundError: javax/interceptor/AroundInvoke Hi, running TRUNK and JSF 2.0, I am getting this when accessing a XHTML page: java.lang.NoClassDefFoundError: javax/interceptor/AroundInvoke at org.apache.webbeans.intercept.InterceptorUtil.isWebBeansBusinessMethod(InterceptorUtil.java:60) at org.apache.webbeans.intercept.InterceptorHandler.invoke(InterceptorHandler.java:68) at org.apache.webbeans.conversation.ConversationImpl_$$_javassist_0.updateTimeOut(ConversationImpl_$$_javassist_0.java) at org.apache.webbeans.jsf.WebBeansPhaseListener.beforePhase(WebBeansPhaseListener.java:167) at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:212) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:311) this was working in June - Question is why is there no dependency bundled ? -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
WebBeans eating JSF 2.0 annotations ?
Hi,
is it possible that the current trunk is _eating_ JSF 2.0 annotations ?
someCode
...
import javax.faces.bean.ManagedBean;
import javax.faces.bean.SessionScoped;
@ManagedBean(name=playersBean)
@SessionScoped
public class ViewParamsBean
{
...
/someCode
In June (before reflecting the javax.enterprise.context changes) it was working.
Now expressions like #{playersBean} are simply ignored ;-)
Demo project is here:
https://facesgoodies.googlecode.com/svn/CGN/trunk/
-Matthias
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: javax.enterprise.inject.CreationException: java.lang.ClassFormatError: Duplicate interface name ...
nope On Wed, Aug 26, 2009 at 3:42 PM, Gurkan Erdogducgurkanerdo...@gmail.com wrote: There may be multiple same jars in your classpath. 2009/8/26 Matthias Wessendorf mat...@apache.org Hi my code is here: https://facesgoodies.googlecode.com/svn/CGN/trunk/ running the command mvn jetty:run and accessing this URL: http://localhost:8080/faces/cocktail.xhtml I am getting this: javax.enterprise.inject.CreationException: java.lang.ClassFormatError: Duplicate interface name in class file de/jug/cologne/webbeans/model/CocktailSet_$$_javassist_2 at org.apache.webbeans.component.AbstractBean.create(AbstractBean.java:174) at org.apache.webbeans.context.AbstractContext.getInstance(AbstractContext.java:173) at org.apache.webbeans.context.AbstractContext.get(AbstractContext.java:147) at org.apache.webbeans.intercept.InterceptorHandler.invoke(InterceptorHandler.java:65) at de.jug.cologne.webbeans.CocktailBean_$$_javassist_1.isInShopping(CocktailBean_$$_javassist_1.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at javax.el.BeanELResolver.getValue(BeanELResolver.java:293) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:175) at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72) at com.sun.el.parser.AstValue.getValue(AstValue.java:138) at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:206) at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:102) at javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:181) at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:412) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1603) at javax.faces.render.Renderer.encodeChildren(Renderer.java:168) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:844) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1609) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1612) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1612) at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:271) at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:126) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:124) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:103) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:311) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502) I am not exactly sure what the really means. No I have done no investigations :-) -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: WebBeans eating JSF 2.0 annotations ?
On Wed, Aug 26, 2009 at 5:17 PM, Mark Strubergstrub...@yahoo.de wrote:
for what I know (discussion on wb-dev) JSF apps should use JSR-299 @ScopeType
annotated scopes (renamed to @NormalScope in the latest spec) and not faces
scopes. I did hope that we could unify all scopes by generally using JSR-330
javax.inject.Scope in all EE fields. But that will not work until JSR-299
also recognizes and treats JSR-330 scopes as normal scopes.
WTF ? :)
It is kinda odd that JSF 2.0 has should use the 299 stuff. Standalone,
ok all fine (not tested).
But even if there are both in the game jsf2.0 and 299, they should
just work (or at least I should
get a warning that the bean is using a (good) -sorry- incorrect... annotation.
Basically this is a total mess. Annontations work standalone, but not
when adding some heavyweight
stuff (like 299) to the game ? Oh boy...
-Matthias
LieGrue,
strub
--- On Wed, 8/26/09, Matthias Wessendorf mat...@apache.org wrote:
From: Matthias Wessendorf mat...@apache.org
Subject: Re: WebBeans eating JSF 2.0 annotations ?
To: openwebbeans-dev@incubator.apache.org
Date: Wednesday, August 26, 2009, 5:11 PM
has no effect. The beast can't find
the JSF beans.
Due to lack of time, I am going with JSF 2.0 standalone.
Question is: as it was working the current behavior is a
regression,
has there been any testing on OBW + JSF 2.0 ?
-Matthias
On Wed, Aug 26, 2009 at 3:45 PM, Gurkan Erdogducgurkanerdo...@gmail.com
wrote:
It must not eat.
But one point,
You still use old XML configuration file format. As a
default OWB uses new
XML format. Add
https://svn.apache.org/repos/asf/incubator/openwebbeans/trunk/samples/guess/src/main/resources/META-INF/openwebbeans/openwebbeans.properties
in your project resources/META-INF/openwebbeans folder
and sure that all
libraries are ok.
You can look necessary libs from guess.war . You can
create it from mvn
package -Pjetty.
--Gurkan
2009/8/26 Matthias Wessendorf mat...@apache.org
Hi,
is it possible that the current trunk is _eating_
JSF 2.0 annotations ?
someCode
...
import javax.faces.bean.ManagedBean;
import javax.faces.bean.SessionScoped;
@ManagedBean(name=playersBean)
@SessionScoped
public class ViewParamsBean
{
...
/someCode
In June (before reflecting the
javax.enterprise.context changes) it was
working.
Now expressions like #{playersBean} are simply
ignored ;-)
Demo project is here:
https://facesgoodies.googlecode.com/svn/CGN/trunk/
-Matthias
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
--
Gurkan Erdogdu
http://gurkanerdogdu.blogspot.com
--
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
Re: WebBeans eating JSF 2.0 annotations ?
On Wed, Aug 26, 2009 at 5:23 PM, Matthias Wessendorfmat...@apache.org wrote:
On Wed, Aug 26, 2009 at 5:17 PM, Mark Strubergstrub...@yahoo.de wrote:
for what I know (discussion on wb-dev) JSF apps should use JSR-299
@ScopeType annotated scopes (renamed to @NormalScope in the latest spec) and
not faces scopes. I did hope that we could unify all scopes by generally
using JSR-330 javax.inject.Scope in all EE fields. But that will not work
until JSR-299 also recognizes and treats JSR-330 scopes as normal scopes.
WTF ? :)
It is kinda odd that JSF 2.0 has should use the 299 stuff. Standalone,
ok all fine (not tested).
But even if there are both in the game jsf2.0 and 299, they should
just work (or at least I should
get a warning that the bean is using a (good) -sorry- incorrect... annotation.
Basically this is a total mess. Annontations work standalone, but not
when adding some heavyweight
stuff (like 299) to the game ? Oh boy...
I am pretty sure that this will introcude a lot of fun to folks
writing JSF 2.0 applications,
if your statement is true. That would worse than the JSP 2.1
dependency (with JSF 1.2)
I filed this bug:
https://issues.apache.org/jira/browse/OWB-133
At least there should be some help. Not everybody is thrilled to
replace annotations based on
the environment (at least not me)
-Matthias
LieGrue,
strub
--- On Wed, 8/26/09, Matthias Wessendorf mat...@apache.org wrote:
From: Matthias Wessendorf mat...@apache.org
Subject: Re: WebBeans eating JSF 2.0 annotations ?
To: openwebbeans-dev@incubator.apache.org
Date: Wednesday, August 26, 2009, 5:11 PM
has no effect. The beast can't find
the JSF beans.
Due to lack of time, I am going with JSF 2.0 standalone.
Question is: as it was working the current behavior is a
regression,
has there been any testing on OBW + JSF 2.0 ?
-Matthias
On Wed, Aug 26, 2009 at 3:45 PM, Gurkan Erdogducgurkanerdo...@gmail.com
wrote:
It must not eat.
But one point,
You still use old XML configuration file format. As a
default OWB uses new
XML format. Add
https://svn.apache.org/repos/asf/incubator/openwebbeans/trunk/samples/guess/src/main/resources/META-INF/openwebbeans/openwebbeans.properties
in your project resources/META-INF/openwebbeans folder
and sure that all
libraries are ok.
You can look necessary libs from guess.war . You can
create it from mvn
package -Pjetty.
--Gurkan
2009/8/26 Matthias Wessendorf mat...@apache.org
Hi,
is it possible that the current trunk is _eating_
JSF 2.0 annotations ?
someCode
...
import javax.faces.bean.ManagedBean;
import javax.faces.bean.SessionScoped;
@ManagedBean(name=playersBean)
@SessionScoped
public class ViewParamsBean
{
...
/someCode
In June (before reflecting the
javax.enterprise.context changes) it was
working.
Now expressions like #{playersBean} are simply
ignored ;-)
Demo project is here:
https://facesgoodies.googlecode.com/svn/CGN/trunk/
-Matthias
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
--
Gurkan Erdogdu
http://gurkanerdogdu.blogspot.com
--
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
Servlet 3.0 ?
Hello, as WebBeans spec is kinda late - so is Servlet 3.0 - I was wondering if you guys could leverage some of their stuff, like the @Filter annotation or the web-xml fragments stuff ? (e.g. for WebBeansJSFFilter), for the -jsf module ? Thx, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: WebBeans eating JSF 2.0 annotations ?
mvn jetty:run-exploded fixes that. I guess that's JSF's problem (I am
currently using the RI)
Oh boy! :)
On Wed, Aug 26, 2009 at 5:45 PM, Matthias Wessendorfmat...@apache.org wrote:
On Wed, Aug 26, 2009 at 5:39 PM, Mark Strubergstrub...@yahoo.de wrote:
In fact we (OWB) should provide standard context implementations for JSF
annotated scopes.
The whole picture:
.) JSF scanns the classpath for JSF annotations
.) OWB scanns the classpath for JSR-299 annotations
In fact, I assume (not having looked at the code) that MyFaces provides kind
of a mini DI container in the EL code. So any EL which will get through to
the faces EL handler will successfully resolve those scoped beans
Otoh, OWB also provides an EL handler which is dominant (prior in the EL
chain). OWB currently simply ignores the javax.faces.scope annotations since
they are 'unknown' for OWB. So this very class will look like a bean which
has no annotations at all.
The problem arises latest if JSF scoped beans need to be injected into
JSR-299 beans and vice versa...
an idea how to resolve this:
We need to provide context implementations for the faces scopes in the
webbeans-jsf module and let OWB do all the resolving.
wdyt?
yes, that's true. It is really a PITA to have three different ways to
@inject stuff (in JavaEE - well the javax.faces.bean.** stuff is
optional)
I am pretty sure this will actually cause lot's of pain, trouble and
bad blogs on JavaEE 6 (heck, deserved! :-) )
Are you able to bring this dilemma up on some EG ?
(mismatch of all the stuff)
-Matthias
LieGrue,
strub
--- On Wed, 8/26/09, Matthias Wessendorf mat...@apache.org wrote:
From: Matthias Wessendorf mat...@apache.org
Subject: Re: WebBeans eating JSF 2.0 annotations ?
To: openwebbeans-dev@incubator.apache.org
Date: Wednesday, August 26, 2009, 5:26 PM
On Wed, Aug 26, 2009 at 5:23 PM,
Matthias Wessendorfmat...@apache.org
wrote:
On Wed, Aug 26, 2009 at 5:17 PM, Mark Strubergstrub...@yahoo.de
wrote:
for what I know (discussion on wb-dev) JSF apps
should use JSR-299 @ScopeType annotated scopes (renamed to
@NormalScope in the latest spec) and not faces scopes. I did
hope that we could unify all scopes by generally using
JSR-330 javax.inject.Scope in all EE fields. But that will
not work until JSR-299 also recognizes and treats JSR-330
scopes as normal scopes.
WTF ? :)
It is kinda odd that JSF 2.0 has should use the 299
stuff. Standalone,
ok all fine (not tested).
But even if there are both in the game jsf2.0 and 299,
they should
just work (or at least I should
get a warning that the bean is using a (good) -sorry-
incorrect... annotation.
Basically this is a total mess. Annontations work
standalone, but not
when adding some heavyweight
stuff (like 299) to the game ? Oh boy...
I am pretty sure that this will introcude a lot of fun to
folks
writing JSF 2.0 applications,
if your statement is true. That would worse than the JSP
2.1
dependency (with JSF 1.2)
I filed this bug:
https://issues.apache.org/jira/browse/OWB-133
At least there should be some help. Not everybody is
thrilled to
replace annotations based on
the environment (at least not me)
-Matthias
LieGrue,
strub
--- On Wed, 8/26/09, Matthias Wessendorf mat...@apache.org
wrote:
From: Matthias Wessendorf mat...@apache.org
Subject: Re: WebBeans eating JSF 2.0
annotations ?
To: openwebbeans-dev@incubator.apache.org
Date: Wednesday, August 26, 2009, 5:11 PM
has no effect. The beast can't find
the JSF beans.
Due to lack of time, I am going with JSF 2.0
standalone.
Question is: as it was working the current
behavior is a
regression,
has there been any testing on OBW + JSF 2.0 ?
-Matthias
On Wed, Aug 26, 2009 at 3:45 PM, Gurkan
Erdogducgurkanerdo...@gmail.com
wrote:
It must not eat.
But one point,
You still use old XML configuration file
format. As a
default OWB uses new
XML format. Add
https://svn.apache.org/repos/asf/incubator/openwebbeans/trunk/samples/guess/src/main/resources/META-INF/openwebbeans/openwebbeans.properties
in your project
resources/META-INF/openwebbeans folder
and sure that all
libraries are ok.
You can look necessary libs from
guess.war . You can
create it from mvn
package -Pjetty.
--Gurkan
2009/8/26 Matthias Wessendorf mat...@apache.org
Hi,
is it possible that the current trunk
is _eating_
JSF 2.0 annotations ?
someCode
...
import javax.faces.bean.ManagedBean;
import
javax.faces.bean.SessionScoped;
@ManagedBean(name=playersBean)
@SessionScoped
public class ViewParamsBean
{
...
/someCode
In June (before reflecting the
javax.enterprise.context changes) it was
working.
Now expressions like #{playersBean}
are simply
ignored ;-)
Demo project is here:
https://facesgoodies.googlecode.com/svn/CGN/trunk
Re: WebBeans eating JSF 2.0 annotations ?
I closed the ticket :-)
On Wed, Aug 26, 2009 at 5:57 PM, Matthias Wessendorfmat...@apache.org wrote:
mvn jetty:run-exploded fixes that. I guess that's JSF's problem (I am
currently using the RI)
Oh boy! :)
On Wed, Aug 26, 2009 at 5:45 PM, Matthias Wessendorfmat...@apache.org wrote:
On Wed, Aug 26, 2009 at 5:39 PM, Mark Strubergstrub...@yahoo.de wrote:
In fact we (OWB) should provide standard context implementations for JSF
annotated scopes.
The whole picture:
.) JSF scanns the classpath for JSF annotations
.) OWB scanns the classpath for JSR-299 annotations
In fact, I assume (not having looked at the code) that MyFaces provides
kind of a mini DI container in the EL code. So any EL which will get
through to the faces EL handler will successfully resolve those scoped beans
Otoh, OWB also provides an EL handler which is dominant (prior in the EL
chain). OWB currently simply ignores the javax.faces.scope annotations
since they are 'unknown' for OWB. So this very class will look like a bean
which has no annotations at all.
The problem arises latest if JSF scoped beans need to be injected into
JSR-299 beans and vice versa...
an idea how to resolve this:
We need to provide context implementations for the faces scopes in the
webbeans-jsf module and let OWB do all the resolving.
wdyt?
yes, that's true. It is really a PITA to have three different ways to
@inject stuff (in JavaEE - well the javax.faces.bean.** stuff is
optional)
I am pretty sure this will actually cause lot's of pain, trouble and
bad blogs on JavaEE 6 (heck, deserved! :-) )
Are you able to bring this dilemma up on some EG ?
(mismatch of all the stuff)
-Matthias
LieGrue,
strub
--- On Wed, 8/26/09, Matthias Wessendorf mat...@apache.org wrote:
From: Matthias Wessendorf mat...@apache.org
Subject: Re: WebBeans eating JSF 2.0 annotations ?
To: openwebbeans-dev@incubator.apache.org
Date: Wednesday, August 26, 2009, 5:26 PM
On Wed, Aug 26, 2009 at 5:23 PM,
Matthias Wessendorfmat...@apache.org
wrote:
On Wed, Aug 26, 2009 at 5:17 PM, Mark Strubergstrub...@yahoo.de
wrote:
for what I know (discussion on wb-dev) JSF apps
should use JSR-299 @ScopeType annotated scopes (renamed to
@NormalScope in the latest spec) and not faces scopes. I did
hope that we could unify all scopes by generally using
JSR-330 javax.inject.Scope in all EE fields. But that will
not work until JSR-299 also recognizes and treats JSR-330
scopes as normal scopes.
WTF ? :)
It is kinda odd that JSF 2.0 has should use the 299
stuff. Standalone,
ok all fine (not tested).
But even if there are both in the game jsf2.0 and 299,
they should
just work (or at least I should
get a warning that the bean is using a (good) -sorry-
incorrect... annotation.
Basically this is a total mess. Annontations work
standalone, but not
when adding some heavyweight
stuff (like 299) to the game ? Oh boy...
I am pretty sure that this will introcude a lot of fun to
folks
writing JSF 2.0 applications,
if your statement is true. That would worse than the JSP
2.1
dependency (with JSF 1.2)
I filed this bug:
https://issues.apache.org/jira/browse/OWB-133
At least there should be some help. Not everybody is
thrilled to
replace annotations based on
the environment (at least not me)
-Matthias
LieGrue,
strub
--- On Wed, 8/26/09, Matthias Wessendorf mat...@apache.org
wrote:
From: Matthias Wessendorf mat...@apache.org
Subject: Re: WebBeans eating JSF 2.0
annotations ?
To: openwebbeans-dev@incubator.apache.org
Date: Wednesday, August 26, 2009, 5:11 PM
has no effect. The beast can't find
the JSF beans.
Due to lack of time, I am going with JSF 2.0
standalone.
Question is: as it was working the current
behavior is a
regression,
has there been any testing on OBW + JSF 2.0 ?
-Matthias
On Wed, Aug 26, 2009 at 3:45 PM, Gurkan
Erdogducgurkanerdo...@gmail.com
wrote:
It must not eat.
But one point,
You still use old XML configuration file
format. As a
default OWB uses new
XML format. Add
https://svn.apache.org/repos/asf/incubator/openwebbeans/trunk/samples/guess/src/main/resources/META-INF/openwebbeans/openwebbeans.properties
in your project
resources/META-INF/openwebbeans folder
and sure that all
libraries are ok.
You can look necessary libs from
guess.war . You can
create it from mvn
package -Pjetty.
--Gurkan
2009/8/26 Matthias Wessendorf mat...@apache.org
Hi,
is it possible that the current trunk
is _eating_
JSF 2.0 annotations ?
someCode
...
import javax.faces.bean.ManagedBean;
import
javax.faces.bean.SessionScoped;
@ManagedBean(name=playersBean)
@SessionScoped
public class ViewParamsBean
{
...
/someCode
In June (before reflecting the
javax.enterprise.context changes) it was
working.
Now expressions like #{playersBean}
are simply
Re: WebBeans eating JSF 2.0 annotations ?
On Wed, Aug 26, 2009 at 6:05 PM, Mark Strubergstrub...@yahoo.de wrote: Matze, I think this would all become ok if _all_ the EE6 parts will simply use the JSR-330 javax.inject.Scope annotation as basis for their scopes. +1 This would make at least the classpath scanning part a hell lot easier (the context implementation in the background still needs to be coded for each DI part, because there is no API defined for it except in JSR-299). I agree I already tried to convince Gavin and Pete to at least use @Scope for JSR-299 scopes, but they refused so far. I hope that there will be a really well founded _technical_ discussion on this topic in the very near future though! +1 this is all political issues... sucks for the poor developers. My 'vision': *) JSR-330 defines the basic annotations for DI in Java generally *) JSR-299 defines the annotations for EE related stuff (@SessionScoped, RequestScoped) BASED ON JSR-330! *) JSF2 uses the @SessionScoped from JSR-299. Why should JSF define own annotations? Even if you don't like to use any 299 container, you may still use the annotations defined in the API and provide an own small DI like MyFaces does it right now. Don't know if it makes sense at all to reinvite the wheel 1 times... ;) Imagine you don't use EJB or anything else from JAvaEE, just JSF (and a servlet container). A dependency to 299-impl is a little heavy, right ? Heck, what we need is clean, simple and extensible injection container in SE land. Which is the base for every damn thing. -Matthias LieGrue, strub --- On Wed, 8/26/09, Matthias Wessendorf mat...@apache.org wrote: From: Matthias Wessendorf mat...@apache.org Subject: Re: WebBeans eating JSF 2.0 annotations ? To: openwebbeans-dev@incubator.apache.org Date: Wednesday, August 26, 2009, 5:45 PM On Wed, Aug 26, 2009 at 5:39 PM, Mark Strubergstrub...@yahoo.de wrote: In fact we (OWB) should provide standard context implementations for JSF annotated scopes. The whole picture: .) JSF scanns the classpath for JSF annotations .) OWB scanns the classpath for JSR-299 annotations In fact, I assume (not having looked at the code) that MyFaces provides kind of a mini DI container in the EL code. So any EL which will get through to the faces EL handler will successfully resolve those scoped beans Otoh, OWB also provides an EL handler which is dominant (prior in the EL chain). OWB currently simply ignores the javax.faces.scope annotations since they are 'unknown' for OWB. So this very class will look like a bean which has no annotations at all. The problem arises latest if JSF scoped beans need to be injected into JSR-299 beans and vice versa... an idea how to resolve this: We need to provide context implementations for the faces scopes in the webbeans-jsf module and let OWB do all the resolving. wdyt? yes, that's true. It is really a PITA to have three different ways to @inject stuff (in JavaEE - well the javax.faces.bean.** stuff is optional) I am pretty sure this will actually cause lot's of pain, trouble and bad blogs on JavaEE 6 (heck, deserved! :-) ) Are you able to bring this dilemma up on some EG ? (mismatch of all the stuff) -Matthias LieGrue, strub --- On Wed, 8/26/09, Matthias Wessendorf mat...@apache.org wrote: From: Matthias Wessendorf mat...@apache.org Subject: Re: WebBeans eating JSF 2.0 annotations ? To: openwebbeans-dev@incubator.apache.org Date: Wednesday, August 26, 2009, 5:26 PM On Wed, Aug 26, 2009 at 5:23 PM, Matthias Wessendorfmat...@apache.org wrote: On Wed, Aug 26, 2009 at 5:17 PM, Mark Strubergstrub...@yahoo.de wrote: for what I know (discussion on wb-dev) JSF apps should use JSR-299 @ScopeType annotated scopes (renamed to @NormalScope in the latest spec) and not faces scopes. I did hope that we could unify all scopes by generally using JSR-330 javax.inject.Scope in all EE fields. But that will not work until JSR-299 also recognizes and treats JSR-330 scopes as normal scopes. WTF ? :) It is kinda odd that JSF 2.0 has should use the 299 stuff. Standalone, ok all fine (not tested). But even if there are both in the game jsf2.0 and 299, they should just work (or at least I should get a warning that the bean is using a (good) -sorry- incorrect... annotation. Basically this is a total mess. Annontations work standalone, but not when adding some heavyweight stuff (like 299) to the game ? Oh boy... I am pretty sure that this will introcude a lot of fun to folks writing JSF 2.0 applications, if your statement is true. That would worse than the JSP 2.1 dependency (with JSF 1.2) I filed this bug: https://issues.apache.org/jira/browse/OWB-133 At least there should be some help. Not everybody is thrilled to replace annotations based on the environment (at least not me
Re: Servlet 3.0 ?
On Wed, Aug 26, 2009 at 6:25 PM, Gurkan Erdogducgurkanerdo...@gmail.com wrote: Maybe Geronimo Java EE 6 OWB integration can add this filter automatically to a web module. Maybe Geronimo MyFaces integration can handle this via looking META-INF/beans.xml file. that would be a benefit. Let's keep this in mind when it comes to that time. 2009/8/26 Matthias Wessendorf mat...@apache.org Hello, as WebBeans spec is kinda late - so is Servlet 3.0 - I was wondering if you guys could leverage some of their stuff, like the @Filter annotation or the web-xml fragments stuff ? (e.g. for WebBeansJSFFilter), for the -jsf module ? Thx, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
maven repo
hey, I wonder why OWB is not deploying bit to here: http://people.apache.org/repo/m2-incubating-repository/org/apache/ Also, is this project already running on any of the ASF continuum servers ? (or any other ASF CI server) -M -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: build problem ?
can you commit the change ? On Thu, May 28, 2009 at 9:57 AM, Gurkan Erdogdu cgurkanerdo...@gmail.com wrote: Yeah, you are right. We forget to update main pom while releasing M2 properties openwebbeans.version1.0.0-incubating-M2/openwebbeans.version -- *This must be 1.0.0-incubating-SNAPSHOT* siteId/OWB/1.0.0-incubating-M2/plugins/siteId /properties Change after M2 release :) Thanks; --Gurkan 2009/5/28 Matthias Wessendorf mat...@apache.org trying to build OWB on my box, I see that the -IMPL has a dependency to org.apache.openwebbeans:openwebbeans-api:jar:1.0.0-incubating-M2 the API from the trunk, however, is declared as openwebbeans-api-1.0.0-incubating-SNAPSHOT so, hard to build, he ? :) -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Sample Application with OWB + JSF + JPA
On Sat, May 16, 2009 at 10:03 AM, Mark Struberg strub...@yahoo.de wrote: Hi Gurkan! I looked over your sample and it does look pretty good, great job! One thing: shouldn't we move the Transactionalnterceptor to openwebbeans-jpa, since this is almost a standard thing, isn't? Also I have not yet checked if we handle long running conversations correctly. Storing a @ConversationScoped bean which has a PersistenceContext may lead to a timeout of the EntityManager. So we have to re-attach some JPA entities. We can look at myfaces-orchestra how Mario did solve this. would it make sense to provide a orchestra module for (O)WB ? I mean currently it is really tied to spring; -M LieGrue, strub - Ursprüngliche Mail Von: Gurkan Erdogdu gurkanerdo...@yahoo.com An: openwebbeans-dev@incubator.apache.org Gesendet: Donnerstag, den 14. Mai 2009, 19:13:41 Uhr Betreff: Re: Sample Application with OWB + JSF + JPA Hi This is my -- mvn help:effective-pom repository setting. java.net http://download.java.net/maven/1 legacy false apache.snapshots Apache Snapshot Repository http://people.apache.org/repo/m2-snapshot-repository false central Maven Repository Switchboard http://repo1.maven.org/maven2 From: Matthias Wessendorf To: openwebbeans-dev@incubator.apache.org Sent: Thursday, May 14, 2009 7:54:08 PM Subject: Re: Sample Application with OWB + JSF + JPA where to find this guy ? [INFO] [INFO] Building OpenWebBeans :: Geronimo integration [INFO] task-segment: [clean, install] [INFO] [INFO] [clean:clean] [INFO] snapshot org.apache.geronimo.specs:specs:1.1-SNAPSHOT: checking for updates from snapshots-corporate Downloading: http://stacy27.us.oracle.com/maven2-snapshots/org/apache/geronimo/specs/specs/1.1-SNAPSHOT/specs-1.1-SNAPSHOT.pom Downloading: http://adfui.us.oracle.com/maven/org.apache.geronimo.specs/poms/specs-1.1-SNAPSHOT.pom Downloading: http://www.ibiblio.org/maven/org/apache/geronimo/specs/specs/1.1-SNAPSHOT/specs-1.1-SNAPSHOT.pom Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/specs/specs/1.1-SNAPSHOT/specs-1.1-SNAPSHOT.pom Downloading: http://download.java.net/maven/1/org.apache.geronimo.specs/poms/specs-1.1-SNAPSHOT.pom Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/geronimo/specs/specs/1.1-SNAPSHOT/specs-1.1-SNAPSHOT.pom Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/geronimo/specs/specs/1.1-SNAPSHOT/specs-1.1-SNAPSHOT.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: null:geronimo-jms_1.1_spec:jar:1.0 Reason: Cannot find parent: org.apache.geronimo.specs:specs for project: null:geronimo-jms_1.1_spec:jar:1.0 for project null:geronimo-jms_1.1_spec:jar:1.0 On Thu, May 14, 2009 at 6:38 PM, Matthias Wessendorf wrote: awesome! just passed that along to the MyFaces community On Thu, May 14, 2009 at 12:37 PM, Mohammad Nour El-Din wrote: Great :), I will check it during the weekend. On Thu, May 14, 2009 at 1:07 AM, Mark Struberg wrote: cool! will check this out tomorrow! LieGrue, strub - Ursprüngliche Mail Von: Gurkan Erdogdu An: openwebbeans-dev@incubator.apache.org; openwebbeans-u...@incubator.apache.org Gesendet: Mittwoch, den 13. Mai 2009, 23:27:26 Uhr Betreff: Sample Application with OWB + JSF + JPA Hi guys; I have finally finished the real sample application written with JSF + JPA + OWB. It is called Hotel Reservation Application. You can create Admin and Normal user accounts. Admin is responsible for defining hotels etc, and user creates a hotel reservation. Altough it is a simple application, it uses and shows most of the functionality that are defined in the JSR-299, including Scope and Contexts, Interceptors, Decorators, Events and Observers etc. STEPS TO RUN --- It is located in the trunk/samples/reservation directory. In this directory mvn clean install -Pjetty -- to compile and install mvn jetty:run -Pjetty -- to run the jetty container Then, http://localhost:8080/reservation Voila, enjoys it! Thanks; Gurkan -- 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 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com
Re: Sample Application with OWB + JSF + JPA
awesome! just passed that along to the MyFaces community On Thu, May 14, 2009 at 12:37 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Great :), I will check it during the weekend. On Thu, May 14, 2009 at 1:07 AM, Mark Struberg strub...@yahoo.de wrote: cool! will check this out tomorrow! LieGrue, strub - Ursprüngliche Mail Von: Gurkan Erdogdu gurkanerdo...@yahoo.com An: openwebbeans-dev@incubator.apache.org; openwebbeans-u...@incubator.apache.org Gesendet: Mittwoch, den 13. Mai 2009, 23:27:26 Uhr Betreff: Sample Application with OWB + JSF + JPA Hi guys; I have finally finished the real sample application written with JSF + JPA + OWB. It is called Hotel Reservation Application. You can create Admin and Normal user accounts. Admin is responsible for defining hotels etc, and user creates a hotel reservation. Altough it is a simple application, it uses and shows most of the functionality that are defined in the JSR-299, including Scope and Contexts, Interceptors, Decorators, Events and Observers etc. STEPS TO RUN --- It is located in the trunk/samples/reservation directory. In this directory mvn clean install -Pjetty -- to compile and install mvn jetty:run -Pjetty -- to run the jetty container Then, http://localhost:8080/reservation Voila, enjoys it! Thanks; Gurkan -- 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 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Sample Application with OWB + JSF + JPA
where to find this guy ? [INFO] [INFO] Building OpenWebBeans :: Geronimo integration [INFO]task-segment: [clean, install] [INFO] [INFO] [clean:clean] [INFO] snapshot org.apache.geronimo.specs:specs:1.1-SNAPSHOT: checking for updates from snapshots-corporate Downloading: http://stacy27.us.oracle.com/maven2-snapshots/org/apache/geronimo/specs/specs/1.1-SNAPSHOT/specs-1.1-SNAPSHOT.pom Downloading: http://adfui.us.oracle.com/maven/org.apache.geronimo.specs/poms/specs-1.1-SNAPSHOT.pom Downloading: http://www.ibiblio.org/maven/org/apache/geronimo/specs/specs/1.1-SNAPSHOT/specs-1.1-SNAPSHOT.pom Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/specs/specs/1.1-SNAPSHOT/specs-1.1-SNAPSHOT.pom Downloading: http://download.java.net/maven/1/org.apache.geronimo.specs/poms/specs-1.1-SNAPSHOT.pom Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/geronimo/specs/specs/1.1-SNAPSHOT/specs-1.1-SNAPSHOT.pom Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/geronimo/specs/specs/1.1-SNAPSHOT/specs-1.1-SNAPSHOT.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: null:geronimo-jms_1.1_spec:jar:1.0 Reason: Cannot find parent: org.apache.geronimo.specs:specs for project: null:geronimo-jms_1.1_spec:jar:1.0 for project null:geronimo-jms_1.1_spec:jar:1.0 On Thu, May 14, 2009 at 6:38 PM, Matthias Wessendorf mat...@apache.org wrote: awesome! just passed that along to the MyFaces community On Thu, May 14, 2009 at 12:37 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Great :), I will check it during the weekend. On Thu, May 14, 2009 at 1:07 AM, Mark Struberg strub...@yahoo.de wrote: cool! will check this out tomorrow! LieGrue, strub - Ursprüngliche Mail Von: Gurkan Erdogdu gurkanerdo...@yahoo.com An: openwebbeans-dev@incubator.apache.org; openwebbeans-u...@incubator.apache.org Gesendet: Mittwoch, den 13. Mai 2009, 23:27:26 Uhr Betreff: Sample Application with OWB + JSF + JPA Hi guys; I have finally finished the real sample application written with JSF + JPA + OWB. It is called Hotel Reservation Application. You can create Admin and Normal user accounts. Admin is responsible for defining hotels etc, and user creates a hotel reservation. Altough it is a simple application, it uses and shows most of the functionality that are defined in the JSR-299, including Scope and Contexts, Interceptors, Decorators, Events and Observers etc. STEPS TO RUN --- It is located in the trunk/samples/reservation directory. In this directory mvn clean install -Pjetty -- to compile and install mvn jetty:run -Pjetty -- to run the jetty container Then, http://localhost:8080/reservation Voila, enjoys it! Thanks; Gurkan -- 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 -- 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
demo ?
hey, I wonder if there is some demo: -JSF (MyFaces ;-), JPA and OWB ? -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: WebBeans and javax.inject*
cool, thanks for sharing. I find the fact of gazillion comments interesting =:-) On Fri, May 8, 2009 at 10:03 AM, Nicklas Karlsson nicka...@gmail.com wrote: I think his reply will be mostly in line with http://in.relation.to/Bloggers/CommentsOnAnnotationsForDependencyInjection On Fri, May 8, 2009 at 9:52 AM, Matthias Wessendorf mat...@apache.org wrote: Hey Gurkan, since you are now our 299 rep., can you ask the EG/Gavin on their/his opinion of the javax.inject proposal ? I think I am interested in that, for some reason. Thx, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- --- Nik -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
FYI: javax.inject* standard ...
FYI: http://google-code-updates.blogspot.com/2009/05/javaxinjectinject.html what does this mean to JSR 299 ? -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Sending mails to jsr-299-comme...@jcp.org, How ?
just send it. (maybe it is mounted to /dev/null) :-) I'd do a CC to Pete as well... (and perhaps this list) -M On Wed, Apr 22, 2009 at 6:10 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: 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 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
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 gurkanerdo...@yahoo.com wrote: Hi Matthias; I have done step 1. Thanks; Gurkan From: Matthias Wessendorf mat...@apache.org To: openwebbeans-dev@incubator.apache.org Cc: Gurkan Erdogdu cgurkanerdo...@gmail.com; James Carman jcar...@carmanconsulting.com 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 mat...@apache.org 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
Re: OpenWebBeans Blog
cool! On Fri, Apr 10, 2009 at 5:27 PM, Gurkan Erdogdu gurkanerdo...@yahoo.com wrote: Hi; OpenWebBeans blog section is created ! http://blogs.apache.org/owb/ Gurkan -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: JSR 299 / WebBeans - Expert Group
On Thu, Apr 16, 2009 at 12:21 PM, Gurkan Erdogdu cgurkanerdo...@gmail.com wrote: Hi Matthias; Is it possible to change the EG representation after forming the EG? If it yes, that should be possible. is possible, and you would like to go on this way, I could take the responsibility, if there will no problem. +1 That would be a good fit, IMO. If there is another one, let's try to add the second person as well. History: James and I were (long time ago) interested in the 299 EG. However, he got sick of it before me :-) So, now it is only me. (- pretty inactive) What is the road map for this changing stuffs? Dunno. Once we have a clear opinion on who (besides Gurkan) is interested in joining the EG, I'll figure it out. -Matthias WDYT guys? Thanks; 2009/4/16 Matthias Wessendorf mat...@apache.org 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 -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: JSR 299 / WebBeans - Expert Group
On Thu, Apr 16, 2009 at 2:31 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: It seems that we need two so why not you and Gurkan :) ? +1 On Thu, Apr 16, 2009 at 2:30 PM, James Carman jcar...@carmanconsulting.com wrote: For the record, I'm +1 on Gurkan, too. I just offered myself up because I have interest in the topic and I do have quite a bit of experience in the dependency injection arena (and dynamic proxies). On Thu, Apr 16, 2009 at 8:19 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: +1 for Gurkan, he has been so active on this project since the first days of it. On Thu, Apr 16, 2009 at 1:31 PM, Matthias Wessendorf mat...@apache.org wrote: On Thu, Apr 16, 2009 at 1:28 PM, Mark Struberg strub...@yahoo.de wrote: Hi! One feature we've discussed was exactly the conversation scope. His opinion as far as I remember was: the spec says JSF but it doesn't say we aren't allowed to make it independent as long as we _also_ have conversations for JSF in place. The same applies to EJB. The 2nd suggestion was the injection of Java natives (int, long, ...) for producer methods via XML. The spec defines this only for field injection but not yet for initializers and producers. Pete said they will probably add this too in the future (but there is no time left to bring it into the spec yet for 1.0). So the underlying message was: make the whining guys happy (you know of whom I'm talking about) Not really. the non-jsf folks ? Or those that want DI on JavaSE layer ? -M and then make the 1,0 spec final the sooner the better! LieGrue, strub --- Matthias Wessendorf mat...@apache.org schrieb am Do, 16.4.2009: Von: Matthias Wessendorf mat...@apache.org Betreff: Re: JSR 299 / WebBeans - Expert Group An: openwebbeans-dev@incubator.apache.org Datum: Donnerstag, 16. April 2009, 13:07 On Thu, Apr 16, 2009 at 1:03 PM, Mark Struberg strub...@yahoo.de wrote: Hi! I've talked with Pete Muir at the JSFDays about the JSR-299 spec a lot. Since he has taken over the lead from Gavin, he is the IMPL lead, at JBoss. And now the JBoss rep. on JSF 2.0 it should be possible to change an EG member also. And also to add another person. Yes, that's correct. That was the reason why I brought this up The Spec for 1.0 is almost finished, there are a few things which should be addressed but there is not enough time to get it rdy for EE6! So this is basically a situation where we have to get rid of all showstoppers but we shouldn't add additional functionality at this point! I think the common ground of the JSR-299 Spec is solid enough and fairly extendable. We have to implement what's in the Spec but are completely free to add additional functionality! I also talked with Pete about a few features they will add, and they now also have SE support which is not mentioned in the Spec. So I think it will not be a problem to have new features added which are compatible in RI and OWB _without_ having them written down in the WebBeans-1.0 Spec but in a later one! sounds interesting. What features you were discussing? Can you bring it up here ? -Matthias One possible thing that still may come is that some functionality (like eventing or interceptors, cannot remember which) may be removed from WebBeans and moved over to EJB or another spec. So one who does this Job really needs to know OWB insideout _plus_ a good amount of understanding of the whole EE business I don't think you are deep enough into OWB yet, but personally would highly appreciate to see you as a committer on OWB in the future :) LieGrue, strub --- James Carman jcar...@carmanconsulting.com schrieb am Do, 16.4.2009: Von: James Carman jcar...@carmanconsulting.com Betreff: Re: JSR 299 / WebBeans - Expert Group An: openwebbeans-dev@incubator.apache.org Datum: Donnerstag, 16. April 2009, 12:35 On Thu, Apr 16, 2009 at 4:35 AM, Matthias Wessendorf mat...@apache.org wrote: 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. I would be interested in joining, but I am not an OWB committer. I'm very interested in making sure the spec stays agnostic when it comes to the environment in which it runs. The specification should make it easy to use in Wicket, or Tapestry, or just plain ole JSP applications. -- 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 -- Thanks - Mohammad Nour - LinkedIn: http://www.linkedin.com/in/mnour Life is like
Re: new blogs at apache
+1 On Fri, Apr 3, 2009 at 5:49 PM, Gurkan Erdogdu gurkanerdo...@yahoo.com wrote: +1; From: Mark Struberg strub...@yahoo.de To: openwebbeans-dev@incubator.apache.org Sent: Friday, April 3, 2009 12:11:29 PM Subject: new blogs at apache Hi! Today I discovered this new page: http://blogs.apache.org Do we also like to blog a bit? LieGrue, strub -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Wiki ?
Hey guys, do we have already an instance of a wiki ? For some reasons, I'd love to use a cwiki.. Thx, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Fwd: [GSoC 2009] Apache is officially participating in Google Summer of Code 2009
FYI -- Forwarded message -- From: Luciano Resende lrese...@apache.org Date: Thu, Mar 19, 2009 at 10:52 PM Subject: [GSoC 2009] Apache is officially participating in Google Summer of Code 2009 To: p...@apache.org Dear PMC, It's now official, Google has announced that The Apache Software Foundation was selected as one of the participating organization in the GSoC 2009 program. This is an excellent opportunity for Apache, as it allows projects to build/increase its community, it also help students to learn about open source, about Apache Software Foundation and how to do things the Apache Way. Please start advertising the program and discussing project ideas with your project community. Then add your project ideas to the ASF GSoC 2009 Official Project Ideas page [1], as this is going to be the most visible place for students. Per GSoC 2009 timeline, Students should officially start applying for these ideas on March 23. ASF Members and committers can volunteer to be mentors in the GSoC 2009 program (see [2] for more details about being a mentor). We invite all mentors and GSoC interested parties to subscribe to the code-awa...@a.o mailing list [3] to coordinate work between mentors, ask questions and get updates related to GSoC 2009 program. Please, feel free to forward this announce to any appropriate dev@ or users@ lists so your larger community can hear about the GSoC 2009 program. [1] http://wiki.apache.org/general/SummerOfCode2009 [2] http://wiki.apache.org/general/SummerOfCodeMentor [3] mailto:code-awards-subscr...@apache.org -- Luciano Resende http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: private-unsubscr...@incubator.apache.org For additional commands, e-mail: private-h...@incubator.apache.org -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Re: [FYI] open discussion list from the JSF 2.0 EG
dunno. Since Gavin is OS experienced I'd have thought that the complete process of that spec is much more open than it really is today... -M On Tue, Mar 10, 2009 at 3:59 PM, Mark Struberg strub...@yahoo.de wrote: Matthias, I was just wondering if there is also a readonly JSR-299 EG list one can subscribe already? txs and LieGrue, strub --- Matthias Wessendorf mat...@apache.org schrieb am Di, 10.3.2009: Von: Matthias Wessendorf mat...@apache.org Betreff: Re: [FYI] open discussion list from the JSF 2.0 EG An: MyFaces Development d...@myfaces.apache.org Datum: Dienstag, 10. März 2009, 10:10 On Tue, Mar 10, 2009 at 9:25 AM, Simon Kitching skitch...@apache.org wrote: Matthias Wessendorf schrieb: pretty late, but better than never: http://weblogs.java.net/blog/edburns/archive/2009/03/response_to_a_c.html I love the way this posting says We have opened the process - and by the way, the JSF2.0 spec is finished. With timing like that, Ed should do stand-up comedy. hahaha :-) Yeah, I totally agree. At least they now have an open process for something like JSF 3.0 :-) -- 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
Re: @Resource handling
On Thu, Mar 12, 2009 at 10:34 PM, Mark Struberg strub...@yahoo.de wrote: Hi! The (EJB centric) Spec of @Resource says that the resource will always be looked up via JNDI [1]. I guess mainly because the whole J2EE stuff is really JNDI centric. Otoh in environments where no or only a read-only JNDI context is available, do we like to allow @Resouce also? I think, that I'd go for it -M I know this feature from Spring and I must say I love it. You can simply write a Bean and inject it via @Resource even without JNDI, So for Spring @Resource is more or less an alias for @Autowired (which is ~ our @Current) I'm not really sure how to interpret the section 5.12.1 of the spec. LieGrue, strub [1] http://java.sun.com/javaee/5/docs/api/javax/annotation/Resource.html -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: project status
Hi Berthold, On Thu, Mar 12, 2009 at 8:27 AM, Gurkan Erdogdu gurkanerdo...@yahoo.com wrote: Hi Berthold; 1* OpenWebBeans will implement the full JSR-299 specification. Currently, nearly all of the functionality of the latest revision of the specification, except some Java EE stuffs (like EJB, JMS), is implemented. correct. Nearly also means, that you are more than welcome to help out ;-) But this does not mean that you are not able to use the OpenWebBeans without full *Java EE 6.0* container. Actually we are trying to separate Java EE specific parts into modules (such as EJB 3.x and JMS modules), so anyone can adapt his project to use any modules he want. Indeed, you can use OpenWebBeans in Java SE environment also. (You can look at the webbeans-tck that how we use the implementation for testing without Java EE container. But a bit work may be needed) 2* Name will be the same foreover :) we can change that, if the community really want to change it ... but doing that would only make sense, once this podling leaves (successfully) the incubator -Matthias Thanks again; /Gurkan From: Berthold Scheuringer berthold.scheurin...@gmail.com To: openwebbeans-dev@incubator.apache.org Sent: Wednesday, March 11, 2009 7:29:54 PM Subject: project status Hi all, I´m pretty new to OpenWebBeans and don´t know that much about the actual project status (especially considering the latest revise of the JSR-299 spec). Therefore I have following questions: 1) first of all the most important question: will OpenWebBeans move onward implementing the JSR 299 considering the latest revise of the spec (where it seems to be more like an extension to EJB 3.x ) ? 2) second (not that important) question: if OpenWebBeans will implement the last spec - will the name still remain (or will then also a renaming be done toward Java Contexts and Dependency Injection) Thanks in advance for answering my pretty fundamental questions. Regards, Berthold -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [DISCUSS] Change API package structure
On Tue, Jan 27, 2009 at 3:37 PM, Kevan Miller kevan.mil...@gmail.com wrote: On Jan 27, 2009, at 8:03 AM, Gurkan Erdogdu wrote: Hi guys, As you know , we would like to create our first release in Friday. There is one point that I like to discuss; In the final specification, API package names are changed from the javax.webbeans.* to different package names. For example, javax.inject, javax.context. etc...After rethinking, I want to update the current API to reflect these changes. What do you think about reflecting these changes in M1-Release? Should we reflect it in the M1-Release or defer it to the M2-Release? If there is no opposite idea I will go and update the API to reflect the current specification requirements. WDYT? Agreed. M1 should be updated to match the latest public draft specification. +1 You used the words final specification. Just want to be clear that the current specification is a public draft. Which means that there can be (will be) changes in the future. --kevan -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: kevan hands out gold stars
+1 I have to second that. Funny is I though the same, before I read it. -M On Fri, Jan 23, 2009 at 9:47 PM, Kevan Miller kevan.mil...@gmail.com wrote: Since I was thinking about this, I thought I'd go ahead and send a note. I think you guys are off to a really good start. You're making a lot of really good progress with the implementation. The release preparation, although potentially delayed for a bit (which is not a bad thing at all), has gone very well. Most importantly, I'm very pleased by the amount of communication that I'm seeing. Keep up the good work! You all deserve a pat on the back this weekend, while reading the updated spec, of course... :-P --kevan -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
WebBeans is dead. Long live the JSR 299
http://in.relation.to/Bloggers/RevisedPublicDraftOfJSR299JavaContextsAndDependencyInjection -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: WebBeans is dead. Long live the JSR 299
On Sat, Jan 24, 2009 at 6:35 PM, Mark Struberg strub...@yahoo.de wrote: There was a long discussion about how to name the baby finally, and I honestly have to admit: maybe I'm to dumb to understand, but the now chosen name is a) not handy as a buzzphrase and b) exactly non_meaningful as the original one. So I'd suggest to at least keep our projects name as 'OpenWebBeans' because the terminus 'WebBeans' is at least shorter to spell :) +1 to OpenWebBeans LieGrue, strub --- Matthias Wessendorf mat...@apache.org schrieb am Sa, 24.1.2009: Von: Matthias Wessendorf mat...@apache.org Betreff: WebBeans is dead. Long live the JSR 299 An: openwebbeans-dev@incubator.apache.org Datum: Samstag, 24. Januar 2009, 18:22 http://in.relation.to/Bloggers/RevisedPublicDraftOfJSR299JavaContextsAndDependencyInjection -- 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
Re: WG: Re: Scanning for annotated classes in MyFaces 2
On Mon, Jan 19, 2009 at 4:59 AM, Mark Struberg strub...@yahoo.de wrote: It's not only the code which can be reused, but this may also be a benefit at runtime. How many times will some kind of annotation scanner be called in a typical geronimo setup? 1.) EJB scanner 2.) JPA scanner 3.) myFaces scanner MyFaces ;-) 4.) WebBeans scanner and I'm sure I forgot a few others ;) Maybe in the future we may do a centralised annotation service which has to scan only once? LieGrue, strub --- Kevan Miller kevan.mil...@gmail.com schrieb am Mo, 19.1.2009: Von: Kevan Miller kevan.mil...@gmail.com Betreff: Re: WG: Re: Scanning for annotated classes in MyFaces 2 An: openwebbeans-dev@incubator.apache.org Datum: Montag, 19. Januar 2009, 13:51 On Jan 19, 2009, at 3:28 AM, Mark Struberg wrote: Hi! There is a discusson on the myFacees list currently about how to scan for annotations. The conclusion was that we should share a common library for apache projects, and this was a very intresting post: I don't think this is for M1, but we should keep this in our mind for a later phase. Sounds reasonable. XBean is a Geronimo subproject. I can certainly help out if we run into any XBean related issues. --kevan -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [site] building the site via maven ?
On Sat, Jan 17, 2009 at 8:57 PM, Matthias Wessendorf mat...@apache.org wrote: Hi, I think (not deeply searched) we don't build the site via maven. That would be much better. in maven, there is metadata for the developers and their roles (PMC ...). So, in most of the other projects, new committers add them self to the master pom. when they become PMC, they maintain their status, too. currently, the page is somehow build. Not a big deal, but one of the future plans should be (IMO) to move the site to the maven-based build system. Currently, this page: http://incubator.apache.org/openwebbeans/whoweare.html does not contain Mohammad, nor Mark. But the news does welcome Mohammad (which is good ;-) ) -Matthias Where is the src for the site ? -M -- 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
Re: M1- Release Content
On Sun, Jan 11, 2009 at 8:38 PM, Kevan Miller kevan.mil...@gmail.com wrote: On Jan 11, 2009, at 5:34 PM, Gurkan Erdogdu wrote: Hi; We are planning to release the M1 version of the OpenWebBeans . So far we have finished the some parts of the specification and the nearly all of the build and release management tasks. M1 release will support the following items; * Simple WebBeans Support * Producer Method Support * Event and Observer Support * Decorator and Interceptor Support * Experimental XML Configuration Support * Lookup and Dependency Injection Support * Java EE Plugin Support (via ServetContextListener interface) Remaining parts of the specification that we did not handle in this release are the following items; * Enterprise WebBeans Support * JMS WebBeans Support * Producer Field Support * Servlet Injection Support * Inheritance and Realization Support * Common Annotations Support * Full Support for Validation Checks * Passivation Scope and Serialization Operations * Full Support for XML Configuration * Java EE Container Integration Support (SPI) ? What do you think about the content of the M1 release ? ? Has it enough functionalities to create the release or we may delay it to another date for adding more functionality ? ? What is your further comments and advices? IMO, that's enough for a M1 release. I built the current trunk code and took a quick review. Here are some comments... * I think the LICENCE file needs to reference the licences directory. I'd actually recommend that these be renamed LICENSE * The NOTICE file does not conform to the requirements of the ASF. See -- http://www.apache.org/legal/src-headers.html#notice (e.g. there's no COPYRIGHT) * Also, I doubt that the contents of the NOTICE file is correct. All it does is provide attribution to embedded projects. However, some licenses (e.g. ASL requires that NOTICES be reproduced). * The binary distributions do not contain the licences directory. The licenses must either be in the LICENSE file, or you must create a licenses directory. I actually prefer a single license file, but licenses dirs are used by some projects. As long as all licenses are available, I'm ok either way. * All OpenWebBeans jars/wars/etc. need to contain a META-INF/LICENSE and META-INF/NOTICE files * Hmmm. Seems like webbeans-impl.jar be openwebbeans-impl.jar the RAT (m2 plugin) is usually helpful for these kinda things (isn't it still in the incubator?) Enough for tonight... --kevan -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
