You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Karan Malhi <ka...@gmail.com> on 2007/06/15 01:40:31 UTC
openejb- ease of use, snapshot and maven
SNAPSHOT RELEASE
I really want to be able to have a downloadable snapshot release. We
want to make it easy for people to download and extract a zipped file
and get started with openejb quickly. Downloading maven first, then
checking out the whole thing and building it and then extracting the
snapshot for usage is really not a very comfortable thought if
somebody had to try to use openejb. It would easily take more than 1.5
hours of somebody's time, before they can even start using openejb. On
top of that they will have to find the zip file from
openejb3\assembly\openejb-standalone\target directory. I dont think
this is very intuitive , even though it is well documented by Jacek on
the wiki.
Maybe we already have a link to the snapshot release, but I dont know
where to find it
SETUP DOCS
I want to be able to add some documentation, so that if anybody wanted
to use openejb with eclipse, then they should be able to setup their
environment in a few minutes, provided they have downloaded eclipse
and openejb. I would also like to provide some step by step kind of
docs to write a few ejb's in eclipse, deploy and test them in openejb.
THE PROBLEM
My biggest hurdle at this point is Maven. I do not fully understand it
and cannot spend enough time on it to be able to fix the problem
mentioned below:
If i run mvn -Dassemble clean install from root, filtering doesnt
work. however, if i simply run mvn from the openejb-standalone module,
filtering works fine. I did try to spend some time on it, but could
not spend too much time. One thing which i have learnt is that we need
to specify explicit versions of any plugins we are using in maven. In
future, maven is going to make it mandatory to specify explicit
versions, so it is going to be a good idea to adopt that strategy
right away.
May I also suggest that we do not use beta versions of plugins if they
have not been properly tested. Lets stick to the stable releases even
if we lose some cool functionality provided by the beta. We atleast
know that it works and will continue to work (unless some bug was
overlooked, but chances of that happening are lesser for stable than
beta versions)
MAVEN and OPENEJB GURUS -- If you can point me in the right direction
to fix the above issue, that would be awesome!!. Once the above
problem is fixed, then if somebody can provide any guidance on how to
automatically link the snapshot release on the openejb website, that
would be a big help.
--
Karan Malhi
Re: openejb- ease of use, snapshot and maven
Posted by Karan Malhi <ka...@gmail.com>.
I did see the implementation for JSR 88 in OpenEJB. OpenEJB supports
most of it, except for redeploy
Look at org.apache.openejb.config.OpenEJBDeploymentManager. It is an
implementation of JSR 88 DeploymentManager interface
On 6/20/07, Manu George <ma...@gmail.com> wrote:
> I was just thinking , does OEJB support JSR 77,JSR-88. I have not read
> the spec and have very limited knowledge of it, but if it did support
> jsr 88 wouldn't any JSR 88 tool be able to deploy to it. So we would
> be able to have say an admin console as well as the eclipse plugin
> using jsr 88 for deployment and so share the code?
>
> Regards
> Manu
>
> On 6/21/07, Manu George <ma...@gmail.com> wrote:
> > Yeah I guess so :). It is the test suite that should be run. It is
> > called from SomeoneBrokeSurefireAndThisIsADirtyHackForItTest because
> > of a problem with the surefire plugin that it can run only test cases
> >
> > Regards
> > Manu
> >
> > On 6/21/07, Karan Malhi <ka...@gmail.com> wrote:
> > > Manu,
> > >
> > > A test question here, is iTest.java just there to create a suite of tests?
> > >
> > > On 6/20/07, Manu George <ma...@gmail.com> wrote:
> > > > I will download 1.0 and have a go at porting this, looks pretty cool
> > > > and we definitely should have it in 3.0 :).
> > > >
> > > > On 6/21/07, Manu George <ma...@gmail.com> wrote:
> > > > > Hi,
> > > > > The webadmin is really cool. I was not at all aware it
> > > > > existed :(. I think it is a valuable feature to have in 3.0.
> > > > >
> > > > > Regards
> > > > > Manu
> > > > >
> > > > > On 6/20/07, Karan Malhi <ka...@gmail.com> wrote:
> > > > > > Thanks David,
> > > > > >
> > > > > > Will start adding stuff to the wiki pages. I saw the webadmin
> > > > > > screenshots. Its really cool.
> > > > > >
> > > > > > On 6/19/07, David Blevins <da...@visi.com> wrote:
> > > > > > >
> > > > > > > On Jun 18, 2007, at 4:24 PM, Karan Malhi wrote:
> > > > > > >
> > > > > > > > Thanks Mohammed,
> > > > > > > >
> > > > > > > > I have been able to finally fix the issue (and understand quite a bit
> > > > > > > > of maven in the process :) ). The whole thing was a combination of a
> > > > > > > > broken plugin and my lack of understanding of lifecycle phases and how
> > > > > > > > it applies differently to packaging types like war, jar and pom.
> > > > > > > > Finally with the help of the resources-plugin, I have been able to fix
> > > > > > > > the build issue.
> > > > > > >
> > > > > > > That's an impressive amount of debugging. It's no small task chasing
> > > > > > > down plugin issues with little maven experience.
> > > > > > >
> > > > > > > > Currently I couldnt find much on eclipse on the openejb website. If
> > > > > > > > Dario has already started to document this, then I would wait for him
> > > > > > > > to post. Meanwhile, I am going to use this snapshot build to create
> > > > > > > > some examples of creating EJB's with openejb.
> > > > > > >
> > > > > > > Don't wait! Two people working in isolation from each other on the
> > > > > > > same thing is bad, yes, but two people working together on the same
> > > > > > > thing is magic.... I just think back when Mohammad and Manu were
> > > > > > > both hacking on the itests together, did wonders for encouraging
> > > > > > > others to jump -- not to mention showing them how.
> > > > > > >
> > > > > > > Whatever the two of you'd like to do, I started a page here:
> > > > > > >
> > > > > > > http://cwiki.apache.org/OPENEJB/openejb-and-eclipse.html
> > > > > > >
> > > > > > > > What happened to the eclipse plugin though? Is anybody working on
> > > > > > > > that?. I have a semi-working swing based admin console. An eclipse
> > > > > > > > plugin would've been cool. Also, do you know if there is any web based
> > > > > > > > administrative console for openejb?
> > > > > > >
> > > > > > > Don't think anything is going on with the Eclipse plugin, feel
> > > > > > > encouraged to grab the yoke and start pulling. We did have a web
> > > > > > > console at one point, but it didn't survive the 1.0 -> 3.0 refactor.
> > > > > > > The code is definitely there in 1.0 if you wanted to try porting in
> > > > > > > over.
> > > > > > >
> > > > > > > Here are some docs on it: http://cwiki.apache.org/OPENEJB/webadmin.html
> > > > > > >
> > > > > > > Not fancy but it was an extremely small amount of code.
> > > > > > >
> > > > > > > -David
> > > > > > >
> > > > > > > > On 6/18/07, Mohammad Nour El-Din <no...@gmail.com> wrote:
> > > > > > > >> Hi Karan...
> > > > > > > >>
> > > > > > > >> On 6/15/07, Karan Malhi <ka...@gmail.com> wrote:
> > > > > > > >> >
> > > > > > > >> > SNAPSHOT RELEASE
> > > > > > > >> > I really want to be able to have a downloadable snapshot
> > > > > > > >> release. We
> > > > > > > >> > want to make it easy for people to download and extract a zipped
> > > > > > > >> file
> > > > > > > >> > and get started with openejb quickly. Downloading maven first, then
> > > > > > > >> > checking out the whole thing and building it and then extracting
> > > > > > > >> the
> > > > > > > >> > snapshot for usage is really not a very comfortable thought if
> > > > > > > >> > somebody had to try to use openejb. It would easily take more
> > > > > > > >> than 1.5
> > > > > > > >> > hours of somebody's time, before they can even start using
> > > > > > > >> openejb. On
> > > > > > > >> > top of that they will have to find the zip file from
> > > > > > > >> > openejb3\assembly\openejb-standalone\target directory. I dont think
> > > > > > > >> > this is very intuitive , even though it is well documented by
> > > > > > > >> Jacek on
> > > > > > > >> > the wiki.
> > > > > > > >> > Maybe we already have a link to the snapshot release, but I dont
> > > > > > > >> know
> > > > > > > >> > where to find it
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> For this issue I have a nice solution Prasad follows for providing
> > > > > > > >> daily
> > > > > > > >> snapshots for Apache Gernimo. At the end of each day, I will provide
> > > > > > > >> snapshots of OpenEJB3.0.0 with the build logs, just like what
> > > > > > > >> Prasad does
> > > > > > > >> and I will send a note with that on the dev-list.
> > > > > > > >>
> > > > > > > >> SETUP DOCS
> > > > > > > >> >
> > > > > > > >> > I want to be able to add some documentation, so that if anybody
> > > > > > > >> wanted
> > > > > > > >> > to use openejb with eclipse, then they should be able to setup
> > > > > > > >> their
> > > > > > > >> > environment in a few minutes, provided they have downloaded eclipse
> > > > > > > >> > and openejb. I would also like to provide some step by step
> > > > > > > >> kind of
> > > > > > > >> > docs to write a few ejb's in eclipse, deploy and test them in
> > > > > > > >> openejb.
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> Did u give sometime to search for that on the OpenEJB confluence
> > > > > > > >> http://docs.codehaus.org/display/OPENEJB/Home, I think you will
> > > > > > > >> find such
> > > > > > > >> info there. And if not I am glad to provide these info for OpenEJB
> > > > > > > >> users.
> > > > > > > >>
> > > > > > > >> THE PROBLEM
> > > > > > > >> >
> > > > > > > >> > My biggest hurdle at this point is Maven. I do not fully
> > > > > > > >> understand it
> > > > > > > >> > and cannot spend enough time on it to be able to fix the problem
> > > > > > > >> > mentioned below:
> > > > > > > >> >
> > > > > > > >> > If i run mvn -Dassemble clean install from root, filtering doesnt
> > > > > > > >> > work. however, if i simply run mvn from the openejb-standalone
> > > > > > > >> module,
> > > > > > > >> > filtering works fine. I did try to spend some time on it, but could
> > > > > > > >> > not spend too much time. One thing which i have learnt is that
> > > > > > > >> we need
> > > > > > > >> > to specify explicit versions of any plugins we are using in
> > > > > > > >> maven. In
> > > > > > > >> > future, maven is going to make it mandatory to specify explicit
> > > > > > > >> > versions, so it is going to be a good idea to adopt that strategy
> > > > > > > >> > right away.
> > > > > > > >> >
> > > > > > > >> > May I also suggest that we do not use beta versions of plugins
> > > > > > > >> if they
> > > > > > > >> > have not been properly tested. Lets stick to the stable releases
> > > > > > > >> even
> > > > > > > >> > if we lose some cool functionality provided by the beta. We atleast
> > > > > > > >> > know that it works and will continue to work (unless some bug was
> > > > > > > >> > overlooked, but chances of that happening are lesser for stable
> > > > > > > >> than
> > > > > > > >> > beta versions)
> > > > > > > >> >
> > > > > > > >> > MAVEN and OPENEJB GURUS -- If you can point me in the right
> > > > > > > >> direction
> > > > > > > >> > to fix the above issue, that would be awesome!!. Once the above
> > > > > > > >> > problem is fixed, then if somebody can provide any guidance on
> > > > > > > >> how to
> > > > > > > >> > automatically link the snapshot release on the openejb website,
> > > > > > > >> that
> > > > > > > >> > would be a big help.
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> In this point I am just like you :), I think we both need help
> > > > > > > >> from Apache
> > > > > > > >> Maven2 gurus.
> > > > > > > >>
> > > > > > > >> --
> > > > > > > >> > Karan Malhi
> > > > > > > >> >
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> --
> > > > > > > >> Thanks
> > > > > > > >> - Mohammad Nour
> > > > > > > >>
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Karan Malhi
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Karan Malhi
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Karan Malhi
> > >
> >
>
--
Karan Malhi
Re: openejb- ease of use, snapshot and maven
Posted by Manu George <ma...@gmail.com>.
I was just thinking , does OEJB support JSR 77,JSR-88. I have not read
the spec and have very limited knowledge of it, but if it did support
jsr 88 wouldn't any JSR 88 tool be able to deploy to it. So we would
be able to have say an admin console as well as the eclipse plugin
using jsr 88 for deployment and so share the code?
Regards
Manu
On 6/21/07, Manu George <ma...@gmail.com> wrote:
> Yeah I guess so :). It is the test suite that should be run. It is
> called from SomeoneBrokeSurefireAndThisIsADirtyHackForItTest because
> of a problem with the surefire plugin that it can run only test cases
>
> Regards
> Manu
>
> On 6/21/07, Karan Malhi <ka...@gmail.com> wrote:
> > Manu,
> >
> > A test question here, is iTest.java just there to create a suite of tests?
> >
> > On 6/20/07, Manu George <ma...@gmail.com> wrote:
> > > I will download 1.0 and have a go at porting this, looks pretty cool
> > > and we definitely should have it in 3.0 :).
> > >
> > > On 6/21/07, Manu George <ma...@gmail.com> wrote:
> > > > Hi,
> > > > The webadmin is really cool. I was not at all aware it
> > > > existed :(. I think it is a valuable feature to have in 3.0.
> > > >
> > > > Regards
> > > > Manu
> > > >
> > > > On 6/20/07, Karan Malhi <ka...@gmail.com> wrote:
> > > > > Thanks David,
> > > > >
> > > > > Will start adding stuff to the wiki pages. I saw the webadmin
> > > > > screenshots. Its really cool.
> > > > >
> > > > > On 6/19/07, David Blevins <da...@visi.com> wrote:
> > > > > >
> > > > > > On Jun 18, 2007, at 4:24 PM, Karan Malhi wrote:
> > > > > >
> > > > > > > Thanks Mohammed,
> > > > > > >
> > > > > > > I have been able to finally fix the issue (and understand quite a bit
> > > > > > > of maven in the process :) ). The whole thing was a combination of a
> > > > > > > broken plugin and my lack of understanding of lifecycle phases and how
> > > > > > > it applies differently to packaging types like war, jar and pom.
> > > > > > > Finally with the help of the resources-plugin, I have been able to fix
> > > > > > > the build issue.
> > > > > >
> > > > > > That's an impressive amount of debugging. It's no small task chasing
> > > > > > down plugin issues with little maven experience.
> > > > > >
> > > > > > > Currently I couldnt find much on eclipse on the openejb website. If
> > > > > > > Dario has already started to document this, then I would wait for him
> > > > > > > to post. Meanwhile, I am going to use this snapshot build to create
> > > > > > > some examples of creating EJB's with openejb.
> > > > > >
> > > > > > Don't wait! Two people working in isolation from each other on the
> > > > > > same thing is bad, yes, but two people working together on the same
> > > > > > thing is magic.... I just think back when Mohammad and Manu were
> > > > > > both hacking on the itests together, did wonders for encouraging
> > > > > > others to jump -- not to mention showing them how.
> > > > > >
> > > > > > Whatever the two of you'd like to do, I started a page here:
> > > > > >
> > > > > > http://cwiki.apache.org/OPENEJB/openejb-and-eclipse.html
> > > > > >
> > > > > > > What happened to the eclipse plugin though? Is anybody working on
> > > > > > > that?. I have a semi-working swing based admin console. An eclipse
> > > > > > > plugin would've been cool. Also, do you know if there is any web based
> > > > > > > administrative console for openejb?
> > > > > >
> > > > > > Don't think anything is going on with the Eclipse plugin, feel
> > > > > > encouraged to grab the yoke and start pulling. We did have a web
> > > > > > console at one point, but it didn't survive the 1.0 -> 3.0 refactor.
> > > > > > The code is definitely there in 1.0 if you wanted to try porting in
> > > > > > over.
> > > > > >
> > > > > > Here are some docs on it: http://cwiki.apache.org/OPENEJB/webadmin.html
> > > > > >
> > > > > > Not fancy but it was an extremely small amount of code.
> > > > > >
> > > > > > -David
> > > > > >
> > > > > > > On 6/18/07, Mohammad Nour El-Din <no...@gmail.com> wrote:
> > > > > > >> Hi Karan...
> > > > > > >>
> > > > > > >> On 6/15/07, Karan Malhi <ka...@gmail.com> wrote:
> > > > > > >> >
> > > > > > >> > SNAPSHOT RELEASE
> > > > > > >> > I really want to be able to have a downloadable snapshot
> > > > > > >> release. We
> > > > > > >> > want to make it easy for people to download and extract a zipped
> > > > > > >> file
> > > > > > >> > and get started with openejb quickly. Downloading maven first, then
> > > > > > >> > checking out the whole thing and building it and then extracting
> > > > > > >> the
> > > > > > >> > snapshot for usage is really not a very comfortable thought if
> > > > > > >> > somebody had to try to use openejb. It would easily take more
> > > > > > >> than 1.5
> > > > > > >> > hours of somebody's time, before they can even start using
> > > > > > >> openejb. On
> > > > > > >> > top of that they will have to find the zip file from
> > > > > > >> > openejb3\assembly\openejb-standalone\target directory. I dont think
> > > > > > >> > this is very intuitive , even though it is well documented by
> > > > > > >> Jacek on
> > > > > > >> > the wiki.
> > > > > > >> > Maybe we already have a link to the snapshot release, but I dont
> > > > > > >> know
> > > > > > >> > where to find it
> > > > > > >>
> > > > > > >>
> > > > > > >> For this issue I have a nice solution Prasad follows for providing
> > > > > > >> daily
> > > > > > >> snapshots for Apache Gernimo. At the end of each day, I will provide
> > > > > > >> snapshots of OpenEJB3.0.0 with the build logs, just like what
> > > > > > >> Prasad does
> > > > > > >> and I will send a note with that on the dev-list.
> > > > > > >>
> > > > > > >> SETUP DOCS
> > > > > > >> >
> > > > > > >> > I want to be able to add some documentation, so that if anybody
> > > > > > >> wanted
> > > > > > >> > to use openejb with eclipse, then they should be able to setup
> > > > > > >> their
> > > > > > >> > environment in a few minutes, provided they have downloaded eclipse
> > > > > > >> > and openejb. I would also like to provide some step by step
> > > > > > >> kind of
> > > > > > >> > docs to write a few ejb's in eclipse, deploy and test them in
> > > > > > >> openejb.
> > > > > > >>
> > > > > > >>
> > > > > > >> Did u give sometime to search for that on the OpenEJB confluence
> > > > > > >> http://docs.codehaus.org/display/OPENEJB/Home, I think you will
> > > > > > >> find such
> > > > > > >> info there. And if not I am glad to provide these info for OpenEJB
> > > > > > >> users.
> > > > > > >>
> > > > > > >> THE PROBLEM
> > > > > > >> >
> > > > > > >> > My biggest hurdle at this point is Maven. I do not fully
> > > > > > >> understand it
> > > > > > >> > and cannot spend enough time on it to be able to fix the problem
> > > > > > >> > mentioned below:
> > > > > > >> >
> > > > > > >> > If i run mvn -Dassemble clean install from root, filtering doesnt
> > > > > > >> > work. however, if i simply run mvn from the openejb-standalone
> > > > > > >> module,
> > > > > > >> > filtering works fine. I did try to spend some time on it, but could
> > > > > > >> > not spend too much time. One thing which i have learnt is that
> > > > > > >> we need
> > > > > > >> > to specify explicit versions of any plugins we are using in
> > > > > > >> maven. In
> > > > > > >> > future, maven is going to make it mandatory to specify explicit
> > > > > > >> > versions, so it is going to be a good idea to adopt that strategy
> > > > > > >> > right away.
> > > > > > >> >
> > > > > > >> > May I also suggest that we do not use beta versions of plugins
> > > > > > >> if they
> > > > > > >> > have not been properly tested. Lets stick to the stable releases
> > > > > > >> even
> > > > > > >> > if we lose some cool functionality provided by the beta. We atleast
> > > > > > >> > know that it works and will continue to work (unless some bug was
> > > > > > >> > overlooked, but chances of that happening are lesser for stable
> > > > > > >> than
> > > > > > >> > beta versions)
> > > > > > >> >
> > > > > > >> > MAVEN and OPENEJB GURUS -- If you can point me in the right
> > > > > > >> direction
> > > > > > >> > to fix the above issue, that would be awesome!!. Once the above
> > > > > > >> > problem is fixed, then if somebody can provide any guidance on
> > > > > > >> how to
> > > > > > >> > automatically link the snapshot release on the openejb website,
> > > > > > >> that
> > > > > > >> > would be a big help.
> > > > > > >>
> > > > > > >>
> > > > > > >> In this point I am just like you :), I think we both need help
> > > > > > >> from Apache
> > > > > > >> Maven2 gurus.
> > > > > > >>
> > > > > > >> --
> > > > > > >> > Karan Malhi
> > > > > > >> >
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >> --
> > > > > > >> Thanks
> > > > > > >> - Mohammad Nour
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Karan Malhi
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Karan Malhi
> > > > >
> > > >
> > >
> >
> >
> > --
> > Karan Malhi
> >
>
Re: openejb- ease of use, snapshot and maven
Posted by Manu George <ma...@gmail.com>.
Yeah I guess so :). It is the test suite that should be run. It is
called from SomeoneBrokeSurefireAndThisIsADirtyHackForItTest because
of a problem with the surefire plugin that it can run only test cases
Regards
Manu
On 6/21/07, Karan Malhi <ka...@gmail.com> wrote:
> Manu,
>
> A test question here, is iTest.java just there to create a suite of tests?
>
> On 6/20/07, Manu George <ma...@gmail.com> wrote:
> > I will download 1.0 and have a go at porting this, looks pretty cool
> > and we definitely should have it in 3.0 :).
> >
> > On 6/21/07, Manu George <ma...@gmail.com> wrote:
> > > Hi,
> > > The webadmin is really cool. I was not at all aware it
> > > existed :(. I think it is a valuable feature to have in 3.0.
> > >
> > > Regards
> > > Manu
> > >
> > > On 6/20/07, Karan Malhi <ka...@gmail.com> wrote:
> > > > Thanks David,
> > > >
> > > > Will start adding stuff to the wiki pages. I saw the webadmin
> > > > screenshots. Its really cool.
> > > >
> > > > On 6/19/07, David Blevins <da...@visi.com> wrote:
> > > > >
> > > > > On Jun 18, 2007, at 4:24 PM, Karan Malhi wrote:
> > > > >
> > > > > > Thanks Mohammed,
> > > > > >
> > > > > > I have been able to finally fix the issue (and understand quite a bit
> > > > > > of maven in the process :) ). The whole thing was a combination of a
> > > > > > broken plugin and my lack of understanding of lifecycle phases and how
> > > > > > it applies differently to packaging types like war, jar and pom.
> > > > > > Finally with the help of the resources-plugin, I have been able to fix
> > > > > > the build issue.
> > > > >
> > > > > That's an impressive amount of debugging. It's no small task chasing
> > > > > down plugin issues with little maven experience.
> > > > >
> > > > > > Currently I couldnt find much on eclipse on the openejb website. If
> > > > > > Dario has already started to document this, then I would wait for him
> > > > > > to post. Meanwhile, I am going to use this snapshot build to create
> > > > > > some examples of creating EJB's with openejb.
> > > > >
> > > > > Don't wait! Two people working in isolation from each other on the
> > > > > same thing is bad, yes, but two people working together on the same
> > > > > thing is magic.... I just think back when Mohammad and Manu were
> > > > > both hacking on the itests together, did wonders for encouraging
> > > > > others to jump -- not to mention showing them how.
> > > > >
> > > > > Whatever the two of you'd like to do, I started a page here:
> > > > >
> > > > > http://cwiki.apache.org/OPENEJB/openejb-and-eclipse.html
> > > > >
> > > > > > What happened to the eclipse plugin though? Is anybody working on
> > > > > > that?. I have a semi-working swing based admin console. An eclipse
> > > > > > plugin would've been cool. Also, do you know if there is any web based
> > > > > > administrative console for openejb?
> > > > >
> > > > > Don't think anything is going on with the Eclipse plugin, feel
> > > > > encouraged to grab the yoke and start pulling. We did have a web
> > > > > console at one point, but it didn't survive the 1.0 -> 3.0 refactor.
> > > > > The code is definitely there in 1.0 if you wanted to try porting in
> > > > > over.
> > > > >
> > > > > Here are some docs on it: http://cwiki.apache.org/OPENEJB/webadmin.html
> > > > >
> > > > > Not fancy but it was an extremely small amount of code.
> > > > >
> > > > > -David
> > > > >
> > > > > > On 6/18/07, Mohammad Nour El-Din <no...@gmail.com> wrote:
> > > > > >> Hi Karan...
> > > > > >>
> > > > > >> On 6/15/07, Karan Malhi <ka...@gmail.com> wrote:
> > > > > >> >
> > > > > >> > SNAPSHOT RELEASE
> > > > > >> > I really want to be able to have a downloadable snapshot
> > > > > >> release. We
> > > > > >> > want to make it easy for people to download and extract a zipped
> > > > > >> file
> > > > > >> > and get started with openejb quickly. Downloading maven first, then
> > > > > >> > checking out the whole thing and building it and then extracting
> > > > > >> the
> > > > > >> > snapshot for usage is really not a very comfortable thought if
> > > > > >> > somebody had to try to use openejb. It would easily take more
> > > > > >> than 1.5
> > > > > >> > hours of somebody's time, before they can even start using
> > > > > >> openejb. On
> > > > > >> > top of that they will have to find the zip file from
> > > > > >> > openejb3\assembly\openejb-standalone\target directory. I dont think
> > > > > >> > this is very intuitive , even though it is well documented by
> > > > > >> Jacek on
> > > > > >> > the wiki.
> > > > > >> > Maybe we already have a link to the snapshot release, but I dont
> > > > > >> know
> > > > > >> > where to find it
> > > > > >>
> > > > > >>
> > > > > >> For this issue I have a nice solution Prasad follows for providing
> > > > > >> daily
> > > > > >> snapshots for Apache Gernimo. At the end of each day, I will provide
> > > > > >> snapshots of OpenEJB3.0.0 with the build logs, just like what
> > > > > >> Prasad does
> > > > > >> and I will send a note with that on the dev-list.
> > > > > >>
> > > > > >> SETUP DOCS
> > > > > >> >
> > > > > >> > I want to be able to add some documentation, so that if anybody
> > > > > >> wanted
> > > > > >> > to use openejb with eclipse, then they should be able to setup
> > > > > >> their
> > > > > >> > environment in a few minutes, provided they have downloaded eclipse
> > > > > >> > and openejb. I would also like to provide some step by step
> > > > > >> kind of
> > > > > >> > docs to write a few ejb's in eclipse, deploy and test them in
> > > > > >> openejb.
> > > > > >>
> > > > > >>
> > > > > >> Did u give sometime to search for that on the OpenEJB confluence
> > > > > >> http://docs.codehaus.org/display/OPENEJB/Home, I think you will
> > > > > >> find such
> > > > > >> info there. And if not I am glad to provide these info for OpenEJB
> > > > > >> users.
> > > > > >>
> > > > > >> THE PROBLEM
> > > > > >> >
> > > > > >> > My biggest hurdle at this point is Maven. I do not fully
> > > > > >> understand it
> > > > > >> > and cannot spend enough time on it to be able to fix the problem
> > > > > >> > mentioned below:
> > > > > >> >
> > > > > >> > If i run mvn -Dassemble clean install from root, filtering doesnt
> > > > > >> > work. however, if i simply run mvn from the openejb-standalone
> > > > > >> module,
> > > > > >> > filtering works fine. I did try to spend some time on it, but could
> > > > > >> > not spend too much time. One thing which i have learnt is that
> > > > > >> we need
> > > > > >> > to specify explicit versions of any plugins we are using in
> > > > > >> maven. In
> > > > > >> > future, maven is going to make it mandatory to specify explicit
> > > > > >> > versions, so it is going to be a good idea to adopt that strategy
> > > > > >> > right away.
> > > > > >> >
> > > > > >> > May I also suggest that we do not use beta versions of plugins
> > > > > >> if they
> > > > > >> > have not been properly tested. Lets stick to the stable releases
> > > > > >> even
> > > > > >> > if we lose some cool functionality provided by the beta. We atleast
> > > > > >> > know that it works and will continue to work (unless some bug was
> > > > > >> > overlooked, but chances of that happening are lesser for stable
> > > > > >> than
> > > > > >> > beta versions)
> > > > > >> >
> > > > > >> > MAVEN and OPENEJB GURUS -- If you can point me in the right
> > > > > >> direction
> > > > > >> > to fix the above issue, that would be awesome!!. Once the above
> > > > > >> > problem is fixed, then if somebody can provide any guidance on
> > > > > >> how to
> > > > > >> > automatically link the snapshot release on the openejb website,
> > > > > >> that
> > > > > >> > would be a big help.
> > > > > >>
> > > > > >>
> > > > > >> In this point I am just like you :), I think we both need help
> > > > > >> from Apache
> > > > > >> Maven2 gurus.
> > > > > >>
> > > > > >> --
> > > > > >> > Karan Malhi
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >> Thanks
> > > > > >> - Mohammad Nour
> > > > > >>
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Karan Malhi
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Karan Malhi
> > > >
> > >
> >
>
>
> --
> Karan Malhi
>
Re: openejb- ease of use, snapshot and maven
Posted by Karan Malhi <ka...@gmail.com>.
Manu,
A test question here, is iTest.java just there to create a suite of tests?
On 6/20/07, Manu George <ma...@gmail.com> wrote:
> I will download 1.0 and have a go at porting this, looks pretty cool
> and we definitely should have it in 3.0 :).
>
> On 6/21/07, Manu George <ma...@gmail.com> wrote:
> > Hi,
> > The webadmin is really cool. I was not at all aware it
> > existed :(. I think it is a valuable feature to have in 3.0.
> >
> > Regards
> > Manu
> >
> > On 6/20/07, Karan Malhi <ka...@gmail.com> wrote:
> > > Thanks David,
> > >
> > > Will start adding stuff to the wiki pages. I saw the webadmin
> > > screenshots. Its really cool.
> > >
> > > On 6/19/07, David Blevins <da...@visi.com> wrote:
> > > >
> > > > On Jun 18, 2007, at 4:24 PM, Karan Malhi wrote:
> > > >
> > > > > Thanks Mohammed,
> > > > >
> > > > > I have been able to finally fix the issue (and understand quite a bit
> > > > > of maven in the process :) ). The whole thing was a combination of a
> > > > > broken plugin and my lack of understanding of lifecycle phases and how
> > > > > it applies differently to packaging types like war, jar and pom.
> > > > > Finally with the help of the resources-plugin, I have been able to fix
> > > > > the build issue.
> > > >
> > > > That's an impressive amount of debugging. It's no small task chasing
> > > > down plugin issues with little maven experience.
> > > >
> > > > > Currently I couldnt find much on eclipse on the openejb website. If
> > > > > Dario has already started to document this, then I would wait for him
> > > > > to post. Meanwhile, I am going to use this snapshot build to create
> > > > > some examples of creating EJB's with openejb.
> > > >
> > > > Don't wait! Two people working in isolation from each other on the
> > > > same thing is bad, yes, but two people working together on the same
> > > > thing is magic.... I just think back when Mohammad and Manu were
> > > > both hacking on the itests together, did wonders for encouraging
> > > > others to jump -- not to mention showing them how.
> > > >
> > > > Whatever the two of you'd like to do, I started a page here:
> > > >
> > > > http://cwiki.apache.org/OPENEJB/openejb-and-eclipse.html
> > > >
> > > > > What happened to the eclipse plugin though? Is anybody working on
> > > > > that?. I have a semi-working swing based admin console. An eclipse
> > > > > plugin would've been cool. Also, do you know if there is any web based
> > > > > administrative console for openejb?
> > > >
> > > > Don't think anything is going on with the Eclipse plugin, feel
> > > > encouraged to grab the yoke and start pulling. We did have a web
> > > > console at one point, but it didn't survive the 1.0 -> 3.0 refactor.
> > > > The code is definitely there in 1.0 if you wanted to try porting in
> > > > over.
> > > >
> > > > Here are some docs on it: http://cwiki.apache.org/OPENEJB/webadmin.html
> > > >
> > > > Not fancy but it was an extremely small amount of code.
> > > >
> > > > -David
> > > >
> > > > > On 6/18/07, Mohammad Nour El-Din <no...@gmail.com> wrote:
> > > > >> Hi Karan...
> > > > >>
> > > > >> On 6/15/07, Karan Malhi <ka...@gmail.com> wrote:
> > > > >> >
> > > > >> > SNAPSHOT RELEASE
> > > > >> > I really want to be able to have a downloadable snapshot
> > > > >> release. We
> > > > >> > want to make it easy for people to download and extract a zipped
> > > > >> file
> > > > >> > and get started with openejb quickly. Downloading maven first, then
> > > > >> > checking out the whole thing and building it and then extracting
> > > > >> the
> > > > >> > snapshot for usage is really not a very comfortable thought if
> > > > >> > somebody had to try to use openejb. It would easily take more
> > > > >> than 1.5
> > > > >> > hours of somebody's time, before they can even start using
> > > > >> openejb. On
> > > > >> > top of that they will have to find the zip file from
> > > > >> > openejb3\assembly\openejb-standalone\target directory. I dont think
> > > > >> > this is very intuitive , even though it is well documented by
> > > > >> Jacek on
> > > > >> > the wiki.
> > > > >> > Maybe we already have a link to the snapshot release, but I dont
> > > > >> know
> > > > >> > where to find it
> > > > >>
> > > > >>
> > > > >> For this issue I have a nice solution Prasad follows for providing
> > > > >> daily
> > > > >> snapshots for Apache Gernimo. At the end of each day, I will provide
> > > > >> snapshots of OpenEJB3.0.0 with the build logs, just like what
> > > > >> Prasad does
> > > > >> and I will send a note with that on the dev-list.
> > > > >>
> > > > >> SETUP DOCS
> > > > >> >
> > > > >> > I want to be able to add some documentation, so that if anybody
> > > > >> wanted
> > > > >> > to use openejb with eclipse, then they should be able to setup
> > > > >> their
> > > > >> > environment in a few minutes, provided they have downloaded eclipse
> > > > >> > and openejb. I would also like to provide some step by step
> > > > >> kind of
> > > > >> > docs to write a few ejb's in eclipse, deploy and test them in
> > > > >> openejb.
> > > > >>
> > > > >>
> > > > >> Did u give sometime to search for that on the OpenEJB confluence
> > > > >> http://docs.codehaus.org/display/OPENEJB/Home, I think you will
> > > > >> find such
> > > > >> info there. And if not I am glad to provide these info for OpenEJB
> > > > >> users.
> > > > >>
> > > > >> THE PROBLEM
> > > > >> >
> > > > >> > My biggest hurdle at this point is Maven. I do not fully
> > > > >> understand it
> > > > >> > and cannot spend enough time on it to be able to fix the problem
> > > > >> > mentioned below:
> > > > >> >
> > > > >> > If i run mvn -Dassemble clean install from root, filtering doesnt
> > > > >> > work. however, if i simply run mvn from the openejb-standalone
> > > > >> module,
> > > > >> > filtering works fine. I did try to spend some time on it, but could
> > > > >> > not spend too much time. One thing which i have learnt is that
> > > > >> we need
> > > > >> > to specify explicit versions of any plugins we are using in
> > > > >> maven. In
> > > > >> > future, maven is going to make it mandatory to specify explicit
> > > > >> > versions, so it is going to be a good idea to adopt that strategy
> > > > >> > right away.
> > > > >> >
> > > > >> > May I also suggest that we do not use beta versions of plugins
> > > > >> if they
> > > > >> > have not been properly tested. Lets stick to the stable releases
> > > > >> even
> > > > >> > if we lose some cool functionality provided by the beta. We atleast
> > > > >> > know that it works and will continue to work (unless some bug was
> > > > >> > overlooked, but chances of that happening are lesser for stable
> > > > >> than
> > > > >> > beta versions)
> > > > >> >
> > > > >> > MAVEN and OPENEJB GURUS -- If you can point me in the right
> > > > >> direction
> > > > >> > to fix the above issue, that would be awesome!!. Once the above
> > > > >> > problem is fixed, then if somebody can provide any guidance on
> > > > >> how to
> > > > >> > automatically link the snapshot release on the openejb website,
> > > > >> that
> > > > >> > would be a big help.
> > > > >>
> > > > >>
> > > > >> In this point I am just like you :), I think we both need help
> > > > >> from Apache
> > > > >> Maven2 gurus.
> > > > >>
> > > > >> --
> > > > >> > Karan Malhi
> > > > >> >
> > > > >>
> > > > >>
> > > > >>
> > > > >> --
> > > > >> Thanks
> > > > >> - Mohammad Nour
> > > > >>
> > > > >
> > > > >
> > > > > --
> > > > > Karan Malhi
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Karan Malhi
> > >
> >
>
--
Karan Malhi
Re: WebAdmin (was Re: openejb- ease of use, snapshot and maven)
Posted by Jeremy Whitlock <jc...@gmail.com>.
Hi All,
Since I was involved in the original, maybe I could help. Let me
give a peek as well.
Take care,
Jeremy
On 8/3/07, David Blevins <da...@visi.com> wrote:
>
> On Jun 20, 2007, at 12:30 PM, Manu George wrote:
>
> >
> > On 6/21/07, Manu George <ma...@gmail.com> wrote:
> >>
> >> On 6/20/07, Karan Malhi <ka...@gmail.com> wrote:
> >> > Thanks David,
> >> >
> >> > Will start adding stuff to the wiki pages. I saw the webadmin
> >> > screenshots. Its really cool.
> >>
> >> Hi,
> >> The webadmin is really cool. I was not at all aware it
> >> existed :(. I think it is a valuable feature to have in 3.0.
> >>
> >
> > I will download 1.0 and have a go at porting this, looks pretty cool
> > and we definitely should have it in 3.0 :).
> >
>
> I took a crack at porting some of the webadmin over. I had to cut
> out several beans and it still doesn't work yet.
>
> Hoping I can get at least a limited amount of it working for the
> release, but there'll still be a lot of work to do.
>
> -David
>
>
Re: WebAdmin
Posted by David Blevins <da...@visi.com>.
On Aug 3, 2007, at 7:09 PM, David Blevins wrote:
>
> On Jun 20, 2007, at 12:30 PM, Manu George wrote:
>
>>
>> On 6/21/07, Manu George <ma...@gmail.com> wrote:
>>>
>>> On 6/20/07, Karan Malhi <ka...@gmail.com> wrote:
>>> > Thanks David,
>>> >
>>> > Will start adding stuff to the wiki pages. I saw the webadmin
>>> > screenshots. Its really cool.
>>>
>>> Hi,
>>> The webadmin is really cool. I was not at all aware it
>>> existed :(. I think it is a valuable feature to have in 3.0.
>>>
>>
>> I will download 1.0 and have a go at porting this, looks pretty cool
>> and we definitely should have it in 3.0 :).
>>
>
> I took a crack at porting some of the webadmin over. I had to cut
> out several beans and it still doesn't work yet.
>
> Hoping I can get at least a limited amount of it working for the
> release, but there'll still be a lot of work to do.
Someone was asking about this offline, so here's the info I can recall
about the WebAdmin.
This module is a bit out of date and not shipped. I don't exactly
recall what state it's in. It's not a bad concept though and does
allow people to write beans that are dynamically included in the
WebAdmin UI, which is sort of neat. Basically any bean that
implements the HttpObject interface and declares it's jndi name in the
format 'WebAdmin/<section>/<page>' gets included in the UI.
It's not a terribly complex chunk of code actually and the JSP
equivalent of all that functionality in the Tomcat OpenEJB console has
been actively updated, so it might not be terribly difficult to get it
all running again. Anyone is more than welcome to hack on it.
Just had a quick look at it and it seems like there's no longer an
openejb-jar.xml file there. I dug in the old 1.0 codebase and found
them here:
http://svn.apache.org/repos/asf/openejb/tags/v1_0/modules/webadmin/src/java/org/openejb/webadmin/clienttools/ejb-jar.xml
http://svn.apache.org/repos/asf/openejb/tags/v1_0/modules/webadmin/src/java/org/openejb/webadmin/clienttools/openejb-jar.xml
http://svn.apache.org/repos/asf/openejb/tags/v1_0/modules/webadmin/src/java/org/openejb/webadmin/main/ejb-jar.xml
http://svn.apache.org/repos/asf/openejb/tags/v1_0/modules/webadmin/src/java/org/openejb/webadmin/main/openejb-jar.xml
Seems like if you combined the all together into one ejb-jar.xml and
openejb-jar.xml file and put them in the META-INF/ dir of the webadmin
jar, the beans would deploy and show up in the viewer.
You'd probably want to add this to the openejb-jar.xml file though so
the JNDI names are formatted the way they used to be.
<?xml version="1.0"?>
<openejb-jar>
<properties>
openejb.jndiname.format = {deploymentId}
{interfaceType.openejbLegacyName}
</properties>
...
</openejb-jar>
Should be enough to see a little action.
-David
Re: WebAdmin (was Re: openejb- ease of use, snapshot and maven)
Posted by David Blevins <da...@visi.com>.
On Jun 20, 2007, at 12:30 PM, Manu George wrote:
>
> On 6/21/07, Manu George <ma...@gmail.com> wrote:
>>
>> On 6/20/07, Karan Malhi <ka...@gmail.com> wrote:
>> > Thanks David,
>> >
>> > Will start adding stuff to the wiki pages. I saw the webadmin
>> > screenshots. Its really cool.
>>
>> Hi,
>> The webadmin is really cool. I was not at all aware it
>> existed :(. I think it is a valuable feature to have in 3.0.
>>
>
> I will download 1.0 and have a go at porting this, looks pretty cool
> and we definitely should have it in 3.0 :).
>
I took a crack at porting some of the webadmin over. I had to cut
out several beans and it still doesn't work yet.
Hoping I can get at least a limited amount of it working for the
release, but there'll still be a lot of work to do.
-David
Re: WebAdmin (was Re: openejb- ease of use, snapshot and maven)
Posted by Manu George <ma...@gmail.com>.
Thanks for the link Karan.
regards
Manu
On 6/21/07, Karan Malhi <ka...@gmail.com> wrote:
> Here is the link which talks about service-jar.xml and xbean. Still
> havent been able to get it to the website. :(
>
> http://www.nabble.com/How-is-XBean-used-in-OpenEJB-3--tf2148639.html#a5959172
>
> On 6/20/07, David Blevins <da...@visi.com> wrote:
> >
> > On Jun 20, 2007, at 12:30 PM, Manu George wrote:
> >
> > > I will download 1.0 and have a go at porting this, looks pretty cool
> > > and we definitely should have it in 3.0 :).
> >
> > Cool. Here is some info to arm you in how it worked. Knowledge
> > transfer commencing in 3.. 2.. 1....
> >
> > Plain old stateless beans were used as the "servlets". To make a
> > bean that would show up in the Webadmin Console you simply had to
> > implement the HttpBean interface (i think it's now called
> > HttpListener) and give your bean a deploymentId following this format
> > "webadmin/{section}/{page}". Anyone could add to the Webadmin
> > console by doing both of these things, which is really cool as people
> > developing EJB apps can also deploy beans for administering those
> > apps right in the exact same jar. This is not only easy for
> > packaging but means new sections can be added/removed on the fly.
> >
> > Using the described "webadmin/{section}/{page}" deploymentId format,
> > things end up automagically grouped in the JNDI tree. There's a
> > 'webadmin' context we grab which will contain any number of "section"
> > contexts ("ClientTools", "EJBGenerator", etc.). Each of those
> > section subcontexts will contain several beans which we will use to
> > make the pages. Making the menu is pretty easy as we just iterate
> > over the webadmin section of the global jndi tree.
> >
> > When an http request came in we just took the path part of the GET or
> > POST request, prepended "webadmin/" and then went looking for a bean
> > with that deployment id and invoked it via it's HttpBean (now called
> > HttpListener) interface passing in a HttpRequest and HttpResponse
> > objects which are trimmed down versions of similar servlet classes.
> > There'll be some changes to this as now we support our plain ejb
> > protocol over our http implementation, so the two will have to find a
> > way to share the URL space. See the openejb-http module.
> >
> > To implement session state, we had a stateful session bean
> > implementing an HttpSession interface (again, similar to the servlet
> > equivalent) and simply wrote the internal ID of the bean instance
> > into a Cookie sent to the browser. For some reason we would write
> > the javax.ejb.Handle of the stateful bean's EJBObject to disk and
> > read it back out on subsequent requests then used it to get a
> > reference to the EJBObject again. I'm not sure why we didn't just
> > keep a static hashmap and put the EJBObject right in it using an ID
> > we could just make up like UUID (that would have been way simpler).
> >
> > We had a standard superclass we favored for beans that implemented
> > the HttpBean (HttpListener) interface that did templating and the
> > aforementioned menu construction. The templating was perhaps too
> > tricky as we used a non-printable character to determine where to
> > insert data. Now we could just use swizzle-stream for some pretty
> > decent templating ability or even velocity. I'd be hesitant to
> > endorse velocity as we already have a dep on swizzle-stream and
> > wouldn't want to see us add another meg to our distro size if we can
> > avoid it -- we have like 3 times as many deps as 1.0 did and we
> > should probably start tightening the belt.
> >
> > To serve static things like images, we had a "default" HttpBean which
> > searched for the items in the classpath and wrote them into the
> > response setting the mime type, etc. correctly. One thing that we
> > never did which still needs to happen is that the bean didn't have
> > the logic to set the modification information into the response so
> > the "If modified since" header which would allow the browser to rely
> > on it's cache instead of requesting the same images over and over again.
> >
> > That pretty much covers the way it was put together.
> >
> > As for the individual pages, I have to give a shout out to the people
> > who worked on them.
> >
> > - The Jndi Viewer, Class Viewer, Ejb Viewer, and Object Invoker
> > were written by yours truly
> > - The EJB Generator was written by Jeremy Whitlock
> > - Everything else was written by Tim Urberg. Tim was "WebAdmin
> > guy" for a good long while. Before Tim came along the webadmin was
> > just some experimental code I had in a branch, he did more than he
> > realizes by putting his energy into it -- active people attract/
> > create more active people. Maybe we can convince him to come back
> > and work on it ;)
> >
> > And of course I have to mention our own Paulo Lopes who wrote a
> > really cool project out in SF.net (http://beangen.sourceforge.net/)
> > which was the first plugin for the OpenEJB Webadmin. He wrote it
> > before we even had shipped a release containing the Webadmin or had
> > any docs at all on it, which in my mind shows just how neat the idea
> > of using ejb's and simple conventions to do the console really is.
> >
> > Some notes going forward is that we have a truck load of meta-data
> > now available via SystemInstance.get().get
> > (OpenEjbConfiguration.class). Certainly JSR-77 is one option, but we
> > could do far better with plain old java code. That tree is the
> > primary source of meta-data for OpenEJB, it's what was used to
> > construct every container, bean, resource adapter, database connector
> > and *everything* in the system (well, sans the protocols). Someone
> > new to the project can look at it and understand it without having to
> > read any abstract specs. Something to consider. The tree is read
> > only in it's function, however it is possible to copy then edit and
> > make new containers, etc. based on existing definitions.
> >
> > Additionally, using this same data structure it's possible to show
> > the potential services available via the service-jar.xml files in the
> > classpath that detail containers, resource adapters, database
> > connectors, etc. which can be configured/created at runtime. So we
> > could also display a sort of catalogue of components (aka. services)
> > that someone could click and deploy via the console.
> >
> > I wrote a big long email about the service-jar.xml some time ago. I
> > think Karan knows which one I'm referring to as he had mentioned a
> > couple times he'd like to add it to the website -- assuming my memory
> > hasn't gone bad :)
> >
> > -David
> >
> >
> >
> >
> >
>
>
> --
> Karan Malhi
>
Re: WebAdmin (was Re: openejb- ease of use, snapshot and maven)
Posted by Manu George <ma...@gmail.com>.
ok found it it is there in svn.
On 6/21/07, Manu George <ma...@gmail.com> wrote:
> Where do i download the source from? Is it there in svn? Currently i
> can find it in http://cwiki.apache.org/OPENEJB/download.html. Is that
> the latest
>
> Regards
> Manu
>
> On 6/21/07, Karan Malhi <ka...@gmail.com> wrote:
> > Here is the link which talks about service-jar.xml and xbean. Still
> > havent been able to get it to the website. :(
> >
> > http://www.nabble.com/How-is-XBean-used-in-OpenEJB-3--tf2148639.html#a5959172
> >
> > On 6/20/07, David Blevins <da...@visi.com> wrote:
> > >
> > > On Jun 20, 2007, at 12:30 PM, Manu George wrote:
> > >
> > > > I will download 1.0 and have a go at porting this, looks pretty cool
> > > > and we definitely should have it in 3.0 :).
> > >
> > > Cool. Here is some info to arm you in how it worked. Knowledge
> > > transfer commencing in 3.. 2.. 1....
> > >
> > > Plain old stateless beans were used as the "servlets". To make a
> > > bean that would show up in the Webadmin Console you simply had to
> > > implement the HttpBean interface (i think it's now called
> > > HttpListener) and give your bean a deploymentId following this format
> > > "webadmin/{section}/{page}". Anyone could add to the Webadmin
> > > console by doing both of these things, which is really cool as people
> > > developing EJB apps can also deploy beans for administering those
> > > apps right in the exact same jar. This is not only easy for
> > > packaging but means new sections can be added/removed on the fly.
> > >
> > > Using the described "webadmin/{section}/{page}" deploymentId format,
> > > things end up automagically grouped in the JNDI tree. There's a
> > > 'webadmin' context we grab which will contain any number of "section"
> > > contexts ("ClientTools", "EJBGenerator", etc.). Each of those
> > > section subcontexts will contain several beans which we will use to
> > > make the pages. Making the menu is pretty easy as we just iterate
> > > over the webadmin section of the global jndi tree.
> > >
> > > When an http request came in we just took the path part of the GET or
> > > POST request, prepended "webadmin/" and then went looking for a bean
> > > with that deployment id and invoked it via it's HttpBean (now called
> > > HttpListener) interface passing in a HttpRequest and HttpResponse
> > > objects which are trimmed down versions of similar servlet classes.
> > > There'll be some changes to this as now we support our plain ejb
> > > protocol over our http implementation, so the two will have to find a
> > > way to share the URL space. See the openejb-http module.
> > >
> > > To implement session state, we had a stateful session bean
> > > implementing an HttpSession interface (again, similar to the servlet
> > > equivalent) and simply wrote the internal ID of the bean instance
> > > into a Cookie sent to the browser. For some reason we would write
> > > the javax.ejb.Handle of the stateful bean's EJBObject to disk and
> > > read it back out on subsequent requests then used it to get a
> > > reference to the EJBObject again. I'm not sure why we didn't just
> > > keep a static hashmap and put the EJBObject right in it using an ID
> > > we could just make up like UUID (that would have been way simpler).
> > >
> > > We had a standard superclass we favored for beans that implemented
> > > the HttpBean (HttpListener) interface that did templating and the
> > > aforementioned menu construction. The templating was perhaps too
> > > tricky as we used a non-printable character to determine where to
> > > insert data. Now we could just use swizzle-stream for some pretty
> > > decent templating ability or even velocity. I'd be hesitant to
> > > endorse velocity as we already have a dep on swizzle-stream and
> > > wouldn't want to see us add another meg to our distro size if we can
> > > avoid it -- we have like 3 times as many deps as 1.0 did and we
> > > should probably start tightening the belt.
> > >
> > > To serve static things like images, we had a "default" HttpBean which
> > > searched for the items in the classpath and wrote them into the
> > > response setting the mime type, etc. correctly. One thing that we
> > > never did which still needs to happen is that the bean didn't have
> > > the logic to set the modification information into the response so
> > > the "If modified since" header which would allow the browser to rely
> > > on it's cache instead of requesting the same images over and over again.
> > >
> > > That pretty much covers the way it was put together.
> > >
> > > As for the individual pages, I have to give a shout out to the people
> > > who worked on them.
> > >
> > > - The Jndi Viewer, Class Viewer, Ejb Viewer, and Object Invoker
> > > were written by yours truly
> > > - The EJB Generator was written by Jeremy Whitlock
> > > - Everything else was written by Tim Urberg. Tim was "WebAdmin
> > > guy" for a good long while. Before Tim came along the webadmin was
> > > just some experimental code I had in a branch, he did more than he
> > > realizes by putting his energy into it -- active people attract/
> > > create more active people. Maybe we can convince him to come back
> > > and work on it ;)
> > >
> > > And of course I have to mention our own Paulo Lopes who wrote a
> > > really cool project out in SF.net (http://beangen.sourceforge.net/)
> > > which was the first plugin for the OpenEJB Webadmin. He wrote it
> > > before we even had shipped a release containing the Webadmin or had
> > > any docs at all on it, which in my mind shows just how neat the idea
> > > of using ejb's and simple conventions to do the console really is.
> > >
> > > Some notes going forward is that we have a truck load of meta-data
> > > now available via SystemInstance.get().get
> > > (OpenEjbConfiguration.class). Certainly JSR-77 is one option, but we
> > > could do far better with plain old java code. That tree is the
> > > primary source of meta-data for OpenEJB, it's what was used to
> > > construct every container, bean, resource adapter, database connector
> > > and *everything* in the system (well, sans the protocols). Someone
> > > new to the project can look at it and understand it without having to
> > > read any abstract specs. Something to consider. The tree is read
> > > only in it's function, however it is possible to copy then edit and
> > > make new containers, etc. based on existing definitions.
> > >
> > > Additionally, using this same data structure it's possible to show
> > > the potential services available via the service-jar.xml files in the
> > > classpath that detail containers, resource adapters, database
> > > connectors, etc. which can be configured/created at runtime. So we
> > > could also display a sort of catalogue of components (aka. services)
> > > that someone could click and deploy via the console.
> > >
> > > I wrote a big long email about the service-jar.xml some time ago. I
> > > think Karan knows which one I'm referring to as he had mentioned a
> > > couple times he'd like to add it to the website -- assuming my memory
> > > hasn't gone bad :)
> > >
> > > -David
> > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> > Karan Malhi
> >
>
Re: WebAdmin (was Re: openejb- ease of use, snapshot and maven)
Posted by Manu George <ma...@gmail.com>.
Where do i download the source from? Is it there in svn? Currently i
can find it in http://cwiki.apache.org/OPENEJB/download.html. Is that
the latest
Regards
Manu
On 6/21/07, Karan Malhi <ka...@gmail.com> wrote:
> Here is the link which talks about service-jar.xml and xbean. Still
> havent been able to get it to the website. :(
>
> http://www.nabble.com/How-is-XBean-used-in-OpenEJB-3--tf2148639.html#a5959172
>
> On 6/20/07, David Blevins <da...@visi.com> wrote:
> >
> > On Jun 20, 2007, at 12:30 PM, Manu George wrote:
> >
> > > I will download 1.0 and have a go at porting this, looks pretty cool
> > > and we definitely should have it in 3.0 :).
> >
> > Cool. Here is some info to arm you in how it worked. Knowledge
> > transfer commencing in 3.. 2.. 1....
> >
> > Plain old stateless beans were used as the "servlets". To make a
> > bean that would show up in the Webadmin Console you simply had to
> > implement the HttpBean interface (i think it's now called
> > HttpListener) and give your bean a deploymentId following this format
> > "webadmin/{section}/{page}". Anyone could add to the Webadmin
> > console by doing both of these things, which is really cool as people
> > developing EJB apps can also deploy beans for administering those
> > apps right in the exact same jar. This is not only easy for
> > packaging but means new sections can be added/removed on the fly.
> >
> > Using the described "webadmin/{section}/{page}" deploymentId format,
> > things end up automagically grouped in the JNDI tree. There's a
> > 'webadmin' context we grab which will contain any number of "section"
> > contexts ("ClientTools", "EJBGenerator", etc.). Each of those
> > section subcontexts will contain several beans which we will use to
> > make the pages. Making the menu is pretty easy as we just iterate
> > over the webadmin section of the global jndi tree.
> >
> > When an http request came in we just took the path part of the GET or
> > POST request, prepended "webadmin/" and then went looking for a bean
> > with that deployment id and invoked it via it's HttpBean (now called
> > HttpListener) interface passing in a HttpRequest and HttpResponse
> > objects which are trimmed down versions of similar servlet classes.
> > There'll be some changes to this as now we support our plain ejb
> > protocol over our http implementation, so the two will have to find a
> > way to share the URL space. See the openejb-http module.
> >
> > To implement session state, we had a stateful session bean
> > implementing an HttpSession interface (again, similar to the servlet
> > equivalent) and simply wrote the internal ID of the bean instance
> > into a Cookie sent to the browser. For some reason we would write
> > the javax.ejb.Handle of the stateful bean's EJBObject to disk and
> > read it back out on subsequent requests then used it to get a
> > reference to the EJBObject again. I'm not sure why we didn't just
> > keep a static hashmap and put the EJBObject right in it using an ID
> > we could just make up like UUID (that would have been way simpler).
> >
> > We had a standard superclass we favored for beans that implemented
> > the HttpBean (HttpListener) interface that did templating and the
> > aforementioned menu construction. The templating was perhaps too
> > tricky as we used a non-printable character to determine where to
> > insert data. Now we could just use swizzle-stream for some pretty
> > decent templating ability or even velocity. I'd be hesitant to
> > endorse velocity as we already have a dep on swizzle-stream and
> > wouldn't want to see us add another meg to our distro size if we can
> > avoid it -- we have like 3 times as many deps as 1.0 did and we
> > should probably start tightening the belt.
> >
> > To serve static things like images, we had a "default" HttpBean which
> > searched for the items in the classpath and wrote them into the
> > response setting the mime type, etc. correctly. One thing that we
> > never did which still needs to happen is that the bean didn't have
> > the logic to set the modification information into the response so
> > the "If modified since" header which would allow the browser to rely
> > on it's cache instead of requesting the same images over and over again.
> >
> > That pretty much covers the way it was put together.
> >
> > As for the individual pages, I have to give a shout out to the people
> > who worked on them.
> >
> > - The Jndi Viewer, Class Viewer, Ejb Viewer, and Object Invoker
> > were written by yours truly
> > - The EJB Generator was written by Jeremy Whitlock
> > - Everything else was written by Tim Urberg. Tim was "WebAdmin
> > guy" for a good long while. Before Tim came along the webadmin was
> > just some experimental code I had in a branch, he did more than he
> > realizes by putting his energy into it -- active people attract/
> > create more active people. Maybe we can convince him to come back
> > and work on it ;)
> >
> > And of course I have to mention our own Paulo Lopes who wrote a
> > really cool project out in SF.net (http://beangen.sourceforge.net/)
> > which was the first plugin for the OpenEJB Webadmin. He wrote it
> > before we even had shipped a release containing the Webadmin or had
> > any docs at all on it, which in my mind shows just how neat the idea
> > of using ejb's and simple conventions to do the console really is.
> >
> > Some notes going forward is that we have a truck load of meta-data
> > now available via SystemInstance.get().get
> > (OpenEjbConfiguration.class). Certainly JSR-77 is one option, but we
> > could do far better with plain old java code. That tree is the
> > primary source of meta-data for OpenEJB, it's what was used to
> > construct every container, bean, resource adapter, database connector
> > and *everything* in the system (well, sans the protocols). Someone
> > new to the project can look at it and understand it without having to
> > read any abstract specs. Something to consider. The tree is read
> > only in it's function, however it is possible to copy then edit and
> > make new containers, etc. based on existing definitions.
> >
> > Additionally, using this same data structure it's possible to show
> > the potential services available via the service-jar.xml files in the
> > classpath that detail containers, resource adapters, database
> > connectors, etc. which can be configured/created at runtime. So we
> > could also display a sort of catalogue of components (aka. services)
> > that someone could click and deploy via the console.
> >
> > I wrote a big long email about the service-jar.xml some time ago. I
> > think Karan knows which one I'm referring to as he had mentioned a
> > couple times he'd like to add it to the website -- assuming my memory
> > hasn't gone bad :)
> >
> > -David
> >
> >
> >
> >
> >
>
>
> --
> Karan Malhi
>
Re: WebAdmin (was Re: openejb- ease of use, snapshot and maven)
Posted by Karan Malhi <ka...@gmail.com>.
Here is the link which talks about service-jar.xml and xbean. Still
havent been able to get it to the website. :(
http://www.nabble.com/How-is-XBean-used-in-OpenEJB-3--tf2148639.html#a5959172
On 6/20/07, David Blevins <da...@visi.com> wrote:
>
> On Jun 20, 2007, at 12:30 PM, Manu George wrote:
>
> > I will download 1.0 and have a go at porting this, looks pretty cool
> > and we definitely should have it in 3.0 :).
>
> Cool. Here is some info to arm you in how it worked. Knowledge
> transfer commencing in 3.. 2.. 1....
>
> Plain old stateless beans were used as the "servlets". To make a
> bean that would show up in the Webadmin Console you simply had to
> implement the HttpBean interface (i think it's now called
> HttpListener) and give your bean a deploymentId following this format
> "webadmin/{section}/{page}". Anyone could add to the Webadmin
> console by doing both of these things, which is really cool as people
> developing EJB apps can also deploy beans for administering those
> apps right in the exact same jar. This is not only easy for
> packaging but means new sections can be added/removed on the fly.
>
> Using the described "webadmin/{section}/{page}" deploymentId format,
> things end up automagically grouped in the JNDI tree. There's a
> 'webadmin' context we grab which will contain any number of "section"
> contexts ("ClientTools", "EJBGenerator", etc.). Each of those
> section subcontexts will contain several beans which we will use to
> make the pages. Making the menu is pretty easy as we just iterate
> over the webadmin section of the global jndi tree.
>
> When an http request came in we just took the path part of the GET or
> POST request, prepended "webadmin/" and then went looking for a bean
> with that deployment id and invoked it via it's HttpBean (now called
> HttpListener) interface passing in a HttpRequest and HttpResponse
> objects which are trimmed down versions of similar servlet classes.
> There'll be some changes to this as now we support our plain ejb
> protocol over our http implementation, so the two will have to find a
> way to share the URL space. See the openejb-http module.
>
> To implement session state, we had a stateful session bean
> implementing an HttpSession interface (again, similar to the servlet
> equivalent) and simply wrote the internal ID of the bean instance
> into a Cookie sent to the browser. For some reason we would write
> the javax.ejb.Handle of the stateful bean's EJBObject to disk and
> read it back out on subsequent requests then used it to get a
> reference to the EJBObject again. I'm not sure why we didn't just
> keep a static hashmap and put the EJBObject right in it using an ID
> we could just make up like UUID (that would have been way simpler).
>
> We had a standard superclass we favored for beans that implemented
> the HttpBean (HttpListener) interface that did templating and the
> aforementioned menu construction. The templating was perhaps too
> tricky as we used a non-printable character to determine where to
> insert data. Now we could just use swizzle-stream for some pretty
> decent templating ability or even velocity. I'd be hesitant to
> endorse velocity as we already have a dep on swizzle-stream and
> wouldn't want to see us add another meg to our distro size if we can
> avoid it -- we have like 3 times as many deps as 1.0 did and we
> should probably start tightening the belt.
>
> To serve static things like images, we had a "default" HttpBean which
> searched for the items in the classpath and wrote them into the
> response setting the mime type, etc. correctly. One thing that we
> never did which still needs to happen is that the bean didn't have
> the logic to set the modification information into the response so
> the "If modified since" header which would allow the browser to rely
> on it's cache instead of requesting the same images over and over again.
>
> That pretty much covers the way it was put together.
>
> As for the individual pages, I have to give a shout out to the people
> who worked on them.
>
> - The Jndi Viewer, Class Viewer, Ejb Viewer, and Object Invoker
> were written by yours truly
> - The EJB Generator was written by Jeremy Whitlock
> - Everything else was written by Tim Urberg. Tim was "WebAdmin
> guy" for a good long while. Before Tim came along the webadmin was
> just some experimental code I had in a branch, he did more than he
> realizes by putting his energy into it -- active people attract/
> create more active people. Maybe we can convince him to come back
> and work on it ;)
>
> And of course I have to mention our own Paulo Lopes who wrote a
> really cool project out in SF.net (http://beangen.sourceforge.net/)
> which was the first plugin for the OpenEJB Webadmin. He wrote it
> before we even had shipped a release containing the Webadmin or had
> any docs at all on it, which in my mind shows just how neat the idea
> of using ejb's and simple conventions to do the console really is.
>
> Some notes going forward is that we have a truck load of meta-data
> now available via SystemInstance.get().get
> (OpenEjbConfiguration.class). Certainly JSR-77 is one option, but we
> could do far better with plain old java code. That tree is the
> primary source of meta-data for OpenEJB, it's what was used to
> construct every container, bean, resource adapter, database connector
> and *everything* in the system (well, sans the protocols). Someone
> new to the project can look at it and understand it without having to
> read any abstract specs. Something to consider. The tree is read
> only in it's function, however it is possible to copy then edit and
> make new containers, etc. based on existing definitions.
>
> Additionally, using this same data structure it's possible to show
> the potential services available via the service-jar.xml files in the
> classpath that detail containers, resource adapters, database
> connectors, etc. which can be configured/created at runtime. So we
> could also display a sort of catalogue of components (aka. services)
> that someone could click and deploy via the console.
>
> I wrote a big long email about the service-jar.xml some time ago. I
> think Karan knows which one I'm referring to as he had mentioned a
> couple times he'd like to add it to the website -- assuming my memory
> hasn't gone bad :)
>
> -David
>
>
>
>
>
--
Karan Malhi
WebAdmin (was Re: openejb- ease of use, snapshot and maven)
Posted by David Blevins <da...@visi.com>.
On Jun 20, 2007, at 12:30 PM, Manu George wrote:
> I will download 1.0 and have a go at porting this, looks pretty cool
> and we definitely should have it in 3.0 :).
Cool. Here is some info to arm you in how it worked. Knowledge
transfer commencing in 3.. 2.. 1....
Plain old stateless beans were used as the "servlets". To make a
bean that would show up in the Webadmin Console you simply had to
implement the HttpBean interface (i think it's now called
HttpListener) and give your bean a deploymentId following this format
"webadmin/{section}/{page}". Anyone could add to the Webadmin
console by doing both of these things, which is really cool as people
developing EJB apps can also deploy beans for administering those
apps right in the exact same jar. This is not only easy for
packaging but means new sections can be added/removed on the fly.
Using the described "webadmin/{section}/{page}" deploymentId format,
things end up automagically grouped in the JNDI tree. There's a
'webadmin' context we grab which will contain any number of "section"
contexts ("ClientTools", "EJBGenerator", etc.). Each of those
section subcontexts will contain several beans which we will use to
make the pages. Making the menu is pretty easy as we just iterate
over the webadmin section of the global jndi tree.
When an http request came in we just took the path part of the GET or
POST request, prepended "webadmin/" and then went looking for a bean
with that deployment id and invoked it via it's HttpBean (now called
HttpListener) interface passing in a HttpRequest and HttpResponse
objects which are trimmed down versions of similar servlet classes.
There'll be some changes to this as now we support our plain ejb
protocol over our http implementation, so the two will have to find a
way to share the URL space. See the openejb-http module.
To implement session state, we had a stateful session bean
implementing an HttpSession interface (again, similar to the servlet
equivalent) and simply wrote the internal ID of the bean instance
into a Cookie sent to the browser. For some reason we would write
the javax.ejb.Handle of the stateful bean's EJBObject to disk and
read it back out on subsequent requests then used it to get a
reference to the EJBObject again. I'm not sure why we didn't just
keep a static hashmap and put the EJBObject right in it using an ID
we could just make up like UUID (that would have been way simpler).
We had a standard superclass we favored for beans that implemented
the HttpBean (HttpListener) interface that did templating and the
aforementioned menu construction. The templating was perhaps too
tricky as we used a non-printable character to determine where to
insert data. Now we could just use swizzle-stream for some pretty
decent templating ability or even velocity. I'd be hesitant to
endorse velocity as we already have a dep on swizzle-stream and
wouldn't want to see us add another meg to our distro size if we can
avoid it -- we have like 3 times as many deps as 1.0 did and we
should probably start tightening the belt.
To serve static things like images, we had a "default" HttpBean which
searched for the items in the classpath and wrote them into the
response setting the mime type, etc. correctly. One thing that we
never did which still needs to happen is that the bean didn't have
the logic to set the modification information into the response so
the "If modified since" header which would allow the browser to rely
on it's cache instead of requesting the same images over and over again.
That pretty much covers the way it was put together.
As for the individual pages, I have to give a shout out to the people
who worked on them.
- The Jndi Viewer, Class Viewer, Ejb Viewer, and Object Invoker
were written by yours truly
- The EJB Generator was written by Jeremy Whitlock
- Everything else was written by Tim Urberg. Tim was "WebAdmin
guy" for a good long while. Before Tim came along the webadmin was
just some experimental code I had in a branch, he did more than he
realizes by putting his energy into it -- active people attract/
create more active people. Maybe we can convince him to come back
and work on it ;)
And of course I have to mention our own Paulo Lopes who wrote a
really cool project out in SF.net (http://beangen.sourceforge.net/)
which was the first plugin for the OpenEJB Webadmin. He wrote it
before we even had shipped a release containing the Webadmin or had
any docs at all on it, which in my mind shows just how neat the idea
of using ejb's and simple conventions to do the console really is.
Some notes going forward is that we have a truck load of meta-data
now available via SystemInstance.get().get
(OpenEjbConfiguration.class). Certainly JSR-77 is one option, but we
could do far better with plain old java code. That tree is the
primary source of meta-data for OpenEJB, it's what was used to
construct every container, bean, resource adapter, database connector
and *everything* in the system (well, sans the protocols). Someone
new to the project can look at it and understand it without having to
read any abstract specs. Something to consider. The tree is read
only in it's function, however it is possible to copy then edit and
make new containers, etc. based on existing definitions.
Additionally, using this same data structure it's possible to show
the potential services available via the service-jar.xml files in the
classpath that detail containers, resource adapters, database
connectors, etc. which can be configured/created at runtime. So we
could also display a sort of catalogue of components (aka. services)
that someone could click and deploy via the console.
I wrote a big long email about the service-jar.xml some time ago. I
think Karan knows which one I'm referring to as he had mentioned a
couple times he'd like to add it to the website -- assuming my memory
hasn't gone bad :)
-David
Re: openejb- ease of use, snapshot and maven
Posted by Manu George <ma...@gmail.com>.
I will download 1.0 and have a go at porting this, looks pretty cool
and we definitely should have it in 3.0 :).
On 6/21/07, Manu George <ma...@gmail.com> wrote:
> Hi,
> The webadmin is really cool. I was not at all aware it
> existed :(. I think it is a valuable feature to have in 3.0.
>
> Regards
> Manu
>
> On 6/20/07, Karan Malhi <ka...@gmail.com> wrote:
> > Thanks David,
> >
> > Will start adding stuff to the wiki pages. I saw the webadmin
> > screenshots. Its really cool.
> >
> > On 6/19/07, David Blevins <da...@visi.com> wrote:
> > >
> > > On Jun 18, 2007, at 4:24 PM, Karan Malhi wrote:
> > >
> > > > Thanks Mohammed,
> > > >
> > > > I have been able to finally fix the issue (and understand quite a bit
> > > > of maven in the process :) ). The whole thing was a combination of a
> > > > broken plugin and my lack of understanding of lifecycle phases and how
> > > > it applies differently to packaging types like war, jar and pom.
> > > > Finally with the help of the resources-plugin, I have been able to fix
> > > > the build issue.
> > >
> > > That's an impressive amount of debugging. It's no small task chasing
> > > down plugin issues with little maven experience.
> > >
> > > > Currently I couldnt find much on eclipse on the openejb website. If
> > > > Dario has already started to document this, then I would wait for him
> > > > to post. Meanwhile, I am going to use this snapshot build to create
> > > > some examples of creating EJB's with openejb.
> > >
> > > Don't wait! Two people working in isolation from each other on the
> > > same thing is bad, yes, but two people working together on the same
> > > thing is magic.... I just think back when Mohammad and Manu were
> > > both hacking on the itests together, did wonders for encouraging
> > > others to jump -- not to mention showing them how.
> > >
> > > Whatever the two of you'd like to do, I started a page here:
> > >
> > > http://cwiki.apache.org/OPENEJB/openejb-and-eclipse.html
> > >
> > > > What happened to the eclipse plugin though? Is anybody working on
> > > > that?. I have a semi-working swing based admin console. An eclipse
> > > > plugin would've been cool. Also, do you know if there is any web based
> > > > administrative console for openejb?
> > >
> > > Don't think anything is going on with the Eclipse plugin, feel
> > > encouraged to grab the yoke and start pulling. We did have a web
> > > console at one point, but it didn't survive the 1.0 -> 3.0 refactor.
> > > The code is definitely there in 1.0 if you wanted to try porting in
> > > over.
> > >
> > > Here are some docs on it: http://cwiki.apache.org/OPENEJB/webadmin.html
> > >
> > > Not fancy but it was an extremely small amount of code.
> > >
> > > -David
> > >
> > > > On 6/18/07, Mohammad Nour El-Din <no...@gmail.com> wrote:
> > > >> Hi Karan...
> > > >>
> > > >> On 6/15/07, Karan Malhi <ka...@gmail.com> wrote:
> > > >> >
> > > >> > SNAPSHOT RELEASE
> > > >> > I really want to be able to have a downloadable snapshot
> > > >> release. We
> > > >> > want to make it easy for people to download and extract a zipped
> > > >> file
> > > >> > and get started with openejb quickly. Downloading maven first, then
> > > >> > checking out the whole thing and building it and then extracting
> > > >> the
> > > >> > snapshot for usage is really not a very comfortable thought if
> > > >> > somebody had to try to use openejb. It would easily take more
> > > >> than 1.5
> > > >> > hours of somebody's time, before they can even start using
> > > >> openejb. On
> > > >> > top of that they will have to find the zip file from
> > > >> > openejb3\assembly\openejb-standalone\target directory. I dont think
> > > >> > this is very intuitive , even though it is well documented by
> > > >> Jacek on
> > > >> > the wiki.
> > > >> > Maybe we already have a link to the snapshot release, but I dont
> > > >> know
> > > >> > where to find it
> > > >>
> > > >>
> > > >> For this issue I have a nice solution Prasad follows for providing
> > > >> daily
> > > >> snapshots for Apache Gernimo. At the end of each day, I will provide
> > > >> snapshots of OpenEJB3.0.0 with the build logs, just like what
> > > >> Prasad does
> > > >> and I will send a note with that on the dev-list.
> > > >>
> > > >> SETUP DOCS
> > > >> >
> > > >> > I want to be able to add some documentation, so that if anybody
> > > >> wanted
> > > >> > to use openejb with eclipse, then they should be able to setup
> > > >> their
> > > >> > environment in a few minutes, provided they have downloaded eclipse
> > > >> > and openejb. I would also like to provide some step by step
> > > >> kind of
> > > >> > docs to write a few ejb's in eclipse, deploy and test them in
> > > >> openejb.
> > > >>
> > > >>
> > > >> Did u give sometime to search for that on the OpenEJB confluence
> > > >> http://docs.codehaus.org/display/OPENEJB/Home, I think you will
> > > >> find such
> > > >> info there. And if not I am glad to provide these info for OpenEJB
> > > >> users.
> > > >>
> > > >> THE PROBLEM
> > > >> >
> > > >> > My biggest hurdle at this point is Maven. I do not fully
> > > >> understand it
> > > >> > and cannot spend enough time on it to be able to fix the problem
> > > >> > mentioned below:
> > > >> >
> > > >> > If i run mvn -Dassemble clean install from root, filtering doesnt
> > > >> > work. however, if i simply run mvn from the openejb-standalone
> > > >> module,
> > > >> > filtering works fine. I did try to spend some time on it, but could
> > > >> > not spend too much time. One thing which i have learnt is that
> > > >> we need
> > > >> > to specify explicit versions of any plugins we are using in
> > > >> maven. In
> > > >> > future, maven is going to make it mandatory to specify explicit
> > > >> > versions, so it is going to be a good idea to adopt that strategy
> > > >> > right away.
> > > >> >
> > > >> > May I also suggest that we do not use beta versions of plugins
> > > >> if they
> > > >> > have not been properly tested. Lets stick to the stable releases
> > > >> even
> > > >> > if we lose some cool functionality provided by the beta. We atleast
> > > >> > know that it works and will continue to work (unless some bug was
> > > >> > overlooked, but chances of that happening are lesser for stable
> > > >> than
> > > >> > beta versions)
> > > >> >
> > > >> > MAVEN and OPENEJB GURUS -- If you can point me in the right
> > > >> direction
> > > >> > to fix the above issue, that would be awesome!!. Once the above
> > > >> > problem is fixed, then if somebody can provide any guidance on
> > > >> how to
> > > >> > automatically link the snapshot release on the openejb website,
> > > >> that
> > > >> > would be a big help.
> > > >>
> > > >>
> > > >> In this point I am just like you :), I think we both need help
> > > >> from Apache
> > > >> Maven2 gurus.
> > > >>
> > > >> --
> > > >> > Karan Malhi
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Thanks
> > > >> - Mohammad Nour
> > > >>
> > > >
> > > >
> > > > --
> > > > Karan Malhi
> > > >
> > >
> > >
> >
> >
> > --
> > Karan Malhi
> >
>
Re: openejb- ease of use, snapshot and maven
Posted by Manu George <ma...@gmail.com>.
Hi,
The webadmin is really cool. I was not at all aware it
existed :(. I think it is a valuable feature to have in 3.0.
Regards
Manu
On 6/20/07, Karan Malhi <ka...@gmail.com> wrote:
> Thanks David,
>
> Will start adding stuff to the wiki pages. I saw the webadmin
> screenshots. Its really cool.
>
> On 6/19/07, David Blevins <da...@visi.com> wrote:
> >
> > On Jun 18, 2007, at 4:24 PM, Karan Malhi wrote:
> >
> > > Thanks Mohammed,
> > >
> > > I have been able to finally fix the issue (and understand quite a bit
> > > of maven in the process :) ). The whole thing was a combination of a
> > > broken plugin and my lack of understanding of lifecycle phases and how
> > > it applies differently to packaging types like war, jar and pom.
> > > Finally with the help of the resources-plugin, I have been able to fix
> > > the build issue.
> >
> > That's an impressive amount of debugging. It's no small task chasing
> > down plugin issues with little maven experience.
> >
> > > Currently I couldnt find much on eclipse on the openejb website. If
> > > Dario has already started to document this, then I would wait for him
> > > to post. Meanwhile, I am going to use this snapshot build to create
> > > some examples of creating EJB's with openejb.
> >
> > Don't wait! Two people working in isolation from each other on the
> > same thing is bad, yes, but two people working together on the same
> > thing is magic.... I just think back when Mohammad and Manu were
> > both hacking on the itests together, did wonders for encouraging
> > others to jump -- not to mention showing them how.
> >
> > Whatever the two of you'd like to do, I started a page here:
> >
> > http://cwiki.apache.org/OPENEJB/openejb-and-eclipse.html
> >
> > > What happened to the eclipse plugin though? Is anybody working on
> > > that?. I have a semi-working swing based admin console. An eclipse
> > > plugin would've been cool. Also, do you know if there is any web based
> > > administrative console for openejb?
> >
> > Don't think anything is going on with the Eclipse plugin, feel
> > encouraged to grab the yoke and start pulling. We did have a web
> > console at one point, but it didn't survive the 1.0 -> 3.0 refactor.
> > The code is definitely there in 1.0 if you wanted to try porting in
> > over.
> >
> > Here are some docs on it: http://cwiki.apache.org/OPENEJB/webadmin.html
> >
> > Not fancy but it was an extremely small amount of code.
> >
> > -David
> >
> > > On 6/18/07, Mohammad Nour El-Din <no...@gmail.com> wrote:
> > >> Hi Karan...
> > >>
> > >> On 6/15/07, Karan Malhi <ka...@gmail.com> wrote:
> > >> >
> > >> > SNAPSHOT RELEASE
> > >> > I really want to be able to have a downloadable snapshot
> > >> release. We
> > >> > want to make it easy for people to download and extract a zipped
> > >> file
> > >> > and get started with openejb quickly. Downloading maven first, then
> > >> > checking out the whole thing and building it and then extracting
> > >> the
> > >> > snapshot for usage is really not a very comfortable thought if
> > >> > somebody had to try to use openejb. It would easily take more
> > >> than 1.5
> > >> > hours of somebody's time, before they can even start using
> > >> openejb. On
> > >> > top of that they will have to find the zip file from
> > >> > openejb3\assembly\openejb-standalone\target directory. I dont think
> > >> > this is very intuitive , even though it is well documented by
> > >> Jacek on
> > >> > the wiki.
> > >> > Maybe we already have a link to the snapshot release, but I dont
> > >> know
> > >> > where to find it
> > >>
> > >>
> > >> For this issue I have a nice solution Prasad follows for providing
> > >> daily
> > >> snapshots for Apache Gernimo. At the end of each day, I will provide
> > >> snapshots of OpenEJB3.0.0 with the build logs, just like what
> > >> Prasad does
> > >> and I will send a note with that on the dev-list.
> > >>
> > >> SETUP DOCS
> > >> >
> > >> > I want to be able to add some documentation, so that if anybody
> > >> wanted
> > >> > to use openejb with eclipse, then they should be able to setup
> > >> their
> > >> > environment in a few minutes, provided they have downloaded eclipse
> > >> > and openejb. I would also like to provide some step by step
> > >> kind of
> > >> > docs to write a few ejb's in eclipse, deploy and test them in
> > >> openejb.
> > >>
> > >>
> > >> Did u give sometime to search for that on the OpenEJB confluence
> > >> http://docs.codehaus.org/display/OPENEJB/Home, I think you will
> > >> find such
> > >> info there. And if not I am glad to provide these info for OpenEJB
> > >> users.
> > >>
> > >> THE PROBLEM
> > >> >
> > >> > My biggest hurdle at this point is Maven. I do not fully
> > >> understand it
> > >> > and cannot spend enough time on it to be able to fix the problem
> > >> > mentioned below:
> > >> >
> > >> > If i run mvn -Dassemble clean install from root, filtering doesnt
> > >> > work. however, if i simply run mvn from the openejb-standalone
> > >> module,
> > >> > filtering works fine. I did try to spend some time on it, but could
> > >> > not spend too much time. One thing which i have learnt is that
> > >> we need
> > >> > to specify explicit versions of any plugins we are using in
> > >> maven. In
> > >> > future, maven is going to make it mandatory to specify explicit
> > >> > versions, so it is going to be a good idea to adopt that strategy
> > >> > right away.
> > >> >
> > >> > May I also suggest that we do not use beta versions of plugins
> > >> if they
> > >> > have not been properly tested. Lets stick to the stable releases
> > >> even
> > >> > if we lose some cool functionality provided by the beta. We atleast
> > >> > know that it works and will continue to work (unless some bug was
> > >> > overlooked, but chances of that happening are lesser for stable
> > >> than
> > >> > beta versions)
> > >> >
> > >> > MAVEN and OPENEJB GURUS -- If you can point me in the right
> > >> direction
> > >> > to fix the above issue, that would be awesome!!. Once the above
> > >> > problem is fixed, then if somebody can provide any guidance on
> > >> how to
> > >> > automatically link the snapshot release on the openejb website,
> > >> that
> > >> > would be a big help.
> > >>
> > >>
> > >> In this point I am just like you :), I think we both need help
> > >> from Apache
> > >> Maven2 gurus.
> > >>
> > >> --
> > >> > Karan Malhi
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Thanks
> > >> - Mohammad Nour
> > >>
> > >
> > >
> > > --
> > > Karan Malhi
> > >
> >
> >
>
>
> --
> Karan Malhi
>
Re: openejb- ease of use, snapshot and maven
Posted by Karan Malhi <ka...@gmail.com>.
Thanks David,
Will start adding stuff to the wiki pages. I saw the webadmin
screenshots. Its really cool.
On 6/19/07, David Blevins <da...@visi.com> wrote:
>
> On Jun 18, 2007, at 4:24 PM, Karan Malhi wrote:
>
> > Thanks Mohammed,
> >
> > I have been able to finally fix the issue (and understand quite a bit
> > of maven in the process :) ). The whole thing was a combination of a
> > broken plugin and my lack of understanding of lifecycle phases and how
> > it applies differently to packaging types like war, jar and pom.
> > Finally with the help of the resources-plugin, I have been able to fix
> > the build issue.
>
> That's an impressive amount of debugging. It's no small task chasing
> down plugin issues with little maven experience.
>
> > Currently I couldnt find much on eclipse on the openejb website. If
> > Dario has already started to document this, then I would wait for him
> > to post. Meanwhile, I am going to use this snapshot build to create
> > some examples of creating EJB's with openejb.
>
> Don't wait! Two people working in isolation from each other on the
> same thing is bad, yes, but two people working together on the same
> thing is magic.... I just think back when Mohammad and Manu were
> both hacking on the itests together, did wonders for encouraging
> others to jump -- not to mention showing them how.
>
> Whatever the two of you'd like to do, I started a page here:
>
> http://cwiki.apache.org/OPENEJB/openejb-and-eclipse.html
>
> > What happened to the eclipse plugin though? Is anybody working on
> > that?. I have a semi-working swing based admin console. An eclipse
> > plugin would've been cool. Also, do you know if there is any web based
> > administrative console for openejb?
>
> Don't think anything is going on with the Eclipse plugin, feel
> encouraged to grab the yoke and start pulling. We did have a web
> console at one point, but it didn't survive the 1.0 -> 3.0 refactor.
> The code is definitely there in 1.0 if you wanted to try porting in
> over.
>
> Here are some docs on it: http://cwiki.apache.org/OPENEJB/webadmin.html
>
> Not fancy but it was an extremely small amount of code.
>
> -David
>
> > On 6/18/07, Mohammad Nour El-Din <no...@gmail.com> wrote:
> >> Hi Karan...
> >>
> >> On 6/15/07, Karan Malhi <ka...@gmail.com> wrote:
> >> >
> >> > SNAPSHOT RELEASE
> >> > I really want to be able to have a downloadable snapshot
> >> release. We
> >> > want to make it easy for people to download and extract a zipped
> >> file
> >> > and get started with openejb quickly. Downloading maven first, then
> >> > checking out the whole thing and building it and then extracting
> >> the
> >> > snapshot for usage is really not a very comfortable thought if
> >> > somebody had to try to use openejb. It would easily take more
> >> than 1.5
> >> > hours of somebody's time, before they can even start using
> >> openejb. On
> >> > top of that they will have to find the zip file from
> >> > openejb3\assembly\openejb-standalone\target directory. I dont think
> >> > this is very intuitive , even though it is well documented by
> >> Jacek on
> >> > the wiki.
> >> > Maybe we already have a link to the snapshot release, but I dont
> >> know
> >> > where to find it
> >>
> >>
> >> For this issue I have a nice solution Prasad follows for providing
> >> daily
> >> snapshots for Apache Gernimo. At the end of each day, I will provide
> >> snapshots of OpenEJB3.0.0 with the build logs, just like what
> >> Prasad does
> >> and I will send a note with that on the dev-list.
> >>
> >> SETUP DOCS
> >> >
> >> > I want to be able to add some documentation, so that if anybody
> >> wanted
> >> > to use openejb with eclipse, then they should be able to setup
> >> their
> >> > environment in a few minutes, provided they have downloaded eclipse
> >> > and openejb. I would also like to provide some step by step
> >> kind of
> >> > docs to write a few ejb's in eclipse, deploy and test them in
> >> openejb.
> >>
> >>
> >> Did u give sometime to search for that on the OpenEJB confluence
> >> http://docs.codehaus.org/display/OPENEJB/Home, I think you will
> >> find such
> >> info there. And if not I am glad to provide these info for OpenEJB
> >> users.
> >>
> >> THE PROBLEM
> >> >
> >> > My biggest hurdle at this point is Maven. I do not fully
> >> understand it
> >> > and cannot spend enough time on it to be able to fix the problem
> >> > mentioned below:
> >> >
> >> > If i run mvn -Dassemble clean install from root, filtering doesnt
> >> > work. however, if i simply run mvn from the openejb-standalone
> >> module,
> >> > filtering works fine. I did try to spend some time on it, but could
> >> > not spend too much time. One thing which i have learnt is that
> >> we need
> >> > to specify explicit versions of any plugins we are using in
> >> maven. In
> >> > future, maven is going to make it mandatory to specify explicit
> >> > versions, so it is going to be a good idea to adopt that strategy
> >> > right away.
> >> >
> >> > May I also suggest that we do not use beta versions of plugins
> >> if they
> >> > have not been properly tested. Lets stick to the stable releases
> >> even
> >> > if we lose some cool functionality provided by the beta. We atleast
> >> > know that it works and will continue to work (unless some bug was
> >> > overlooked, but chances of that happening are lesser for stable
> >> than
> >> > beta versions)
> >> >
> >> > MAVEN and OPENEJB GURUS -- If you can point me in the right
> >> direction
> >> > to fix the above issue, that would be awesome!!. Once the above
> >> > problem is fixed, then if somebody can provide any guidance on
> >> how to
> >> > automatically link the snapshot release on the openejb website,
> >> that
> >> > would be a big help.
> >>
> >>
> >> In this point I am just like you :), I think we both need help
> >> from Apache
> >> Maven2 gurus.
> >>
> >> --
> >> > Karan Malhi
> >> >
> >>
> >>
> >>
> >> --
> >> Thanks
> >> - Mohammad Nour
> >>
> >
> >
> > --
> > Karan Malhi
> >
>
>
--
Karan Malhi
Re: openejb- ease of use, snapshot and maven
Posted by David Blevins <da...@visi.com>.
On Jun 18, 2007, at 4:24 PM, Karan Malhi wrote:
> Thanks Mohammed,
>
> I have been able to finally fix the issue (and understand quite a bit
> of maven in the process :) ). The whole thing was a combination of a
> broken plugin and my lack of understanding of lifecycle phases and how
> it applies differently to packaging types like war, jar and pom.
> Finally with the help of the resources-plugin, I have been able to fix
> the build issue.
That's an impressive amount of debugging. It's no small task chasing
down plugin issues with little maven experience.
> Currently I couldnt find much on eclipse on the openejb website. If
> Dario has already started to document this, then I would wait for him
> to post. Meanwhile, I am going to use this snapshot build to create
> some examples of creating EJB's with openejb.
Don't wait! Two people working in isolation from each other on the
same thing is bad, yes, but two people working together on the same
thing is magic.... I just think back when Mohammad and Manu were
both hacking on the itests together, did wonders for encouraging
others to jump -- not to mention showing them how.
Whatever the two of you'd like to do, I started a page here:
http://cwiki.apache.org/OPENEJB/openejb-and-eclipse.html
> What happened to the eclipse plugin though? Is anybody working on
> that?. I have a semi-working swing based admin console. An eclipse
> plugin would've been cool. Also, do you know if there is any web based
> administrative console for openejb?
Don't think anything is going on with the Eclipse plugin, feel
encouraged to grab the yoke and start pulling. We did have a web
console at one point, but it didn't survive the 1.0 -> 3.0 refactor.
The code is definitely there in 1.0 if you wanted to try porting in
over.
Here are some docs on it: http://cwiki.apache.org/OPENEJB/webadmin.html
Not fancy but it was an extremely small amount of code.
-David
> On 6/18/07, Mohammad Nour El-Din <no...@gmail.com> wrote:
>> Hi Karan...
>>
>> On 6/15/07, Karan Malhi <ka...@gmail.com> wrote:
>> >
>> > SNAPSHOT RELEASE
>> > I really want to be able to have a downloadable snapshot
>> release. We
>> > want to make it easy for people to download and extract a zipped
>> file
>> > and get started with openejb quickly. Downloading maven first, then
>> > checking out the whole thing and building it and then extracting
>> the
>> > snapshot for usage is really not a very comfortable thought if
>> > somebody had to try to use openejb. It would easily take more
>> than 1.5
>> > hours of somebody's time, before they can even start using
>> openejb. On
>> > top of that they will have to find the zip file from
>> > openejb3\assembly\openejb-standalone\target directory. I dont think
>> > this is very intuitive , even though it is well documented by
>> Jacek on
>> > the wiki.
>> > Maybe we already have a link to the snapshot release, but I dont
>> know
>> > where to find it
>>
>>
>> For this issue I have a nice solution Prasad follows for providing
>> daily
>> snapshots for Apache Gernimo. At the end of each day, I will provide
>> snapshots of OpenEJB3.0.0 with the build logs, just like what
>> Prasad does
>> and I will send a note with that on the dev-list.
>>
>> SETUP DOCS
>> >
>> > I want to be able to add some documentation, so that if anybody
>> wanted
>> > to use openejb with eclipse, then they should be able to setup
>> their
>> > environment in a few minutes, provided they have downloaded eclipse
>> > and openejb. I would also like to provide some step by step
>> kind of
>> > docs to write a few ejb's in eclipse, deploy and test them in
>> openejb.
>>
>>
>> Did u give sometime to search for that on the OpenEJB confluence
>> http://docs.codehaus.org/display/OPENEJB/Home, I think you will
>> find such
>> info there. And if not I am glad to provide these info for OpenEJB
>> users.
>>
>> THE PROBLEM
>> >
>> > My biggest hurdle at this point is Maven. I do not fully
>> understand it
>> > and cannot spend enough time on it to be able to fix the problem
>> > mentioned below:
>> >
>> > If i run mvn -Dassemble clean install from root, filtering doesnt
>> > work. however, if i simply run mvn from the openejb-standalone
>> module,
>> > filtering works fine. I did try to spend some time on it, but could
>> > not spend too much time. One thing which i have learnt is that
>> we need
>> > to specify explicit versions of any plugins we are using in
>> maven. In
>> > future, maven is going to make it mandatory to specify explicit
>> > versions, so it is going to be a good idea to adopt that strategy
>> > right away.
>> >
>> > May I also suggest that we do not use beta versions of plugins
>> if they
>> > have not been properly tested. Lets stick to the stable releases
>> even
>> > if we lose some cool functionality provided by the beta. We atleast
>> > know that it works and will continue to work (unless some bug was
>> > overlooked, but chances of that happening are lesser for stable
>> than
>> > beta versions)
>> >
>> > MAVEN and OPENEJB GURUS -- If you can point me in the right
>> direction
>> > to fix the above issue, that would be awesome!!. Once the above
>> > problem is fixed, then if somebody can provide any guidance on
>> how to
>> > automatically link the snapshot release on the openejb website,
>> that
>> > would be a big help.
>>
>>
>> In this point I am just like you :), I think we both need help
>> from Apache
>> Maven2 gurus.
>>
>> --
>> > Karan Malhi
>> >
>>
>>
>>
>> --
>> Thanks
>> - Mohammad Nour
>>
>
>
> --
> Karan Malhi
>
Re: openejb- ease of use, snapshot and maven
Posted by Karan Malhi <ka...@gmail.com>.
Thanks Mohammed,
I have been able to finally fix the issue (and understand quite a bit
of maven in the process :) ). The whole thing was a combination of a
broken plugin and my lack of understanding of lifecycle phases and how
it applies differently to packaging types like war, jar and pom.
Finally with the help of the resources-plugin, I have been able to fix
the build issue.
I am at the airport right now with a very slow internet connection,
and really have to do some clean up of the pom's and assembly
descriptors before I can submit a usable patch. Will try and do it
tomorrow.
Regarding manually building the snapshot, wouldnt there be an easier
way to do that. I am aware of the continuum plugin but am not sure if
that could be used to automatically generate the snapshot and add a
link to the site. Now that we have the build issue fixed, we should
have the ability to do that. Is there any reason why Prasad does the
build manually?
Currently I couldnt find much on eclipse on the openejb website. If
Dario has already started to document this, then I would wait for him
to post. Meanwhile, I am going to use this snapshot build to create
some examples of creating EJB's with openejb.
What happened to the eclipse plugin though? Is anybody working on
that?. I have a semi-working swing based admin console. An eclipse
plugin would've been cool. Also, do you know if there is any web based
administrative console for openejb?
On 6/18/07, Mohammad Nour El-Din <no...@gmail.com> wrote:
> Hi Karan...
>
> On 6/15/07, Karan Malhi <ka...@gmail.com> wrote:
> >
> > SNAPSHOT RELEASE
> > I really want to be able to have a downloadable snapshot release. We
> > want to make it easy for people to download and extract a zipped file
> > and get started with openejb quickly. Downloading maven first, then
> > checking out the whole thing and building it and then extracting the
> > snapshot for usage is really not a very comfortable thought if
> > somebody had to try to use openejb. It would easily take more than 1.5
> > hours of somebody's time, before they can even start using openejb. On
> > top of that they will have to find the zip file from
> > openejb3\assembly\openejb-standalone\target directory. I dont think
> > this is very intuitive , even though it is well documented by Jacek on
> > the wiki.
> > Maybe we already have a link to the snapshot release, but I dont know
> > where to find it
>
>
> For this issue I have a nice solution Prasad follows for providing daily
> snapshots for Apache Gernimo. At the end of each day, I will provide
> snapshots of OpenEJB3.0.0 with the build logs, just like what Prasad does
> and I will send a note with that on the dev-list.
>
> SETUP DOCS
> >
> > I want to be able to add some documentation, so that if anybody wanted
> > to use openejb with eclipse, then they should be able to setup their
> > environment in a few minutes, provided they have downloaded eclipse
> > and openejb. I would also like to provide some step by step kind of
> > docs to write a few ejb's in eclipse, deploy and test them in openejb.
>
>
> Did u give sometime to search for that on the OpenEJB confluence
> http://docs.codehaus.org/display/OPENEJB/Home, I think you will find such
> info there. And if not I am glad to provide these info for OpenEJB users.
>
> THE PROBLEM
> >
> > My biggest hurdle at this point is Maven. I do not fully understand it
> > and cannot spend enough time on it to be able to fix the problem
> > mentioned below:
> >
> > If i run mvn -Dassemble clean install from root, filtering doesnt
> > work. however, if i simply run mvn from the openejb-standalone module,
> > filtering works fine. I did try to spend some time on it, but could
> > not spend too much time. One thing which i have learnt is that we need
> > to specify explicit versions of any plugins we are using in maven. In
> > future, maven is going to make it mandatory to specify explicit
> > versions, so it is going to be a good idea to adopt that strategy
> > right away.
> >
> > May I also suggest that we do not use beta versions of plugins if they
> > have not been properly tested. Lets stick to the stable releases even
> > if we lose some cool functionality provided by the beta. We atleast
> > know that it works and will continue to work (unless some bug was
> > overlooked, but chances of that happening are lesser for stable than
> > beta versions)
> >
> > MAVEN and OPENEJB GURUS -- If you can point me in the right direction
> > to fix the above issue, that would be awesome!!. Once the above
> > problem is fixed, then if somebody can provide any guidance on how to
> > automatically link the snapshot release on the openejb website, that
> > would be a big help.
>
>
> In this point I am just like you :), I think we both need help from Apache
> Maven2 gurus.
>
> --
> > Karan Malhi
> >
>
>
>
> --
> Thanks
> - Mohammad Nour
>
--
Karan Malhi
Re: openejb- ease of use, snapshot and maven
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Hi Karan...
On 6/15/07, Karan Malhi <ka...@gmail.com> wrote:
>
> SNAPSHOT RELEASE
> I really want to be able to have a downloadable snapshot release. We
> want to make it easy for people to download and extract a zipped file
> and get started with openejb quickly. Downloading maven first, then
> checking out the whole thing and building it and then extracting the
> snapshot for usage is really not a very comfortable thought if
> somebody had to try to use openejb. It would easily take more than 1.5
> hours of somebody's time, before they can even start using openejb. On
> top of that they will have to find the zip file from
> openejb3\assembly\openejb-standalone\target directory. I dont think
> this is very intuitive , even though it is well documented by Jacek on
> the wiki.
> Maybe we already have a link to the snapshot release, but I dont know
> where to find it
For this issue I have a nice solution Prasad follows for providing daily
snapshots for Apache Gernimo. At the end of each day, I will provide
snapshots of OpenEJB3.0.0 with the build logs, just like what Prasad does
and I will send a note with that on the dev-list.
SETUP DOCS
>
> I want to be able to add some documentation, so that if anybody wanted
> to use openejb with eclipse, then they should be able to setup their
> environment in a few minutes, provided they have downloaded eclipse
> and openejb. I would also like to provide some step by step kind of
> docs to write a few ejb's in eclipse, deploy and test them in openejb.
Did u give sometime to search for that on the OpenEJB confluence
http://docs.codehaus.org/display/OPENEJB/Home, I think you will find such
info there. And if not I am glad to provide these info for OpenEJB users.
THE PROBLEM
>
> My biggest hurdle at this point is Maven. I do not fully understand it
> and cannot spend enough time on it to be able to fix the problem
> mentioned below:
>
> If i run mvn -Dassemble clean install from root, filtering doesnt
> work. however, if i simply run mvn from the openejb-standalone module,
> filtering works fine. I did try to spend some time on it, but could
> not spend too much time. One thing which i have learnt is that we need
> to specify explicit versions of any plugins we are using in maven. In
> future, maven is going to make it mandatory to specify explicit
> versions, so it is going to be a good idea to adopt that strategy
> right away.
>
> May I also suggest that we do not use beta versions of plugins if they
> have not been properly tested. Lets stick to the stable releases even
> if we lose some cool functionality provided by the beta. We atleast
> know that it works and will continue to work (unless some bug was
> overlooked, but chances of that happening are lesser for stable than
> beta versions)
>
> MAVEN and OPENEJB GURUS -- If you can point me in the right direction
> to fix the above issue, that would be awesome!!. Once the above
> problem is fixed, then if somebody can provide any guidance on how to
> automatically link the snapshot release on the openejb website, that
> would be a big help.
In this point I am just like you :), I think we both need help from Apache
Maven2 gurus.
--
> Karan Malhi
>
--
Thanks
- Mohammad Nour
Re: openejb- ease of use, snapshot and maven
Posted by David Blevins <da...@visi.com>.
Dario,
Thanks for posting! Been wondering when we would see something from
you :)
You give some really great feedback and I think you're right that the
number of people who might get through build part are very slim. Our
build isn't very complicated as maven builds go, but all the standard
issues are there. We definitely need some snapshots up and I would
add we need to start shipping some releases.
This isn't as precise as i'd like to see, but there are some
snapshots available from our continuous integration system
(continuum) here:
http://vmbuild.apache.org:8080/continuum/servlet/browse?file=177/
target/openejb-3.0.0-SNAPSHOT-bin.zip
But it would be really nice to get something like this going again,
but for 3.0:
http://cwiki.apache.org/OPENEJB/latest-unstable.html
On the note if the suggestions for the website updates, definitely
feel free to make those changes. Our site is run from the wiki and
you'll be able to edit just by opening an account and logging in.
Every bit helps and it'd be very great for others in the same shoes.
On the DNS and hostname issue, do you have any stack traces or some
detailed info we could put in JIRA?
-David
On Jun 14, 2007, at 6:31 PM, Dario Laverde wrote:
> Hello all,
>
> A first (belated) post to the list here - congrats for the
> incubator graduation.
>
> And a thanks to David Blevins for some hands on help at JavaOne.
> I've been
> championing OpenEJB since pre 1.0, and have gotten back to it with
> OpenEJB 3 and
> look forward to spreading the word on using OpenEJB 3 as the
> reference for learning
> EJB 3. However...
>
> I have to second some of the issues posted here, a SNAPSHOT release
> is badly needed
> (should have been a requirement for graduating IMO).
>
> Numerous maven issues abound (corrupt repository when building both
> offline and
> online, issues with 2.0.6 vs 2.0.5...). Then there's itest
> failures when dns
> doesn't resolve correctly for the local machine (my machine used a
> numeric name that
> caused lookup failures for cmp tests). I've wasted a lot of time
> with these and
> other issues - especially manually setting Eclipse projects to
> build OpenEJB 3 in
> Eclipse as maven doesn't properly create them (doesn't expand the
> library variable).
> And then there's the Java 6 compile errors...
>
> I'd suggest changing the following instructions on the website from:
>
> $ cd openejb3
> $ mvn clean install -Dassemble
>
> or alternatively when on Unix-like systems
>
> $cd openejb3
> $ mvn -o -Dmaven.{test,itest}.skip -Dassemble clean install
>
> to simply:
>
> mvn -Dmaven.{test,itest}.skip -Dassemble clean install
>
> as it's unclear why you would want to build in offline mode
> initially or to skip
> tests only on unix-like platforms.
>
> And you should probably add somewhere on that page that if you're
> having problems,
> to clear the .m2 repository folder.
>
> I waited until after the graduation to see if perhaps some issues
> would clear up but
> I'm currently still having build issues:
>
> java/org/apache/openejb/config/AnnotationDeployer.java:[108,17]
> package javax.jws does not exist
>
> I'm working on a how-to tutorial for Eclipse+OpenEJB and would like
> to get past all
> these build issues and move on to helping out on the examples
> initiative.
>
> thanks,
> Dario Laverde
> JUG leader - NYCJava.net
>
>
>> SNAPSHOT RELEASE
>> I really want to be able to have a downloadable snapshot release. We
>> want to make it easy for people to download and extract a zipped file
>> and get started with openejb quickly. Downloading maven first, then
>> checking out the whole thing and building it and then extracting the
>> snapshot for usage is really not a very comfortable thought if
>> somebody had to try to use openejb. It would easily take more than
>> 1.5
>> hours of somebody's time, before they can even start using
>> openejb. On
>> top of that they will have to find the zip file from
>> openejb3\assembly\openejb-standalone\target directory. I dont think
>> this is very intuitive , even though it is well documented by
>> Jacek on
>> the wiki.
>> Maybe we already have a link to the snapshot release, but I dont know
>> where to find it
>>
>> SETUP DOCS
>>
>> I want to be able to add some documentation, so that if anybody
>> wanted
>> to use openejb with eclipse, then they should be able to setup their
>> environment in a few minutes, provided they have downloaded eclipse
>> and openejb. I would also like to provide some step by step kind of
>> docs to write a few ejb's in eclipse, deploy and test them in
>> openejb.
>>
>> THE PROBLEM
>>
>> My biggest hurdle at this point is Maven. I do not fully
>> understand it
>> and cannot spend enough time on it to be able to fix the problem
>> mentioned below:
>>
>> If i run mvn -Dassemble clean install from root, filtering doesnt
>> work. however, if i simply run mvn from the openejb-standalone
>> module,
>> filtering works fine. I did try to spend some time on it, but could
>> not spend too much time. One thing which i have learnt is that we
>> need
>> to specify explicit versions of any plugins we are using in maven. In
>> future, maven is going to make it mandatory to specify explicit
>> versions, so it is going to be a good idea to adopt that strategy
>> right away.
>>
>> May I also suggest that we do not use beta versions of plugins if
>> they
>> have not been properly tested. Lets stick to the stable releases even
>> if we lose some cool functionality provided by the beta. We atleast
>> know that it works and will continue to work (unless some bug was
>> overlooked, but chances of that happening are lesser for stable than
>> beta versions)
>>
>> MAVEN and OPENEJB GURUS -- If you can point me in the right
>> direction
>> to fix the above issue, that would be awesome!!. Once the above
>> problem is fixed, then if somebody can provide any guidance on how to
>> automatically link the snapshot release on the openejb website, that
>> would be a big help.
>> --
>> Karan Malhi
>>
>
>
>
Re: openejb- ease of use, snapshot and maven
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Hi Dario...
On 6/15/07, Dario Laverde <da...@nycjava.net> wrote:
>
> Hello all,
>
> A first (belated) post to the list here - congrats for the incubator
> graduation.
>
> And a thanks to David Blevins for some hands on help at JavaOne. I've been
> championing OpenEJB since pre 1.0, and have gotten back to it with OpenEJB
> 3 and
> look forward to spreading the word on using OpenEJB 3 as the reference for
> learning
> EJB 3. However...
>
> I have to second some of the issues posted here, a SNAPSHOT release is
> badly needed
> (should have been a requirement for graduating IMO).
>
> Numerous maven issues abound (corrupt repository when building both
> offline and
> online, issues with 2.0.6 vs 2.0.5...). Then there's itest failures when
> dns
> doesn't resolve correctly for the local machine (my machine used a numeric
> name that
> caused lookup failures for cmp tests). I've wasted a lot of time with
> these and
> other issues - especially manually setting Eclipse projects to build
> OpenEJB 3 in
> Eclipse as maven doesn't properly create them (doesn't expand the library
> variable).
> And then there's the Java 6 compile errors...
I always use Apache Maven2 eclipse plugin to import maven projects into
Eclipse, and it always work fine, maybe something not configured conrrectly
in your environment.
I'd suggest changing the following instructions on the website from:
>
> $ cd openejb3
> $ mvn clean install -Dassemble
>
> or alternatively when on Unix-like systems
>
> $cd openejb3
> $ mvn -o -Dmaven.{test,itest}.skip -Dassemble clean install
>
> to simply:
>
> mvn -Dmaven.{test,itest}.skip -Dassemble clean install
>
> as it's unclear why you would want to build in offline mode initially or
> to skip
> tests only on unix-like platforms.
>
> And you should probably add somewhere on that page that if you're having
> problems,
> to clear the .m2 repository folder.
>
> I waited until after the graduation to see if perhaps some issues would
> clear up but
> I'm currently still having build issues:
>
> java/org/apache/openejb/config/AnnotationDeployer.java:[108,17]
> package javax.jws does not exist
>
> I'm working on a how-to tutorial for Eclipse+OpenEJB and would like to get
> past all
> these build issues and move on to helping out on the examples initiative.
I can build a fresh copy of source code correctly, I suggest you should
start with a clean environment and see what happen.
thanks,
> Dario Laverde
> JUG leader - NYCJava.net
>
>
> > SNAPSHOT RELEASE
> > I really want to be able to have a downloadable snapshot release. We
> > want to make it easy for people to download and extract a zipped file
> > and get started with openejb quickly. Downloading maven first, then
> > checking out the whole thing and building it and then extracting the
> > snapshot for usage is really not a very comfortable thought if
> > somebody had to try to use openejb. It would easily take more than 1.5
> > hours of somebody's time, before they can even start using openejb. On
> > top of that they will have to find the zip file from
> > openejb3\assembly\openejb-standalone\target directory. I dont think
> > this is very intuitive , even though it is well documented by Jacek on
> > the wiki.
> > Maybe we already have a link to the snapshot release, but I dont know
> > where to find it
> >
> > SETUP DOCS
> >
> > I want to be able to add some documentation, so that if anybody wanted
> > to use openejb with eclipse, then they should be able to setup their
> > environment in a few minutes, provided they have downloaded eclipse
> > and openejb. I would also like to provide some step by step kind of
> > docs to write a few ejb's in eclipse, deploy and test them in openejb.
> >
> > THE PROBLEM
> >
> > My biggest hurdle at this point is Maven. I do not fully understand it
> > and cannot spend enough time on it to be able to fix the problem
> > mentioned below:
> >
> > If i run mvn -Dassemble clean install from root, filtering doesnt
> > work. however, if i simply run mvn from the openejb-standalone module,
> > filtering works fine. I did try to spend some time on it, but could
> > not spend too much time. One thing which i have learnt is that we need
> > to specify explicit versions of any plugins we are using in maven. In
> > future, maven is going to make it mandatory to specify explicit
> > versions, so it is going to be a good idea to adopt that strategy
> > right away.
> >
> > May I also suggest that we do not use beta versions of plugins if they
> > have not been properly tested. Lets stick to the stable releases even
> > if we lose some cool functionality provided by the beta. We atleast
> > know that it works and will continue to work (unless some bug was
> > overlooked, but chances of that happening are lesser for stable than
> > beta versions)
> >
> > MAVEN and OPENEJB GURUS -- If you can point me in the right direction
> > to fix the above issue, that would be awesome!!. Once the above
> > problem is fixed, then if somebody can provide any guidance on how to
> > automatically link the snapshot release on the openejb website, that
> > would be a big help.
> > --
> > Karan Malhi
> >
>
>
>
--
Thanks
- Mohammad Nour
Re: openejb- ease of use, snapshot and maven
Posted by Dario Laverde <da...@nycjava.net>.
Hello all,
A first (belated) post to the list here - congrats for the incubator graduation.
And a thanks to David Blevins for some hands on help at JavaOne. I've been
championing OpenEJB since pre 1.0, and have gotten back to it with OpenEJB 3 and
look forward to spreading the word on using OpenEJB 3 as the reference for learning
EJB 3. However...
I have to second some of the issues posted here, a SNAPSHOT release is badly needed
(should have been a requirement for graduating IMO).
Numerous maven issues abound (corrupt repository when building both offline and
online, issues with 2.0.6 vs 2.0.5...). Then there's itest failures when dns
doesn't resolve correctly for the local machine (my machine used a numeric name that
caused lookup failures for cmp tests). I've wasted a lot of time with these and
other issues - especially manually setting Eclipse projects to build OpenEJB 3 in
Eclipse as maven doesn't properly create them (doesn't expand the library variable).
And then there's the Java 6 compile errors...
I'd suggest changing the following instructions on the website from:
$ cd openejb3
$ mvn clean install -Dassemble
or alternatively when on Unix-like systems
$cd openejb3
$ mvn -o -Dmaven.{test,itest}.skip -Dassemble clean install
to simply:
mvn -Dmaven.{test,itest}.skip -Dassemble clean install
as it's unclear why you would want to build in offline mode initially or to skip
tests only on unix-like platforms.
And you should probably add somewhere on that page that if you're having problems,
to clear the .m2 repository folder.
I waited until after the graduation to see if perhaps some issues would clear up but
I'm currently still having build issues:
java/org/apache/openejb/config/AnnotationDeployer.java:[108,17]
package javax.jws does not exist
I'm working on a how-to tutorial for Eclipse+OpenEJB and would like to get past all
these build issues and move on to helping out on the examples initiative.
thanks,
Dario Laverde
JUG leader - NYCJava.net
> SNAPSHOT RELEASE
> I really want to be able to have a downloadable snapshot release. We
> want to make it easy for people to download and extract a zipped file
> and get started with openejb quickly. Downloading maven first, then
> checking out the whole thing and building it and then extracting the
> snapshot for usage is really not a very comfortable thought if
> somebody had to try to use openejb. It would easily take more than 1.5
> hours of somebody's time, before they can even start using openejb. On
> top of that they will have to find the zip file from
> openejb3\assembly\openejb-standalone\target directory. I dont think
> this is very intuitive , even though it is well documented by Jacek on
> the wiki.
> Maybe we already have a link to the snapshot release, but I dont know
> where to find it
>
> SETUP DOCS
>
> I want to be able to add some documentation, so that if anybody wanted
> to use openejb with eclipse, then they should be able to setup their
> environment in a few minutes, provided they have downloaded eclipse
> and openejb. I would also like to provide some step by step kind of
> docs to write a few ejb's in eclipse, deploy and test them in openejb.
>
> THE PROBLEM
>
> My biggest hurdle at this point is Maven. I do not fully understand it
> and cannot spend enough time on it to be able to fix the problem
> mentioned below:
>
> If i run mvn -Dassemble clean install from root, filtering doesnt
> work. however, if i simply run mvn from the openejb-standalone module,
> filtering works fine. I did try to spend some time on it, but could
> not spend too much time. One thing which i have learnt is that we need
> to specify explicit versions of any plugins we are using in maven. In
> future, maven is going to make it mandatory to specify explicit
> versions, so it is going to be a good idea to adopt that strategy
> right away.
>
> May I also suggest that we do not use beta versions of plugins if they
> have not been properly tested. Lets stick to the stable releases even
> if we lose some cool functionality provided by the beta. We atleast
> know that it works and will continue to work (unless some bug was
> overlooked, but chances of that happening are lesser for stable than
> beta versions)
>
> MAVEN and OPENEJB GURUS -- If you can point me in the right direction
> to fix the above issue, that would be awesome!!. Once the above
> problem is fixed, then if somebody can provide any guidance on how to
> automatically link the snapshot release on the openejb website, that
> would be a big help.
> --
> Karan Malhi
>