cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Bosschaert <david.bosscha...@gmail.com>
Subject Re: CXF-DOSGi passing the OSGi Remote Services and Remote Service Admin CT
Date Fri, 04 Jun 2010 06:25:47 GMT
On 3 June 2010 23:42, Sergey Beryozkin <sberyozkin@gmail.com> wrote:
>> >> 3. Anything else?
>> Well, the Remote Services Admin spec mandates that the configuration
>> properties follow a certain pattern. If the configuration type is
>> called org.apache.cxf.ws then its specific configuration variables
>> should be called org.apache.cxf.ws.something (see table 122.1 in the
>> OSGi 4.2 Enterprise Spec http://www.osgi.org/Download/Release4V42).
>> This is to avoid name clashes when you want to expose a service using
>> multiple Remote Service implementations that may not be aware of each
>> other. So to be compliant we have to live with parallel properties.
>>
>Having some properties in the CXF space "org.apache.cxf" seems to be
> totally compliant ? Then they can be 'inherited' by cxf.ws, cxf.rs.

Not entirely sure what you mean here, but a 'reverse domain' name is
used here to avoid overlap between two technologies that are unaware
of each other. Just like in Java Package names. So using just 'cxf.ws'
is a shorter but not entirely compliant.

>> I do agree on matching up the properties where this makes sense across
>> org.apache.cxf.ws and org.apache.cxf.rs
>>
>> So how would you rename a property like "org.apache.cxf.ws.port" ?

org.apache.cxf.rs.port

David

Mime
View raw message