You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Scott England-Sullivan (JIRA)" <ji...@apache.org> on 2012/07/03 22:22:35 UTC
[jira] [Created] (CAMEL-5416) Camel Simple JMS Component
Scott England-Sullivan created CAMEL-5416:
---------------------------------------------
Summary: Camel Simple JMS Component
Key: CAMEL-5416
URL: https://issues.apache.org/jira/browse/CAMEL-5416
Project: Camel
Issue Type: New Feature
Reporter: Scott England-Sullivan
I am developing a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
Thanks,
Scott ES
http://fusesource.com
--
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-5416) Camel Simple JMS Component
Posted by "Scott England-Sullivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott England-Sullivan updated CAMEL-5416:
------------------------------------------
Description:
I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
_First Iteration:_
* Full Queue and Topic Support (Durable & Non-Durable)
* Full InOnly & InOut Support
* Internal Connection, Session, Consumer, & Producer pooling/caching management
* Full Asynchronous Support
* JMS Internal Transaction Support
_Future Iterations:_
* Robust JMX Support
* Camel Transaction Support
* JTA Support (Pure Java)
* Robust-InOnly
* Full Migration of Core Camel-JMS Unit Tests (where applicable)
* Batch List support
Thanks,
Scott ES
http://fusesource.com
was:
I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
_First Iteration:_
* Full Queue and Topic Support (Durable & Non-Durable)
* Full InOnly & InOut Support
* Internal Connection, Session, Consumer, & Producer pooling/caching management
* Full Asynchronous Support
* JMS Internal Transaction Support
_Future Iterations:_
* Robust JMX Support
* Camel Transaction Support
* JTA Support (Pure Java)
* Robust-InOnly
* Full Migration of Core Camel-JMS Unit Tests (where applicable)
The source can be found here: https://github.com/sully6768/camel-sandbox
Thanks,
Scott ES
http://fusesource.com
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
> Attachments: CAMEL-5416.patch, camel-sjms.tar.gz, camel-sjms_wiki_documentation.txt
>
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> * Batch List support
> Thanks,
> Scott ES
> http://fusesource.com
--
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-5416) Camel Simple JMS Component
Posted by "Scott England-Sullivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott England-Sullivan updated CAMEL-5416:
------------------------------------------
Attachment: CAMEL-5416-resources-updates.patch
Updates:
* Fixed OSGi exports for the Connection Resources.
* Created a cleaner ConnectionFactoryResource as the default.
* Began refactoring JMS APIs to a single package structure.
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
> Assignee: Willem Jiang
> Attachments: CAMEL-5416-resources-updates.patch, CAMEL-5416.patch, camel-sjms.tar.gz, camel-sjms_wiki_documentation.txt
>
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> * Batch List support
> Thanks,
> Scott ES
> http://fusesource.com
--
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] [Commented] (CAMEL-5416) Camel Simple JMS Component
Posted by "Scott England-Sullivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428967#comment-13428967 ]
Scott England-Sullivan commented on CAMEL-5416:
-----------------------------------------------
Willem,
Thanks so much for adding the component to SVN. Much appreciated.
Scott ES
http://fusesource.com
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
> Assignee: Willem Jiang
> Attachments: CAMEL-5416.patch, camel-sjms.tar.gz, camel-sjms_wiki_documentation.txt
>
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> * Batch List support
> Thanks,
> Scott ES
> http://fusesource.com
--
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-5416) Camel Simple JMS Component
Posted by "Scott England-Sullivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott England-Sullivan updated CAMEL-5416:
------------------------------------------
Description:
I am developing a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
_First Iteration:_
* Full Queue and Topic Support (Durable & Non-Durable)
* Full InOnly & InOut Support
* Internal Connection, Session, Consumer, & Producer pooling/caching management
* Full Asynchronous Support
* JMS Internal Transaction Support
_Future Iterations:_
* Robust JMX Support
* Camel Transaction Support
* JTA Support (Pure Java)
* Robust-InOnly
* Full Migration of Core Camel-JMS Unit Tests (where applicable)
The source can be found here: https://github.com/sully6768/camel-sandbox
Thanks,
Scott ES
http://fusesource.com
was:
I am developing a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
_First Iteration:_
* Full Queue and Topic Support (Durable & Non-Durable)
* Full InOnly & InOut Support
* Internal Connection, Session, Consumer, & Producer pooling/caching * management
* Full Asynchronous Support
* JMS Internal Transaction Support
_Future Iterations:_
* Robust JMX Support
* Camel Transaction Support
* JTA Support (Pure Java)
* Robust-InOnly
* Full Migration of Core Camel-JMS Unit Tests (where applicable)
The source can be found here: https://github.com/sully6768/camel-sandbox
Thanks,
Scott ES
http://fusesource.com
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
>
> I am developing a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> The source can be found here: https://github.com/sully6768/camel-sandbox
> Thanks,
> Scott ES
> http://fusesource.com
--
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] [Commented] (CAMEL-5416) Camel Simple JMS Component
Posted by "Babak Vahdat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427828#comment-13427828 ]
Babak Vahdat commented on CAMEL-5416:
-------------------------------------
On the other hand running
{code}
mvn clean install -Pfastinstall
{code}
has *still* got the expected behaviour.
So the problem is only when you want to run with the sourcecheck profile but *without* executing the tests.
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
> Assignee: Willem Jiang
> Attachments: CAMEL-5416.patch, camel-sjms.tar.gz, camel-sjms_wiki_documentation.txt
>
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> * Batch List support
> Thanks,
> Scott ES
> http://fusesource.com
--
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] [Commented] (CAMEL-5416) Camel Simple JMS Component
Posted by "Scott England-Sullivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429634#comment-13429634 ]
Scott England-Sullivan commented on CAMEL-5416:
-----------------------------------------------
Hi Babak,
It does exist, just not in trunk yet. :S
I submitted it as part of the CAMEL-5486 subtask. The patch has some issues so Willem is going to go through it with me tonight.
For the time being you would only need that for a durable subscription so for the sake of the examples today it isn't needed. It contains some refactoring that brings it into alignment with the JMS spec though. Hopefully we will be through it tonight. If not I will pull it out of the docs until we can get it in.
I will send out an update when we are done.
Thanks,
Scott ES
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
> Assignee: Willem Jiang
> Attachments: CAMEL-5416.patch, camel-sjms.tar.gz, camel-sjms_wiki_documentation.txt
>
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> * Batch List support
> Thanks,
> Scott ES
> http://fusesource.com
--
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] [Commented] (CAMEL-5416) Camel Simple JMS Component
Posted by "Babak Vahdat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429379#comment-13429379 ]
Babak Vahdat commented on CAMEL-5416:
-------------------------------------
Yeah the
{code}
-Dtest=false
{code}
is the nasty way we've got used to it in Camel :-)
And as you already mentioned
{code}
mvn clean install -Pfastinstall,sourcecheck
{code}
brings the behaviour back I was looking for.
And also just noticed that on the SJMS Wiki we talk about a class called:
{code}
ConnectionFactoryResource connectionResource = new ConnectionFactoryResource();
...
{code}
Which doesn't exist in the codebase! Could you maybe please take a look at the code sample on the Wiki?
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
> Assignee: Willem Jiang
> Attachments: CAMEL-5416.patch, camel-sjms.tar.gz, camel-sjms_wiki_documentation.txt
>
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> * Batch List support
> Thanks,
> Scott ES
> http://fusesource.com
--
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] [Assigned] (CAMEL-5416) Camel Simple JMS Component
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CAMEL-5416:
-----------------------------------
Assignee: Willem Jiang
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
> Assignee: Willem Jiang
> Attachments: CAMEL-5416.patch, camel-sjms.tar.gz, camel-sjms_wiki_documentation.txt
>
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> * Batch List support
> Thanks,
> Scott ES
> http://fusesource.com
--
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] [Commented] (CAMEL-5416) Camel Simple JMS Component
Posted by "Scott England-Sullivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428966#comment-13428966 ]
Scott England-Sullivan commented on CAMEL-5416:
-----------------------------------------------
Hi Babak,
-Dtest is used to specify the name of a test. If you want to skip the tests as they are in *fastinstall* then you would need to pass in the -Dmaven.test.skip.exec=true.
I believe to do what you are attempting though can be accomplished as follows:
mvn -Psourcecheck,fastinstall
FYI, I am also uploading a new patch to fix some errors I found while documenting.
Best Regards,
Scott ES
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
> Assignee: Willem Jiang
> Attachments: CAMEL-5416.patch, camel-sjms.tar.gz, camel-sjms_wiki_documentation.txt
>
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> * Batch List support
> Thanks,
> Scott ES
> http://fusesource.com
--
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-5416) Camel Simple JMS Component
Posted by "Scott England-Sullivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott England-Sullivan updated CAMEL-5416:
------------------------------------------
Description:
I am developing a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
_First Iteration:_
* Full Queue and Topic Support (Durable & Non-Durable)
* Full InOnly & InOut Support
* Internal Connection, Session, Consumer, & Producer pooling/caching * management
* Full Asynchronous Support
* JMS Internal Transaction Support
_Future Iterations:_
* Robust JMX Support
* Camel Transaction Support
* JTA Support (Pure Java)
* Robust-InOnly
* Full Migration of Core Camel-JMS Unit Tests (where applicable)
The source can be found here: https://github.com/sully6768/camel-sandbox
Thanks,
Scott ES
http://fusesource.com
was:
I am developing a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
Thanks,
Scott ES
http://fusesource.com
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
>
> I am developing a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching * management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> The source can be found here: https://github.com/sully6768/camel-sandbox
> Thanks,
> Scott ES
> http://fusesource.com
--
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-5416) Camel Simple JMS Component
Posted by "Scott England-Sullivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott England-Sullivan updated CAMEL-5416:
------------------------------------------
Description:
I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
_First Iteration:_
* Full Queue and Topic Support (Durable & Non-Durable)
* Full InOnly & InOut Support
* Internal Connection, Session, Consumer, & Producer pooling/caching management
* Full Asynchronous Support
* JMS Internal Transaction Support
_Future Iterations:_
* Robust JMX Support
* Camel Transaction Support
* JTA Support (Pure Java)
* Robust-InOnly
* Full Migration of Core Camel-JMS Unit Tests (where applicable)
The source can be found here: https://github.com/sully6768/camel-sandbox
Thanks,
Scott ES
http://fusesource.com
was:
I am developing a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
_First Iteration:_
* Full Queue and Topic Support (Durable & Non-Durable)
* Full InOnly & InOut Support
* Internal Connection, Session, Consumer, & Producer pooling/caching management
* Full Asynchronous Support
* JMS Internal Transaction Support
_Future Iterations:_
* Robust JMX Support
* Camel Transaction Support
* JTA Support (Pure Java)
* Robust-InOnly
* Full Migration of Core Camel-JMS Unit Tests (where applicable)
The source can be found here: https://github.com/sully6768/camel-sandbox
Thanks,
Scott ES
http://fusesource.com
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> The source can be found here: https://github.com/sully6768/camel-sandbox
> Thanks,
> Scott ES
> http://fusesource.com
--
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-5416) Camel Simple JMS Component
Posted by "Scott England-Sullivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott England-Sullivan updated CAMEL-5416:
------------------------------------------
Attachment: (was: CAMEL-5416-resources-updates.patch)
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
> Assignee: Willem Jiang
> Attachments: CAMEL-5416.patch, camel-sjms.tar.gz, camel-sjms_wiki_documentation.txt
>
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> * Batch List support
> Thanks,
> Scott ES
> http://fusesource.com
--
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] [Commented] (CAMEL-5416) Camel Simple JMS Component
Posted by "Scott England-Sullivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428978#comment-13428978 ]
Scott England-Sullivan commented on CAMEL-5416:
-----------------------------------------------
Moving latest patch to subtask.
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
> Assignee: Willem Jiang
> Attachments: CAMEL-5416-resources-updates.patch, CAMEL-5416.patch, camel-sjms.tar.gz, camel-sjms_wiki_documentation.txt
>
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> * Batch List support
> Thanks,
> Scott ES
> http://fusesource.com
--
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] [Resolved] (CAMEL-5416) Camel Simple JMS Component
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-5416.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.11.0
I think we can resolve this issue, as the code has been committed into trunk and we can create new issue if we have future enhancement on it.
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
> Assignee: Willem Jiang
> Fix For: 2.11.0
>
> Attachments: CAMEL-5416.patch, camel-sjms.tar.gz, camel-sjms_wiki_documentation.txt
>
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> * Batch List support
> Thanks,
> Scott ES
> http://fusesource.com
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-5416) Camel Simple JMS Component
Posted by "Scott England-Sullivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott England-Sullivan updated CAMEL-5416:
------------------------------------------
Attachment: camel-sjms.tar.gz
Apache SJMS Component
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
> Attachments: camel-sjms.tar.gz, camel-sjms_wiki_documentation.txt
>
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> The source can be found here: https://github.com/sully6768/camel-sandbox
> Thanks,
> Scott ES
> http://fusesource.com
--
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-5416) Camel Simple JMS Component
Posted by "Christian Müller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Müller updated CAMEL-5416:
------------------------------------
Attachment: camel-sjms_wiki_documentation.txt
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
> Attachments: camel-sjms_wiki_documentation.txt
>
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> The source can be found here: https://github.com/sully6768/camel-sandbox
> Thanks,
> Scott ES
> http://fusesource.com
--
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-5416) Camel Simple JMS Component
Posted by "Scott England-Sullivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott England-Sullivan updated CAMEL-5416:
------------------------------------------
Attachment: CAMEL-5416.patch
Camel SJMS Component Patch
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
> Attachments: CAMEL-5416.patch, camel-sjms.tar.gz, camel-sjms_wiki_documentation.txt
>
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> The source can be found here: https://github.com/sully6768/camel-sandbox
> Thanks,
> Scott ES
> http://fusesource.com
--
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] [Commented] (CAMEL-5416) Camel Simple JMS Component
Posted by "Babak Vahdat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427826#comment-13427826 ]
Babak Vahdat commented on CAMEL-5416:
-------------------------------------
The Integration-Tests @:
https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/test/java/org/apache/camel/component/sjms/it
Have all the IT suffix, so that running:
{code}
mvn clean install -Psourcecheck -Dtest=false
{code}
Does *still* execute these Tests. Just wonder if we should rename them to XXXTest as all the other tests so that they are recognized properly by maven.
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
> Assignee: Willem Jiang
> Attachments: CAMEL-5416.patch, camel-sjms.tar.gz, camel-sjms_wiki_documentation.txt
>
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free. I would like to include it in the next 2.x release of Camel and am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> * Batch List support
> Thanks,
> Scott ES
> http://fusesource.com
--
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