[jira] [Commented] (CAMEL-9856) RestSwaggerProcessor fails with "Provider org.apache.xalan.processor.TransformerFactoryImpl not found"

[Martin Lichtin (JIRA)]

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

Martin Lichtin commented on CAMEL-9856:
---

Running into the same issue with Camel 2.18.4.
The problem appears as soon as one documents a query param.
E.g. this works:

{noformat}
  

  

  
{noformat}

and one can retrieve the Swagger JSON.

But when adding a  the Swagger interface does no longer work:

{noformat}
  



  

  
{noformat}

The full exception is:
{noformat}
2017-09-23 22:38:48,911 | WARN  | qtp1862576107-269| 
RestSwaggerProcessor | mel.swagger.RestSwaggerProcessor  122 | 240 
- org.apache.camel.camel-swagger-java - 2.18.4 | Error rendering Swagger API 
due Error occurred in RequiredModelMBean while trying to invoke operation 
dumpRestsAsXml
javax.management.RuntimeErrorException: Error occurred in RequiredModelMBean 
while trying to invoke operation dumpRestsAsXml
at 
javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1289)[:1.8.0_141]
at 
javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:1085)[:1.8.0_141]
at 
org.apache.camel.management.MixinRequiredModelMBean.invoke(MixinRequiredModelMBean.java:70)[233:org.apache.camel.camel-core:2.18.4]
at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)[:1.8.0_141]
at 
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)[:1.8.0_141]
at 
org.apache.camel.swagger.RestSwaggerSupport.getRestDefinitions(RestSwaggerSupport.java:153)[240:org.apache.camel.camel-swagger-java:2.18.4]
at 
org.apache.camel.swagger.RestSwaggerSupport.renderResourceListing(RestSwaggerSupport.java:202)[240:org.apache.camel.camel-swagger-java:2.18.4]
at 
org.apache.camel.swagger.RestSwaggerProcessor.process(RestSwaggerProcessor.java:118)[240:org.apache.camel.camel-swagger-java:2.18.4]
at 
org.apache.camel.component.rest.RestApiProducer.process(RestApiProducer.java:36)[233:org.apache.camel.camel-core:2.18.4]
at 
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[233:org.apache.camel.camel-core:2.18.4]
at 
org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145)[233:org.apache.camel.camel-core:2.18.4]
at 
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)[233:org.apache.camel.camel-core:2.18.4]
at 
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)[233:org.apache.camel.camel-core:2.18.4]
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)[233:org.apache.camel.camel-core:2.18.4]
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)[233:org.apache.camel.camel-core:2.18.4]
at 
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)[233:org.apache.camel.camel-core:2.18.4]
at 
org.apache.camel.http.common.CamelServlet.doService(CamelServlet.java:195)[234:org.apache.camel.camel-http-common:2.18.4]
at 
org.apache.camel.http.common.CamelServlet.service(CamelServlet.java:74)[234:org.apache.camel.camel-http-common:2.18.4]
at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:790)[220:javax.servlet-api:3.1.0]
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)[330:org.eclipse.jetty.servlet:9.2.19.v20160908]
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)[330:org.eclipse.jetty.servlet:9.2.19.v20160908]
at 
org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71)[372:org.ops4j.pax.web.pax-web-jetty:4.3.0]
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)[329:org.eclipse.jetty.server:9.2.19.v20160908]
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)[328:org.eclipse.jetty.security:9.2.19.v20160908]
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)[329:org.eclipse.jetty.server:9.2.19.v20160908]
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)[329:org.eclipse.jetty.server:9.2.19.v20160908]
at 
org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:287)[372:org.ops4j.pax.web.pax-web-jetty:4.3.0]
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)[330:org.eclipse.jetty.servlet:9.2.19.v20160908]
at 

[jira] [Created] (CAMEL-11818) cluster-service : review spring boot configuration torder

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11818:
---

 Summary: cluster-service : review spring boot configuration torder
 Key: CAMEL-11818
 URL: https://issues.apache.org/jira/browse/CAMEL-11818
 Project: Camel
  Issue Type: Improvement
  Components: camel-spring-boot, camel-spring-boot-starters
Affects Versions: 2.20.0
Reporter: Luca Burgazzoli
Assignee: Luca Burgazzoli
Priority: Minor
 Fix For: 2.21.0


As today cluster services are configured before the camel context starts but 
some implementation may require the camel context to be there already so we 
should investigate if we can use afterPropertiesSet or something similar to 
bind the service to the context.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11816) cluster-service : camel-consul spring boot support

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-11816:

Component/s: (was: camel-zookeeper)
 camel-spring-boot-starters
 camel-consul

> cluster-service : camel-consul spring boot support
> --
>
> Key: CAMEL-11816
> URL: https://issues.apache.org/jira/browse/CAMEL-11816
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-consul, camel-spring-boot-starters
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>  Labels: clustering
> Fix For: 2.20.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11815) cluster-service : camel-zookeeper spring boot support

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-11815:

Component/s: camel-spring-boot-starters

> cluster-service : camel-zookeeper spring boot support
> -
>
> Key: CAMEL-11815
> URL: https://issues.apache.org/jira/browse/CAMEL-11815
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-boot-starters, camel-zookeeper
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>  Labels: clustering
> Fix For: 2.20.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (CAMEL-11816) cluster-service : camel-consul spring boot support

[Luca Burgazzoli (JIRA)]

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

Work on CAMEL-11816 started by Luca Burgazzoli.
---
> cluster-service : camel-consul spring boot support
> --
>
> Key: CAMEL-11816
> URL: https://issues.apache.org/jira/browse/CAMEL-11816
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-consul, camel-spring-boot-starters
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>  Labels: clustering
> Fix For: 2.20.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (CAMEL-11817) cluster-service : camel-atomix spring boot support should have better bean names

[Luca Burgazzoli (JIRA)]

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

Work on CAMEL-11817 started by Luca Burgazzoli.
---
> cluster-service : camel-atomix spring boot support should have better bean 
> names
> 
>
> Key: CAMEL-11817
> URL: https://issues.apache.org/jira/browse/CAMEL-11817
> Project: Camel
>  Issue Type: Task
>  Components: camel-atomix, camel-spring-boot-starters
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>  Labels: clustering
> Fix For: 2.20.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11816) cluster-service : camel-consul spring boot support

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-11816:

Fix Version/s: (was: 2.21.0)
   2.20.0

> cluster-service : camel-consul spring boot support
> --
>
> Key: CAMEL-11816
> URL: https://issues.apache.org/jira/browse/CAMEL-11816
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-zookeeper
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>  Labels: clustering
> Fix For: 2.20.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11817) cluster-service : camel-atomix spring boot support should have better bean names

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11817:
---

 Summary: cluster-service : camel-atomix spring boot support should 
have better bean names
 Key: CAMEL-11817
 URL: https://issues.apache.org/jira/browse/CAMEL-11817
 Project: Camel
  Issue Type: Task
  Components: camel-atomix, camel-spring-boot-starters
Reporter: Luca Burgazzoli
Assignee: Luca Burgazzoli
 Fix For: 2.20.0






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11815) cluster-service : camel-zookeeper spring boot support

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-11815:

Fix Version/s: (was: 2.21.0)
   2.20.0

> cluster-service : camel-zookeeper spring boot support
> -
>
> Key: CAMEL-11815
> URL: https://issues.apache.org/jira/browse/CAMEL-11815
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-zookeeper
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>  Labels: clustering
> Fix For: 2.20.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (CAMEL-11815) cluster-service : camel-zookeeper spring boot support

[Luca Burgazzoli (JIRA)]

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

Work on CAMEL-11815 started by Luca Burgazzoli.
---
> cluster-service : camel-zookeeper spring boot support
> -
>
> Key: CAMEL-11815
> URL: https://issues.apache.org/jira/browse/CAMEL-11815
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-zookeeper
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>  Labels: clustering
> Fix For: 2.21.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11816) cluster-service : camel-consul spring boot support

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11816:
---

 Summary: cluster-service : camel-consul spring boot support
 Key: CAMEL-11816
 URL: https://issues.apache.org/jira/browse/CAMEL-11816
 Project: Camel
  Issue Type: Improvement
  Components: camel-zookeeper
Reporter: Luca Burgazzoli
Assignee: Luca Burgazzoli
Priority: Minor
 Fix For: 2.21.0






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11815) cluster-service : camel-zookeeper spring boot support

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11815:
---

 Summary: cluster-service : camel-zookeeper spring boot support
 Key: CAMEL-11815
 URL: https://issues.apache.org/jira/browse/CAMEL-11815
 Project: Camel
  Issue Type: Improvement
  Components: camel-zookeeper
Reporter: Luca Burgazzoli
Assignee: Luca Burgazzoli
Priority: Minor
 Fix For: 2.21.0






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11806) cluster service : add JMX support

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-11806:

Summary: cluster service : add JMX support  (was: clustered service : add 
JMX support)

> cluster service : add JMX support
> -
>
> Key: CAMEL-11806
> URL: https://issues.apache.org/jira/browse/CAMEL-11806
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>  Labels: clustering
> Fix For: 2.20.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11801) cluster service : use reference count to join/leave a cluster

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-11801:

Summary: cluster service : use reference count to join/leave a cluster  
(was: cluster view : use reference count to join/leave a cluster)

> cluster service : use reference count to join/leave a cluster
> -
>
> Key: CAMEL-11801
> URL: https://issues.apache.org/jira/browse/CAMEL-11801
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>  Labels: clustering
> Fix For: 2.20.0
>
>
> As today when a view is acquired it is also automatically started and never 
> stopped until the service it belongs to is stopped, there should be a way to 
> stop start/stop views according to effective usage.
> {code:java}
> // get and increase reference
> CamelClusterView view = clusterService.getView("...");
> // release the view and stop it when ref count is zero.
> boolean released = clusterService.releaseView(view);
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11808) log4j2 2.9 upgrade causes errors in camel-salesforce and others

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli commented on CAMEL-11808:
-

Salesforce maven plugin uses velocity 1.7 which has hard dependency on log4j 
1.x API, we should think to upgrade to velocity 2.0 which uses slf4j or use 
code generation tools like java poet or forge roaster (CAMEL-11226).

> log4j2 2.9 upgrade causes errors in camel-salesforce and others
> ---
>
> Key: CAMEL-11808
> URL: https://issues.apache.org/jira/browse/CAMEL-11808
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.21.0
>Reporter: Claus Ibsen
>Priority: Minor
>
> [12:28:26]  davsclaus, master build fails with [ERROR] 
> Failed to execute goal 
> org.apache.maven.plugins:maven-plugin-plugin:3.4:helpmojo (help-goal) on 
> project camel-salesforce-maven-plugin: Execution help-goal of goal 
> org.apache.maven.plugins:maven-plugin-plugin:3.4:helpmojo failed. 
> IllegalArgumentException -> [Help 1]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11814) camel-spring-boot - Recent change in startup behaviour can cause camel-test-spring problems

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-11814:
---

 Summary: camel-spring-boot - Recent change in startup behaviour 
can cause camel-test-spring problems
 Key: CAMEL-11814
 URL: https://issues.apache.org/jira/browse/CAMEL-11814
 Project: Camel
  Issue Type: Bug
  Components: camel-spring, camel-spring-boot
Affects Versions: 2.20.0
Reporter: Claus Ibsen
 Fix For: 2.20.0


Creating this ticket up front as I was testing CiA2 source code with 
2.20.0-SNAPSHOT and have issues with a camel spring boot app, that caused the 
test method to be executed without CamelContext been started prior - this works 
fine on 2.19.x and older versions.

Its very likely the new startup/shutdown change in camel-spring / 
camel-spring-boot that is causing a regression problem. A bit weird our own set 
of unit tests at Apache Camel hasn't triggered this.

Doing some more testing on CiA2 before posting more information here.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11813) Wrong check in ConnectorCatalogNexusRepository

[Zoran Regvart (JIRA)]

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

Zoran Regvart resolved CAMEL-11813.
---
   Resolution: Fixed
Fix Version/s: 2.20.0

Fixed via [PR#1953|https://github.com/apache/camel/pull/1953]

> Wrong check in ConnectorCatalogNexusRepository
> --
>
> Key: CAMEL-11813
> URL: https://issues.apache.org/jira/browse/CAMEL-11813
> Project: Camel
>  Issue Type: Bug
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Trivial
> Fix For: 2.20.0
>
>
> {{ConnectorCatalogNexusRepository}} at 109 checks if the return of 
> {{loadConnectorJSonSchema}} is {{null}} but it never can be null, it could 
> hold three null values instead.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (CAMEL-11778) New camel-ldif component

[Tim Hurman (JIRA)]

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

Tim Hurman closed CAMEL-11778.
--

> New camel-ldif component
> 
>
> Key: CAMEL-11778
> URL: https://issues.apache.org/jira/browse/CAMEL-11778
> Project: Camel
>  Issue Type: New Feature
>Reporter: Tim Hurman
>Assignee: Claus Ibsen
>  Labels: patch
> Fix For: 2.20.0
>
> Attachments: camel-ldif.diff
>
>
> I've created a new component to process LDIF files. This is to process update 
> changes to LDAP servers. I've attached a diff file against the Camel git 
> repository.
> Please let me know if this is okay or any changes need to be made. I'm happy 
> to fix them up.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11813) Wrong check in ConnectorCatalogNexusRepository

[Zoran Regvart (JIRA)]

Zoran Regvart created CAMEL-11813:
-

 Summary: Wrong check in ConnectorCatalogNexusRepository
 Key: CAMEL-11813
 URL: https://issues.apache.org/jira/browse/CAMEL-11813
 Project: Camel
  Issue Type: Bug
Reporter: Zoran Regvart
Assignee: Zoran Regvart
Priority: Trivial


{{ConnectorCatalogNexusRepository}} at 109 checks if the return of 
{{loadConnectorJSonSchema}} is {{null}} but it never can be null, it could hold 
three null values instead.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11778) New camel-ldif component

[Tim Hurman (JIRA)]

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

Tim Hurman commented on CAMEL-11778:


No problems, hope it helps someone.

> New camel-ldif component
> 
>
> Key: CAMEL-11778
> URL: https://issues.apache.org/jira/browse/CAMEL-11778
> Project: Camel
>  Issue Type: New Feature
>Reporter: Tim Hurman
>Assignee: Claus Ibsen
>  Labels: patch
> Fix For: 2.20.0
>
> Attachments: camel-ldif.diff
>
>
> I've created a new component to process LDIF files. This is to process update 
> changes to LDAP servers. I've attached a diff file against the Camel git 
> repository.
> Please let me know if this is okay or any changes need to be made. I'm happy 
> to fix them up.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11812) spring-boot-starter - Unit test fail in netty

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11812.
-
Resolution: Fixed
  Assignee: Claus Ibsen

> spring-boot-starter - Unit test fail in netty
> -
>
> Key: CAMEL-11812
> URL: https://issues.apache.org/jira/browse/CAMEL-11812
> Project: Camel
>  Issue Type: Test
>  Components: camel-spring-boot-starters
>Affects Versions: 2.20.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.20.0
>
>
> The netty-http-starter fails unit test with a NPE



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11812) spring-boot-starter - Unit test fail in netty

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11812:
-

Okay I got it to pass, so it looks like a smell when you use singleton scoped 
auto configuration beans and then autowire fields. You should not do the latter 
by provide then as parameters - like the others do

> spring-boot-starter - Unit test fail in netty
> -
>
> Key: CAMEL-11812
> URL: https://issues.apache.org/jira/browse/CAMEL-11812
> Project: Camel
>  Issue Type: Test
>  Components: camel-spring-boot-starters
>Affects Versions: 2.20.0
>Reporter: Claus Ibsen
> Fix For: 2.20.0
>
>
> The netty-http-starter fails unit test with a NPE



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11812) spring-boot-starter - Unit test fail in netty

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11812:
-

Its some spring boot auto configuration that causes the NPE.

> spring-boot-starter - Unit test fail in netty
> -
>
> Key: CAMEL-11812
> URL: https://issues.apache.org/jira/browse/CAMEL-11812
> Project: Camel
>  Issue Type: Test
>  Components: camel-spring-boot-starters
>Affects Versions: 2.20.0
>Reporter: Claus Ibsen
> Fix For: 2.20.0
>
>
> The netty-http-starter fails unit test with a NPE



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11812) spring-boot-starter - Unit test fail in netty

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-11812:
---

 Summary: spring-boot-starter - Unit test fail in netty
 Key: CAMEL-11812
 URL: https://issues.apache.org/jira/browse/CAMEL-11812
 Project: Camel
  Issue Type: Test
  Components: camel-spring-boot-starters
Affects Versions: 2.20.0
Reporter: Claus Ibsen
 Fix For: 2.20.0


The netty-http-starter fails unit test with a NPE




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11811) Camel FTP fails to create intermediate directory

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11811:

Priority: Minor  (was: Major)

> Camel FTP fails to create intermediate directory
> 
>
> Key: CAMEL-11811
> URL: https://issues.apache.org/jira/browse/CAMEL-11811
> Project: Camel
>  Issue Type: Bug
>  Components: camel-ftp
>Affects Versions: 2.18.2
>Reporter: Chi Kim
>Priority: Minor
>
> Camel Ftp fails to create intermediate directory if more than the immediate 
> parent directory is missing.
> in FtpOperations.buildDirectoryChunks,
> the mkdir command for intermediate directories are being made with trailing 
> slash.
> Some ftp does not like the trailing slash with mkdir command.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11811) Camel FTP fails to create intermediate directory

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11811:

Component/s: camel-ftp

> Camel FTP fails to create intermediate directory
> 
>
> Key: CAMEL-11811
> URL: https://issues.apache.org/jira/browse/CAMEL-11811
> Project: Camel
>  Issue Type: Bug
>  Components: camel-ftp
>Affects Versions: 2.18.2
>Reporter: Chi Kim
>
> Camel Ftp fails to create intermediate directory if more than the immediate 
> parent directory is missing.
> in FtpOperations.buildDirectoryChunks,
> the mkdir command for intermediate directories are being made with trailing 
> slash.
> Some ftp does not like the trailing slash with mkdir command.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11811) Camel FTP fails to create intermediate directory

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11811:
-

Can you post some logs or something that shows this problem for you?

> Camel FTP fails to create intermediate directory
> 
>
> Key: CAMEL-11811
> URL: https://issues.apache.org/jira/browse/CAMEL-11811
> Project: Camel
>  Issue Type: Bug
>  Components: camel-ftp
>Affects Versions: 2.18.2
>Reporter: Chi Kim
>
> Camel Ftp fails to create intermediate directory if more than the immediate 
> parent directory is missing.
> in FtpOperations.buildDirectoryChunks,
> the mkdir command for intermediate directories are being made with trailing 
> slash.
> Some ftp does not like the trailing slash with mkdir command.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11778) New camel-ldif component

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11778:


Github user asfgit closed the pull request at:

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


> New camel-ldif component
> 
>
> Key: CAMEL-11778
> URL: https://issues.apache.org/jira/browse/CAMEL-11778
> Project: Camel
>  Issue Type: New Feature
>Reporter: Tim Hurman
>Assignee: Claus Ibsen
>  Labels: patch
> Fix For: 2.20.0
>
> Attachments: camel-ldif.diff
>
>
> I've created a new component to process LDIF files. This is to process update 
> changes to LDAP servers. I've attached a diff file against the Camel git 
> repository.
> Please let me know if this is okay or any changes need to be made. I'm happy 
> to fix them up.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11778) New camel-ldif component

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11778.
-
Resolution: Fixed

Thanks for the contribution

> New camel-ldif component
> 
>
> Key: CAMEL-11778
> URL: https://issues.apache.org/jira/browse/CAMEL-11778
> Project: Camel
>  Issue Type: New Feature
>Reporter: Tim Hurman
>Assignee: Claus Ibsen
>  Labels: patch
> Fix For: 2.20.0
>
> Attachments: camel-ldif.diff
>
>
> I've created a new component to process LDIF files. This is to process update 
> changes to LDAP servers. I've attached a diff file against the Camel git 
> repository.
> Please let me know if this is okay or any changes need to be made. I'm happy 
> to fix them up.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-11778) New camel-ldif component

[Claus Ibsen (JIRA)]

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

Claus Ibsen reassigned CAMEL-11778:
---

Assignee: Claus Ibsen

> New camel-ldif component
> 
>
> Key: CAMEL-11778
> URL: https://issues.apache.org/jira/browse/CAMEL-11778
> Project: Camel
>  Issue Type: New Feature
>Reporter: Tim Hurman
>Assignee: Claus Ibsen
>  Labels: patch
> Fix For: 2.20.0
>
> Attachments: camel-ldif.diff
>
>
> I've created a new component to process LDIF files. This is to process update 
> changes to LDAP servers. I've attached a diff file against the Camel git 
> repository.
> Please let me know if this is okay or any changes need to be made. I'm happy 
> to fix them up.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11778) New camel-ldif component

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11778:


GitHub user kanwhoa opened a pull request:

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

CAMEL-11778: Added LDIF component

See CAMEL-11778

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

$ git pull https://github.com/kanwhoa/camel camel-ldif

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

https://github.com/apache/camel/pull/1952.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 #1952


commit c91fdedacbb5f99db5cb5a21b6dc95b278e0c361
Author: Tim Hurman 
Date:   2017-09-23T06:42:57Z

Added LDIF component




> New camel-ldif component
> 
>
> Key: CAMEL-11778
> URL: https://issues.apache.org/jira/browse/CAMEL-11778
> Project: Camel
>  Issue Type: New Feature
>Reporter: Tim Hurman
>  Labels: patch
> Fix For: 2.20.0
>
> Attachments: camel-ldif.diff
>
>
> I've created a new component to process LDIF files. This is to process update 
> changes to LDAP servers. I've attached a diff file against the Camel git 
> repository.
> Please let me know if this is okay or any changes need to be made. I'm happy 
> to fix them up.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)