Re: jaxrs and minimal bundles for 2.6.0?
Hi Dan On 29/03/12 22:16, Sergey Beryozkin wrote: Hi Dan On 29/03/12 22:06, Daniel Kulp wrote: OK. I'll drop the minimal bundle but keep the jaxrs. That works for me. :-) Thanks, I'll also play with the minimal osgi demo in the next few days and see how it works without the jaxrs bundle. The individual modules can replace the all-like bundles quite nicely, I've tried with one of the Talend demos. The jaxrs bundle might be of help for non-Karaf users during the migration, so if you are OK with keeping it for now then lets keep it :-). The indiv modules approach work great too and would be more preferred in time as well, we can drop then the jaxrs bundle in 2.7.0 for ex Thanks, Sergey Cheers, Sergey Dan On Wednesday, March 28, 2012 04:39:30 PM Sergey Beryozkin wrote: Hi Dan On 28/03/12 16:16, Daniel Kulp wrote: Quick question: Are the jaxrs and minimal bundles still needed for 2.6.0? With the new little bundles, neither really makes any sense anymore. The minimal bundle is far from minimal (it's grown fairly large). Folks needed a more minimal environment are better just grabbing the individual bundles of just the things they need. Definitely +1 to dropping the minimal bundle, it was introduced originally to minimize DOSGi CXF single bundle distributions but it won't be needed when DOSGi CXF gets updated to CXF 2.6.0 Likewise, the jaxrs bundle is likely better served with the smaller bundles. It does not give us much now in Karaf with its features easily pulling in various smaller bundles together but dropping it might make it more difficult for some users to migrate to CXF 2.6.0 in cases they depend upon it for the apps deployed into non-Karaf based OSGI containers (I expect some users do it). The all bundle does have use outside of OSGi since that is the main jar we stick in lib. I'm just wondering if it make sense to keep maintaining the other two. I guess I'd not mind to keep the cxf jaxrs in the 2.6.x main branch if possible till 2.7 for example. But I recognize it is mostly redundant. I'll try to play with some of the demos and migrate them to depending on smaller bundles, if it simply a matter of updating the maven deps then it would be easy to migrate :-) Cheers, Sergey Thoughts? -- Sergey Beryozkin Talend Community Coders http://coders.talend.com/ Blog: http://sberyozkin.blogspot.com
Re: jaxrs and minimal bundles for 2.6.0?
OK. I'll drop the minimal bundle but keep the jaxrs. That works for me. :-) Dan On Wednesday, March 28, 2012 04:39:30 PM Sergey Beryozkin wrote: Hi Dan On 28/03/12 16:16, Daniel Kulp wrote: Quick question: Are the jaxrs and minimal bundles still needed for 2.6.0? With the new little bundles, neither really makes any sense anymore. The minimal bundle is far from minimal (it's grown fairly large). Folks needed a more minimal environment are better just grabbing the individual bundles of just the things they need. Definitely +1 to dropping the minimal bundle, it was introduced originally to minimize DOSGi CXF single bundle distributions but it won't be needed when DOSGi CXF gets updated to CXF 2.6.0 Likewise, the jaxrs bundle is likely better served with the smaller bundles. It does not give us much now in Karaf with its features easily pulling in various smaller bundles together but dropping it might make it more difficult for some users to migrate to CXF 2.6.0 in cases they depend upon it for the apps deployed into non-Karaf based OSGI containers (I expect some users do it). The all bundle does have use outside of OSGi since that is the main jar we stick in lib. I'm just wondering if it make sense to keep maintaining the other two. I guess I'd not mind to keep the cxf jaxrs in the 2.6.x main branch if possible till 2.7 for example. But I recognize it is mostly redundant. I'll try to play with some of the demos and migrate them to depending on smaller bundles, if it simply a matter of updating the maven deps then it would be easy to migrate :-) Cheers, Sergey Thoughts? -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
Re: jaxrs and minimal bundles for 2.6.0?
Hi Dan On 29/03/12 22:06, Daniel Kulp wrote: OK. I'll drop the minimal bundle but keep the jaxrs. That works for me. :-) Thanks, I'll also play with the minimal osgi demo in the next few days and see how it works without the jaxrs bundle. Cheers, Sergey Dan On Wednesday, March 28, 2012 04:39:30 PM Sergey Beryozkin wrote: Hi Dan On 28/03/12 16:16, Daniel Kulp wrote: Quick question: Are the jaxrs and minimal bundles still needed for 2.6.0? With the new little bundles, neither really makes any sense anymore. The minimal bundle is far from minimal (it's grown fairly large). Folks needed a more minimal environment are better just grabbing the individual bundles of just the things they need. Definitely +1 to dropping the minimal bundle, it was introduced originally to minimize DOSGi CXF single bundle distributions but it won't be needed when DOSGi CXF gets updated to CXF 2.6.0 Likewise, the jaxrs bundle is likely better served with the smaller bundles. It does not give us much now in Karaf with its features easily pulling in various smaller bundles together but dropping it might make it more difficult for some users to migrate to CXF 2.6.0 in cases they depend upon it for the apps deployed into non-Karaf based OSGI containers (I expect some users do it). The all bundle does have use outside of OSGi since that is the main jar we stick in lib. I'm just wondering if it make sense to keep maintaining the other two. I guess I'd not mind to keep the cxf jaxrs in the 2.6.x main branch if possible till 2.7 for example. But I recognize it is mostly redundant. I'll try to play with some of the demos and migrate them to depending on smaller bundles, if it simply a matter of updating the maven deps then it would be easy to migrate :-) Cheers, Sergey Thoughts?
Re: jaxrs and minimal bundles for 2.6.0?
Hi Dan On 28/03/12 16:16, Daniel Kulp wrote: Quick question: Are the jaxrs and minimal bundles still needed for 2.6.0? With the new little bundles, neither really makes any sense anymore. The minimal bundle is far from minimal (it's grown fairly large). Folks needed a more minimal environment are better just grabbing the individual bundles of just the things they need. Definitely +1 to dropping the minimal bundle, it was introduced originally to minimize DOSGi CXF single bundle distributions but it won't be needed when DOSGi CXF gets updated to CXF 2.6.0 Likewise, the jaxrs bundle is likely better served with the smaller bundles. It does not give us much now in Karaf with its features easily pulling in various smaller bundles together but dropping it might make it more difficult for some users to migrate to CXF 2.6.0 in cases they depend upon it for the apps deployed into non-Karaf based OSGI containers (I expect some users do it). The all bundle does have use outside of OSGi since that is the main jar we stick in lib. I'm just wondering if it make sense to keep maintaining the other two. I guess I'd not mind to keep the cxf jaxrs in the 2.6.x main branch if possible till 2.7 for example. But I recognize it is mostly redundant. I'll try to play with some of the demos and migrate them to depending on smaller bundles, if it simply a matter of updating the maven deps then it would be easy to migrate :-) Cheers, Sergey Thoughts?
