Hi and welcome aboard! The jetty plugin should work out of the box, Greg deploys it to the maven central repo. But we should upgrade to the latest version anyway ;)
The specification: Gavin posted a new version yesterday: http://markmail.org/message/mcooxuqqpx5qz7k2 This version contains the JSR-330 annotations. @Gurkan: this was faster as expected, should we postpone M3 and implement this now? I'd prefer, so +1. This should be (sic!) the last large change to the JSR-299 spec, so I'd prefer hacking it into M3. The version which has been used to code the current OWB is from 20090610: http://markmail.org/message/gbh6qryxxqpeonus LieGrue, strub ----- Original Message ---- > From: Gurkan Erdogdu <[email protected]> > To: [email protected] > Sent: Tuesday, August 18, 2009 12:04:27 AM > Subject: Re: Preparing for Release M3 > > Hi Paul; > > Thanks for trying to help. > > >>>Is it possible you have a local copy of maven-jetty-plugin? > I removed maven-jetty-plugin from my local repository, then re-execute mvn > commands. Maven try to get plugin > from the below locations. > > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'jetty'. > Downloading: > http://repo1.maven.org/maven2/org/mortbay/jetty/maven-jetty-plugin/6.1.18/maven-jetty-plugin-6.1.18.pom > 5K downloaded > Downloading: > http://repo1.maven.org/maven2/org/mortbay/jetty/maven-jetty-plugin/6.1.18/maven-jetty-plugin-6.1.18.jar > 46K downloaded > > >>>Are all current work items in jira OWB? Are there some we can help with? > Yes. We are planning to release M3 version. But some of the issues under M3 > may propagate to M4 version. > FYI, JSR-299 specification talks about heavy Java EE containers for some of > its functionality. But instead OWB works in Jetty, Tomcat etc. light weight > containers. But it also supports Embeddable OpenEJB in Tomcat. > > You can pick any of the issue from the JIRA, > https://issues.apache.org/jira/browse/OWB. Currenlty we are trying to > support resource injection for managed beans in Embeddable OpenEJB. > (OWB-47). All jira issues explains themselves. If you have further question > about them, you are always welcome to ask in this dev list. We are also > running i...@freenode with channel name #openwebbeans. > > >>>What is the procedure to set up an environment to run the tests and do > development > >>>using eclipse? (i.e. what libs/levels need to be installed, are there > project files we can import to generate a >>>standard dev env, etc) > We are generally use Eclipse for development with Maven Plugin. After you > check out all of the source codes from SVN, use Eclipse Import Maven Project > facility. That is it, you can begin development. Lots of tests are located > in the src/main/test folders. You can run junit test from Eclipse or using > mvn test. > > There is also samples directory. In it, you can find several full-blown web > samples. For example, > > guess --> Simple web application using OWB > Run it with : mvn clean install -Pjetty; mvn jetty:run > -Pjetty; > > ejb-sample --> Shows usage of the OpenEJB within Tomcat. First of all, you > have to install OpenEJB in Tomcat. You can look at the > http://openejb.apache.org/tomcat.html for installation. After that put > "openwebbeans-api.jar" into the tomcat server library (apache-folder/lib). > Then deploy it into the ejb-sample.war to the tomcat "webapps/" folder > (apache-folder/webapps). Currently we have no configuration to use examples > via Tomcat Maven Plugin. There is also one trick to use MyFaces with Tomcat, > put "jasper.jar" and "jasper-el.jar" to the WEB-INF folder of the > application. I can not run application without this trick under Tomcat. You > can directly export war from Eclipse Export War functionality. But, you must > put jasper jars in it. > > jms-sample --> Shows the usage of JMS injections. It uses server JNDI > functionality to get JMS ConnectionFactory etc. I tried it on several > application servers. It requires full blown application servers or JMS > configured lightweight containers. If you look at > "src/main/resource/META-INF" folder, you see a file named with > openwebbeans.properties. It defines several properties for overriding > default configuration. OWB uses some default configuration for its services. > You can find default configuration properties and their explanations from > "webbeans-impl" project. jms-sample currently uses "ConnectionFactory" as > JMS Connection Factory JNDI name. You can override it in > openwebbeans.properties with property name > > #JMS ConnectionFactory JNDI Name > org.apache.webbeans.spi.JNDIService.jmsConnectionFactoryJndi=ConnectionFactory. > > You can deploy it via war file. There is no currently maven deployer for it. > > reservation -->Full blown JSF + JPA + OWB sample. You can test it like guess > sample > mvn jetty:run -Pjetty; > > >>> What are the current plans for handling the separation of JSR-330 and > update the open web beans code to >>>accommodate the changes? > As I am in the EG of JSR-299, for the time being there is no more change in > JSR 299. There are some couple of name changes so far. We will work on these > changes after the final spec is arrived. We will also implement JSR-330 on > top of OWB. > > >>>Will we be making OWB dependency injection pluggable so folks can pick > whatever implementation they want or >>>will we be linking it in directly > (regardless of whether we write or obtain the code)? > Yes, OWB will fully implement specification of JSR-299, so anyone that uses > JSR-299 API can changes its underliyng implementation without changing > single line of code. But as I said, currentlty, we do not support any > specific JAva EE container and no integration. You can use any lightweight > JSP/Servlet container to use OWB. If you wish to use embeddable EJB support, > you can also try to use OpenEJB TOmcat with OWB. > > There are lots of areas that you can help. It is documented in the JIRA. We > are also happy to get any comments from your side. > > All of your contributions are welcome :) > > > Thanks; > > --Gurkan > > > 2009/8/17 Paul J. Reder > > > I've been trying, along with a couple of co-workers, to import OpenWebBeans > > into an eclipse environment and run the tests. I've encountered the > > mentioned issue: > > > > [ERROR] BUILD ERROR > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not > > exist or no valid version could be found > > > > when running: > > > > mvn jetty:run -Pjetty > > > > after having checked out the latest svn trunk and run: > > > > mvn clean install > > mvn clean package -Pjetty > > > > Is it possible you have a local copy of maven-jetty-plugin? > > > > We'd love to start helping with OpenWebBeans development, but we could > > really use some help getting a working environment set up and figuring out > > what we can do to help. > > > > - Are all current work items in jira OWB? Are there some we can help with? > > - What is the procedure to set up an environment to run the tests and do > > development > > using eclipse? (i.e. what libs/levels need to be installed, are there > > project files we can import to generate a standard dev env, etc) > > - What are the current plans for handling the separation of JSR-330 and > > update the open web beans code to accommodate the changes? > > - Will we be making OWB dependency injection pluggable so folks can pick > > whatever implementation they want or will we be linking it in directly > > (regardless of whether we write or obtain the code)? > > > > If you can help us get started, we'd love to help. > > > > Paul J. Reder > > > > > > > > On 08/16/2009 04:58 PM, Gurkan Erdogdu wrote: > > > >> > >> PS: I had problems starting the guess sample with mvn clean package > >>>> -Pjetty jetty run. Need to fix a few things in maven-scm now, and will > >>>> look > >>>> at it on>>thuesday. gn8! > >>>> > >>> > >> I have separated guess/ project into three different modules > >> > >> guess --> for guess sample, removing ejb and jms parts > >> > >> ejb-sample --> using OpenEJB in Tomcat. Have to configure Tomcat with > >> OpenEJB firstly. Then deploy it into Tomcat. It does not work on any other > >> containers like Jetty. > >> > >> jms-sample --> jms injections. Have to deploy it into full blown Java EE > >> server supporting JMS provider. JMS sample currently using > >> "ConnectionFactory" as JMS Connection Factory JNDI. You can also change > >> this > >> with respect to application server JMS JNDI name policy via > >> openwebbeans.properties > >> > >> I run mvn clean package -Pjetty and mvn jetty:run -Pjetty. It works for > >> me. > >> > >> Please ensure that, you check in all recent changes from the svn, and > >> > >> mvn clean install from root folder. > >> > >> Thanks; > >> > >> --Gurkan > >> > >> ----- Original Message ---- > >> > >>> From: Gurkan Erdogdu > >>> To: [email protected] > >>> Sent: Sunday, August 16, 2009 10:18:13 PM > >>> Subject: Preparing for Release M3 > >>> > >>> Hi guys; > >>> > >>> I want to release M3 in this week to include EJB functionality and couple > >>> of bug > >>> fixes. Also adding more documentation. > >>> > >>> WDYT? > >>> > >>> Thanks; > >>> > >>> --Gurkan > >>> > >> > >> > >> > >> > > -- > > Paul J. Reder > > ----------------------------------------------------------- > > "The strength of the Constitution lies entirely in the determination of > > each > > citizen to defend it. Only if every single citizen feels duty bound to do > > his share in this defense are the constitutional rights secure." > > -- Albert Einstein > > > > > > > -- > Gurkan Erdogdu > http://gurkanerdogdu.blogspot.com
