[jira] [Created] (CAMEL-5296) Adding camel-mllp component
Terrien Jean-Yves created CAMEL-5296:
Summary: Adding camel-mllp component
Key: CAMEL-5296
URL: https://issues.apache.org/jira/browse/CAMEL-5296
Project: Camel
Issue Type: New Feature
Components: camel-hl7
Affects Versions: 2.8.0
Reporter: Terrien Jean-Yves
Priority: Minor
I think a camel-mllp component would be welcome.
I therefore propose to add it. this would avoid having to add each time the
same code to set the codec.
I have in my project numerous endpoint mllp and I noticed that the developpers
diverge more or less on how to go about it. the code: from ("mllp://host:8808")
is easy to implement and does not cause confusion.
So I defined a camel-mllp componet which extends camel-mina. this component
does is create a codec mllp and delegates the rest of the work to Mina. it is
simple to implement.
as I suggested Claus Ibsen-2I have built-in HL7 camel.
http://camel.465427.n5.nabble.com/file/n5712567/camel-mllp.zip";>camel-hl7-mllp-patch.zip
http://camel.465427.n5.nabble.com/Suggest-Add-a-camel-mllp-component-into-the-incubator-tt5711304.html
A+JYT
PS:I'm not about to have followed the procedure for submitting this proposal.
Sorry for my approximative english
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-5296) Adding camel-mllp component
[
https://issues.apache.org/jira/browse/CAMEL-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Terrien Jean-Yves updated CAMEL-5296:
-
Description:
I think a camel-mllp component would be welcome.
I therefore propose to add it. this would avoid having to add each time the
same code to set the codec.
I have in my project numerous endpoint mllp and I noticed that the developpers
diverge more or less on how to go about it. the code: from ("mllp://host:8808")
is easy to implement and does not cause confusion.
So I defined a camel-mllp component which extends camel-mina. this component
does is create a codec mllp and delegates the rest of the work to Mina. it is
simple to implement.
as I suggested Claus Ibsen-2I have built-in HL7 camel.
http://camel.465427.n5.nabble.com/Suggest-Add-a-camel-mllp-component-into-the-incubator-tt5711304.html
A+JYT
PS:I'm not about to have followed the procedure for submitting this proposal.
Sorry for my approximative english
was:
I think a camel-mllp component would be welcome.
I therefore propose to add it. this would avoid having to add each time the
same code to set the codec.
I have in my project numerous endpoint mllp and I noticed that the developpers
diverge more or less on how to go about it. the code: from ("mllp://host:8808")
is easy to implement and does not cause confusion.
So I defined a camel-mllp componet which extends camel-mina. this component
does is create a codec mllp and delegates the rest of the work to Mina. it is
simple to implement.
as I suggested Claus Ibsen-2I have built-in HL7 camel.
http://camel.465427.n5.nabble.com/file/n5712567/camel-mllp.zip";>camel-hl7-mllp-patch.zip
http://camel.465427.n5.nabble.com/Suggest-Add-a-camel-mllp-component-into-the-incubator-tt5711304.html
A+JYT
PS:I'm not about to have followed the procedure for submitting this proposal.
Sorry for my approximative english
> Adding camel-mllp component
> ---
>
> Key: CAMEL-5296
> URL: https://issues.apache.org/jira/browse/CAMEL-5296
> Project: Camel
> Issue Type: New Feature
> Components: camel-hl7
>Affects Versions: 2.8.0
>Reporter: Terrien Jean-Yves
>Priority: Minor
> Labels: patch
> Attachments: camel-mllp.zip
>
>
> I think a camel-mllp component would be welcome.
> I therefore propose to add it. this would avoid having to add each time the
> same code to set the codec.
> I have in my project numerous endpoint mllp and I noticed that the
> developpers diverge more or less on how to go about it. the code: from
> ("mllp://host:8808") is easy to implement and does not cause confusion.
> So I defined a camel-mllp component which extends camel-mina. this component
> does is create a codec mllp and delegates the rest of the work to Mina. it is
> simple to implement.
> as I suggested Claus Ibsen-2I have built-in HL7 camel.
> http://camel.465427.n5.nabble.com/Suggest-Add-a-camel-mllp-component-into-the-incubator-tt5711304.html
> A+JYT
> PS:I'm not about to have followed the procedure for submitting this proposal.
> Sorry for my approximative english
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-5296) Adding camel-mllp component
[
https://issues.apache.org/jira/browse/CAMEL-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Terrien Jean-Yves updated CAMEL-5296:
-
Attachment: camel-mllp.zip
the path
> Adding camel-mllp component
> ---
>
> Key: CAMEL-5296
> URL: https://issues.apache.org/jira/browse/CAMEL-5296
> Project: Camel
> Issue Type: New Feature
> Components: camel-hl7
>Affects Versions: 2.8.0
>Reporter: Terrien Jean-Yves
>Priority: Minor
> Labels: patch
> Attachments: camel-mllp.zip
>
>
> I think a camel-mllp component would be welcome.
> I therefore propose to add it. this would avoid having to add each time the
> same code to set the codec.
> I have in my project numerous endpoint mllp and I noticed that the
> developpers diverge more or less on how to go about it. the code: from
> ("mllp://host:8808") is easy to implement and does not cause confusion.
> So I defined a camel-mllp componet which extends camel-mina. this component
> does is create a codec mllp and delegates the rest of the work to Mina. it is
> simple to implement.
> as I suggested Claus Ibsen-2I have built-in HL7 camel.
> href="http://camel.465427.n5.nabble.com/file/n5712567/camel-mllp.zip";>camel-hl7-mllp-patch.zip
> http://camel.465427.n5.nabble.com/Suggest-Add-a-camel-mllp-component-into-the-incubator-tt5711304.html
> A+JYT
> PS:I'm not about to have followed the procedure for submitting this proposal.
> Sorry for my approximative english
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CAMEL-5296) Adding camel-mllp component
[
https://issues.apache.org/jira/browse/CAMEL-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279832#comment-13279832
]
Terrien Jean-Yves edited comment on CAMEL-5296 at 5/20/12 6:02 PM:
---
attach the path
was (Author: sekaijin):
the path
> Adding camel-mllp component
> ---
>
> Key: CAMEL-5296
> URL: https://issues.apache.org/jira/browse/CAMEL-5296
> Project: Camel
> Issue Type: New Feature
> Components: camel-hl7
>Affects Versions: 2.8.0
>Reporter: Terrien Jean-Yves
>Priority: Minor
> Labels: patch
> Attachments: camel-mllp.zip
>
>
> I think a camel-mllp component would be welcome.
> I therefore propose to add it. this would avoid having to add each time the
> same code to set the codec.
> I have in my project numerous endpoint mllp and I noticed that the
> developpers diverge more or less on how to go about it. the code: from
> ("mllp://host:8808") is easy to implement and does not cause confusion.
> So I defined a camel-mllp component which extends camel-mina. this component
> does is create a codec mllp and delegates the rest of the work to Mina. it is
> simple to implement.
> as I suggested Claus Ibsen-2I have built-in HL7 camel.
> http://camel.465427.n5.nabble.com/Suggest-Add-a-camel-mllp-component-into-the-incubator-tt5711304.html
> A+JYT
> PS:I'm not about to have followed the procedure for submitting this proposal.
> Sorry for my approximative english
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-10554) camel-mongodb evolution to driver 3
Terrien Jean-Yves created CAMEL-10554: - Summary: camel-mongodb evolution to driver 3 Key: CAMEL-10554 URL: https://issues.apache.org/jira/browse/CAMEL-10554 Project: Camel Issue Type: Improvement Affects Versions: 2.19.0 Reporter: Terrien Jean-Yves Priority: Minor Hi, The mongodb driver has changed in its foundation. It is recommended not to use many classes of the verion 2 still present in the driver. This is the case with DBObject, which is the basis for the configuration of the camel component. I'm working on the evolution of this component to use the new classes of version 3, like "Document". I've created à patch (no completed) A+JYT Ps: how I can post the patch ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terrien Jean-Yves updated CAMEL-10554: -- Attachment: mongo3.patch Patch to use mongo 3 API. > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Priority: Minor > Attachments: mongo3.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT > Ps: how I can post the patch ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15719681#comment-15719681 ] Terrien Jean-Yves commented on CAMEL-10554: --- this parameters are déprecated and are no effect on driver v3 voidsetOptions(int options) Deprecated. Set options on instances of DBCursor voidsetReadPreference(ReadPreference readPreference) Deprecated. Set the default read preference with either MongoClientURI or MongoClientOptions voidsetWriteConcern(WriteConcern writeConcern) Deprecated. Set the default write concern with either MongoClientURI or MongoClientOptions voidslaveOk() Deprecated. Replaced with ReadPreference.secondaryPreferred() I'm working to solve this problem. In the new version you should put these options on the mongoClient bean and not put them on the camel url. Bye. > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT > Ps: how I can post the patch ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15719691#comment-15719691 ] Terrien Jean-Yves commented on CAMEL-10554: --- In the camel component configuration an option is outputType which is implemented as a MongoDbOutputType enumeration The values are DBObjectList, DBObject, DBCursor which matches in the new API to List, Document, MongoIterable I do not know what to do. This configuration is purely camel I can keep the enumeration values and use the new classes Or define three new values (DocumentList, Document, MongoIterable) and using the new classes. In the first case the values of the option does not have a name to refer to the mongo API but remains compatible with the previous versions of camel-mongodb. In the second the values correspond to the mongo API but are no longer compatible with the previous versions. A+JYT > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT > Ps: how I can post the patch ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terrien Jean-Yves updated CAMEL-10554: -- Attachment: mongo4.patch readPreference writeConcern > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch, mongo4.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT > Ps: how I can post the patch ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terrien Jean-Yves updated CAMEL-10554: -- Description: Hi, The mongodb driver has changed in its foundation. It is recommended not to use many classes of the verion 2 still present in the driver. This is the case with DBObject, which is the basis for the configuration of the camel component. I'm working on the evolution of this component to use the new classes of version 3, like "Document". I've created à patch (no completed) A+JYT was: Hi, The mongodb driver has changed in its foundation. It is recommended not to use many classes of the verion 2 still present in the driver. This is the case with DBObject, which is the basis for the configuration of the camel component. I'm working on the evolution of this component to use the new classes of version 3, like "Document". I've created à patch (no completed) A+JYT Ps: how I can post the patch ? > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch, mongo4.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terrien Jean-Yves updated CAMEL-10554: -- Attachment: mongo5.patch Using Filters class Adding FIELDS_FILTER headers on update operation Update documentation Change MongoDbOutputType to DocumentList, //List Document, //Document MongoIterable //MongoIterable Using Bson class instead of Document when is possible (more generic) Work in progress Using more generic classes (like Bson) Study of the use of MongoCollection where TDocument is generic parameter. > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch, mongo4.patch, mongo5.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740195#comment-15740195 ] Terrien Jean-Yves commented on CAMEL-10554: --- Yes > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch, mongo4.patch, mongo5.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740195#comment-15740195 ] Terrien Jean-Yves edited comment on CAMEL-10554 at 12/11/16 7:23 PM: - Form Mongo Java Driver 3.x mongo drivers support mongo versions Java Driver Version MongoDB 2.4 MongoDB 2.6 MongoDB 3.0 MongoDB 3.2 MongoDB 3.4 Version 3.4 ✓ ✓ ✓✓✓ Version 3.3 ✓ ✓ ✓✓ Version 3.2 ✓ ✓ ✓✓ Version 2.14✓ ✓✓ ✓ [*] The V2 driver does not support more version than the V3 driver. A+JYT was (Author: sekaijin): Yes > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch, mongo4.patch, mongo5.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740195#comment-15740195 ] Terrien Jean-Yves edited comment on CAMEL-10554 at 12/11/16 7:24 PM: - Form Mongo Java Driver 3.x mongo drivers support mongo versions Java Driver|Version|MongoDB 2.4|MongoDB 2.6|MongoDB 3.0|MongoDB 3.2|MongoDB 3.4 Version | 3.4 | ✓ ✓ ✓✓✓ Version 3.3 ✓ ✓ ✓✓ Version 3.2 ✓ ✓ ✓✓ Version 2.14✓ ✓✓ ✓ [*] The V2 driver does not support more version than the V3 driver. A+JYT was (Author: sekaijin): Form Mongo Java Driver 3.x mongo drivers support mongo versions Java Driver Version MongoDB 2.4 MongoDB 2.6 MongoDB 3.0 MongoDB 3.2 MongoDB 3.4 Version 3.4 ✓ ✓ ✓✓✓ Version 3.3 ✓ ✓ ✓✓ Version 3.2 ✓ ✓ ✓✓ Version 2.14✓ ✓✓ ✓ [*] The V2 driver does not support more version than the V3 driver. A+JYT > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch, mongo4.patch, mongo5.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740195#comment-15740195 ] Terrien Jean-Yves edited comment on CAMEL-10554 at 12/11/16 7:26 PM: - Form Mongo Java Driver 3.x mongo drivers support mongo versions Java Driver|Version|MongoDB 2.4|MongoDB 2.6|MongoDB 3.0|MongoDB 3.2|MongoDB 3.4 Version | 3.4 | ✓ | ✓ | ✓ | ✓ | ✓ Version | 3.3| ✓ | ✓| ✓|✓ | Version |3.2 | ✓ |✓| ✓|✓ | Version |2.14 | ✓ |✓| ✓|✓ [*] | The V2 driver does not support more version than the V3 driver. A+JYT was (Author: sekaijin): Form Mongo Java Driver 3.x mongo drivers support mongo versions Java Driver|Version|MongoDB 2.4|MongoDB 2.6|MongoDB 3.0|MongoDB 3.2|MongoDB 3.4 Version | 3.4 | ✓ ✓ ✓✓✓ Version 3.3 ✓ ✓ ✓✓ Version 3.2 ✓ ✓ ✓✓ Version 2.14✓ ✓✓ ✓ [*] The V2 driver does not support more version than the V3 driver. A+JYT > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch, mongo4.patch, mongo5.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740195#comment-15740195 ] Terrien Jean-Yves edited comment on CAMEL-10554 at 12/11/16 7:26 PM: - Form Mongo Java Driver 3.x mongo drivers support mongo versions Java Dr|Ver|MongoDB 2.4|MongoDB 2.6|MongoDB 3.0|MongoDB 3.2|MongoDB 3.4 Version | 3.4. | ✓ | ✓ | ✓ | ✓ | ✓ Version | 3.3.| ✓ | ✓| ✓|✓ | Version |3.2. | ✓ |✓| ✓|✓ | Version |2.14 | ✓ |✓| ✓|✓ [*] | The V2 driver does not support more version than the V3 driver. A+JYT was (Author: sekaijin): Form Mongo Java Driver 3.x mongo drivers support mongo versions Java Driver|Version|MongoDB 2.4|MongoDB 2.6|MongoDB 3.0|MongoDB 3.2|MongoDB 3.4 Version | 3.4 | ✓ | ✓ | ✓ | ✓ | ✓ Version | 3.3| ✓ | ✓| ✓|✓ | Version |3.2 | ✓ |✓| ✓|✓ | Version |2.14 | ✓ |✓| ✓|✓ [*] | The V2 driver does not support more version than the V3 driver. A+JYT > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch, mongo4.patch, mongo5.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740195#comment-15740195 ] Terrien Jean-Yves edited comment on CAMEL-10554 at 12/11/16 7:29 PM: - Form Mongo Java Driver 3.x mongo drivers support mongo versions MongoDB Ver|2.4|2.6|3.0|3.2|3.4 Version | 3.4. | ✓ | ✓ | ✓ | ✓ | ✓ Version | 3.3.| ✓ | ✓| ✓|✓ | Version |3.2. | ✓ |✓| ✓|✓| Version |2.14 | ✓ |✓| ✓|✓ [*] | The V2 driver does not support more version than the V3 driver. A+JYT was (Author: sekaijin): Form Mongo Java Driver 3.x mongo drivers support mongo versions MongoDB Ver2.4|2.6|3.0|3.2|3.4 Version | 3.4. | ✓ | ✓ | ✓ | ✓ | ✓ Version | 3.3.| ✓ | ✓| ✓|✓ | Version |3.2. | ✓ |✓| ✓|✓| Version |2.14 | ✓ |✓| ✓|✓ [*] | The V2 driver does not support more version than the V3 driver. A+JYT > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch, mongo4.patch, mongo5.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740195#comment-15740195 ] Terrien Jean-Yves edited comment on CAMEL-10554 at 12/11/16 7:29 PM: - Form Mongo Java Driver 3.x mongo drivers support mongo versions MongoDB Ver2.4|2.6|3.0|3.2|3.4 Version | 3.4. | ✓ | ✓ | ✓ | ✓ | ✓ Version | 3.3.| ✓ | ✓| ✓|✓ | Version |3.2. | ✓ |✓| ✓|✓| Version |2.14 | ✓ |✓| ✓|✓ [*] | The V2 driver does not support more version than the V3 driver. A+JYT was (Author: sekaijin): Form Mongo Java Driver 3.x mongo drivers support mongo versions Java Dr|Ver|MongoDB 2.4|MongoDB 2.6|MongoDB 3.0|MongoDB 3.2|MongoDB 3.4 Version | 3.4. | ✓ | ✓ | ✓ | ✓ | ✓ Version | 3.3.| ✓ | ✓| ✓|✓ | Version |3.2. | ✓ |✓| ✓|✓ | Version |2.14 | ✓ |✓| ✓|✓ [*] | The V2 driver does not support more version than the V3 driver. A+JYT > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch, mongo4.patch, mongo5.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740195#comment-15740195 ] Terrien Jean-Yves edited comment on CAMEL-10554 at 12/11/16 7:30 PM: - For Mongo Java Driver 3.x mongo drivers support mongo versions MongoDB Ver|2.4|2.6|3.0|3.2|3.4 Version | 3.4. | ✓ | ✓ | ✓ | ✓ | ✓ Version | 3.3.| ✓ | ✓| ✓|✓ | Version |3.2. | ✓ |✓| ✓|✓| Version |2.14 | ✓ |✓| ✓|✓ [*] | The V2 driver does not support more version than the V3 driver. A+JYT was (Author: sekaijin): Form Mongo Java Driver 3.x mongo drivers support mongo versions MongoDB Ver|2.4|2.6|3.0|3.2|3.4 Version | 3.4. | ✓ | ✓ | ✓ | ✓ | ✓ Version | 3.3.| ✓ | ✓| ✓|✓ | Version |3.2. | ✓ |✓| ✓|✓| Version |2.14 | ✓ |✓| ✓|✓ [*] | The V2 driver does not support more version than the V3 driver. A+JYT > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch, mongo4.patch, mongo5.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740195#comment-15740195 ] Terrien Jean-Yves edited comment on CAMEL-10554 at 12/11/16 7:31 PM: - For Mongo Java Driver 3.x mongo drivers support mongo versions MongoDB Ver|2.4|2.6|3.0|3.2|3.4 Version | 3.4. | ✓ | ✓ | ✓ | ✓ | ✓ Version | 3.3.| ✓ | ✓| ✓|✓ | Version |3.2. | ✓ |✓| ✓|✓| Version |2.14 | ✓ |✓| ✓|✓ [*] | The V2 driver does not support more version than the V3 driver. I don't have tested with mongo 2.x A+JYT was (Author: sekaijin): For Mongo Java Driver 3.x mongo drivers support mongo versions MongoDB Ver|2.4|2.6|3.0|3.2|3.4 Version | 3.4. | ✓ | ✓ | ✓ | ✓ | ✓ Version | 3.3.| ✓ | ✓| ✓|✓ | Version |3.2. | ✓ |✓| ✓|✓| Version |2.14 | ✓ |✓| ✓|✓ [*] | The V2 driver does not support more version than the V3 driver. A+JYT > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch, mongo4.patch, mongo5.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15741359#comment-15741359 ] Terrien Jean-Yves commented on CAMEL-10554: --- Yes I'll stabilize the code. Remove options from previous versions in doc. (Put references to camel-mongodb) And create the camel-mongo3 component > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch, mongo4.patch, mongo5.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15747688#comment-15747688 ] Terrien Jean-Yves commented on CAMEL-10554: --- Hi. I've renamed the camel-mongodb3 component. What is the right method? Do I have to rename exported packages? Like org.apache.camel.component.mongodb => org.apache.camel.component.mongodb3 A+JYT > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch, mongo4.patch, mongo5.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15748256#comment-15748256 ] Terrien Jean-Yves commented on CAMEL-10554: --- Sorry I've moved my code to camel-mongodb3. Should the package be "org.apache.camel.component.mongodb" or "org.apache.camel.component.mongodb3"? I am afraid that if I leave "org.apache.camel.component.mongodb", there will be conflicts, if the two components are imported. Bye > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: mongo3.patch, mongo4.patch, mongo5.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terrien Jean-Yves updated CAMEL-10554: -- Attachment: camel-mongodb3.zip Good evening, I think this version is complete enough to create the component in the repository. I have a problem on my Mac The camel-mongodb project in the master version has tests that fail. testPersistentTailTrack testPersistentTailTrackIncreasingDateField testCustomTailTrackLocation The same tests with the same errors fail in the camel-mongodb3 project I posted on the list but it seems that the build works. I could not fix problem on the master. And so I can not test these cases in the new component. cordially PS: I'll have to get familiar with Git. I usually use SVN. > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: camel-mongodb3.zip, mongo3.patch, mongo4.patch, > mongo5.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terrien Jean-Yves updated CAMEL-10554: -- Attachment: (was: mongo5.patch) > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: camel-mongodb3.zip, mongo3.patch, mongo4.patch > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terrien Jean-Yves updated CAMEL-10554: -- Attachment: (was: mongo3.patch) > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: camel-mongodb3.zip > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-10554) camel-mongodb evolution to driver 3
[ https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terrien Jean-Yves updated CAMEL-10554: -- Attachment: (was: mongo4.patch) > camel-mongodb evolution to driver 3 > --- > > Key: CAMEL-10554 > URL: https://issues.apache.org/jira/browse/CAMEL-10554 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.19.0 >Reporter: Terrien Jean-Yves >Assignee: Andrea Cosentino >Priority: Minor > Attachments: camel-mongodb3.zip > > > Hi, > The mongodb driver has changed in its foundation. > It is recommended not to use many classes of the verion 2 still present in > the driver. > This is the case with DBObject, which is the basis for the configuration of > the camel component. > I'm working on the evolution of this component to use the new classes of > version 3, like "Document". > I've created à patch (no completed) > A+JYT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-13809) many erroneous links in the doc
Terrien Jean-Yves created CAMEL-13809: - Summary: many erroneous links in the doc Key: CAMEL-13809 URL: https://issues.apache.org/jira/browse/CAMEL-13809 Project: Camel Issue Type: Bug Components: documentation Environment: https://camel.apache.org/staging/community/articles/ videos Wild Flies and A Camel https://www.youtube.com/watch?v=o8ZRE9DM3Es video not found Camel in the cloud using Fuse Fabric http://fuse.fusesource.org/fabric/ time out Getting started with Apache Camel - Video presentation from Javagruppen https://javagruppen.dk/index.php/moder/historiske-moder/285-javagruppemode-115-apache-camel-i-aarhus 404 Apache Camel Essential Components by Christian Posta http://blip.tv/dzone/apache-camel-essential-components-6511579 Error 523 CamelOne 2012 Videos - All the videos http://fusesource.com/apache-camel-conference-2012/camelone_speakers_2012/ and http://fusesource.com/apache-camel-conference-2012 redirect to jboss.org CamelOne 2011 Video presentations CamelOne 2011 conference (May 2011) all links redirected to jboss.org Paris JUG 2011 - Integration with Apache Camel and ESB by Charles Moulliard http://www.parleys.com/#id=2432&st=5&sl=0 blank page Belgium JUG 2011 - Integration with Apache ServiceMix and Camel by Charles Moulliard http://www.parleys.com/#id=2601&st=5 blank page Devoxx 2011 - Introduction to Apache ActiveMQ, ServiceMix https://devoxx.com/display/DV11/Introduction+to+Apache+ActiveMQ,+ServiceMix,+Camel+and+CXF blank page errors on html structure Devoxx 2010 talk http://www.parleys.com/#id=2158&st=5 blank page errors on html structure at Øredev 2008 conference http://www.oredev.com/ 404 not found Devoxx 2009 talk http://www.parleys.com/#sl=11&st=5&id=1577 blank page Medium Resolution http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-medium-resolution/ unreachable High Resolution http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-high-resolution/ unreachable Taking Camel for a ride http://bsnyderblog.blogspot.com/2008/05/activemq-and-servicemix-at-apachecon-us.html time out JavaZone Conference - Taking Apache Camel for a Rider http://www4.java.no/incogito/session/Taking+Apache+Camel+for+a+Ride.html time out Screencast/Demo of Smooks and Apache Camel processing UN/EDIFACT http://www.screencast.com/users/tfennelly/folders/Camtasia/media/c3cef9dd-e667-41ac-8597-74ca01d39968 Not found Facebook integration Apache Camel http://screencasts.chariotsolutions.com/facebook-integration-using-apache-camel not found Advanced AEM Search - Consuming External Content http://www.circuitdevcon.com/en/session-videos/aem-search-apache-camel.html HTTP ERROR 503 Articles Integration with Apache Camel - Part I - Will get you over http://jaxenter.com/jax-magazine/JAX-Magazine-2013-05 not found Simple DSL OSGi bundle example by Andrej Koelewijn http://www.andrejkoelewijn.com/wp/2008/10/19/simple-camel-dsl-osgi-bundle-example/ not found Realization of EAI Patterns with Apache Camel by Pascal Kolb http://elib.uni-stuttgart.de/opus/volltexte/2008/3520/pdf/STUD_2127.pdf OPUS-ID 3520 nicht gefunden! (redirect error) First step with Apache Camel by Lukasz Budnik http://jee-bpel-soa.blogspot.com/2009/12/first-steps-with-apache-camel.html Sorry, the page you were looking for in this blog does not exist. LEGO Java: Apache Camel Context and Route Basics http://www.canoo.com/blog/2011/03/14/lego-java-apache-camel-context-and-route-basics/ not found LEGO® Java (II): Apache Camel Error Handling, http://www.canoo.com/blog/2011/03/16/lego-java-ii-apache-camel-error-handling-java-beans-and-web-services/ not found What is Camel? a short blog http://bushorn.com/what-is-camel/ Error establishing a database connection A bit more meat: Camel applied : JMS to File http://mikemclean.ca/muse/2009/05/a-bit-more-meat-camel-applied-jms-to-file/ not found Spring Remoting with JMS Example on Amin Abbaspour’s Weblog the second link http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html Le blog a été supprimé blog removed Camel routes and HL7 by Roger Searjeant http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html => blog removed Leverage EIP with Apache Camel and Twitter http://blog.brunoborges.com.br/2009/03/leverage-eip-with-apache-camel-and.html ERR_NAME_NOT_RESOLVED Camel, CXF and JMS by Example by Silvester van der Bijl http://blog.software-art.nl/2009/11/15/camel-cxf-and-jms-by-example/ time out A simple file monitoring console with camel, cometd and jquery http://www.andrejkoelewijn.com/wp/2009/10/27/simple-log-console-with-camel-and-cometd/ not found A composite REST service using Apache Camel by Andrej Koelewijn http://www.andrejkoelewijn.com/wp/2010/06/13/a-composite-rest-service-using-camel/ not found Using Apache Camel to route SOAP calls through mes
[jira] [Updated] (CAMEL-13809) many erroneous links in the doc
[ https://issues.apache.org/jira/browse/CAMEL-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terrien Jean-Yves updated CAMEL-13809: -- Description: Hi, many erroneous links in the doc I manually passed all links on the page. I read the returns to make sure they were still valid. when there was manual redirection I followed the link to check it. here is the list of errors that I found. a not about fusesource. all fusesource links are redirected to www.jboss.org. this does not allow to find the targeted document. hoping that this can be helpful. [https://camel.apache.org/staging/community/articles/] videos Wild Flies and A Camel [https://www.youtube.com/watch?v=o8ZRE9DM3Es] video not found Camel in the cloud using Fuse Fabric [http://fuse.fusesource.org/fabric/] time out Getting started with Apache Camel - Video presentation from Javagruppen [https://javagruppen.dk/index.php/moder/historiske-moder/285-javagruppemode-115-apache-camel-i-aarhus] 404 Apache Camel Essential Components by Christian Posta [http://blip.tv/dzone/apache-camel-essential-components-6511579] Error 523 CamelOne 2012 Videos - All the videos [http://fusesource.com/apache-camel-conference-2012/camelone_speakers_2012/] and [http://fusesource.com/apache-camel-conference-2012] redirect to jboss.org CamelOne 2011 Video presentations CamelOne 2011 conference (May 2011) all links redirected to jboss.org Paris JUG 2011 - Integration with Apache Camel and ESB by Charles Moulliard [http://www.parleys.com/#id=2432&st=5&sl=0] blank page Belgium JUG 2011 - Integration with Apache ServiceMix and Camel by Charles Moulliard [http://www.parleys.com/#id=2601&st=5] blank page Devoxx 2011 - Introduction to Apache ActiveMQ, ServiceMix [https://devoxx.com/display/DV11/Introduction+to+Apache+ActiveMQ,+ServiceMix,+Camel+and+CXF] blank page errors on html structure Devoxx 2010 talk [http://www.parleys.com/#id=2158&st=5] blank page errors on html structure at Øredev 2008 conference [http://www.oredev.com/] 404 not found Devoxx 2009 talk [http://www.parleys.com/#sl=11&st=5&id=1577] blank page Medium Resolution [http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-medium-resolution/] unreachable High Resolution [http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-high-resolution/] unreachable Taking Camel for a ride [http://bsnyderblog.blogspot.com/2008/05/activemq-and-servicemix-at-apachecon-us.html] time out JavaZone Conference - Taking Apache Camel for a Rider [http://www4.java.no/incogito/session/Taking+Apache+Camel+for+a+Ride.html] time out Screencast/Demo of Smooks and Apache Camel processing UN/EDIFACT [http://www.screencast.com/users/tfennelly/folders/Camtasia/media/c3cef9dd-e667-41ac-8597-74ca01d39968] Not found Facebook integration Apache Camel [http://screencasts.chariotsolutions.com/facebook-integration-using-apache-camel] not found Advanced AEM Search - Consuming External Content [http://www.circuitdevcon.com/en/session-videos/aem-search-apache-camel.html] HTTP ERROR 503 Articles Integration with Apache Camel - Part I - Will get you over [http://jaxenter.com/jax-magazine/JAX-Magazine-2013-05] not found Simple DSL OSGi bundle example by Andrej Koelewijn [http://www.andrejkoelewijn.com/wp/2008/10/19/simple-camel-dsl-osgi-bundle-example/] not found Realization of EAI Patterns with Apache Camel by Pascal Kolb [http://elib.uni-stuttgart.de/opus/volltexte/2008/3520/pdf/STUD_2127.pdf] OPUS-ID 3520 nicht gefunden! (redirect error) First step with Apache Camel by Lukasz Budnik [http://jee-bpel-soa.blogspot.com/2009/12/first-steps-with-apache-camel.html] Sorry, the page you were looking for in this blog does not exist. LEGO Java: Apache Camel Context and Route Basics [http://www.canoo.com/blog/2011/03/14/lego-java-apache-camel-context-and-route-basics/] not found LEGO® Java (II): Apache Camel Error Handling, [http://www.canoo.com/blog/2011/03/16/lego-java-ii-apache-camel-error-handling-java-beans-and-web-services/] not found What is Camel? a short blog [http://bushorn.com/what-is-camel/] Error establishing a database connection A bit more meat: Camel applied : JMS to File [http://mikemclean.ca/muse/2009/05/a-bit-more-meat-camel-applied-jms-to-file/] not found Spring Remoting with JMS Example on Amin Abbaspour’s Weblog the second link [http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html] Le blog a été supprimé blog removed Camel routes and HL7 by Roger Searjeant [http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html] => blog removed Leverage EIP with Apache Camel and Twitter [http://blog.brunoborges.com.br/2009/03/leverage-eip-with-apache-camel-and.html] ERR_NAME_NOT_RESOLVED Camel, CXF and JMS by Example by Silvester van der Bijl [http://blog.software-art.nl/2009/11/15/camel-cxf-and-jms-by-example/] time out A simple file monitorin
[jira] [Updated] (CAMEL-13809) many erroneous links in the doc
[ https://issues.apache.org/jira/browse/CAMEL-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terrien Jean-Yves updated CAMEL-13809: -- Environment: (was: https://camel.apache.org/staging/community/articles/ videos Wild Flies and A Camel https://www.youtube.com/watch?v=o8ZRE9DM3Es video not found Camel in the cloud using Fuse Fabric http://fuse.fusesource.org/fabric/ time out Getting started with Apache Camel - Video presentation from Javagruppen https://javagruppen.dk/index.php/moder/historiske-moder/285-javagruppemode-115-apache-camel-i-aarhus 404 Apache Camel Essential Components by Christian Posta http://blip.tv/dzone/apache-camel-essential-components-6511579 Error 523 CamelOne 2012 Videos - All the videos http://fusesource.com/apache-camel-conference-2012/camelone_speakers_2012/ and http://fusesource.com/apache-camel-conference-2012 redirect to jboss.org CamelOne 2011 Video presentations CamelOne 2011 conference (May 2011) all links redirected to jboss.org Paris JUG 2011 - Integration with Apache Camel and ESB by Charles Moulliard http://www.parleys.com/#id=2432&st=5&sl=0 blank page Belgium JUG 2011 - Integration with Apache ServiceMix and Camel by Charles Moulliard http://www.parleys.com/#id=2601&st=5 blank page Devoxx 2011 - Introduction to Apache ActiveMQ, ServiceMix https://devoxx.com/display/DV11/Introduction+to+Apache+ActiveMQ,+ServiceMix,+Camel+and+CXF blank page errors on html structure Devoxx 2010 talk http://www.parleys.com/#id=2158&st=5 blank page errors on html structure at Øredev 2008 conference http://www.oredev.com/ 404 not found Devoxx 2009 talk http://www.parleys.com/#sl=11&st=5&id=1577 blank page Medium Resolution http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-medium-resolution/ unreachable High Resolution http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-high-resolution/ unreachable Taking Camel for a ride http://bsnyderblog.blogspot.com/2008/05/activemq-and-servicemix-at-apachecon-us.html time out JavaZone Conference - Taking Apache Camel for a Rider http://www4.java.no/incogito/session/Taking+Apache+Camel+for+a+Ride.html time out Screencast/Demo of Smooks and Apache Camel processing UN/EDIFACT http://www.screencast.com/users/tfennelly/folders/Camtasia/media/c3cef9dd-e667-41ac-8597-74ca01d39968 Not found Facebook integration Apache Camel http://screencasts.chariotsolutions.com/facebook-integration-using-apache-camel not found Advanced AEM Search - Consuming External Content http://www.circuitdevcon.com/en/session-videos/aem-search-apache-camel.html HTTP ERROR 503 Articles Integration with Apache Camel - Part I - Will get you over http://jaxenter.com/jax-magazine/JAX-Magazine-2013-05 not found Simple DSL OSGi bundle example by Andrej Koelewijn http://www.andrejkoelewijn.com/wp/2008/10/19/simple-camel-dsl-osgi-bundle-example/ not found Realization of EAI Patterns with Apache Camel by Pascal Kolb http://elib.uni-stuttgart.de/opus/volltexte/2008/3520/pdf/STUD_2127.pdf OPUS-ID 3520 nicht gefunden! (redirect error) First step with Apache Camel by Lukasz Budnik http://jee-bpel-soa.blogspot.com/2009/12/first-steps-with-apache-camel.html Sorry, the page you were looking for in this blog does not exist. LEGO Java: Apache Camel Context and Route Basics http://www.canoo.com/blog/2011/03/14/lego-java-apache-camel-context-and-route-basics/ not found LEGO® Java (II): Apache Camel Error Handling, http://www.canoo.com/blog/2011/03/16/lego-java-ii-apache-camel-error-handling-java-beans-and-web-services/ not found What is Camel? a short blog http://bushorn.com/what-is-camel/ Error establishing a database connection A bit more meat: Camel applied : JMS to File http://mikemclean.ca/muse/2009/05/a-bit-more-meat-camel-applied-jms-to-file/ not found Spring Remoting with JMS Example on Amin Abbaspour’s Weblog the second link http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html Le blog a été supprimé blog removed Camel routes and HL7 by Roger Searjeant http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html => blog removed Leverage EIP with Apache Camel and Twitter http://blog.brunoborges.com.br/2009/03/leverage-eip-with-apache-camel-and.html ERR_NAME_NOT_RESOLVED Camel, CXF and JMS by Example by Silvester van der Bijl http://blog.software-art.nl/2009/11/15/camel-cxf-and-jms-by-example/ time out A simple file monitoring console with camel, cometd and jquery http://www.andrejkoelewijn.com/wp/2009/10/27/simple-log-console-with-camel-and-cometd/ not found A composite REST service using Apache Camel by Andrej Koelewijn http://www.andrejkoelewijn.com/wp/2010/06/13/a-composite-rest-service-using-camel/ not found Using Apache Camel to route SOAP calls through message queues by Glen Mazza http://www.jroller.com/gmazza/entry/camel_jms_and_soap time out Using Apache Camel to route
[jira] [Commented] (CAMEL-13809) many erroneous links in the doc
[ https://issues.apache.org/jira/browse/CAMEL-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16897875#comment-16897875 ] Terrien Jean-Yves commented on CAMEL-13809: --- OK, je vais éditer la page articles.md. Je vais essayer de trouver les publications si elles existent encore. Je posterais le résultat ici en pièce jointe. Sincerely JYT > many erroneous links in the doc > --- > > Key: CAMEL-13809 > URL: https://issues.apache.org/jira/browse/CAMEL-13809 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Terrien Jean-Yves >Priority: Major > > Hi, > many erroneous links in the doc > I manually passed all links on the page. I read the returns to make sure > they were still valid. > when there was manual redirection I followed the link to check it. > here is the list of errors that I found. > a not about fusesource. all fusesource links are redirected to > www.jboss.org. this does not allow to find the targeted document. > hoping that this can be helpful. > [https://camel.apache.org/staging/community/articles/] > videos > Wild Flies and A Camel [https://www.youtube.com/watch?v=o8ZRE9DM3Es] video > not found > Camel in the cloud using Fuse Fabric [http://fuse.fusesource.org/fabric/] > time out > Getting started with Apache Camel - Video presentation from Javagruppen > [https://javagruppen.dk/index.php/moder/historiske-moder/285-javagruppemode-115-apache-camel-i-aarhus] > 404 > Apache Camel Essential Components by Christian Posta > [http://blip.tv/dzone/apache-camel-essential-components-6511579] Error 523 > CamelOne 2012 Videos - All the videos > [http://fusesource.com/apache-camel-conference-2012/camelone_speakers_2012/] > and [http://fusesource.com/apache-camel-conference-2012] redirect to jboss.org > CamelOne 2011 Video presentations CamelOne 2011 conference (May 2011) all > links redirected to jboss.org > Paris JUG 2011 - Integration with Apache Camel and ESB by Charles Moulliard > [http://www.parleys.com/#id=2432&st=5&sl=0] blank page > Belgium JUG 2011 - Integration with Apache ServiceMix and Camel by Charles > Moulliard [http://www.parleys.com/#id=2601&st=5] blank page > Devoxx 2011 - Introduction to Apache ActiveMQ, ServiceMix > [https://devoxx.com/display/DV11/Introduction+to+Apache+ActiveMQ,+ServiceMix,+Camel+and+CXF] > blank page errors on html structure > Devoxx 2010 talk [http://www.parleys.com/#id=2158&st=5] blank page errors on > html structure > at Øredev 2008 conference [http://www.oredev.com/] 404 not found > Devoxx 2009 talk [http://www.parleys.com/#sl=11&st=5&id=1577] blank page > Medium Resolution > [http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-medium-resolution/] > unreachable > High Resolution > [http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-high-resolution/] > unreachable > Taking Camel for a ride > [http://bsnyderblog.blogspot.com/2008/05/activemq-and-servicemix-at-apachecon-us.html] > time out > JavaZone Conference - Taking Apache Camel for a Rider > [http://www4.java.no/incogito/session/Taking+Apache+Camel+for+a+Ride.html] > time out > Screencast/Demo of Smooks and Apache Camel processing UN/EDIFACT > [http://www.screencast.com/users/tfennelly/folders/Camtasia/media/c3cef9dd-e667-41ac-8597-74ca01d39968] > Not found > Facebook integration Apache Camel > [http://screencasts.chariotsolutions.com/facebook-integration-using-apache-camel] > not found > Advanced AEM Search - Consuming External Content > [http://www.circuitdevcon.com/en/session-videos/aem-search-apache-camel.html] > HTTP ERROR 503 > Articles > Integration with Apache Camel - Part I - Will get you over > [http://jaxenter.com/jax-magazine/JAX-Magazine-2013-05] not found > Simple DSL OSGi bundle example by Andrej Koelewijn > [http://www.andrejkoelewijn.com/wp/2008/10/19/simple-camel-dsl-osgi-bundle-example/] > not found > Realization of EAI Patterns with Apache Camel by Pascal Kolb > [http://elib.uni-stuttgart.de/opus/volltexte/2008/3520/pdf/STUD_2127.pdf] > OPUS-ID 3520 nicht gefunden! (redirect error) > First step with Apache Camel by Lukasz Budnik > [http://jee-bpel-soa.blogspot.com/2009/12/first-steps-with-apache-camel.html] > Sorry, the page you were looking for in this blog does not exist. > LEGO Java: Apache Camel Context and Route Basics > [http://www.canoo.com/blog/2011/03/14/lego-java-apache-camel-context-and-route-basics/] > not found > LEGO® Java (II): Apache Camel Error Handling, > [http://www.canoo.com/blog/2011/03/16/lego-java-ii-apache-camel-error-handling-java-beans-and-web-services/] > not found > What is Camel? a short blog [http://bushorn.com/what-is-camel/] Error > establishing a database connection > A bit more meat: Camel applied : JMS to
[jira] [Comment Edited] (CAMEL-13809) many erroneous links in the doc
[ https://issues.apache.org/jira/browse/CAMEL-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16897875#comment-16897875 ] Terrien Jean-Yves edited comment on CAMEL-13809 at 8/1/19 8:33 AM: --- OK, I will edit the articles.md page. I will try to find the publications if they still exist. I will post the result here as an attachment. Sincerely JYT was (Author: sekaijin): OK, je vais éditer la page articles.md. Je vais essayer de trouver les publications si elles existent encore. Je posterais le résultat ici en pièce jointe. Sincerely JYT > many erroneous links in the doc > --- > > Key: CAMEL-13809 > URL: https://issues.apache.org/jira/browse/CAMEL-13809 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Terrien Jean-Yves >Priority: Major > > Hi, > many erroneous links in the doc > I manually passed all links on the page. I read the returns to make sure > they were still valid. > when there was manual redirection I followed the link to check it. > here is the list of errors that I found. > a not about fusesource. all fusesource links are redirected to > www.jboss.org. this does not allow to find the targeted document. > hoping that this can be helpful. > [https://camel.apache.org/staging/community/articles/] > videos > Wild Flies and A Camel [https://www.youtube.com/watch?v=o8ZRE9DM3Es] video > not found > Camel in the cloud using Fuse Fabric [http://fuse.fusesource.org/fabric/] > time out > Getting started with Apache Camel - Video presentation from Javagruppen > [https://javagruppen.dk/index.php/moder/historiske-moder/285-javagruppemode-115-apache-camel-i-aarhus] > 404 > Apache Camel Essential Components by Christian Posta > [http://blip.tv/dzone/apache-camel-essential-components-6511579] Error 523 > CamelOne 2012 Videos - All the videos > [http://fusesource.com/apache-camel-conference-2012/camelone_speakers_2012/] > and [http://fusesource.com/apache-camel-conference-2012] redirect to jboss.org > CamelOne 2011 Video presentations CamelOne 2011 conference (May 2011) all > links redirected to jboss.org > Paris JUG 2011 - Integration with Apache Camel and ESB by Charles Moulliard > [http://www.parleys.com/#id=2432&st=5&sl=0] blank page > Belgium JUG 2011 - Integration with Apache ServiceMix and Camel by Charles > Moulliard [http://www.parleys.com/#id=2601&st=5] blank page > Devoxx 2011 - Introduction to Apache ActiveMQ, ServiceMix > [https://devoxx.com/display/DV11/Introduction+to+Apache+ActiveMQ,+ServiceMix,+Camel+and+CXF] > blank page errors on html structure > Devoxx 2010 talk [http://www.parleys.com/#id=2158&st=5] blank page errors on > html structure > at Øredev 2008 conference [http://www.oredev.com/] 404 not found > Devoxx 2009 talk [http://www.parleys.com/#sl=11&st=5&id=1577] blank page > Medium Resolution > [http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-medium-resolution/] > unreachable > High Resolution > [http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-high-resolution/] > unreachable > Taking Camel for a ride > [http://bsnyderblog.blogspot.com/2008/05/activemq-and-servicemix-at-apachecon-us.html] > time out > JavaZone Conference - Taking Apache Camel for a Rider > [http://www4.java.no/incogito/session/Taking+Apache+Camel+for+a+Ride.html] > time out > Screencast/Demo of Smooks and Apache Camel processing UN/EDIFACT > [http://www.screencast.com/users/tfennelly/folders/Camtasia/media/c3cef9dd-e667-41ac-8597-74ca01d39968] > Not found > Facebook integration Apache Camel > [http://screencasts.chariotsolutions.com/facebook-integration-using-apache-camel] > not found > Advanced AEM Search - Consuming External Content > [http://www.circuitdevcon.com/en/session-videos/aem-search-apache-camel.html] > HTTP ERROR 503 > Articles > Integration with Apache Camel - Part I - Will get you over > [http://jaxenter.com/jax-magazine/JAX-Magazine-2013-05] not found > Simple DSL OSGi bundle example by Andrej Koelewijn > [http://www.andrejkoelewijn.com/wp/2008/10/19/simple-camel-dsl-osgi-bundle-example/] > not found > Realization of EAI Patterns with Apache Camel by Pascal Kolb > [http://elib.uni-stuttgart.de/opus/volltexte/2008/3520/pdf/STUD_2127.pdf] > OPUS-ID 3520 nicht gefunden! (redirect error) > First step with Apache Camel by Lukasz Budnik > [http://jee-bpel-soa.blogspot.com/2009/12/first-steps-with-apache-camel.html] > Sorry, the page you were looking for in this blog does not exist. > LEGO Java: Apache Camel Context and Route Basics > [http://www.canoo.com/blog/2011/03/14/lego-java-apache-camel-context-and-route-basics/] > not found > LEGO® Java (II): Apache Camel Error Handling, > [http://www.canoo.com/blog/2011/03/16/lego-java-
[jira] [Commented] (CAMEL-13809) many erroneous links in the doc
[ https://issues.apache.org/jira/browse/CAMEL-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16898925#comment-16898925 ] Terrien Jean-Yves commented on CAMEL-13809: --- Hi I am posting you the progress of my work. *: I treated or started to process the error * removed =>: link removed * replaced =>: link replaced * mail =>: I contacted the author and the answer and waiting. without *: to do I do not know what to do for devoxx. the pages exist but contain errors and therefore do not appear. I contacted the site. for camelone I do not know if it's worth going back to archives that do not contain much. https://camel.apache.org/staging/community/articles/ videos * removed => Wild Flies and A Camel https://www.youtube.com/watch?v=o8ZRE9DM3Es video not found * mail claus => Camel in the cloud using Fuse Fabric http://fuse.fusesource.org/fabric/ time out * removed => Getting started with Apache Camel - Video presentation from Javagruppen https://javagruppen.dk/index.php/moder/historiske-moder/285-javagruppemode-115-apache-camel-i-aarhus 404 * replaced => Apache Camel Essential Components by Christian Posta http://blip.tv/dzone/apache-camel-essential-components-6511579 Error 523 CamelOne 2012 Videos - All the videos http://fusesource.com/apache-camel-conference-2012/camelone_speakers_2012/ and http://fusesource.com/apache-camel-conference-2012 redirect to jboss.org CamelOne 2011 Video presentations CamelOne 2011 conference (May 2011) all links redirected to jboss.org * Replaced => Paris JUG 2011 - Integration with Apache Camel and ESB by Charles Moulliard http://www.parleys.com/#id=2432&st=5&sl=0 blank page * mail => Belgium JUG 2011 - Integration with Apache ServiceMix and Camel by Charles Moulliard http://www.parleys.com/#id=2601&st=5 blank page * mail => Devoxx 2011 - Introduction to Apache ActiveMQ, ServiceMix https://devoxx.com/display/DV11/Introduction+to+Apache+ActiveMQ,+ServiceMix,+Camel+and+CXF blank page errors on html structure * mail => Devoxx 2010 talk http://www.parleys.com/#id=2158&st=5 blank page errors on html structure at Øredev 2008 conference http://www.oredev.com/ 404 not found * mail => Devoxx 2009 talk http://www.parleys.com/#sl=11&st=5&id=1577 blank page Medium Resolution http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-medium-resolution/ unreachable High Resolution http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-high-resolution/ unreachable Taking Camel for a ride http://bsnyderblog.blogspot.com/2008/05/activemq-and-servicemix-at-apachecon-us.html time out JavaZone Conference - Taking Apache Camel for a Rider http://www4.java.no/incogito/session/Taking+Apache+Camel+for+a+Ride.html time out * removed => Screencast/Demo of Smooks and Apache Camel processing UN/EDIFACT http://www.screencast.com/users/tfennelly/folders/Camtasia/media/c3cef9dd-e667-41ac-8597-74ca01d39968 Not found Facebook integration Apache Camel http://screencasts.chariotsolutions.com/facebook-integration-using-apache-camel not found Advanced AEM Search - Consuming External Content http://www.circuitdevcon.com/en/session-videos/aem-search-apache-camel.html HTTP ERROR 503 Articles Integration with Apache Camel - Part I - Will get you over http://jaxenter.com/jax-magazine/JAX-Magazine-2013-05 not found Simple DSL OSGi bundle example by Andrej Koelewijn http://www.andrejkoelewijn.com/wp/2008/10/19/simple-camel-dsl-osgi-bundle-example/ not found Realization of EAI Patterns with Apache Camel by Pascal Kolb http://elib.uni-stuttgart.de/opus/volltexte/2008/3520/pdf/STUD_2127.pdf OPUS-ID 3520 nicht gefunden! (redirect error) First step with Apache Camel by Lukasz Budnik http://jee-bpel-soa.blogspot.com/2009/12/first-steps-with-apache-camel.html Sorry, the page you were looking for in this blog does not exist. LEGO Java: Apache Camel Context and Route Basics http://www.canoo.com/blog/2011/03/14/lego-java-apache-camel-context-and-route-basics/ not found LEGO® Java (II): Apache Camel Error Handling, http://www.canoo.com/blog/2011/03/16/lego-java-ii-apache-camel-error-handling-java-beans-and-web-services/ not found What is Camel? a short blog http://bushorn.com/what-is-camel/ Error establishing a database connection A bit more meat: Camel applied : JMS to File http://mikemclean.ca/muse/2009/05/a-bit-more-meat-camel-applied-jms-to-file/ not found Spring Remoting with JMS Example on Amin Abbaspour’s Weblog the second link http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html Le blog a été supprimé blog removed Camel routes and HL7 by Roger Searjeant http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html => blog removed Leverage EIP with Apache Camel and Twitter http://blog.brunoborges.com.br/2009/03/leverage-eip-with-apache-camel-and.html ERR_NAME_NOT_RESOLVED Camel, CXF and JMS by Example by Sil
[jira] [Created] (CAMEL-13824) the documentation references a deleted component
Terrien Jean-Yves created CAMEL-13824: - Summary: the documentation references a deleted component Key: CAMEL-13824 URL: https://issues.apache.org/jira/browse/CAMEL-13824 Project: Camel Issue Type: Task Components: camel-mongodb, camel-mongodb3 Reporter: Terrien Jean-Yves [https://camel.apache.org/staging/components/latest/mongodb-component.html] the documentation refers to the older version. "Note: MongoDB Camel component Use the Mongo Driver for Java 3.x. If your are looking for previews versions look the Camel MongoDB component." This corresponds to the doc of the older Camel MongoDB 3 component (using v3 driver). which referenced the older MongoDB Camel component (using V2 driver) But the MongoDB Camel component (using V2 driver) has been removed and the component Camel MongoDB 3 component (using v3 driver) renamed Camel MongoDB component (using v3 driver). The doc must be retifyed to no longer refer to the deleted version. I propose to simply put "Note: MongoDB Camel component Use the Mongo Driver for Java 3.x." I have not followed mongodb these last time, but it seems to me that there is a V4 driver. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-13824) the documentation references a deleted component
[ https://issues.apache.org/jira/browse/CAMEL-13824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16899503#comment-16899503 ] Terrien Jean-Yves commented on CAMEL-13824: --- My memory fails me. the drivers versions 3.8 and up are compatible with mongodb 4. camel uses 3.10.2 (latest) everything is ok on this side. > the documentation references a deleted component > > > Key: CAMEL-13824 > URL: https://issues.apache.org/jira/browse/CAMEL-13824 > Project: Camel > Issue Type: Task > Components: camel-mongodb, camel-mongodb3 >Reporter: Terrien Jean-Yves >Priority: Major > > [https://camel.apache.org/staging/components/latest/mongodb-component.html] > the documentation refers to the older version. > "Note: MongoDB Camel component Use the Mongo Driver for Java 3.x. If your are > looking for previews versions look the Camel MongoDB component." > This corresponds to the doc of the older Camel MongoDB 3 component (using v3 > driver). which referenced the older MongoDB Camel component (using V2 driver) > But the MongoDB Camel component (using V2 driver) has been removed and the > component Camel MongoDB 3 component (using v3 driver) renamed Camel MongoDB > component (using v3 driver). > The doc must be retifyed to no longer refer to the deleted version. > I propose to simply put > "Note: MongoDB Camel component Use the Mongo Driver for Java 3.x." > I have not followed mongodb these last time, but it seems to me that there is > a V4 driver. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-13809) many erroneous links in the doc
[ https://issues.apache.org/jira/browse/CAMEL-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terrien Jean-Yves updated CAMEL-13809: -- Attachment: articles.md > many erroneous links in the doc > --- > > Key: CAMEL-13809 > URL: https://issues.apache.org/jira/browse/CAMEL-13809 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Terrien Jean-Yves >Priority: Major > Attachments: articles.md > > > Hi, > many erroneous links in the doc > I manually passed all links on the page. I read the returns to make sure > they were still valid. > when there was manual redirection I followed the link to check it. > here is the list of errors that I found. > a not about fusesource. all fusesource links are redirected to > www.jboss.org. this does not allow to find the targeted document. > hoping that this can be helpful. > [https://camel.apache.org/staging/community/articles/] > videos > Wild Flies and A Camel [https://www.youtube.com/watch?v=o8ZRE9DM3Es] video > not found > Camel in the cloud using Fuse Fabric [http://fuse.fusesource.org/fabric/] > time out > Getting started with Apache Camel - Video presentation from Javagruppen > [https://javagruppen.dk/index.php/moder/historiske-moder/285-javagruppemode-115-apache-camel-i-aarhus] > 404 > Apache Camel Essential Components by Christian Posta > [http://blip.tv/dzone/apache-camel-essential-components-6511579] Error 523 > CamelOne 2012 Videos - All the videos > [http://fusesource.com/apache-camel-conference-2012/camelone_speakers_2012/] > and [http://fusesource.com/apache-camel-conference-2012] redirect to jboss.org > CamelOne 2011 Video presentations CamelOne 2011 conference (May 2011) all > links redirected to jboss.org > Paris JUG 2011 - Integration with Apache Camel and ESB by Charles Moulliard > [http://www.parleys.com/#id=2432&st=5&sl=0] blank page > Belgium JUG 2011 - Integration with Apache ServiceMix and Camel by Charles > Moulliard [http://www.parleys.com/#id=2601&st=5] blank page > Devoxx 2011 - Introduction to Apache ActiveMQ, ServiceMix > [https://devoxx.com/display/DV11/Introduction+to+Apache+ActiveMQ,+ServiceMix,+Camel+and+CXF] > blank page errors on html structure > Devoxx 2010 talk [http://www.parleys.com/#id=2158&st=5] blank page errors on > html structure > at Øredev 2008 conference [http://www.oredev.com/] 404 not found > Devoxx 2009 talk [http://www.parleys.com/#sl=11&st=5&id=1577] blank page > Medium Resolution > [http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-medium-resolution/] > unreachable > High Resolution > [http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-high-resolution/] > unreachable > Taking Camel for a ride > [http://bsnyderblog.blogspot.com/2008/05/activemq-and-servicemix-at-apachecon-us.html] > time out > JavaZone Conference - Taking Apache Camel for a Rider > [http://www4.java.no/incogito/session/Taking+Apache+Camel+for+a+Ride.html] > time out > Screencast/Demo of Smooks and Apache Camel processing UN/EDIFACT > [http://www.screencast.com/users/tfennelly/folders/Camtasia/media/c3cef9dd-e667-41ac-8597-74ca01d39968] > Not found > Facebook integration Apache Camel > [http://screencasts.chariotsolutions.com/facebook-integration-using-apache-camel] > not found > Advanced AEM Search - Consuming External Content > [http://www.circuitdevcon.com/en/session-videos/aem-search-apache-camel.html] > HTTP ERROR 503 > Articles > Integration with Apache Camel - Part I - Will get you over > [http://jaxenter.com/jax-magazine/JAX-Magazine-2013-05] not found > Simple DSL OSGi bundle example by Andrej Koelewijn > [http://www.andrejkoelewijn.com/wp/2008/10/19/simple-camel-dsl-osgi-bundle-example/] > not found > Realization of EAI Patterns with Apache Camel by Pascal Kolb > [http://elib.uni-stuttgart.de/opus/volltexte/2008/3520/pdf/STUD_2127.pdf] > OPUS-ID 3520 nicht gefunden! (redirect error) > First step with Apache Camel by Lukasz Budnik > [http://jee-bpel-soa.blogspot.com/2009/12/first-steps-with-apache-camel.html] > Sorry, the page you were looking for in this blog does not exist. > LEGO Java: Apache Camel Context and Route Basics > [http://www.canoo.com/blog/2011/03/14/lego-java-apache-camel-context-and-route-basics/] > not found > LEGO® Java (II): Apache Camel Error Handling, > [http://www.canoo.com/blog/2011/03/16/lego-java-ii-apache-camel-error-handling-java-beans-and-web-services/] > not found > What is Camel? a short blog [http://bushorn.com/what-is-camel/] Error > establishing a database connection > A bit more meat: Camel applied : JMS to File > [http://mikemclean.ca/muse/2009/05/a-bit-more-meat-camel-applied-jms-to-file/] > not found > Spring Remoting with JMS Example on Amin Abbaspour’s Weblog the
[jira] [Commented] (CAMEL-13809) many erroneous links in the doc
[ https://issues.apache.org/jira/browse/CAMEL-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16901268#comment-16901268 ] Terrien Jean-Yves commented on CAMEL-13809: --- https://camel.apache.org/staging/community/articles/ videos * removed => Wild Flies and A Camel https://www.youtube.com/watch?v=o8ZRE9DM3Es video not found * replaced => Camel in the cloud using Fuse Fabric http://fuse.fusesource.org/fabric/ time out * removed => Getting started with Apache Camel - Video presentation from Javagruppen https://javagruppen.dk/index.php/moder/historiske-moder/285-javagruppemode-115-apache-camel-i-aarhus 404 * replaced => Apache Camel Essential Components by Christian Posta http://blip.tv/dzone/apache-camel-essential-components-6511579 Error 523 * replaced => CamelOne 2012 Videos - All the videos http://fusesource.com/apache-camel-conference-2012/camelone_speakers_2012/ and http://fusesource.com/apache-camel-conference-2012 redirect to jboss.org * replaced => CamelOne 2011 Video presentations CamelOne 2011 conference (May 2011) all links redirected to jboss.org * Replaced => Paris JUG 2011 - Integration with Apache Camel and ESB by Charles Moulliard http://www.parleys.com/#id=2432&st=5&sl=0 blank page * removed => Belgium JUG 2011 - Integration with Apache ServiceMix and Camel by Charles Moulliard http://www.parleys.com/#id=2601&st=5 blank page * removed => Devoxx 2011 - Introduction to Apache ActiveMQ, ServiceMix https://devoxx.com/display/DV11/Introduction+to+Apache+ActiveMQ,+ServiceMix,+Camel+and+CXF blank page errors on html structure * removed => Devoxx 2010 talk http://www.parleys.com/#id=2158&st=5 blank page errors on html structure * replaced => at Øredev 2008 conference http://www.oredev.com/ 404 not found * removed => Devoxx 2009 talk http://www.parleys.com/#sl=11&st=5&id=1577 blank page * replaced => Medium Resolution http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-medium-resolution/ unreachable * replaced => High Resolution http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-high-resolution/ unreachable * Ok => Taking Camel for a ride http://bsnyderblog.blogspot.com/2008/05/activemq-and-servicemix-at-apachecon-us.html time out * removed => JavaZone Conference - Taking Apache Camel for a Rider http://www4.java.no/incogito/session/Taking+Apache+Camel+for+a+Ride.html time out * removed => Screencast/Demo of Smooks and Apache Camel processing UN/EDIFACT http://www.screencast.com/users/tfennelly/folders/Camtasia/media/c3cef9dd-e667-41ac-8597-74ca01d39968 Not found * replaced => Facebook integration Apache Camel http://screencasts.chariotsolutions.com/facebook-integration-using-apache-camel not found * replaced => Advanced AEM Search - Consuming External Content http://www.circuitdevcon.com/en/session-videos/aem-search-apache-camel.html HTTP ERROR 503 Articles * replaced => Integration with Apache Camel - Part I - Will get you over http://jaxenter.com/jax-magazine/JAX-Magazine-2013-05 not found * replaced => Simple DSL OSGi bundle example by Andrej Koelewijn http://www.andrejkoelewijn.com/wp/2008/10/19/simple-camel-dsl-osgi-bundle-example/ not found * replaced => Realization of EAI Patterns with Apache Camel by Pascal Kolb http://elib.uni-stuttgart.de/opus/volltexte/2008/3520/pdf/STUD_2127.pdf OPUS-ID 3520 nicht gefunden! (redirect error) * replaced => First step with Apache Camel by Lukasz Budnik http://jee-bpel-soa.blogspot.com/2009/12/first-steps-with-apache-camel.html Sorry, the page you were looking for in this blog does not exist. * removed => LEGO Java: Apache Camel Context and Route Basics http://www.canoo.com/blog/2011/03/14/lego-java-apache-camel-context-and-route-basics/ not found * removed => LEGO® Java (II): Apache Camel Error Handling, http://www.canoo.com/blog/2011/03/16/lego-java-ii-apache-camel-error-handling-java-beans-and-web-services/ not found * removed => What is Camel? a short blog http://bushorn.com/what-is-camel/ Error establishing a database connection * removed => A bit more meat: Camel applied : JMS to File http://mikemclean.ca/muse/2009/05/a-bit-more-meat-camel-applied-jms-to-file/ not found * removed => Spring Remoting with JMS Example on Amin Abbaspour’s Weblog the second link http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html Le blog a été supprimé blog removed * removed => Camel routes and HL7 by Roger Searjeant http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html => blog removed * removed => Leverage EIP with Apache Camel and Twitter http://blog.brunoborges.com.br/2009/03/leverage-eip-with-apache-camel-and.html ERR_NAME_NOT_RESOLVED * removed => Camel, CXF and JMS by Example by Silvester van der Bijl http://blog.software-art.nl/2009/11/15/camel-cxf-and-jms-by-example/ time out * replaced => A simple file monitoring console with camel, cometd and jquery h
[jira] [Created] (CAMEL-15511) wrap async-http-client in camel-karaf feature
Terrien Jean-Yves created CAMEL-15511:
-
Summary: wrap async-http-client in camel-karaf feature
Key: CAMEL-15511
URL: https://issues.apache.org/jira/browse/CAMEL-15511
Project: Camel
Issue Type: Improvement
Components: karaf
Affects Versions: 3.5.0, 3.4.3
Reporter: Terrien Jean-Yves
the camel-ahc feature add async-http-client and async-http-client-netty-utils
with wrap protocol
wrap:mvn:org.asynchttpclient/async-http-client/${ahc-version}$Export-Package=org.asynchttpclient.*;version=${ahc-version}
wrap:mvn:org.asynchttpclient/async-http-client-netty-utils/${ahc-version}$Export-Package=org.asynchttpclient.netty.util.*;version=${ahc-version}
but sync-http-client.jar and async-http-client-netty-utils.jar are bundles with
an osgi manifest
Bnd-LastModified: 1586331593189
Build-Jdk: 1.8.0_242
Built-By: slandelle
Bundle-Description: The Async Http Client (AHC) classes.
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt
Bundle-ManifestVersion: 2
Bundle-Name: Asynchronous Http Client
Bundle-SymbolicName: org.asynchttpclient.async-http-client
Bundle-Vendor: The AsyncHttpClient Project
Bundle-Version: 2.12.1
Created-By: Apache Maven Bundle Plugin
...
Manifest-Version: 1.0
Bnd-LastModified: 1586331569314
Build-Jdk: 1.8.0_242
Built-By: slandelle
Bundle-Description: The Async Http Client (AHC) library's purpose is to
allow Java applications to easily execute HTTP requests and async
hronously process the response.
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt
Bundle-ManifestVersion: 2
Bundle-Name: Asynchronous Http Client Netty Utils
Bundle-SymbolicName: org.asynchttpclient.async-http-client-netty-utils
Bundle-Vendor: The AsyncHttpClient Project
Bundle-Version: 2.12.1
Created-By: Apache Maven Bundle Plugin
...
I propose to replace them with
mvn:org.asynchttpclient/async-http-client/${ahc-version}/bundle>
mvn:org.asynchttpclient/async-http-client-netty-utils/${ahc-version}
Bye
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15511) wrap async-http-client in camel-karaf feature
[
https://issues.apache.org/jira/browse/CAMEL-15511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192042#comment-17192042
]
Terrien Jean-Yves commented on CAMEL-15511:
---
Sorry
The same goes with
wrap:mvn:com.typesafe.netty/netty-reactive-streams/$
\{netty-reactive-streams-version}
> wrap async-http-client in camel-karaf feature
> -
>
> Key: CAMEL-15511
> URL: https://issues.apache.org/jira/browse/CAMEL-15511
> Project: Camel
> Issue Type: Improvement
> Components: karaf
>Affects Versions: 3.4.3, 3.5.0
>Reporter: Terrien Jean-Yves
>Priority: Major
>
> the camel-ahc feature add async-http-client and async-http-client-netty-utils
> with wrap protocol
> dependency='true'>wrap:mvn:org.asynchttpclient/async-http-client/${ahc-version}$Export-Package=org.asynchttpclient.*;version=${ahc-version}
> dependency='true'>wrap:mvn:org.asynchttpclient/async-http-client-netty-utils/${ahc-version}$Export-Package=org.asynchttpclient.netty.util.*;version=${ahc-version}
> but sync-http-client.jar and async-http-client-netty-utils.jar are bundles
> with an osgi manifest
> Bnd-LastModified: 1586331593189
> Build-Jdk: 1.8.0_242
> Built-By: slandelle
> Bundle-Description: The Async Http Client (AHC) classes.
> Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt
> Bundle-ManifestVersion: 2
> Bundle-Name: Asynchronous Http Client
> Bundle-SymbolicName: org.asynchttpclient.async-http-client
> Bundle-Vendor: The AsyncHttpClient Project
> Bundle-Version: 2.12.1
> Created-By: Apache Maven Bundle Plugin
> ...
> Manifest-Version: 1.0
> Bnd-LastModified: 1586331569314
> Build-Jdk: 1.8.0_242
> Built-By: slandelle
> Bundle-Description: The Async Http Client (AHC) library's purpose is to
> allow Java applications to easily execute HTTP requests and async
> hronously process the response.
> Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt
> Bundle-ManifestVersion: 2
> Bundle-Name: Asynchronous Http Client Netty Utils
> Bundle-SymbolicName: org.asynchttpclient.async-http-client-netty-utils
> Bundle-Vendor: The AsyncHttpClient Project
> Bundle-Version: 2.12.1
> Created-By: Apache Maven Bundle Plugin
> ...
>
> I propose to replace them with
> dependency='true'>mvn:org.asynchttpclient/async-http-client/${ahc-version}/bundle>
> dependency='true'>mvn:org.asynchttpclient/async-http-client-netty-utils/${ahc-version}
>
> Bye
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-15513) no symbolic name for Rdf4j in camel-karaf feature
Terrien Jean-Yves created CAMEL-15513:
-
Summary: no symbolic name for Rdf4j in camel-karaf feature
Key: CAMEL-15513
URL: https://issues.apache.org/jira/browse/CAMEL-15513
Project: Camel
Issue Type: Improvement
Components: karaf
Reporter: Terrien Jean-Yves
in camel-any23 features the rdf4j-model and rdf4j-rio-api jars does not have
symbolic name and version
wrap:mvn:org.eclipse.rdf4j/rdf4j-model/${rdf4j-model-version}
wrap:mvn:org.eclipse.rdf4j/rdf4j-rio-api/${rdf4j-rio-version}
I propose to add them
wrap:mvn:org.eclipse.rdf4j/rdf4j-model/${rdf4j-model-version}$Bundle-SymbolicName=rdf4j-model&Bundle-Version=${rdf4j-model-version}
wrap:mvn:org.eclipse.rdf4j/rdf4j-rio-api/${rdf4j-rio-version}$Bundle-SymbolicName=rdf4j-rio-api&Bundle-Version=${rdf4j-rio-version}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-5296) Adding camel-mllp component
[
https://issues.apache.org/jira/browse/CAMEL-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192164#comment-17192164
]
Terrien Jean-Yves commented on CAMEL-5296:
--
[https://camel.apache.org/components/latest/mllp-component.html] Since Camel
2.17
> Adding camel-mllp component
> ---
>
> Key: CAMEL-5296
> URL: https://issues.apache.org/jira/browse/CAMEL-5296
> Project: Camel
> Issue Type: New Feature
> Components: camel-hl7
>Affects Versions: 2.8.0
>Reporter: Terrien Jean-Yves
>Priority: Minor
> Labels: patch
> Attachments: camel-mllp.zip
>
>
> I think a camel-mllp component would be welcome.
> I therefore propose to add it. this would avoid having to add each time the
> same code to set the codec.
> I have in my project numerous endpoint mllp and I noticed that the
> developpers diverge more or less on how to go about it. the code: from
> ("mllp://host:8808") is easy to implement and does not cause confusion.
> So I defined a camel-mllp component which extends camel-mina. this component
> does is create a codec mllp and delegates the rest of the work to Mina. it is
> simple to implement.
> as I suggested Claus Ibsen-2I have built-in HL7 camel.
> http://camel.465427.n5.nabble.com/Suggest-Add-a-camel-mllp-component-into-the-incubator-tt5711304.html
> A+JYT
> PS:I'm not about to have followed the procedure for submitting this proposal.
> Sorry for my approximative english
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15513) no symbolic name for Rdf4j in camel-karaf feature
[
https://issues.apache.org/jira/browse/CAMEL-15513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195947#comment-17195947
]
Terrien Jean-Yves commented on CAMEL-15513:
---
Thank
https://issues.apache.org/jira/browse/KARAF-6853?filter=-2
> no symbolic name for Rdf4j in camel-karaf feature
> -
>
> Key: CAMEL-15513
> URL: https://issues.apache.org/jira/browse/CAMEL-15513
> Project: Camel
> Issue Type: Improvement
> Components: karaf
>Reporter: Terrien Jean-Yves
>Priority: Trivial
>
> in camel-any23 features the rdf4j-model and rdf4j-rio-api jars does not have
> symbolic name and version
> dependency='true'>wrap:mvn:org.eclipse.rdf4j/rdf4j-model/${rdf4j-model-version}
> dependency='true'>wrap:mvn:org.eclipse.rdf4j/rdf4j-rio-api/${rdf4j-rio-version}
> I propose to add them
> dependency='true'>wrap:mvn:org.eclipse.rdf4j/rdf4j-model/${rdf4j-model-version}$Bundle-SymbolicName=rdf4j-model&Bundle-Version=${rdf4j-model-version}
> dependency='true'>wrap:mvn:org.eclipse.rdf4j/rdf4j-rio-api/${rdf4j-rio-version}$Bundle-SymbolicName=rdf4j-rio-api&Bundle-Version=${rdf4j-rio-version}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-12416) standardization of api xpath.
Terrien Jean-Yves created CAMEL-12416:
-
Summary: standardization of api xpath.
Key: CAMEL-12416
URL: https://issues.apache.org/jira/browse/CAMEL-12416
Project: Camel
Issue Type: Improvement
Components: camel-core
Affects Versions: 2.16.2
Reporter: Terrien Jean-Yves
standardization of api xpath.
if you use the syntax .setHeader("name"). xpath (...) it is possible to define
the namespaces.
if you use the syntax .setHeader("name", xpath (...)) you can not specify the
namesapces.
in the syntax .setHeader ("name"). xpath (...) the xpath methods are defined in
ExpressionClauseSupport. these methods use new XPathExpression.
the syntax .setHeader ("name", xpath (...)) the methods are defined in
BuilderSupport. these methods use XPathBuilder
could not we standardize all that to have the same syntax in both cases.?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12417) Camel documentation
Terrien Jean-Yves created CAMEL-12417: - Summary: Camel documentation Key: CAMEL-12417 URL: https://issues.apache.org/jira/browse/CAMEL-12417 Project: Camel Issue Type: Improvement Affects Versions: 2.21.0 Reporter: Terrien Jean-Yves I am rewriting the doc to fit github. [https://github.com/jyterrien/camel/blob/master/readme.adoc] I replaced .md files with .adoc I started correcting the links in readme.adoc contributing.adoc and in camel-core. (in alphabetic order from bean-component to file-component) I did not find, on github, docs like https://camel.apache.org/data-format.html [https://camel.apache.org/enterprise-integration-patterns.html] in every page I've changed the definition = title page I'e added :toc: left and I corrected the links <> link:doc.adoc[Doc] I also when I found the target corrected the relative links like : === See Also * link:file-language.adoc[File Language] * link:../../../../components/camel-ftp/src/main/docs/ftp-component.adoc[FTP] * Polling Consumer as soon as I corrected all camel-core I think to make a pull-request -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12417) Camel documentation
[ https://issues.apache.org/jira/browse/CAMEL-12417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429284#comment-16429284 ] Terrien Jean-Yves commented on CAMEL-12417: --- Hi, I thought I understood that now the doc was no longer generated on camel.apache.org. But she was directly available on Github. But today, it is impossible to navigate in the document on Github. Maybe I'm wrong. in this case where is the documentation? On camel.apapche.org a note gives a link to github and on github the documentation does not allow to navigate. If in the end the documentation must be on github it is not about internal references but the contrary of external references. A + JYT > Camel documentation > --- > > Key: CAMEL-12417 > URL: https://issues.apache.org/jira/browse/CAMEL-12417 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.21.0 >Reporter: Terrien Jean-Yves >Priority: Major > > I am rewriting the doc to fit github. > [https://github.com/jyterrien/camel/blob/master/readme.adoc] > I replaced .md files with .adoc > I started correcting the links in readme.adoc contributing.adoc > and in camel-core. (in alphabetic order from bean-component to file-component) > I did not find, on github, docs like > https://camel.apache.org/data-format.html > [https://camel.apache.org/enterprise-integration-patterns.html] > > in every page I've changed the definition > = title page > I'e added > :toc: left > and I corrected the links <> link:doc.adoc[Doc] > I also when I found the target corrected the relative links like : > === See Also > * link:file-language.adoc[File Language] > * link:../../../../components/camel-ftp/src/main/docs/ftp-component.adoc[FTP] > * Polling Consumer > as soon as I corrected all camel-core I think to make a pull-request -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12523) Camel-cdi blueprint smx7
Terrien Jean-Yves created CAMEL-12523:
-
Summary: Camel-cdi blueprint smx7
Key: CAMEL-12523
URL: https://issues.apache.org/jira/browse/CAMEL-12523
Project: Camel
Issue Type: Test
Components: camel-cdi
Environment: Hi,
I'm using annotations to define my route builder in blueprint
I have a blueprint.xml file that only contains:
{code:xml}
http://www.osgi.org/xmlns/blueprint/v1.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:camel="http://camel.apache.org/schema/blueprint";
xsi:schemaLocation="
http://www.osgi.org/xmlns/blueprint/v1.0.0
http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
http://camel.apache.org/schema/blueprint
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd";>
http://camel.apache.org/schema/blueprint";>
{code}
I was looking for how to remove this file. I found the annotation
{code:java}
@ContextName ("mycontext")
{code}
But I can not create the context.
I added the camel-cdi feature to ServiceMix
But without the blueprint.xml file the context is not created.
Thank
Reporter: Terrien Jean-Yves
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12523) Camel-cdi blueprint smx7
[
https://issues.apache.org/jira/browse/CAMEL-12523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16513516#comment-16513516
]
Terrien Jean-Yves commented on CAMEL-12523:
---
I posted on the mailing list but it's a black hole.
my question never appeared on nabble and I never got an answer.
> Camel-cdi blueprint smx7
>
>
> Key: CAMEL-12523
> URL: https://issues.apache.org/jira/browse/CAMEL-12523
> Project: Camel
> Issue Type: Test
> Components: camel-cdi
> Environment: Hi,
> I'm using annotations to define my route builder in blueprint
> I have a blueprint.xml file that only contains:
> {code:xml}
>
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:camel="http://camel.apache.org/schema/blueprint";
> xsi:schemaLocation="
>http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://camel.apache.org/schema/blueprint
> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd";>
> xmlns="http://camel.apache.org/schema/blueprint";>
>
>
>
> {code}
> I was looking for how to remove this file. I found the annotation
> {code:java}
> @ContextName ("mycontext")
> {code}
> But I can not create the context.
> I added the camel-cdi feature to ServiceMix
> But without the blueprint.xml file the context is not created.
>
> Thank
>Reporter: Terrien Jean-Yves
>Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
