[jira] [Assigned] (CAMEL-10493) Typo in documentation

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino reassigned CAMEL-10493:


Assignee: Andrea Cosentino

> Typo in documentation
> -
>
> Key: CAMEL-10493
> URL: https://issues.apache.org/jira/browse/CAMEL-10493
> Project: Camel
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 2.15.3
>Reporter: Tatyana Bardakh
>Assignee: Andrea Cosentino
>Priority: Trivial
> Fix For: Future
>
>
> Splitter doc:
> Camel 2.14: If enabled then the aggregate method on AggregationStrategy can 
> be called concurrently. Notice that this would require the implementation of 
> AggregationStrategy to be implemented as thread-safe. By default this is 
> false meaning that Camel synchronizes the call to the aggregate method. 
> Though in some use-cases this can be used to {color: red}archive{color} 
> higher performance when the AggregationStrategy is implemented as thread-safe.
> Should be: achieve



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

[jira] [Created] (CAMEL-10493) Typo in documentation

[Tatyana Bardakh (JIRA)]

Tatyana Bardakh created CAMEL-10493:
---

 Summary: Typo in documentation
 Key: CAMEL-10493
 URL: https://issues.apache.org/jira/browse/CAMEL-10493
 Project: Camel
  Issue Type: Improvement
  Components: documentation
Affects Versions: 2.15.3
Reporter: Tatyana Bardakh
Priority: Trivial
 Fix For: Future


Splitter doc:

Camel 2.14: If enabled then the aggregate method on AggregationStrategy can be 
called concurrently. Notice that this would require the implementation of 
AggregationStrategy to be implemented as thread-safe. By default this is false 
meaning that Camel synchronizes the call to the aggregate method. Though in 
some use-cases this can be used to {color: red}archive{color} higher 
performance when the AggregationStrategy is implemented as thread-safe.

Should be: achieve



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

[jira] [Updated] (CAMEL-10492) Camel Servlet, headers instance of String

[Fabrizio Spataro (JIRA)]

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

Fabrizio Spataro updated CAMEL-10492:
-
Attachment: camel-example-servlet-attachment.zip

> Camel Servlet, headers instance of String
> -
>
> Key: CAMEL-10492
> URL: https://issues.apache.org/jira/browse/CAMEL-10492
> Project: Camel
>  Issue Type: Bug
>  Components: camel-servlet
>Reporter: Fabrizio Spataro
>Priority: Minor
> Attachments: camel-example-servlet-attachment.zip
>
>
> Since 2.18 i have a new bug!
> I send a multipart form data to my camel servlet, before camel 2.18 i have an 
> attachment object every form field.
> Now i have an header every form field.
> It is ok but ALL header (form field) are instance of java.lang.String
> So, I can not post any binary file.
> Is it a camel bug? 
> This is my filter into web.xml
> {code:xml}
>   
>   MultipartFilter
>   
> org.eclipse.jetty.servlets.MultiPartFilter
>   
>   
>   MultipartFilter
>   CamelServlet
>   
> {code}
> Into zip file, you can found an example.



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

[jira] [Updated] (CAMEL-10492) Camel Servlet, headers instance of String

[Fabrizio Spataro (JIRA)]

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

Fabrizio Spataro updated CAMEL-10492:
-
Description: 
Since 2.18 i have a new bug!

I send a multipart form data to my camel servlet, before camel 2.18 i have an 
*attachment object* every form field.
Now i have an *header* every form field.
It is ok but ALL header (form field) are instance of java.lang.String

So, I can not post any binary file.

Is it a camel bug? 

This is my filter into web.xml

{code:xml}

MultipartFilter

org.eclipse.jetty.servlets.MultiPartFilter


MultipartFilter
CamelServlet

{code}

Into zip file, you can found an example.

  was:
Since 2.18 i have a new bug!

I send a multipart form data to my camel servlet, before camel 2.18 i have an 
attachment object every form field.
Now i have an header every form field.
It is ok but ALL header (form field) are instance of java.lang.String

So, I can not post any binary file.

Is it a camel bug? 

This is my filter into web.xml

{code:xml}

MultipartFilter

org.eclipse.jetty.servlets.MultiPartFilter


MultipartFilter
CamelServlet

{code}

Into zip file, you can found an example.


> Camel Servlet, headers instance of String
> -
>
> Key: CAMEL-10492
> URL: https://issues.apache.org/jira/browse/CAMEL-10492
> Project: Camel
>  Issue Type: Bug
>  Components: camel-servlet
>Reporter: Fabrizio Spataro
>Priority: Minor
> Attachments: camel-example-servlet-attachment.zip
>
>
> Since 2.18 i have a new bug!
> I send a multipart form data to my camel servlet, before camel 2.18 i have an 
> *attachment object* every form field.
> Now i have an *header* every form field.
> It is ok but ALL header (form field) are instance of java.lang.String
> So, I can not post any binary file.
> Is it a camel bug? 
> This is my filter into web.xml
> {code:xml}
>   
>   MultipartFilter
>   
> org.eclipse.jetty.servlets.MultiPartFilter
>   
>   
>   MultipartFilter
>   CamelServlet
>   
> {code}
> Into zip file, you can found an example.



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

[jira] [Created] (CAMEL-10492) Camel Servlet, headers instance of String

[Fabrizio Spataro (JIRA)]

Fabrizio Spataro created CAMEL-10492:


 Summary: Camel Servlet, headers instance of String
 Key: CAMEL-10492
 URL: https://issues.apache.org/jira/browse/CAMEL-10492
 Project: Camel
  Issue Type: Bug
  Components: camel-servlet
Reporter: Fabrizio Spataro
Priority: Minor


Since 2.18 i have a new bug!

I send a multipart form data to my camel servlet, before camel 2.18 i have an 
attachment object every form field.
Now i have an header every form field.
It is ok but ALL header (form field) are instance of java.lang.String

So, I can not post any binary file.

Is it a camel bug? 

This is my filter into web.xml

{code:xml}

MultipartFilter

org.eclipse.jetty.servlets.MultiPartFilter


MultipartFilter
CamelServlet

{code}

Into zip file, you can found an example.



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

[jira] [Assigned] (CAMEL-10491) Spring-LDAP - Add support for authenticate, modify_attributes and function_driven operations

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino reassigned CAMEL-10491:


Assignee: Andrea Cosentino

> Spring-LDAP - Add support for authenticate, modify_attributes and 
> function_driven operations
> 
>
> Key: CAMEL-10491
> URL: https://issues.apache.org/jira/browse/CAMEL-10491
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 2.19.0
>Reporter: Bhavesh
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.19.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>




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

[jira] [Commented] (CAMEL-10491) Spring-LDAP - Add support for authenticate, modify_attributes and function_driven operations

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-10491:


GitHub user bhaveshdt opened a pull request:

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

CAMEL-10491 - Spring-LDAP - Add support for authenticate, modify_attributes 
and function_driven operations 

Please pay special attention to the newly added FUNCTION_DRIVEN operation.

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

$ git pull https://github.com/bhaveshdt/camel master

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

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


commit 2f26ffe96e085df7e2bb6f0a52d6a6e1d3852e6f
Author: Bhavesh Thakker 
Date:   2016-11-16T20:59:45Z

Added support for authenticate, modify_attributes and function_driven 
operations

commit bb73292c44dd916dba51304edceee0c1d16307aa
Author: THAKKBH 
Date:   2016-11-16T21:23:17Z

Check-style related changes

commit 1a4519f25036b415707a49cc020d1b3b99c7f0ae
Author: Bhavesh Thakker 
Date:   2016-11-16T21:23:17Z

Check-style related changes

commit 77e763aec6e21b5aee523db00ef70054157c9dc8
Author: Thakker 
Date:   2016-11-16T21:25:34Z

Merge branch 'master' of https://github.com/bhaveshdt/camel

commit ded7ebdb0ee5b8272d8d3107c217cb8555e818e8
Author: Thakker 
Date:   2016-11-17T14:52:10Z

Merge remote-tracking branch 'camel_upstream/master'




> Spring-LDAP - Add support for authenticate, modify_attributes and 
> function_driven operations
> 
>
> Key: CAMEL-10491
> URL: https://issues.apache.org/jira/browse/CAMEL-10491
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 2.19.0
>Reporter: Bhavesh
>Priority: Minor
> Fix For: 2.19.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>




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

[jira] [Created] (CAMEL-10491) Spring-LDAP - Add support for authenticate, modify_attributes and function_driven operations

[Bhavesh (JIRA)]

Bhavesh created CAMEL-10491:
---

 Summary: Spring-LDAP - Add support for authenticate, 
modify_attributes and function_driven operations
 Key: CAMEL-10491
 URL: https://issues.apache.org/jira/browse/CAMEL-10491
 Project: Camel
  Issue Type: Improvement
Affects Versions: 2.19.0
Reporter: Bhavesh
Priority: Minor
 Fix For: 2.19.0






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

[jira] [Commented] (CAMEL-10490) JpaPollingConsumer does not support consumeLockEntity and others

[Bob Gaudaen (JIRA)]

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

Bob Gaudaen commented on CAMEL-10490:
-

@[~davsclaus], I'll try to submit a patch in the next days unless you think it 
is not a bug.

> JpaPollingConsumer does not support consumeLockEntity and others
> 
>
> Key: CAMEL-10490
> URL: https://issues.apache.org/jira/browse/CAMEL-10490
> Project: Camel
>  Issue Type: Bug
>  Components: camel-jpa
>Affects Versions: 2.18.0
>Reporter: Bob Gaudaen
>
> Since the introduction of JpaPollingConsumer in camel 2.18.0, it is not 
> possible anymore to use some of jpa consumer options (consumeLockEntity, 
> consumeDelete, ...).
> Documentation also lacks some information on which option can be used by the 
> jpa consumer and not by the polling consumer.



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

[jira] [Created] (CAMEL-10490) JpaPollingConsumer does not support consumeLockEntity and others

[Bob Gaudaen (JIRA)]

Bob Gaudaen created CAMEL-10490:
---

 Summary: JpaPollingConsumer does not support consumeLockEntity and 
others
 Key: CAMEL-10490
 URL: https://issues.apache.org/jira/browse/CAMEL-10490
 Project: Camel
  Issue Type: Bug
  Components: camel-jpa
Affects Versions: 2.18.0
Reporter: Bob Gaudaen


Since the introduction of JpaPollingConsumer in camel 2.18.0, it is not 
possible anymore to use some of jpa consumer options (consumeLockEntity, 
consumeDelete, ...).

Documentation also lacks some information on which option can be used by the 
jpa consumer and not by the polling consumer.




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

[jira] [Resolved] (CAMEL-10489) Camel-Nats: Add Flush option with timeout

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino resolved CAMEL-10489.
--
Resolution: Fixed

> Camel-Nats: Add Flush option with timeout
> -
>
> Key: CAMEL-10489
> URL: https://issues.apache.org/jira/browse/CAMEL-10489
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-nats
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.19.0
>
>
> As you may see from the docs of Jnats, we can specify a timeout while 
> flushing the connection to server.
> It can be useful to specify the flush option and a timeout related to it, to 
> be sure we will try to be reliable with our component.



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

[jira] [Created] (CAMEL-10489) Camel-Nats: Add Flush option with timeout

[Andrea Cosentino (JIRA)]

Andrea Cosentino created CAMEL-10489:


 Summary: Camel-Nats: Add Flush option with timeout
 Key: CAMEL-10489
 URL: https://issues.apache.org/jira/browse/CAMEL-10489
 Project: Camel
  Issue Type: New Feature
  Components: camel-nats
Reporter: Andrea Cosentino
Assignee: Andrea Cosentino
Priority: Minor
 Fix For: 2.19.0


As you may see from the docs of Jnats, we can specify a timeout while flushing 
the connection to server.

It can be useful to specify the flush option and a timeout related to it, to be 
sure we will try to be reliable with our component.



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