Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

[PATCH] Support for Jetty-Plus #11

Closed
GoogleCodeExporter opened this Issue Jul 7, 2015 · 16 comments

Comments

Projects
None yet
1 participant
Adding support for jetty-plus services (e.g. datasources, javamail, etc) is
quite easy and will make this tool much more complete.
In addition to the attached patch for Bootstrap.java, you'll also need to
add the following jars (from the lib/naming and lib/plus directory of the
jetty distribution) to the classpath of each jetty webapp run profile:
jetty-plus.jar
jetty-naming.jar
activation.jar
mail.jar

Original issue reported on code.google.com by paul.m.f...@gmail.com on 17 Mar 2008 at 3:33

Attachments:

You may recall that Eelco's goal for Run Jetty Run is that it be very simple, 
and 
easy to use.  I'm reluctant to add more features with out a solid understanding 
of 
their value.  Please feel free to make the case.


Original comment by James.Sy...@gmail.com on 4 May 2009 at 12:49

  • Changed state: More-Info
  • Added labels: Priority-Low, Type-Enhancement
  • Removed labels: Priority-Medium, Type-Defect
I have been using run-jetty-run for some simple applications, but for some of 
our
compicated applicatons, we use JNDI JDBC resources.

It's only possible to use these as Paul mentioned if we have the plus 
components of
Jetty bundled, too.

As of now, there is no way to use/test applications which use JNDI naming 
resources,
forcing me to package/deploy test on a separate server which is time consuming.

Original comment by dree...@gmail.com on 6 Aug 2009 at 12:36

I could really use this as well.  I'm working with client code that uses JNDI to
access the database.

Original comment by hls...@gmail.com on 12 Nov 2009 at 11:32

Revisiting this again.

We really need to be able to define JNDI resources as our applications use 
them.  Without the features of jetty-plus - run-jetty-run is basically useless.

I could fork the project internally - and apply paul's patch, but that seems 
like a hack when it's others obviously would like this feature, too.

Original comment by dree...@gmail.com on 21 Apr 2011 at 2:24

ok , I will get it in next build, give me some time (will not longer then two 
weeks) ,

I am very busy for my job now. :-|

Original comment by tonylovejava on 27 Apr 2011 at 3:02

  • Changed state: Accepted
Thank you very much, Tony! :-)

Original comment by dree...@gmail.com on 27 Apr 2011 at 5:03

Original comment by tonylovejava on 2 May 2011 at 1:56

  • Added labels: 1.2.1.2
Ready since 2011/4/5 , committed in r123 , 
will get it in next build , after I got the LaunchShortcut ready.
(Next build is scheduling on this weekend.)


I am not familiar with JNDI, and I just merged the patch Paul provide .

It's a experimental feature , 
please feel free to report bugs you found,I will try to fix it soon.



Original comment by tonylovejava on 4 May 2011 at 3:24

  • Changed state: Fixed

Original comment by tonylovejava on 4 May 2011 at 3:27

  • Added labels: 1.2.1.1
  • Removed labels: 1.2.1.2
I have done all the features for 1.2.2 just now, 
(it's more difficult then my image , so it taking more time.)

and am going to publish it in few days.


Since I change some core API for it, so I need to test it carefully ,
will get it ready in this week. 

This's a simple update to let you guys know the progressing.

Original comment by tonylovejava on 16 May 2011 at 5:33

It works for me with WEB-INF/jetty-env.xml containing jndi configuration.

Original comment by tiendung.tran on 19 May 2011 at 12:47

The newer package is out for few days , 
if you got any error or have any feedback ,
please let me know , thanks. ;)

Original comment by tonylovejava on 24 May 2011 at 11:30

Just updated to the new plugin version - works great for my JNDI database 
connection.

Thanks for the work - it was just in time.

Original comment by grobme...@gmail.com on 25 May 2011 at 10:12

Thanks , It's good to hear that. ;)

Original comment by tonylovejava on 25 May 2011 at 12:43

I'm still looking for #9 to be resolved so I don't have to add a jetty-env.xml 
to my webapp to define JNDI datasources, but this does get me half-way there 
for now.

Original comment by dree...@gmail.com on 21 Jul 2011 at 1:06

Ok , I will try to take Issue 9 into 1.3.1.

Original comment by tonylovejava on 21 Jul 2011 at 4:32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment