Ok thanks,
indeed i am using the all-in-one bundle.
Regarding my question about osgi environment properties,
i am not sure to understand the concept of OSGI environment properties.
After having a look at the source code,
i read this :
" Configuration properties are generally the sole means to configure
the framework's default behavior; the framework does not typically refer to
any system properties for configuration information" (...) " The
following configuration properties can be specified (properties starting
with felix are specific to Felix, while those starting with org.osgi are
standard OSGi properties"
But when i read the source code of the Felix http service, i have seen that
the configuration properties
are retrieved using the bundleContext.getProperty(String key) method which
also searches in the system
properties, so i guess these properties can be set dynamically using the
System.setProperty(String key,String value) method.
On Wed, Sep 1, 2010 at 9:56 AM, Felix Meschberger <[email protected]>wrote:
> Hi,
>
> Don't take the full CXF distro all-in-one bundle. This contains lots of
> stuff to enable out-of-the-box use of it.
>
> For real-world use, my experience is to go with the other distro and
> remove the bundles you don't need or you have in another form.
>
> For example, for using the CXF dOSGi implementation in an Apache Sling
> environment, I would remove the pax-web-service bundle, all logging
> bundles (Sling has its own), configuration admin, and probably a few more.
>
> Depending on your application you even might want to add a few bundles
> from someplace else.
>
> Regards
> Felix
>
> On 01.09.2010 15:49, Luc Dewavrin wrote:
> > Hi,
> >
> > i would like to turn Declarative Services into WS endpoints. I have
> tried
> > with Apache CXF and it seems to work so far.
> > My main concern is that CXF uses pax-web-service HTTP service and the
> only
> > way to configure the embedded
> > Jetty server is by deploying a bundle fragment that contains the Jetty
> > configuration file.
> > I don't want this solution since the Jetty configuration has to be
> > externalized and configured without re-packaging.
> >
> > I wanted to replace the pax-web-service HTTP service with the felix one.
> I
> > have seen that the port/address and SSL configuration
> > could be modified with OSGI environment properties.
> >
> > Is it possible to modify OSGI environment properties dynamically through
> the
> > API ? (The http service must be defined in our
> > own XML format, so i thought about creating a bundle that sets these
> > properties dynamically).
> >
> > Regards,
> > Luc
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>