I'm working on improving and refactoring the OSGi bits and I'd like to
propose the following:
* make camel-osgi a plain jar just used to share common code between
camel-blueprint and camel-spring
this jar would contain osgi specific classes and also common code for
jaxb parsing / factory lo
[
https://issues.apache.org/activemq/browse/CAMEL-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-2688.
-
Resolution: Fixed
updated the smpp wiki page for this feature.
> Add SSL support to camel-sm
[
https://issues.apache.org/activemq/browse/CAMEL-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-2694.
-
Resolution: Fixed
> HttpEntityConverter should not create a InputStreamEntity by using the
>
[
https://issues.apache.org/activemq/browse/CAMEL-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-2686.
-
Resolution: Fixed
> camel-http should support to disable the gzip when it working in proxy mo
[
https://issues.apache.org/activemq/browse/CAMEL-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-2663.
-
Fix Version/s: 2.3.0
Resolution: Fixed
Created a camel-eclipse component for this reso
On Fri, May 7, 2010 at 9:06 AM, Guillaume Nodet wrote:
> I'm working on improving and refactoring the OSGi bits and I'd like to
> propose the following:
> * make camel-osgi a plain jar just used to share common code between
> camel-blueprint and camel-spring
> this jar would contain osgi spe
[
https://issues.apache.org/activemq/browse/CAMEL-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-2693:
---
Fix Version/s: 2.4.0
(was: 2.3.0)
> camle-osgi should use an extender patt
[
https://issues.apache.org/activemq/browse/CAMEL-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-2022:
---
Fix Version/s: 2.4.0
(was: 2.3.0)
> Blueprint support
> -
[
https://issues.apache.org/activemq/browse/CAMEL-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-2695:
---
Fix Version/s: 2.4.0
(was: 2.3.0)
> Add documentation for camel-blueprint
[
https://issues.apache.org/activemq/browse/CAMEL-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59245#action_59245
]
Claus Ibsen commented on CAMEL-2594:
Fernando any update about edit rights?
> Constants
[
https://issues.apache.org/activemq/browse/CAMEL-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59244#action_59244
]
Claus Ibsen commented on CAMEL-2213:
Could you elaborate what you mean?
> Configure proj
[
https://issues.apache.org/activemq/browse/CAMEL-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-2702:
---
Fix Version/s: 2.4.0
Component/s: osgi
(was: camel-spring)
> Extract
[
https://issues.apache.org/activemq/browse/CAMEL-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-313:
--
Issue Type: New Feature (was: Improvement)
Fix Version/s: 2.4.0
(was:
[
https://issues.apache.org/activemq/browse/CAMEL-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1267.
Fix Version/s: (was: Future)
Resolution: Incomplete
No demand for SDO
> add support
Guillaume Nodet wrote:
I'm working on improving and refactoring the OSGi bits and I'd like to
propose the following:
* make camel-osgi a plain jar just used to share common code between
camel-blueprint and camel-spring
this jar would contain osgi specific classes and also common code for
L.S.,
Guillaume's suggestion is to create a separate JAR with the OSGi
helper bits and embed that in both camel-blueprint and camel-spring.
I don't think there's a real problem with a compile-time dependency,
as long as we mark the Maven dependency optional in the pom.xml -- we
just have to make
On Fri, May 7, 2010 at 10:34 AM, Gert Vanthienen
wrote:
> L.S.,
>
> Guillaume's suggestion is to create a separate JAR with the OSGi
> helper bits and embed that in both camel-blueprint and camel-spring.
> I don't think there's a real problem with a compile-time dependency,
> as long as we mark th
On Fri, May 7, 2010 at 10:34, Gert Vanthienen wrote:
> L.S.,
>
> Guillaume's suggestion is to create a separate JAR with the OSGi
> helper bits and embed that in both camel-blueprint and camel-spring.
> I don't think there's a real problem with a compile-time dependency,
> as long as we mark the M
Gert Vanthienen wrote:
L.S.,
Guillaume's suggestion is to create a separate JAR with the OSGi
helper bits and embed that in both camel-blueprint and camel-spring.
I don't think there's a real problem with a compile-time dependency,
as long as we mark the Maven dependency optional in the pom.xml
To be more clear and let room for discussion (and still be able to work),
i'll do the following:
* extract the xml / jabx logic in a separate maven module named
components/camel-core-xml
* extract the osgi bits in a new module components/camel-core-osgi
To minimize changes, camel-spring will em
[
https://issues.apache.org/activemq/browse/CAMEL-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59249#action_59249
]
Cott Lang commented on CAMEL-2688:
--
Thanks, Willem. Sorry, I was trying to get to the wiki b
On Fri, May 7, 2010 at 2:26 PM, Guillaume Nodet wrote:
> To be more clear and let room for discussion (and still be able to work),
> i'll do the following:
> * extract the xml / jabx logic in a separate maven module named
> components/camel-core-xml
> * extract the osgi bits in a new module comp
On Fri, May 7, 2010 at 14:44, Claus Ibsen wrote:
> On Fri, May 7, 2010 at 2:26 PM, Guillaume Nodet wrote:
> > To be more clear and let room for discussion (and still be able to work),
> > i'll do the following:
> > * extract the xml / jabx logic in a separate maven module named
> > components/c
+1
On May 7, 2010, at 1:06 AM, Guillaume Nodet wrote:
> I'm working on improving and refactoring the OSGi bits and I'd like to
> propose the following:
> * make camel-osgi a plain jar just used to share common code between
> camel-blueprint and camel-spring
> this jar would contain osgi spe
[
https://issues.apache.org/activemq/browse/CAMEL-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59255#action_59255
]
Christian Mueller commented on CAMEL-1537:
--
Hello Claus!
Sorry for the late reply, b
Upgrade the maven plugin dependencies
-
Key: CAMEL-2703
URL: https://issues.apache.org/activemq/browse/CAMEL-2703
Project: Apache Camel
Issue Type: Improvement
Environment: All
Reporte
26 matches
Mail list logo