I use them a fair bit. Its a personal preference I guess, but if I'm trying something out, I like to try my own thing with a generated POM to get me started, rather than hack about someone else's example.
Examples are extremely useful though, and I've always thought the OpenEJB examples are really great. They're also a great place to start contributing to the project :) Jon On Mon, May 23, 2011 at 12:48 PM, Romain Manni-Bucau <[email protected]>wrote: > Do you really use ma en archetypes? Personaly examples are more useful. > - Romain > > Le 23 mai 2011 10:26, "Jonathan Gallimore" <[email protected]> > a > écrit : > > They've been there for a pretty long time. It looks like they should > work, > > and basically run the OpenEJB standalone server. I personally haven't > used > > them, but it would be great to see them being used as well. > > > > Jon > > > > On Mon, May 23, 2011 at 9:17 AM, Aldrin Leal <[email protected]> wrote: > > > >> Thank you. I just noticed there were already some archetypes. > >> > >> After that, I noticed the sandboxes also had some OpenEJB Mojos. Any > >> opinions about it as well? > >> > >> Thank you > >> > >> -- > >> -- Aldrin Leal, <[email protected]> / > http://www.leal.eng.br/mnemetica/ > >> > >> > >> On Mon, May 23, 2011 at 5:15 AM, Jonathan Gallimore < > >> [email protected]> wrote: > >> > >> > Hi Aldrin, > >> > > >> > I wrote a couple of Maven Archetypes a while back - one is for a > simple > >> > ejb-jar and the other is a multi module ear project, with OpenEJB > mixed > >> in > >> > to do testing. They were based on some generic J2EE archetypes that > were > >> > around at the time - not sure if they still are or not. > >> > > >> > I also committed an Arquillian adapter for our Tomcat integration > (known > >> as > >> > Apache TomEE) and it should also work for Tomcat 7 on its own as well. > >> > > >> > If you fancy taking a look at either of those, any feedback or > >> improvements > >> > you have for either will be gratefully received! I'd love to see these > >> > taken > >> > further. > >> > > >> > This is all in our sandbox area here: > >> > > >> > Maven Archetypes: > >> > > >> > > >> > > https://svn.apache.org/repos/asf/openejb/trunk/sandbox/openejb-maven-archetypes/ > >> > Arquillian Adapter: > >> > > https://svn.apache.org/repos/asf/openejb/trunk/sandbox/arquillian-tomee/ > >> > > >> > In terms of answering your specific points: > >> > > >> > - Which kind of situations you've often found into, which could be > >> mapped > >> > into archetypes? > >> > > >> > Generally the two mentioned above, the simple jar, and the full ear. I > >> > think > >> > an archetype for a web profile .war with ejbs mixed in that runs on > TomEE > >> > would be great as well. > >> > > >> > - Which kind of persistence frameworks do you often use? > >> > > >> > OpenJPA which the default, but Hibernate is really popular as well. We > >> also > >> > support EclipseLink, so it might be catering for that too. > >> > > >> > - Beside the choice of persistence, which other aspects would you like > >> to > >> > be able to tune from an archetype? > >> > > >> > Not really given that one much thought to be honest. Running OpenEJB > >> > embedded in a unit test, most things are configurable using properties > in > >> > the test itself. I'd be interested to see what suggestions others > might > >> > have. > >> > > >> > - Which special spices would you like to get, beyond testing? I mean, > to > >> > be able to turn into a full geronimo deployable artifact, or another > >> > container, using Archillian with OpenEJB wrapped inside, or simply > being > >> > able to tweak properties easily? > >> > > >> > I'd definitely love to see things being more testable with TomEE, > which > >> is > >> > why did some work on the TomEE Arquillian adapter. Currently TomEE's > >> config > >> > in that adapter is very hardcoded, being able to tweak any of that > >> > including > >> > the system properties would be a real bonus. > >> > > >> > Jon > >> > > >> > On Mon, May 23, 2011 at 8:32 AM, Aldrin Leal <[email protected]> > wrote: > >> > > >> > > Here is something I've been thinking about two days ago, and pinged > >> about > >> > > on > >> > > twitter do dblevins. However, I'd like your feedback. > >> > > > >> > > I love using OpenEJB. Not only I write articles on it, I simply use > it > >> as > >> > > an > >> > > embedded container. Given its ease of use, I figure it would be a > great > >> > > idea > >> > > to supply OpenEJB users with a set of M3 Archetypes for quickstart, > >> > ranging > >> > > from a simple, fully embedded jar for primary development, as well > as > a > >> > > full > >> > > multimodule project envolving persistence, remoting, ejbs and ears. > >> > > > >> > > I am taking this opportunity to study and learn it, based from > trunk. > >> > > Meanwhile, here is what I need your advice: > >> > > > >> > > - Which kind of situations you've often found into, which could be > >> > mapped > >> > > into archetypes? > >> > > - Which kind of persistence frameworks do you often use? > >> > > - Beside the choice of persistence, which other aspects would you > >> like > >> > to > >> > > be able to tune from an archetype? > >> > > - Which special spices would you like to get, beyond testing? I > mean, > >> > to > >> > > be able to turn into a full geronimo deployable artifact, or another > >> > > container, using Archillian with OpenEJB wrapped inside, or simply > >> > being > >> > > able to tweak properties easily? > >> > > > >> > > Your comments are welcome. Thank you :) > >> > > > >> > > > >> > > -- > >> > > -- Aldrin Leal, <[email protected]> / > >> http://www.leal.eng.br/mnemetica/ > >> > > > >> > > >> >
