cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Colm O hEigeartaigh <cohei...@apache.org>
Subject Re: [DISCUSS] api+rt-core -> core
Date Thu, 04 Jul 2013 08:52:04 GMT
+1.

Colm.


On Thu, Jul 4, 2013 at 3:54 AM, Dennis Sosnoski <dms@sosnoski.com> wrote:

> +1
>
>   - Dennis
>
>
> On 07/04/2013 06:39 AM, Daniel Kulp wrote:
>
>> For 3.0, I'd like to combine both cxf-api and cxf-rt-core into a single
>> jar/bundle.   I'd likely just call it cxf-core, but I'm open to other
>> suggestions (cxf-kernel?).
>>
>> We originally tried to have a separate jar for "api" to make javadoc
>> generation easier, but it pretty much doesn't work.   Many of the classes
>> (like the Service Factories and client factories and JAX-RS client things
>> and much much more) that you really would need are not part of api and thus
>> don't appear in the "api" javadoc anyway.   Thus, that reason is pointless
>> and not working.
>>
>> API is also WAY WAY more than just "API" now.   There are interceptors,
>> data binding things, all kinds of concrete utility things, etc…   API is
>> about 1MB whereas "core" is about 270K.   Kind of shows where the real
>> "core" stuff is.
>>
>> As it is, right now, you cannot really have api without rt-core anyway.
>>  By combining them, we can get rid of some of the dynamic import things and
>> such in OSGi (to find the Bus factory).   One less jar to deal with as
>> well.  The jaxrs basic sample would be down to cxf-core,
>> cxf-transports-http, cxf-rt-frontend-jaxrs, and the related 3rd party deps.
>>
>> Thoughts?
>>
>>
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message