[
https://issues.apache.org/jira/browse/CAMEL-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14600834#comment-14600834
]
Tarek CHAOUALI edited comment on CAMEL-8852 at 6/25/15 8:06 AM:
----------------------------------------------------------------
I Think That the best way is to add a new header the JCR header's list , it
may be called : CamelWorkspaceName
If the header is null or empty a connection to the default workspace is
provided otherwise a connection to the mentionned workspace is provided
The test on the workspace name should be done on both cases: node insertion and
node retreiving.
was (Author: tarek chaouali):
I Think That the best why is to add a new header the JCR header's list , it
may be called : CamelWorkspaceName
If the header is null or empty a connection to the default workspace is
provided otherwise a connection to the mentionned workspace is provided
The test on the workspace name should be done on both cases: node insertion and
node retreiving.
> Camel JCR doesnt include Connection to a repository workspace except the
> default one
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-8852
> URL: https://issues.apache.org/jira/browse/CAMEL-8852
> Project: Camel
> Issue Type: Improvement
> Components: camel-jcr
> Reporter: Tarek CHAOUALI
> Fix For: Future
>
>
> This bug exists in all camel jcr component version
> Camel JCR component provides a connection to the default workspace
> no custom workspace connection is allowed .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
