Re: [equinox-dev] servlet container incubator

[Simon J Archer <sarcher@xxxxxxxxxx>]

Scott

Yeah, I think you'll see that the property
is the same regardless of whether you're running in the Eclipse IDE or
an RCP app since they both use the same OSGi implementation.  In this
regards, the Eclipse IDE is an RCP app.  The property I described
is only useful for detecting which vendor implementation you're running
on, which in many case you probably should not be caring about.

Good luck,

Simon

Scott Lewis <slewis@xxxxxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

02/20/2006 10:04 PM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To	Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc	Pete Mackie <pete@xxxxxxxxxxxx>
Subject	Re: [equinox-dev] servlet container incubator

Hi Simon,

Thanks.  I see that for this property "Eclipse" is used
for for the 
bridge, Eclipse 3.2m5, and an rcp app that I've constructed.  Any
thoughts about having this vary for different environments...or having
another property to do so?  I don't currently see another property
that 
contains information to distinguish Equinox runtimes...unless I'm 
missing it in listing.

Thanks,

Scott


Simon J Archer wrote:

>
> Partial answer... Section 4.4.3 of the OSGi R4 spec describes 
> properties that should be set by an OSGi framework implementation.
>  For example, you can tell which vendor the framework is from
with the 
> following property:
>
>  org.osgi.framework.vendor = Eclipse
>
> You can easily query the system properties by typing "props"
at the 
> OSGi console.
>
>
>
> *Scott Lewis <slewis@xxxxxxxxxxxxx>*
> Sent by: equinox-dev-bounces@xxxxxxxxxxx
>
> 02/20/2006 09:22 PM
> Please respond to
> Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
>
>
>                  
> To
>                  Equinox
development mailing list <equinox-dev@xxxxxxxxxxx>
> cc
>                  Pete
Mackie <pete@xxxxxxxxxxxx>
> Subject
>                  Re:
[equinox-dev] servlet container incubator
>
>
>
>                  
>
>
>
>
>
> One more question:
>
> Is there a way to plugin code to detect whether it's running via this
> servlet container bridge or whether it's running in Eclipse or some
> other OSGI environment?
>
> Thanksinadvance,
>
> Scott
>
> Scott Lewis wrote:
>
> > Hi Folks,
> >
> > The ECF team is using the equinox servlet container incubator
(thanks
> > Simon) to build/deploy a simple 'generic' collaboration server
to
> > ecf.eclipse.org (for testing and usage by project team members).
> >
> > We've got the basics running...servlet container, bridge, OSGI
> > runtime, our server bundles, etc.  We're just working through
some
> > firewall issues at eclipse.org, some config changes/generalizations
> > for our server, and then it will be running constantly/consistently
> > there...and made available to Eclipse Foundation project teams
for
> > online team collaboration.
> >
> > A couple of quick questions about the osgi runtime in servlet
container:
> >
> > 1) Is anyone working on an html interface for the OSGI console...if
> > so, where is that?  We would like to start/stop/restart,
etc., etc our
> > server bundle(s) without using the servlet container and OSGI
> > console.  I've seen the httpconsole pointers on the incubator
page and
> > haven't worked with it yet, but probably will start...but wanted
to
> > know what work is going on here
> > 2) I've seen in passing discussion of a consistent programmatic
> > interface for startup bundle initialization but haven't read
the whole
> > thread.  Where is that work at this point? 3) Are there
any
> > changes/additions for 3.2M5? 4) What are the plans WRT the servlet
> > container incubator?  Is there any need/desire to show/show
(off) such
> > a server running ECF (in ~ production) at EclipseCon?
> > 5) Is there jaas-based authentication work in 3.2M5?  If
so, is there
> > a description of how to use it somewhere?  Thanksinadvance?
> >
> > BTW, congrats to all on the 3.2M5 release.
> >
> > Thanks,
> >
> > Scott
> >
> >
> >
> > _______________________________________________
> > equinox-dev mailing list
> > equinox-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
>
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
>------------------------------------------------------------------------
>
>_______________________________________________
>equinox-dev mailing list
>equinox-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/equinox-dev
>  
>


_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev