[jira] [Commented] (CAMEL-8830) Upgrade to Saxon HE 9.6

2016-09-13 Thread Edstrom Johan (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-8830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15489138#comment-15489138
 ] 

Edstrom Johan commented on CAMEL-8830:
--

And maybe we should do something for Saxon here or get Saxonica involved? 
It is a really strange API to work with as they don't deprecate with how to do 
it in a new API, 
but it seems we (Camel) really would benefit from allowing their PE and EE jars 
to also work.

Just a thought.

> Upgrade to Saxon HE 9.6
> ---
>
> Key: CAMEL-8830
> URL: https://issues.apache.org/jira/browse/CAMEL-8830
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-saxon
>Affects Versions: 2.15.2
>Reporter: Kartik
> Fix For: 2.18.0
>
>
> Upgrade to Saxon HE 9.6 which uses XQuery 3.0 by default, allowing to use 
> powerful new XQuery 3.0 features such as 'group by'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8830) Upgrade to Saxon HE 9.6

2016-09-13 Thread Edstrom Johan (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-8830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15489107#comment-15489107
 ] 

Edstrom Johan commented on CAMEL-8830:
--

I did some work on this for a customer, I upgraded to Saxon PE 9.7.0.8 - The 
main changes after getting Luca's fixes for 
XpathBuilder the changes mainly were ;

 //dynamicQueryContext.setParameter(parameterPrefix + entry.getKey(), 
entry.getValue());
dynamicQueryContext.setParameter(new 
StructuredQName(parameterPrefix+entry.getKey(),"",parameterPrefix+entry.getKey()),
 new StringValue (entry.getValue().toString()));

For the Saxon component, I have to check with the customer what I can release 
but shading the jar also wasn't a big deal and if 
we need to I could get a new bundle out in ServiceMix.

> Upgrade to Saxon HE 9.6
> ---
>
> Key: CAMEL-8830
> URL: https://issues.apache.org/jira/browse/CAMEL-8830
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-saxon
>Affects Versions: 2.15.2
>Reporter: Kartik
> Fix For: 2.18.0
>
>
> Upgrade to Saxon HE 9.6 which uses XQuery 3.0 by default, allowing to use 
> powerful new XQuery 3.0 features such as 'group by'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10263) Several log refactoring/improvement suggestions

2016-09-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15488173#comment-15488173
 ] 

ASF GitHub Bot commented on CAMEL-10263:


GitHub user tkopczynski opened a pull request:

https://github.com/apache/camel/pull/1174

CAMEL-10263: Logging improvements

This PR introduces several logging improvements as described in 
https://issues.apache.org/jira/browse/CAMEL-10263

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tkopczynski/camel camel-10263

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1174.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1174


commit 16716d6021e3416e78239e01dd1bcf5c56d1822e
Author: Tomasz Kopczynski 
Date:   2016-09-12T21:08:17Z

CAMEL-10263: Logging improvements




> Several log refactoring/improvement suggestions
> ---
>
> Key: CAMEL-10263
> URL: https://issues.apache.org/jira/browse/CAMEL-10263
> Project: Camel
>  Issue Type: Task
>Affects Versions: 2.17.3
>Reporter: Nemo Chen
>Priority: Trivial
> Fix For: 2.18.0
>
>
> *method invocation replaced by variable*
> file: 
> apache-camel-2.17.3/camel-core/src/main/java/org/apache/camel/processor/interceptor/BacklogDebugger.java
> method: void beforeProcess (Exchange exchange, Processor processor, 
> ProcessorDefinition definition)
> {code}exchangeId=exchange.getExchangeId(){code}
> {code}logger.log("NodeBreakpoint at node " + toNode + " is waiting to 
> continue for exchangeId: "+ exchange.getExchangeId());{code}
> file: 
> apache-camel-2.17.3/components/camel-core-osgi/src/main/java/org/apache/camel/core/osgi/OsgiCamelContextPublisher.java
> method : ServiceRegistration registerCamelContext (CamelContext 
> camelContext)
> {code}name=camelContext.getName(){code}
> {code}log.debug("Registering CamelContext [{}] of in OSGi 
> registry",camelContext.getName());{code}
> The method invocations in above examples are assigned to variables before, we 
> should replace the method invocation with the variable for simpliciy and 
> readabiliy of logs.
> 
> *method invocation in return statement*
> file: 
> apache-camel-2.17.3/camel-core/src/main/java/org/apache/camel/processor/aggregate/AggregateProcessor.java
> void doForceCompletionOnStop ()
> {code}LOG.trace("Waiting for {} inflight exchanges to 
> complete",inProgressCompleteExchanges.size());{code}
> {code}
> public int getInProgressCompleteExchanges() {
> return inProgressCompleteExchanges.size();
> }
> {code}
> file: 
> apache-camel-2.17.3/components/camel-disruptor/src/main/java/org/apache/camel/component/disruptor/DisruptorReference.java
> method:void removeEndpoint (final DisruptorEndpoint disruptorEndpoint)
> {code}LOGGER.debug("Endpoint removed: {}, new total endpoints 
> {}",disruptorEndpoint,endpoints.size());{code}
> {code}
> public synchronized int getEndpointCount() {
> return endpoints.size();
> }
> {code}
> file: 
> apache-camel-2.17.3/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsEndpoint.java
> method: void configureListenerContainer (AbstractMessageListenerContainer 
> listenerContainer, JmsConsumer consumer)
> {code}
> log.debug("Deferring creation of TaskExecutor for listener container: {} as 
> per policy: {}",listenerContainer,configuration.getDefaultTaskExecutorType());
> {code}
> {code}
> @ManagedAttribute
> public DefaultTaskExecutorType getDefaultTaskExecutorType() {
> return configuration.getDefaultTaskExecutorType();
> }
> {code}
> In the above examples, the method invocations are in the return statements of 
> the method in the same class. Replace the method invocations with the methods 
> will make the log more readable and easy to maintain.
> 
> *Check if variable is null*
> file: 
> apache-camel-2.17.3/components/camel-guice/src/test/java/org/apache/camel/guice/testing/InjectorManager.java
> void afterClasses ()
> {code}
> System.out.println("Could not close Class scope as there is no Injector for 
> module type " + injector);
> {code}
> file: 
> apache-camel-2.17.3/components/camel-snmp/src/main/java/org/apache/camel/component/snmp/SnmpTrapConsumer.java
> void processPdu (CommandResponderEvent event)
> {code}
> LOG.debug("Received invalid trap PDU: " + pdu);
> {code}
> In the above examples, the variable is null in the log. There is no need to 
> print the invalid variable in the logs. Suggestion: delete the variables in 
> the logs to avoid confusion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10307) Upgrade docker java version

2016-09-13 Thread Fabrizio Spataro (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487587#comment-15487587
 ] 

Fabrizio Spataro commented on CAMEL-10307:
--

:-( 

http://camel.465427.n5.nabble.com/Camel-docker-upgrade-library-test-failure-td5787511.html

> Upgrade docker java version
> ---
>
> Key: CAMEL-10307
> URL: https://issues.apache.org/jira/browse/CAMEL-10307
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-docker
>Reporter: Fabrizio Spataro
>
> Hello,
> Today the component use a very old docker-java lib 1.0.4, current docker-java 
> version is 3.0.5
> Could be nice to upgrade all component code



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8830) Upgrade to Saxon HE 9.6

2016-09-13 Thread Luca Burgazzoli (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-8830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487476#comment-15487476
 ] 

Luca Burgazzoli commented on CAMEL-8830:


I've tried to upgrade saxon here 
https://github.com/lburgazzoli/apache-camel/tree/CAMEL-8830:

- there is one test not working (SaxonXslIncludetEmptyHrefTest)
- selecting saxon using the object model url does not work anymore (see 
[doc|http://www.saxonica.com/documentation/index.html#!xpath-api/jaxp-xpath/factory])
 so I had to disable all the test using such way to enable saxon and amend 
XPathBuilder to be smart in instantiating a saxon factory.

Any feedback wold be really appreciated




> Upgrade to Saxon HE 9.6
> ---
>
> Key: CAMEL-8830
> URL: https://issues.apache.org/jira/browse/CAMEL-8830
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-saxon
>Affects Versions: 2.15.2
>Reporter: Kartik
> Fix For: 2.18.0
>
>
> Upgrade to Saxon HE 9.6 which uses XQuery 3.0 by default, allowing to use 
> powerful new XQuery 3.0 features such as 'group by'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10317) Add support to use Http synchronous client with Olingo2 Component

2016-09-13 Thread Kiran G (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487472#comment-15487472
 ] 

Kiran G commented on CAMEL-10317:
-

I have submitted pull request in github. Please check.
https://github.com/apache/camel/pull/1173


> Add support to use Http synchronous client with Olingo2 Component
> -
>
> Key: CAMEL-10317
> URL: https://issues.apache.org/jira/browse/CAMEL-10317
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-olingo2
>Affects Versions: 2.17.3
>Reporter: Kiran G
>Priority: Minor
>
> At present Olingo2 component only supports configuring Http Asynchronous 
> Client. Asynchronous client lagging behind in feature wrt features (but 
> steadily catching up). Using Synchronous client makes debugging issues 
> easier. Also, this will make things easier for those using ThreadLocals. 
> The proposed change provides an option to the user to choose between 
> Synchronous and Asynchronous client while keeping the Asynchronous client as 
> default and keeping the existing functionality intact.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10317) Add support to use Http synchronous client with Olingo2 Component

2016-09-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487464#comment-15487464
 ] 

ASF GitHub Bot commented on CAMEL-10317:


GitHub user kiransg opened a pull request:

https://github.com/apache/camel/pull/1173

CAMEL-10317: Added support to use Http synchronous client with Olingo…

…2 Component

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Infosys/camel CAMEL-10317

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1173.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1173


commit 4ffb337a646e6c4a248041afc29da5cb3c5eb9dc
Author: Kiran Govindaiah 
Date:   2016-09-13T15:05:34Z

CAMEL-10317: Added support to use Http synchronous client with Olingo2 
Component




> Add support to use Http synchronous client with Olingo2 Component
> -
>
> Key: CAMEL-10317
> URL: https://issues.apache.org/jira/browse/CAMEL-10317
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-olingo2
>Affects Versions: 2.17.3
>Reporter: Kiran G
>Priority: Minor
>
> At present Olingo2 component only supports configuring Http Asynchronous 
> Client. Asynchronous client lagging behind in feature wrt features (but 
> steadily catching up). Using Synchronous client makes debugging issues 
> easier. Also, this will make things easier for those using ThreadLocals. 
> The proposed change provides an option to the user to choose between 
> Synchronous and Asynchronous client while keeping the Asynchronous client as 
> default and keeping the existing functionality intact.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10317) Add support to use Http synchronous client with Olingo2 Component

2016-09-13 Thread Kiran G (JIRA) 
Kiran G created CAMEL-10317:
---

 Summary: Add support to use Http synchronous client with Olingo2 
Component
 Key: CAMEL-10317
 URL: https://issues.apache.org/jira/browse/CAMEL-10317
 Project: Camel
  Issue Type: New Feature
  Components: camel-olingo2
Affects Versions: 2.17.3
Reporter: Kiran G
Priority: Minor


At present Olingo2 component only supports configuring Http Asynchronous 
Client. Asynchronous client lagging behind in feature wrt features (but 
steadily catching up). Using Synchronous client makes debugging issues easier. 
Also, this will make things easier for those using ThreadLocals. 

The proposed change provides an option to the user to choose between 
Synchronous and Asynchronous client while keeping the Asynchronous client as 
default and keeping the existing functionality intact.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10307) Upgrade docker java version

2016-09-13 Thread Fabrizio Spataro (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487209#comment-15487209
 ] 

Fabrizio Spataro commented on CAMEL-10307:
--

Hello everybody, my code is OK, i have connected succerfully with docker rest 
api 1.24 (docker 1.12.x)

Now i am fixing test

stay tuned!

> Upgrade docker java version
> ---
>
> Key: CAMEL-10307
> URL: https://issues.apache.org/jira/browse/CAMEL-10307
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-docker
>Reporter: Fabrizio Spataro
>
> Hello,
> Today the component use a very old docker-java lib 1.0.4, current docker-java 
> version is 3.0.5
> Could be nice to upgrade all component code



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-10316) Upgrade Weld to version 2.4.0.Final

2016-09-13 Thread Antonin Stefanutti (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CAMEL-10316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antonin Stefanutti resolved CAMEL-10316.

Resolution: Fixed

> Upgrade Weld to version 2.4.0.Final
> ---
>
> Key: CAMEL-10316
> URL: https://issues.apache.org/jira/browse/CAMEL-10316
> Project: Camel
>  Issue Type: Task
>  Components: camel-cdi
>Reporter: Antonin Stefanutti
>Assignee: Antonin Stefanutti
>Priority: Minor
> Fix For: 2.18.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10316) Upgrade Weld to version 2.4.0.Final

2016-09-13 Thread Antonin Stefanutti (JIRA) 
Antonin Stefanutti created CAMEL-10316:
--

 Summary: Upgrade Weld to version 2.4.0.Final
 Key: CAMEL-10316
 URL: https://issues.apache.org/jira/browse/CAMEL-10316
 Project: Camel
  Issue Type: Task
  Components: camel-cdi
Reporter: Antonin Stefanutti
Assignee: Antonin Stefanutti
Priority: Minor
 Fix For: 2.18.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10304) Apache Camel Docker component not working in OSGi environment

2016-09-13 Thread Philip Andrew (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486844#comment-15486844
 ] 

Philip Andrew commented on CAMEL-10304:
---

I think I might be wrong and this may not be a buy because, I deleted my .ivy2 
data and tried again and its working, so this may not be a problem.

> Apache Camel Docker component not working in OSGi environment
> -
>
> Key: CAMEL-10304
> URL: https://issues.apache.org/jira/browse/CAMEL-10304
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.17.3
> Environment: Windows
>Reporter: Philip Andrew
>Priority: Minor
>
> I can not use camel-docker in the OSGi environment, exception is thrown.
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Provider 
> org.glass fish.jersey.internal.RuntimeDelegateImpl could not be instantiated: 
> java.lang.Il legalStateException: No generator was provided and there is no 
> default generator registered
> If I do the following workaround then it can work
> RuntimeDelegate.setInstance(new 
> org.glassfish.jersey.server.internal.RuntimeDelegateImpl())
> http://stackoverflow.com/questions/39382056/how-to-get-apache-camel-docker-component-to-work-in-osgi-or-jersey-does-not-wo



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10314) cannot execute mvn install -Pfastinstall

2016-09-13 Thread Fabrizio Spataro (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486744#comment-15486744
 ] 

Fabrizio Spataro commented on CAMEL-10314:
--

Thanks andrea!

> cannot execute mvn install -Pfastinstall 
> -
>
> Key: CAMEL-10314
> URL: https://issues.apache.org/jira/browse/CAMEL-10314
> Project: Camel
>  Issue Type: Task
>  Components: camel-jsch
>Reporter: Fabrizio Spataro
>Assignee: Andrea Cosentino
>
> Hello, i am using master source. 
> When i execute *mvn clean install -Pfastinstall* i have an error
> 
> [INFO] --- maven-bundle-plugin:3.2.0:manifest (bundle-manifest) @ camel-jsch 
> ---
> [WARNING] Manifest org.apache.camel:camel-jsch:jar:2.18.0-SNAPSHOT : Unused 
> Import-Package instructions: [org.springframework.ws.*, 
> org.springframework.xml.*, org.springframework.*, 
> org.apache.commons.logging.*, org.apache.cxf.*, org.apache.qpid.*, 
> org.apache.abdera.*, org.apache.commons.httpclient.*, org.apache.velocity.*, 
> org.apache.xmlbeans.*, org.eclipse.jetty.*, com.thoughtworks.xstream.*, 
> org.antlr.stringtemplate.*, org.ccil.cowan.tagsoup.*, org.mortbay.cometd.*, 
> net.sf.flatpack.*, net.sf.saxon.*, freemarker.*, javax.persistence.*, 
> org.apache.lucene.*, org.apache.solr.*] 
> [INFO] 
> [INFO] --- camel-package-maven-plugin:2.18.0-SNAPSHOT:validate-components 
> (validate) @ camel-jsch ---
> [WARNING] The component: scp has validation errors
> [WARNING] Missing endpoint documentation for the following options:
>   host
>   port
>   directoryName
>   disconnect
>   disconnectOnBatchComplete
>   fileName
>   flatten
>   allowNullBody
>   connectTimeout
>   soTimeout
>   timeout
>   password
>   username
> 
> king regards
> fabryprog



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (CAMEL-10314) cannot execute mvn install -Pfastinstall

2016-09-13 Thread Andrea Cosentino (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CAMEL-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino reassigned CAMEL-10314:


Assignee: Andrea Cosentino

> cannot execute mvn install -Pfastinstall 
> -
>
> Key: CAMEL-10314
> URL: https://issues.apache.org/jira/browse/CAMEL-10314
> Project: Camel
>  Issue Type: Task
>  Components: camel-jsch
>Reporter: Fabrizio Spataro
>Assignee: Andrea Cosentino
>
> Hello, i am using master source. 
> When i execute *mvn clean install -Pfastinstall* i have an error
> 
> [INFO] --- maven-bundle-plugin:3.2.0:manifest (bundle-manifest) @ camel-jsch 
> ---
> [WARNING] Manifest org.apache.camel:camel-jsch:jar:2.18.0-SNAPSHOT : Unused 
> Import-Package instructions: [org.springframework.ws.*, 
> org.springframework.xml.*, org.springframework.*, 
> org.apache.commons.logging.*, org.apache.cxf.*, org.apache.qpid.*, 
> org.apache.abdera.*, org.apache.commons.httpclient.*, org.apache.velocity.*, 
> org.apache.xmlbeans.*, org.eclipse.jetty.*, com.thoughtworks.xstream.*, 
> org.antlr.stringtemplate.*, org.ccil.cowan.tagsoup.*, org.mortbay.cometd.*, 
> net.sf.flatpack.*, net.sf.saxon.*, freemarker.*, javax.persistence.*, 
> org.apache.lucene.*, org.apache.solr.*] 
> [INFO] 
> [INFO] --- camel-package-maven-plugin:2.18.0-SNAPSHOT:validate-components 
> (validate) @ camel-jsch ---
> [WARNING] The component: scp has validation errors
> [WARNING] Missing endpoint documentation for the following options:
>   host
>   port
>   directoryName
>   disconnect
>   disconnectOnBatchComplete
>   fileName
>   flatten
>   allowNullBody
>   connectTimeout
>   soTimeout
>   timeout
>   password
>   username
> 
> king regards
> fabryprog



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-10314) cannot execute mvn install -Pfastinstall

2016-09-13 Thread Andrea Cosentino (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CAMEL-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-10314.
--
Resolution: Not A Problem

> cannot execute mvn install -Pfastinstall 
> -
>
> Key: CAMEL-10314
> URL: https://issues.apache.org/jira/browse/CAMEL-10314
> Project: Camel
>  Issue Type: Task
>  Components: camel-jsch
>Reporter: Fabrizio Spataro
>Assignee: Andrea Cosentino
>
> Hello, i am using master source. 
> When i execute *mvn clean install -Pfastinstall* i have an error
> 
> [INFO] --- maven-bundle-plugin:3.2.0:manifest (bundle-manifest) @ camel-jsch 
> ---
> [WARNING] Manifest org.apache.camel:camel-jsch:jar:2.18.0-SNAPSHOT : Unused 
> Import-Package instructions: [org.springframework.ws.*, 
> org.springframework.xml.*, org.springframework.*, 
> org.apache.commons.logging.*, org.apache.cxf.*, org.apache.qpid.*, 
> org.apache.abdera.*, org.apache.commons.httpclient.*, org.apache.velocity.*, 
> org.apache.xmlbeans.*, org.eclipse.jetty.*, com.thoughtworks.xstream.*, 
> org.antlr.stringtemplate.*, org.ccil.cowan.tagsoup.*, org.mortbay.cometd.*, 
> net.sf.flatpack.*, net.sf.saxon.*, freemarker.*, javax.persistence.*, 
> org.apache.lucene.*, org.apache.solr.*] 
> [INFO] 
> [INFO] --- camel-package-maven-plugin:2.18.0-SNAPSHOT:validate-components 
> (validate) @ camel-jsch ---
> [WARNING] The component: scp has validation errors
> [WARNING] Missing endpoint documentation for the following options:
>   host
>   port
>   directoryName
>   disconnect
>   disconnectOnBatchComplete
>   fileName
>   flatten
>   allowNullBody
>   connectTimeout
>   soTimeout
>   timeout
>   password
>   username
> 
> king regards
> fabryprog



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10314) cannot execute mvn install -Pfastinstall

2016-09-13 Thread Andrea Cosentino (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486665#comment-15486665
 ] 

Andrea Cosentino commented on CAMEL-10314:
--

You need to run the entire installation of all camel to get a complete SNAPSHOT.

Try to run mvn clean install -DskipTests from the project root and after that 
try again mvn -Pfastinstall from camel-jsch

> cannot execute mvn install -Pfastinstall 
> -
>
> Key: CAMEL-10314
> URL: https://issues.apache.org/jira/browse/CAMEL-10314
> Project: Camel
>  Issue Type: Task
>  Components: camel-jsch
>Reporter: Fabrizio Spataro
>
> Hello, i am using master source. 
> When i execute *mvn clean install -Pfastinstall* i have an error
> 
> [INFO] --- maven-bundle-plugin:3.2.0:manifest (bundle-manifest) @ camel-jsch 
> ---
> [WARNING] Manifest org.apache.camel:camel-jsch:jar:2.18.0-SNAPSHOT : Unused 
> Import-Package instructions: [org.springframework.ws.*, 
> org.springframework.xml.*, org.springframework.*, 
> org.apache.commons.logging.*, org.apache.cxf.*, org.apache.qpid.*, 
> org.apache.abdera.*, org.apache.commons.httpclient.*, org.apache.velocity.*, 
> org.apache.xmlbeans.*, org.eclipse.jetty.*, com.thoughtworks.xstream.*, 
> org.antlr.stringtemplate.*, org.ccil.cowan.tagsoup.*, org.mortbay.cometd.*, 
> net.sf.flatpack.*, net.sf.saxon.*, freemarker.*, javax.persistence.*, 
> org.apache.lucene.*, org.apache.solr.*] 
> [INFO] 
> [INFO] --- camel-package-maven-plugin:2.18.0-SNAPSHOT:validate-components 
> (validate) @ camel-jsch ---
> [WARNING] The component: scp has validation errors
> [WARNING] Missing endpoint documentation for the following options:
>   host
>   port
>   directoryName
>   disconnect
>   disconnectOnBatchComplete
>   fileName
>   flatten
>   allowNullBody
>   connectTimeout
>   soTimeout
>   timeout
>   password
>   username
> 
> king regards
> fabryprog



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-10315) Apache Camel Blueprint continuously Restarts in Karaf with update-strategy = 'reload'

2016-09-13 Thread Cetra Free (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CAMEL-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cetra Free updated CAMEL-10315:
---
Summary: Apache Camel Blueprint continuously Restarts in Karaf with 
update-strategy = 'reload'  (was: Apache Camel Blueprint continuosly Restarts 
in Karaf with update-strategy = 'reload')

> Apache Camel Blueprint continuously Restarts in Karaf with update-strategy = 
> 'reload'
> -
>
> Key: CAMEL-10315
> URL: https://issues.apache.org/jira/browse/CAMEL-10315
> Project: Camel
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 2.17.0
>Reporter: Cetra Free
>
> Not sure if this one has been logged.
> I have seen the following chats which describe this behaviour, but it's hard 
> to reliably replicate.  It seems to be a race condition or a timeout being 
> hit on starting a camel context.
> Basically the steps to replicate are:
> * Deploy a blueprint.xml file to the karaf deploy directory, which has the 
> following:
> {code}
>  update-strategy="reload" />
> {code}
> * Notice that karaf will continuously reload the camel blueprint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-10315) Apache Camel Blueprint continuously Restarts in Karaf with update-strategy = 'reload'

2016-09-13 Thread Cetra Free (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CAMEL-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cetra Free updated CAMEL-10315:
---
Description: 
Not sure if this one has been logged.

I have seen the following chats which describe this behaviour, but it's hard to 
reliably replicate.  It seems to be a race condition or a timeout being hit on 
starting a camel context:

http://grokbase.com/t/camel/users/135qqay2x1/prevent-camelcontext-from-shutting-down-in-blueprint

http://camel.465427.n5.nabble.com/Upgrade-Camel-2-10-1-2-11-0-Camel-keeps-restarting-td5731854.html


Basically the steps to replicate are:

* Deploy a blueprint.xml file to the karaf deploy directory, which has the 
following:
{code}

{code}

* Notice that karaf will continuously reload the camel blueprint.


  was:
Not sure if this one has been logged.

I have seen the following chats which describe this behaviour, but it's hard to 
reliably replicate.  It seems to be a race condition or a timeout being hit on 
starting a camel context.

Basically the steps to replicate are:

* Deploy a blueprint.xml file to the karaf deploy directory, which has the 
following:
{code}

{code}

* Notice that karaf will continuously reload the camel blueprint.



> Apache Camel Blueprint continuously Restarts in Karaf with update-strategy = 
> 'reload'
> -
>
> Key: CAMEL-10315
> URL: https://issues.apache.org/jira/browse/CAMEL-10315
> Project: Camel
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 2.17.0
>Reporter: Cetra Free
>
> Not sure if this one has been logged.
> I have seen the following chats which describe this behaviour, but it's hard 
> to reliably replicate.  It seems to be a race condition or a timeout being 
> hit on starting a camel context:
> http://grokbase.com/t/camel/users/135qqay2x1/prevent-camelcontext-from-shutting-down-in-blueprint
> http://camel.465427.n5.nabble.com/Upgrade-Camel-2-10-1-2-11-0-Camel-keeps-restarting-td5731854.html
> Basically the steps to replicate are:
> * Deploy a blueprint.xml file to the karaf deploy directory, which has the 
> following:
> {code}
>  update-strategy="reload" />
> {code}
> * Notice that karaf will continuously reload the camel blueprint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10315) Apache Camel Blueprint continuosly Restarts in Karaf with update-strategy = 'reload'

2016-09-13 Thread Cetra Free (JIRA) 
Cetra Free created CAMEL-10315:
--

 Summary: Apache Camel Blueprint continuosly Restarts in Karaf with 
update-strategy = 'reload'
 Key: CAMEL-10315
 URL: https://issues.apache.org/jira/browse/CAMEL-10315
 Project: Camel
  Issue Type: Bug
  Components: karaf
Affects Versions: 2.17.0
Reporter: Cetra Free


Not sure if this one has been logged.

I have seen the following chats which describe this behaviour, but it's hard to 
reliably replicate.  It seems to be a race condition or a timeout being hit on 
starting a camel context.

Basically the steps to replicate are:

* Deploy a blueprint.xml file to the karaf deploy directory, which has the 
following:
{code}

{code}

* Notice that karaf will continuously reload the camel blueprint.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10304) Apache Camel Docker component not working in OSGi environment

2016-09-13 Thread Philip Andrew (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486633#comment-15486633
 ] 

Philip Andrew commented on CAMEL-10304:
---

Also I should add, this is only what is necessary for it to work in OSGi Felix 
in embedded mode. I see another error in non-embedded mode which I'm 
investigating.

> Apache Camel Docker component not working in OSGi environment
> -
>
> Key: CAMEL-10304
> URL: https://issues.apache.org/jira/browse/CAMEL-10304
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.17.3
> Environment: Windows
>Reporter: Philip Andrew
>Priority: Minor
>
> I can not use camel-docker in the OSGi environment, exception is thrown.
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Provider 
> org.glass fish.jersey.internal.RuntimeDelegateImpl could not be instantiated: 
> java.lang.Il legalStateException: No generator was provided and there is no 
> default generator registered
> If I do the following workaround then it can work
> RuntimeDelegate.setInstance(new 
> org.glassfish.jersey.server.internal.RuntimeDelegateImpl())
> http://stackoverflow.com/questions/39382056/how-to-get-apache-camel-docker-component-to-work-in-osgi-or-jersey-does-not-wo



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10314) cannot execute mvn install -Pfastinstall

2016-09-13 Thread Fabrizio Spataro (JIRA) 
Fabrizio Spataro created CAMEL-10314:


 Summary: cannot execute mvn install -Pfastinstall 
 Key: CAMEL-10314
 URL: https://issues.apache.org/jira/browse/CAMEL-10314
 Project: Camel
  Issue Type: Task
  Components: camel-jsch
Reporter: Fabrizio Spataro


Hello, i am using master source. 

When i execute *mvn clean install -Pfastinstall* i have an error


[INFO] --- maven-bundle-plugin:3.2.0:manifest (bundle-manifest) @ camel-jsch ---
[WARNING] Manifest org.apache.camel:camel-jsch:jar:2.18.0-SNAPSHOT : Unused 
Import-Package instructions: [org.springframework.ws.*, 
org.springframework.xml.*, org.springframework.*, org.apache.commons.logging.*, 
org.apache.cxf.*, org.apache.qpid.*, org.apache.abdera.*, 
org.apache.commons.httpclient.*, org.apache.velocity.*, org.apache.xmlbeans.*, 
org.eclipse.jetty.*, com.thoughtworks.xstream.*, org.antlr.stringtemplate.*, 
org.ccil.cowan.tagsoup.*, org.mortbay.cometd.*, net.sf.flatpack.*, 
net.sf.saxon.*, freemarker.*, javax.persistence.*, org.apache.lucene.*, 
org.apache.solr.*] 
[INFO] 
[INFO] --- camel-package-maven-plugin:2.18.0-SNAPSHOT:validate-components 
(validate) @ camel-jsch ---
[WARNING] The component: scp has validation errors
[WARNING] Missing endpoint documentation for the following options:
host
port
directoryName
disconnect
disconnectOnBatchComplete
fileName
flatten
allowNullBody
connectTimeout
soTimeout
timeout
password
username


king regards

fabryprog



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10304) Apache Camel Docker component not working in OSGi environment

2016-09-13 Thread Philip Andrew (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486616#comment-15486616
 ] 

Philip Andrew commented on CAMEL-10304:
---

At the moment, in my BundleActivator in the class itself, so when the class is 
instated then it runs, I assume before many other things.

  RuntimeDelegate.setInstance(new 
org.glassfish.jersey.server.internal.RuntimeDelegateImpl())



> Apache Camel Docker component not working in OSGi environment
> -
>
> Key: CAMEL-10304
> URL: https://issues.apache.org/jira/browse/CAMEL-10304
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.17.3
> Environment: Windows
>Reporter: Philip Andrew
>Priority: Minor
>
> I can not use camel-docker in the OSGi environment, exception is thrown.
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Provider 
> org.glass fish.jersey.internal.RuntimeDelegateImpl could not be instantiated: 
> java.lang.Il legalStateException: No generator was provided and there is no 
> default generator registered
> If I do the following workaround then it can work
> RuntimeDelegate.setInstance(new 
> org.glassfish.jersey.server.internal.RuntimeDelegateImpl())
> http://stackoverflow.com/questions/39382056/how-to-get-apache-camel-docker-component-to-work-in-osgi-or-jersey-does-not-wo



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)