Re: Jetty Security Handler

Hi Amit,

You can provide basic yes/no authentication by registering your
servlets/resources with a custom HttpContext and implementing
HttpContext.handleSecurity().
This has been used to support BASIC authentication with UserAdmin although
I'm not aware of an open source implementation.

If you're doing something a bit more sophisticated where you need to
decouple your HttpContext from your authentication then you might want to
write a Servlet Filter. Unfortunately the OSGi Http Service does not
currently provide Filter support however you can wrap your Servlets and
Resources fairly easily. See FilterServletAdaptor in "cvsroot/eclipse"
"equinox-incubator/org.eclipse.equinox.http.helper"

-Simon

equinox-dev-bounces@... wrote on 12/30/2007 06:56:55 AM:

> Hello Equinox Developers,
>
> I am using Jetty osgi bundle v5_1_11, but now I find myself  needing
> to add a security handler  to support basic http and looking at the
> properties exposed in the OSGI/metatype/config.xml, I don't see that
> it has been exposed (I couldn't find it in the code -Let me know if I
> missed something). Has anyone worked on providing such a
> functionality in the  OSGi context? What would you recommend?
>
> Best,
> Amit

Re: Jetty Security Handler

Thanks Simon,
I ended up writing a custom HttpContext that does the basic  
authentication.

Best,
Amit
On Jan 2, 2008, at 9:55 AM, Simon Kaegi wrote:

> Hi Amit,
>
> You can provide basic yes/no authentication by registering your
> servlets/resources with a custom HttpContext and implementing
> HttpContext.handleSecurity().
> This has been used to support BASIC authentication with UserAdmin  
> although
> I'm not aware of an open source implementation.
>
> If you're doing something a bit more sophisticated where you need to
> decouple your HttpContext from your authentication then you might  
> want to
> write a Servlet Filter. Unfortunately the OSGi Http Service does not
> currently provide Filter support however you can wrap your Servlets  
> and
> Resources fairly easily. See FilterServletAdaptor in "cvsroot/eclipse"
> "equinox-incubator/org.eclipse.equinox.http.helper"
>
> -Simon
>
> equinox-dev-bounces@... wrote on 12/30/2007 06:56:55 AM:
>

Re: AOSGi is not recognized after installing features

First of all, Happy New Year to all!!!

And Hi Oren!

The new year starts good: I found our problem and fixed it. 

The reason was a wrong folder layout of the feature within the zip 
download. A new fixed version is ready for download:

http://www.eclipse.org/equinox/incubator/aspects/downloads/org.aspectj.osgi_1.0.3a_archive.zip

Sorry again for the long delay. Promise to be more responsive from now on...

Cheers,
-Martin

Oren Mishali wrote:
 > Hi Martin,
 >
 > Have you tried to reproduce the bug? It is quite a limitation since I 
cannot
 > install additional plug-ins...
 >
 > Oren
 >
 > -----Original Message-----
 > From: equinox-dev-bounces@...
 > [mailto:equinox-dev-bounces@...] On Behalf Of Martin Lippert
 > Sent: Wednesday, October 24, 2007 10:11 AM
 > To: Equinox development mailing list

Copyright comments

Re: Copyright comments

Re: Copyright comments

Jetty and commons logging

I just had a terrible time getting a simple web app integration to work
because of a version mismatch between bundles. I assume that the folks here
have something to do with the bundles I was trying to use
(http://repo1.maven.org/eclipse), but please correct me if I am wrong. 

The issue is to do with the fact that the jetty plugin, in maven notation
org.mortbay:jetty, has a dependence on commons logging, in OSGi notation
org.apache.commons.logging;version=[1.0.0,2.0.0). But the only commons
logging bundles I could find do not specify a version (hence the default
version 0.0.0 does not match).

Looks like it should be a common problem? I had to hack the jetty plugin to
remove the version range.  Is there a better solution?  Can someone deploy a
new build of the jetty plugin without the restriction? (The opposite
solution, to change commons-logging, doesn't appeal because I'd far rather
use the jcl104-over-sl4j version, which also doesn't specify a version.)
--

-- 
View this message in context: http://www.nabble.com/Jetty-and-commons-logging-tp14625344p14625344.html
Sent from the Equinox - Dev mailing list archive at Nabble.com.

Re: Jetty and commons logging

Re: Jetty and commons logging

On Saturday 05 January 2008 05:28, Dave Syer wrote:

> The issue is to do with the fact that the jetty plugin, in maven notation
> org.mortbay:jetty, has a dependence on commons logging, in OSGi notation
> org.apache.commons.logging;version=[1.0.0,2.0.0). But the only commons
> logging bundles I could find do not specify a version (hence the default
> version 0.0.0 does not match).

If you use Pax Logging from OPS4J, it probably solves your problem. Pax Logger 
is explicitly created to handle legacy logging APIs and route those into a 
shared Log Service implementation backed by Log4J.

More info at http://www.ops4j.org/projects/pax/logging/

Cheers
--

-- 
Niclas Hedhman, Software Developer

I  live here; http://tinyurl.com/2qq9er
I  work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug

Re: Jetty and commons logging

Jeff McAffer wrote:
> 
> Try and get the stuff from Eclipse rather than Maven.
> 

Oops, my apologies.  Where is the Maven repo at Eclipse then?  That one at
repo1.maven.org was the nearest thing I could find.

Dave.
--

-- 
View this message in context: http://www.nabble.com/Jetty-and-commons-logging-tp14625344p14631427.html
Sent from the Equinox - Dev mailing list archive at Nabble.com.