On 11.12.2014 07:32, Claus Ibsen wrote:
And frankly a camel-http-core would maybe also be good, which has no
or only dependency on the servlet api. Then there can be some shared
code that the various HTTP components can rely and reuse.
Yes it would avoid that we depend on camel-http which bring
On Wed, Dec 10, 2014 at 10:04 AM, Christian Schneider
wrote:
> I agree with Dan that a common module and one module for jetty8 and one for
> jetty9 is probably the best route to go. Like Willem mentioned we can even
> try to create a http common module if possible. I would start with a jetty
> bas
It sounds good to me, we can do the http common module work later.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On December 10, 2014 at 5:06:02 PM, Christian Schn
I agree with Dan that a common module and one module for jetty8 and one
for jetty9 is probably the best route to go. Like Willem mentioned we
can even try to create a http common module if possible. I would start
with a jetty based common module first as it is probably the easier step.
I am no
Jetty 8 (and 7) are already end of life so we’re trying to figure out the
“best” way to get Jetty 9 support so we can get a camel-jetty component that
can use a supported version of Jetty. So for Camel 2.15, the question, to me,
is how to support both 8 and 9 (assuming we need to support 8 wh
As we don’t release camel components separately, I need to support the Jetty7,8
for very long time. It make sense that we can share the common logics in these
components to avoid the duplication.
Camel-http, camel-http4 share some common logic at the same time, maybe it’s
time for us to go thr
On Tue, Dec 9, 2014 at 9:29 AM, Christian Schneider
wrote:
> Probably having two versions of camel-jetty is the only viable way then.
> I am a bit concerned about the code duplication though. The component it
> self is already quite big and the tests are even bigger. Should we try to
> move the co
Probably having two versions of camel-jetty is the only viable way then.
I am a bit concerned about the code duplication though. The component it
self is already quite big and the tests are even bigger. Should we try
to move the common things into a separate jar?
I think one deciding factor he
It’s hard to support two major release version.
How about fork another version of camel-jetty (camel-jetty8) which supports
Jetty7 and Jetty8 and move camel-jetty to support Jetty9 instead.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
On Mon, Dec 8, 2014 at 5:17 PM, Christian Schneider
wrote:
> There are some changes we need to do in camel to support the upcoming karaf
> 4. The most visible difference is that karaf 4 will include jetty 9.
> Recently Dan migrated the camel-jetty component to support jetty 8 and 9 on
> the consum
10 matches
Mail list logo
