[jira] [Created] (CAMEL-11231) JSON Api Dataformat

2017-05-04 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-11231:
-

 Summary: JSON Api Dataformat
 Key: CAMEL-11231
 URL: https://issues.apache.org/jira/browse/CAMEL-11231
 Project: Camel
  Issue Type: New Feature
Reporter: Charles Moulliard


Implement a new DataFormat to support to serialize/deserialize JSONApi 
Objects/Strings as defined within the spec : http://jsonapi.org/

Potential candidate projects to be evaluated :
- https://github.com/jasminb/jsonapi-converter
- https://github.com/faogustavo/JSONApi



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Reopened] (CAMEL-10136) Missing Group attribute for Tokenize DSL added to the Body Expression

2016-07-16 Thread Charles Moulliard (JIRA)

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

Charles Moulliard reopened CAMEL-10136:
---

> Missing Group attribute for Tokenize DSL added to the Body Expression
> -
>
> Key: CAMEL-10136
> URL: https://issues.apache.org/jira/browse/CAMEL-10136
> Project: Camel
>  Issue Type: Bug
>Reporter: Charles Moulliard
>Assignee: Claus Ibsen
>
> The option group ("",".tokenize("\n", 
> 1000)") doesn't exist when we use the Tokenize DSL after a body expression
> {code}
> .split(body(String.class).tokenize("\n")).streaming()
> {code}
> but only when we create append the .tokenize() DSL to the splitter
> {code}
> .split().tokenize("\n",3).streaming()
> {code}
> Question : Is it the expected behaviour or something missing ?



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


[jira] [Commented] (CAMEL-10136) Missing Group attribute for Tokenize DSL added to the Body Expression

2016-07-15 Thread Charles Moulliard (JIRA)

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

Charles Moulliard commented on CAMEL-10136:
---

There is an inconsistency as the Java Fluent API ".split().tokenize("\n",3)" 
supports the group option and not this other syntax 
".split(body(String.class).tokenize("\n"))"

> Missing Group attribute for Tokenize DSL added to the Body Expression
> -
>
> Key: CAMEL-10136
> URL: https://issues.apache.org/jira/browse/CAMEL-10136
> Project: Camel
>  Issue Type: Bug
>Reporter: Charles Moulliard
>Assignee: Claus Ibsen
>
> The option group ("",".tokenize("\n", 
> 1000)") doesn't exist when we use the Tokenize DSL after a body expression
> {code}
> .split(body(String.class).tokenize("\n")).streaming()
> {code}
> but only when we create append the .tokenize() DSL to the splitter
> {code}
> .split().tokenize("\n",3).streaming()
> {code}
> Question : Is it the expected behaviour or something missing ?



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


[jira] [Updated] (CAMEL-10136) Missing Group attribute for Tokenize DSL added to the Body Expression

2016-07-11 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-10136:
--
Affects Version/s: (was: 2.15.3)

> Missing Group attribute for Tokenize DSL added to the Body Expression
> -
>
> Key: CAMEL-10136
> URL: https://issues.apache.org/jira/browse/CAMEL-10136
> Project: Camel
>  Issue Type: Bug
>Reporter: Charles Moulliard
>
> The option group ("",".tokenize("\n", 
> 1000)") doesn't exist when we use the Tokenize DSL after a body expression
> {code}
> .split(body(String.class).tokenize("\n")).streaming()
> {code}
> but only when we create append the .tokenize() DSL to the splitter
> {code}
> .split().tokenize("\n",3).streaming()
> {code}
> Question : Is it the expected behaviour or something missing ?



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


[jira] [Updated] (CAMEL-10136) Missing Group attribute for Tokenize DSL added to the Body Expression

2016-07-11 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-10136:
--
Summary: Missing Group attribute for Tokenize DSL added to the Body 
Expression  (was: Missing Group attribute for Token DSL)

> Missing Group attribute for Tokenize DSL added to the Body Expression
> -
>
> Key: CAMEL-10136
> URL: https://issues.apache.org/jira/browse/CAMEL-10136
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.15.3
>Reporter: Charles Moulliard
>
> The option group ("",".tokenize("\n", 
> 1000)") doesn't exist when we use the Tokenize DSL after a body expression
> {code}
> .split(body(String.class).tokenize("\n")).streaming()
> {code}
> but only when we create append the .tokenize() DSL to the splitter
> {code}
> .split().tokenize("\n",3).streaming()
> {code}
> Question : Is it the expected behaviour or something missing ?



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


[jira] [Updated] (CAMEL-10136) Missing Group attribute for Token DSL

2016-07-11 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-10136:
--
Description: 
The option group ("",".tokenize("\n", 
1000)") doesn't exist when we use the Tokenize DSL after a body expression
{code}
.split(body(String.class).tokenize("\n")).streaming()
{code}

but only when we create append the .tokenize() DSL to the splitter

{code}
.split().tokenize("\n",3).streaming()
{code}

Question : Is it the expected behaviour or something missing ?

  was:
The option group ("",".tokenize("\n", 
1000)") doesn't exist when using the Token DSL but only when we create a 
TokenExpression

{code}
TokenizerExpression token = new TokenizerExpression();
token.setGroup(1000);
token.setToken("\n");
{code}

Either the code is incomplete or the Camel Doc  (See Splitting by Grouping N 
lines) - http://camel.apache.org/splitter.html


> Missing Group attribute for Token DSL
> -
>
> Key: CAMEL-10136
> URL: https://issues.apache.org/jira/browse/CAMEL-10136
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.15.3
>Reporter: Charles Moulliard
>
> The option group ("",".tokenize("\n", 
> 1000)") doesn't exist when we use the Tokenize DSL after a body expression
> {code}
> .split(body(String.class).tokenize("\n")).streaming()
> {code}
> but only when we create append the .tokenize() DSL to the splitter
> {code}
> .split().tokenize("\n",3).streaming()
> {code}
> Question : Is it the expected behaviour or something missing ?



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


[jira] [Updated] (CAMEL-10136) Missing Group attribute for Token DSL

2016-07-11 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-10136:
--
Affects Version/s: (was: 2.17.1)
   (was: 2.16.3)
   (was: 2.15.6)
   2.15.3

> Missing Group attribute for Token DSL
> -
>
> Key: CAMEL-10136
> URL: https://issues.apache.org/jira/browse/CAMEL-10136
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.15.3
>Reporter: Charles Moulliard
>
> The option group ("",".tokenize("\n", 
> 1000)") doesn't exist when using the Token DSL but only when we create a 
> TokenExpression
> {code}
> TokenizerExpression token = new TokenizerExpression();
> token.setGroup(1000);
> token.setToken("\n");
> {code}
> Either the code is incomplete or the Camel Doc  (See Splitting by Grouping N 
> lines) - http://camel.apache.org/splitter.html



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


[jira] [Updated] (CAMEL-10136) Missing Group attribute for Token DSL

2016-07-11 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-10136:
--
Description: 
The option group ("",".tokenize("\n", 
1000)") doesn't exist when using the Token DSL but only when we create a 
TokenExpression

{code}
TokenizerExpression token = new TokenizerExpression();
token.setGroup(1000);
token.setToken("\n");
{code}

Either the code is incomplete or the Camel Doc  (See Splitting by Grouping N 
lines) - http://camel.apache.org/splitter.html

  was:
The option group ("",".tokenize("\n", 
1000)") doesn't exist when using the Token DSL but only when we create a 
TokenExpression

{code}
TokenizerExpression token = new TokenizerExpression();
token.setGroup(1000);
token.setToken("\n");
{coee}

Either the code is incomplete or the Camel Doc  (See Splitting by Grouping N 
lines) - http://camel.apache.org/splitter.html


> Missing Group attribute for Token DSL
> -
>
> Key: CAMEL-10136
> URL: https://issues.apache.org/jira/browse/CAMEL-10136
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.15.6, 2.16.3, 2.17.1
>Reporter: Charles Moulliard
>
> The option group ("",".tokenize("\n", 
> 1000)") doesn't exist when using the Token DSL but only when we create a 
> TokenExpression
> {code}
> TokenizerExpression token = new TokenizerExpression();
> token.setGroup(1000);
> token.setToken("\n");
> {code}
> Either the code is incomplete or the Camel Doc  (See Splitting by Grouping N 
> lines) - http://camel.apache.org/splitter.html



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


[jira] [Created] (CAMEL-10136) Missing Group attribute for Token DSL

2016-07-11 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-10136:
-

 Summary: Missing Group attribute for Token DSL
 Key: CAMEL-10136
 URL: https://issues.apache.org/jira/browse/CAMEL-10136
 Project: Camel
  Issue Type: Bug
Affects Versions: 2.17.1, 2.16.3, 2.15.6
Reporter: Charles Moulliard


The option group ("",".tokenize("\n", 
1000)") doesn't exist when using the Token DSL but only when we create a 
TokenExpression

{code}
TokenizerExpression token = new TokenizerExpression();
token.setGroup(1000);
token.setToken("\n");
{coee}

Either the code is incomplete or the Camel Doc  (See Splitting by Grouping N 
lines) - http://camel.apache.org/splitter.html



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


[jira] [Assigned] (CAMEL-9895) Setup a by default password to access the spring boot ssh server

2016-04-21 Thread Charles Moulliard (JIRA)

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

Charles Moulliard reassigned CAMEL-9895:


Assignee: Charles Moulliard

> Setup a by default password to access the spring boot ssh server
> 
>
> Key: CAMEL-9895
> URL: https://issues.apache.org/jira/browse/CAMEL-9895
> Project: Camel
>  Issue Type: Bug
>  Components: examples
>Reporter: Charles Moulliard
>Assignee: Charles Moulliard
> Fix For: 2.18.0
>
>
> Setup a by default password to access the spring boot ssh server in order to 
> simplify the access to the SSH server as it is not so easy to get the random 
> generated password
> {code}
> Parameter to be added within the application.yml file
> shell.auth.simple.user.password: password
> {code}



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


[jira] [Resolved] (CAMEL-9895) Setup a by default password to access the spring boot ssh server

2016-04-21 Thread Charles Moulliard (JIRA)

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

Charles Moulliard resolved CAMEL-9895.
--
Resolution: Fixed

> Setup a by default password to access the spring boot ssh server
> 
>
> Key: CAMEL-9895
> URL: https://issues.apache.org/jira/browse/CAMEL-9895
> Project: Camel
>  Issue Type: Bug
>  Components: examples
>Reporter: Charles Moulliard
>Assignee: Charles Moulliard
> Fix For: 2.18.0
>
>
> Setup a by default password to access the spring boot ssh server in order to 
> simplify the access to the SSH server as it is not so easy to get the random 
> generated password
> {code}
> Parameter to be added within the application.yml file
> shell.auth.simple.user.password: password
> {code}



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


[jira] [Created] (CAMEL-9895) Setup a by default password to access the spring boot ssh server

2016-04-21 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-9895:


 Summary: Setup a by default password to access the spring boot ssh 
server
 Key: CAMEL-9895
 URL: https://issues.apache.org/jira/browse/CAMEL-9895
 Project: Camel
  Issue Type: Bug
  Components: examples
Reporter: Charles Moulliard
 Fix For: 2.18.0


Setup a by default password to access the spring boot ssh server in order to 
simplify the access to the SSH server as it is not so easy to get the random 
generated password

{code}
Parameter to be added within the application.yml file
shell.auth.simple.user.password: password
{code}



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


[jira] [Commented] (CAMEL-9514) camel-netty4 maximumPoolSize option is ignored

2016-01-14 Thread Charles Moulliard (JIRA)

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

Charles Moulliard commented on CAMEL-9514:
--

And maybe the other params as well

> camel-netty4 maximumPoolSize option is ignored
> --
>
> Key: CAMEL-9514
> URL: https://issues.apache.org/jira/browse/CAMEL-9514
> Project: Camel
>  Issue Type: Task
>Affects Versions: 2.16.1, 2.15.5
>Reporter: Willem Jiang
>Assignee: Willem Jiang
> Fix For: 2.15.6, 2.16.2, 2.17.0
>
>
> We need to move the maximumPoolSize option to the camel-netty4 component as 
> wile.



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


[jira] [Created] (CAMEL-9272) openweathermap.org requires an APPID id since 09/10/2015

2015-10-29 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-9272:


 Summary: openweathermap.org requires an APPID id since 09/10/2015
 Key: CAMEL-9272
 URL: https://issues.apache.org/jira/browse/CAMEL-9272
 Project: Camel
  Issue Type: Bug
  Components: weather
Reporter: Charles Moulliard


Code must be updated as openweathermap.org requires an APPID id since 
09/10/2015 & by consequence, the component can't be used anymore as we will get 
a HTTP 401 error.

{code}
Caused by: org.apache.camel.TypeConversionException: Error during type 
conversion from type: java.net.URL to the required type: java.lang.String with 
value http://api.openweathermap.org/data/2.5/weather?q=Paris,France due 
java.io.IOException: Server returned HTTP response code: 401 for URL: 
http://api.openweathermap.org/data/2.5/weather?q=Paris,France
at 
org.apache.camel.impl.converter.BaseTypeConverterRegistry.createTypeConversionException(BaseTypeConverterRegistry.java:610)
at 
org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:177)
at 
org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:156)
at 
org.apache.camel.component.weather.WeatherProducer.process(WeatherProducer.java:48)
{code}



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


[jira] [Updated] (CAMEL-9272) openweathermap.org requires an APPID id since 09/10/2015

2015-10-29 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-9272:
-
Fix Version/s: 2.15.5
   2.16.1
   2.17

> openweathermap.org requires an APPID id since 09/10/2015
> 
>
> Key: CAMEL-9272
> URL: https://issues.apache.org/jira/browse/CAMEL-9272
> Project: Camel
>  Issue Type: Bug
>  Components: weather
>Reporter: Charles Moulliard
> Fix For: 2.16.1, 2.15.5, 2.17
>
>
> Code must be updated as openweathermap.org requires an APPID id since 
> 09/10/2015 & by consequence, the component can't be used anymore as we will 
> get a HTTP 401 error.
> {code}
> Caused by: org.apache.camel.TypeConversionException: Error during type 
> conversion from type: java.net.URL to the required type: java.lang.String 
> with value http://api.openweathermap.org/data/2.5/weather?q=Paris,France due 
> java.io.IOException: Server returned HTTP response code: 401 for URL: 
> http://api.openweathermap.org/data/2.5/weather?q=Paris,France
>   at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.createTypeConversionException(BaseTypeConverterRegistry.java:610)
>   at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:177)
>   at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:156)
>   at 
> org.apache.camel.component.weather.WeatherProducer.process(WeatherProducer.java:48)
> {code}



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


[jira] [Created] (CAMEL-9273) Enhance camel-weather component to support all the options of Api 2.5

2015-10-29 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-9273:


 Summary: Enhance camel-weather component to support all the 
options of Api 2.5
 Key: CAMEL-9273
 URL: https://issues.apache.org/jira/browse/CAMEL-9273
 Project: Camel
  Issue Type: Bug
  Components: camel-weather
Reporter: Charles Moulliard


Many others queries are supported by the weather Api.
We should update the component to support more options

{code}
WEATHER

Access current weather data for any location on Earth including over 200,000 
cities! Current weather is frequently updated based on global models and data 
from more than 40,000 weather stations. Data is available in JSON, XML, or HTML 
format.

api.openweathermap.org/data/2.5/weather?q={city name}
api.openweathermap.org/data/2.5/weather?q={city name},{country code}

api.openweathermap.org/data/2.5/weather?id=2172797

api.openweathermap.org/data/2.5/weather?lat={lat}={lon}

api.openweathermap.org/data/2.5/weather?zip={zip code},{country code}

api.openweathermap.org/data/2.5/box/city?bbox=12,32,15,37,10=yes

api.openweathermap.org/data/2.5/find?lat=55.5=37.5=10

api.openweathermap.org/data/2.5/group?id=524901,703448,2643743=metric

FORECAST - 5d

5 day forecast is available at any location or city. It includes weather data 
every 3 hours. Forecast is available in JSON, XML, or HTML format.

api.openweathermap.org/data/2.5/forecast?q={city name},{country code}
api.openweathermap.org/data/2.5/forecast?id={city ID}
api.openweathermap.org/data/2.5/forecast?lat={lat}={lon}

FORECAST - 16d

16 day forecasts is available at any location or city. Forecasts include daily 
weather and available in JSON, XML, or HTML format.

api.openweathermap.org/data/2.5/forecast/daily?q={city name},{country 
code}={cnt}
api.openweathermap.org/data/2.5/forecast/daily?id={city ID}={cnt}
api.openweathermap.org/data/2.5/forecast/daily?lat={lat}={lon}={cnt}

HISTORY

http://api.openweathermap.org/data/2.5/history/city?id={id}=hour={start}={end}
http://api.openweathermap.org/data/2.5/history/city?id={id}=hour={start}={cnt}

start start date (unix time, UTC time zone), e.g. start=1369728000
end end date (unix time, UTC time zone), e.g. end=1369789200
cnt amount of returned data (one per hour, can be used instead of 'end')

http://api.openweathermap.org/data/2.5/history/city?q={city ID},{country 
code}=hour={start}={end}

http://api.openweathermap.org/data/2.5/history/city?q={city ID},{country 
code}=hour={start}={cnt}

http://api.openweathermap.org/data/2.5/history/city?lat={lat}={lon}=hour={start}={end}
http://api.openweathermap.org/data/2.5/history/city?lat={lat}={lon}=hour={start}={cnt}

http://api.openweathermap.org/data/2.5/history/station?id={id}=tick
http://api.openweathermap.org/data/2.5/history/station?id={id}=hour
http://api.openweathermap.org/data/2.5/history/station?id={id}=day

STATION

http://api.openweathermap.org/data/2.5/station?id={id}
http://api.openweathermap.org/data/2.5/box/station?cluster={yes/no}={cnt}={bbox}
http://api.openweathermap.org/data/2.5/station/find?lat=55=37=30

{code}






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


[jira] [Commented] (CAMEL-9273) Enhance camel-weather component to support all the options of Api 2.5

2015-10-29 Thread Charles Moulliard (JIRA)

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

Charles Moulliard commented on CAMEL-9273:
--

Use HttpURLConnection class instead of calling the HTTP Server (Weather API) 
when the URL(q) is converted into a String.
That will allow to specify the method to be used, to define a timeout, to 
handle the response code

> Enhance camel-weather component to support all the options of Api 2.5
> -
>
> Key: CAMEL-9273
> URL: https://issues.apache.org/jira/browse/CAMEL-9273
> Project: Camel
>  Issue Type: Bug
>  Components: camel-weather
>Reporter: Charles Moulliard
>
> Many others queries are supported by the weather Api - 
> http://openweathermap.org/api.
> We should update the component to support more options
> {code}
> WEATHER
> Access current weather data for any location on Earth including over 200,000 
> cities! Current weather is frequently updated based on global models and data 
> from more than 40,000 weather stations. Data is available in JSON, XML, or 
> HTML format.
> api.openweathermap.org/data/2.5/weather?q={city name}
> api.openweathermap.org/data/2.5/weather?q={city name},{country code}
> api.openweathermap.org/data/2.5/weather?id=2172797
> api.openweathermap.org/data/2.5/weather?lat={lat}={lon}
> api.openweathermap.org/data/2.5/weather?zip={zip code},{country code}
> api.openweathermap.org/data/2.5/box/city?bbox=12,32,15,37,10=yes
> api.openweathermap.org/data/2.5/find?lat=55.5=37.5=10
> api.openweathermap.org/data/2.5/group?id=524901,703448,2643743=metric
> FORECAST - 5d
> 5 day forecast is available at any location or city. It includes weather data 
> every 3 hours. Forecast is available in JSON, XML, or HTML format.
> api.openweathermap.org/data/2.5/forecast?q={city name},{country code}
> api.openweathermap.org/data/2.5/forecast?id={city ID}
> api.openweathermap.org/data/2.5/forecast?lat={lat}={lon}
> FORECAST - 16d
> 16 day forecasts is available at any location or city. Forecasts include 
> daily weather and available in JSON, XML, or HTML format.
> api.openweathermap.org/data/2.5/forecast/daily?q={city name},{country 
> code}={cnt}
> api.openweathermap.org/data/2.5/forecast/daily?id={city ID}={cnt}
> api.openweathermap.org/data/2.5/forecast/daily?lat={lat}={lon}={cnt}
> HISTORY
> http://api.openweathermap.org/data/2.5/history/city?id={id}=hour={start}={end}
> http://api.openweathermap.org/data/2.5/history/city?id={id}=hour={start}={cnt}
> start start date (unix time, UTC time zone), e.g. start=1369728000
> end end date (unix time, UTC time zone), e.g. end=1369789200
> cnt amount of returned data (one per hour, can be used instead of 'end')
> http://api.openweathermap.org/data/2.5/history/city?q={city ID},{country 
> code}=hour={start}={end}
> http://api.openweathermap.org/data/2.5/history/city?q={city ID},{country 
> code}=hour={start}={cnt}
> http://api.openweathermap.org/data/2.5/history/city?lat={lat}={lon}=hour={start}={end}
> http://api.openweathermap.org/data/2.5/history/city?lat={lat}={lon}=hour={start}={cnt}
> http://api.openweathermap.org/data/2.5/history/station?id={id}=tick
> http://api.openweathermap.org/data/2.5/history/station?id={id}=hour
> http://api.openweathermap.org/data/2.5/history/station?id={id}=day
> STATION
> http://api.openweathermap.org/data/2.5/station?id={id}
> http://api.openweathermap.org/data/2.5/box/station?cluster={yes/no}={cnt}={bbox}
> http://api.openweathermap.org/data/2.5/station/find?lat=55=37=30
> {code}



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


[jira] [Updated] (CAMEL-9273) Enhance camel-weather component to support all the options of Api 2.5

2015-10-29 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-9273:
-
Description: 
Many others queries are supported by the weather Api - 
http://openweathermap.org/api.
We should update the component to support more options

{code}
WEATHER

Access current weather data for any location on Earth including over 200,000 
cities! Current weather is frequently updated based on global models and data 
from more than 40,000 weather stations. Data is available in JSON, XML, or HTML 
format.

api.openweathermap.org/data/2.5/weather?q={city name}
api.openweathermap.org/data/2.5/weather?q={city name},{country code}

api.openweathermap.org/data/2.5/weather?id=2172797

api.openweathermap.org/data/2.5/weather?lat={lat}={lon}

api.openweathermap.org/data/2.5/weather?zip={zip code},{country code}

api.openweathermap.org/data/2.5/box/city?bbox=12,32,15,37,10=yes

api.openweathermap.org/data/2.5/find?lat=55.5=37.5=10

api.openweathermap.org/data/2.5/group?id=524901,703448,2643743=metric

FORECAST - 5d

5 day forecast is available at any location or city. It includes weather data 
every 3 hours. Forecast is available in JSON, XML, or HTML format.

api.openweathermap.org/data/2.5/forecast?q={city name},{country code}
api.openweathermap.org/data/2.5/forecast?id={city ID}
api.openweathermap.org/data/2.5/forecast?lat={lat}={lon}

FORECAST - 16d

16 day forecasts is available at any location or city. Forecasts include daily 
weather and available in JSON, XML, or HTML format.

api.openweathermap.org/data/2.5/forecast/daily?q={city name},{country 
code}={cnt}
api.openweathermap.org/data/2.5/forecast/daily?id={city ID}={cnt}
api.openweathermap.org/data/2.5/forecast/daily?lat={lat}={lon}={cnt}

HISTORY

http://api.openweathermap.org/data/2.5/history/city?id={id}=hour={start}={end}
http://api.openweathermap.org/data/2.5/history/city?id={id}=hour={start}={cnt}

start start date (unix time, UTC time zone), e.g. start=1369728000
end end date (unix time, UTC time zone), e.g. end=1369789200
cnt amount of returned data (one per hour, can be used instead of 'end')

http://api.openweathermap.org/data/2.5/history/city?q={city ID},{country 
code}=hour={start}={end}

http://api.openweathermap.org/data/2.5/history/city?q={city ID},{country 
code}=hour={start}={cnt}

http://api.openweathermap.org/data/2.5/history/city?lat={lat}={lon}=hour={start}={end}
http://api.openweathermap.org/data/2.5/history/city?lat={lat}={lon}=hour={start}={cnt}

http://api.openweathermap.org/data/2.5/history/station?id={id}=tick
http://api.openweathermap.org/data/2.5/history/station?id={id}=hour
http://api.openweathermap.org/data/2.5/history/station?id={id}=day

STATION

http://api.openweathermap.org/data/2.5/station?id={id}
http://api.openweathermap.org/data/2.5/box/station?cluster={yes/no}={cnt}={bbox}
http://api.openweathermap.org/data/2.5/station/find?lat=55=37=30

{code}




  was:
Many others queries are supported by the weather Api.
We should update the component to support more options

{code}
WEATHER

Access current weather data for any location on Earth including over 200,000 
cities! Current weather is frequently updated based on global models and data 
from more than 40,000 weather stations. Data is available in JSON, XML, or HTML 
format.

api.openweathermap.org/data/2.5/weather?q={city name}
api.openweathermap.org/data/2.5/weather?q={city name},{country code}

api.openweathermap.org/data/2.5/weather?id=2172797

api.openweathermap.org/data/2.5/weather?lat={lat}={lon}

api.openweathermap.org/data/2.5/weather?zip={zip code},{country code}

api.openweathermap.org/data/2.5/box/city?bbox=12,32,15,37,10=yes

api.openweathermap.org/data/2.5/find?lat=55.5=37.5=10

api.openweathermap.org/data/2.5/group?id=524901,703448,2643743=metric

FORECAST - 5d

5 day forecast is available at any location or city. It includes weather data 
every 3 hours. Forecast is available in JSON, XML, or HTML format.

api.openweathermap.org/data/2.5/forecast?q={city name},{country code}
api.openweathermap.org/data/2.5/forecast?id={city ID}
api.openweathermap.org/data/2.5/forecast?lat={lat}={lon}

FORECAST - 16d

16 day forecasts is available at any location or city. Forecasts include daily 
weather and available in JSON, XML, or HTML format.

api.openweathermap.org/data/2.5/forecast/daily?q={city name},{country 
code}={cnt}
api.openweathermap.org/data/2.5/forecast/daily?id={city ID}={cnt}
api.openweathermap.org/data/2.5/forecast/daily?lat={lat}={lon}={cnt}

HISTORY

http://api.openweathermap.org/data/2.5/history/city?id={id}=hour={start}={end}
http://api.openweathermap.org/data/2.5/history/city?id={id}=hour={start}={cnt}

start start date (unix time, UTC time zone), e.g. start=1369728000
end end date (unix time, UTC time zone), e.g. end=1369789200
cnt amount of returned data (one per hour, can be used instead of 'end')


[jira] [Commented] (CAMEL-9272) openweathermap.org requires an APPID id since 09/10/2015

2015-10-29 Thread Charles Moulliard (JIRA)

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

Charles Moulliard commented on CAMEL-9272:
--

Can somebody backport the modification to 2.15.x & 2.16.x branches please ?

> openweathermap.org requires an APPID id since 09/10/2015
> 
>
> Key: CAMEL-9272
> URL: https://issues.apache.org/jira/browse/CAMEL-9272
> Project: Camel
>  Issue Type: Bug
>  Components: weather
>Reporter: Charles Moulliard
> Fix For: 2.16.1, 2.15.5, 2.17
>
>
> Code must be updated as openweathermap.org requires an APPID id since 
> 09/10/2015 & by consequence, the component can't be used anymore as we will 
> get a HTTP 401 error.
> {code}
> Caused by: org.apache.camel.TypeConversionException: Error during type 
> conversion from type: java.net.URL to the required type: java.lang.String 
> with value http://api.openweathermap.org/data/2.5/weather?q=Paris,France due 
> java.io.IOException: Server returned HTTP response code: 401 for URL: 
> http://api.openweathermap.org/data/2.5/weather?q=Paris,France
>   at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.createTypeConversionException(BaseTypeConverterRegistry.java:610)
>   at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:177)
>   at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:156)
>   at 
> org.apache.camel.component.weather.WeatherProducer.process(WeatherProducer.java:48)
> {code}



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


[jira] [Commented] (CAMEL-9259) enableTrace of the Main class doesn't work

2015-10-27 Thread Charles Moulliard (JIRA)

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

Charles Moulliard commented on CAMEL-9259:
--

Fix required. Add the trace option if the boolean is true when the postProcess 
method is called

{code}
protected void postProcessContext() throws Exception {
Map map = getCamelContextMap();
Set> entries = map.entrySet();
int size = entries.size();
for (Map.Entry entry : entries) {
String name = entry.getKey();
CamelContext camelContext = entry.getValue();
{code}

> enableTrace of the Main class doesn't work
> --
>
> Key: CAMEL-9259
> URL: https://issues.apache.org/jira/browse/CAMEL-9259
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core, el-core
>Affects Versions: 2.15.3
>Reporter: Charles Moulliard
>
> The enableTrace() method of the Camel Main class doesn't work.
> When we setup the code as such
> {code}
> public static void main(String... args) throws Exception {
> Main main = new Main();
> main.enableHangupSupport();
> main.addRouteBuilder(new MyRouteBuilder());
> main.enableTrace();
> main.run(args);
> {code}
> and launch the Main class, than the messages reported by the route in the log 
> are not traced at all.
> If we debug, we can see that there is not CamelContext object when this 
> method of the MainSupport class is called
> {code}
> public void enableTrace() {
> this.trace = true;
> for (CamelContext context : camelContexts) { // EMPTY
> context.setTracing(true);
> }
> }
> {code}
> The workaround is to enable the tracing within the route definition
> {code}
> public void configure() {
> getContext().setTracing(true);
> {code}



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


[jira] [Created] (CAMEL-9259) enableTrace of the Main class doesn't work

2015-10-27 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-9259:


 Summary: enableTrace of the Main class doesn't work
 Key: CAMEL-9259
 URL: https://issues.apache.org/jira/browse/CAMEL-9259
 Project: Camel
  Issue Type: Bug
  Components: el-core, camel-core
Affects Versions: 2.15.3
Reporter: Charles Moulliard


The enableTrace() method of the Camel Main class doesn't work.
When we setup the code as such

{code}
public static void main(String... args) throws Exception {
Main main = new Main();
main.enableHangupSupport();
main.addRouteBuilder(new MyRouteBuilder());
main.enableTrace();
main.run(args);
{code}

and launch the Main class, than the messages reported by the route in the log 
are not traced at all.

If we debug, we can see that there is not CamelContext object when this method 
of the MainSupport class is called

{code}
public void enableTrace() {
this.trace = true;
for (CamelContext context : camelContexts) { // EMPTY
context.setTracing(true);
}
}
{code}

The workaround is to enable the tracing within the route definition

{code}
public void configure() {

getContext().setTracing(true);
{code}



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


[jira] [Created] (CAMEL-9183) java.lang.IllegalArgumentException: Unsupported namespaces: [http://camel.apache.org/schema/blueprint]

2015-09-30 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-9183:


 Summary: java.lang.IllegalArgumentException: Unsupported 
namespaces: [http://camel.apache.org/schema/blueprint]
 Key: CAMEL-9183
 URL: https://issues.apache.org/jira/browse/CAMEL-9183
 Project: Camel
  Issue Type: Bug
  Components: examples
Affects Versions: 2.16.0
Reporter: Charles Moulliard


Version used of Blueprint Web : 1.0

I don't know if this example has ever work - 
https://github.com/apache/camel/blob/master/examples/camel-example-servlet-tomcat-blueprintweb/src/main/resources/META-INF/blueprint.xml
 but this is apparently not the longer case.

When we start mvn jetty:run within the project, we get this error

2015-09-30 10:37:29.054:WARN:/:Failed to startup blueprint container. 
java.lang.IllegalArgumentException: Unsupported namespaces: 
[http://camel.apache.org/schema/blueprint]
java.lang.IllegalArgumentException: Unsupported namespaces: 
[http://camel.apache.org/schema/blueprint]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.init(BlueprintContainerImpl.java:99)
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.(BlueprintContainerImpl.java:73)
at 
org.apache.aries.blueprint.web.BlueprintContextListener.contextInitialized(BlueprintContextListener.java:86)

Why, when the BlueprintContext is created, then it fails to load the camel 
namespace handler

We should upgrade to this version of Blueprint Web :

https://github.com/apache/aries/blob/trunk/blueprint/blueprint-web/src/main/java/org/apache/aries/blueprint/web/BlueprintContextListener.java#L55-L56

which allow to specify :

blueprintNamespaceHandlers OR META-INF/blueprint.handlers

and adapt the example to pass the blueprintNamespaceHandlers



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


[jira] [Commented] (CAMEL-9183) java.lang.IllegalArgumentException: Unsupported namespaces: [http://camel.apache.org/schema/blueprint]

2015-09-30 Thread Charles Moulliard (JIRA)

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

Charles Moulliard commented on CAMEL-9183:
--

If we upgrade to Aries Blueprint Web 1.1.1 and add also as reference blueprint 
parser 1.3.1, then we will have again the same error as this part of the code 
of Aries Blueprint Web is not able to find the @Namespaces annotation 

{code}
NamespaceHandler nsHandler = (NamespaceHandler)instance;
Namespaces namespaces = 
nsHandler.getClass().getAnnotation(Namespaces.class);
if (namespaces != null) { // WE WILL GET NULL HERE
for (String ns : namespaces.value()) {
nsSet.addNamespace(URI.create(ns), 
nsHandler.getSchemaLocation(ns), nsHandler);   
}
}
{code}

> java.lang.IllegalArgumentException: Unsupported namespaces: 
> [http://camel.apache.org/schema/blueprint]
> --
>
> Key: CAMEL-9183
> URL: https://issues.apache.org/jira/browse/CAMEL-9183
> Project: Camel
>  Issue Type: Bug
>  Components: examples
>Affects Versions: 2.16.0
>Reporter: Charles Moulliard
>
> Version used of Blueprint Web : 1.0
> I don't know if this example has ever work - 
> https://github.com/apache/camel/blob/master/examples/camel-example-servlet-tomcat-blueprintweb/src/main/resources/META-INF/blueprint.xml
>  but this is apparently not the longer case.
> When we start mvn jetty:run within the project, we get this error
> 2015-09-30 10:37:29.054:WARN:/:Failed to startup blueprint container. 
> java.lang.IllegalArgumentException: Unsupported namespaces: 
> [http://camel.apache.org/schema/blueprint]
> java.lang.IllegalArgumentException: Unsupported namespaces: 
> [http://camel.apache.org/schema/blueprint]
>   at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.init(BlueprintContainerImpl.java:99)
>   at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.(BlueprintContainerImpl.java:73)
>   at 
> org.apache.aries.blueprint.web.BlueprintContextListener.contextInitialized(BlueprintContextListener.java:86)
> Why, when the BlueprintContext is created, then it fails to load the camel 
> namespace handler
> We should upgrade to this version of Blueprint Web :
> https://github.com/apache/aries/blob/trunk/blueprint/blueprint-web/src/main/java/org/apache/aries/blueprint/web/BlueprintContextListener.java#L55-L56
> which allow to specify :
> blueprintNamespaceHandlers OR META-INF/blueprint.handlers
> and adapt the example to pass the blueprintNamespaceHandlers



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


[jira] [Assigned] (CAMEL-9129) Create OptionsVerbDefinition - REST

2015-09-13 Thread Charles Moulliard (JIRA)

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

Charles Moulliard reassigned CAMEL-9129:


Assignee: Charles Moulliard

> Create OptionsVerbDefinition - REST
> ---
>
> Key: CAMEL-9129
> URL: https://issues.apache.org/jira/browse/CAMEL-9129
> Project: Camel
>  Issue Type: New Feature
>Reporter: Charles Moulliard
>Assignee: Charles Moulliard
>
> Some API like Swagger sends HTTP OPTIONS method request 
> (http://restcookbook.com/HTTP%20Methods/options/) to get, when CORS is 
> enable, the CORS HTTP Headers (Access-Control-Allow-*) prior to run a 
> POST/PUT or DELETE operation
> A workaround has been proposed to pass using the verb("") method the 
> ("OPTIONS") (see camel-8373) - but it should be better that we propose also a 
> OptionsVerbDefinition.



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


[jira] [Resolved] (CAMEL-9129) Create OptionsVerbDefinition - REST

2015-09-13 Thread Charles Moulliard (JIRA)

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

Charles Moulliard resolved CAMEL-9129.
--
Resolution: Fixed

> Create OptionsVerbDefinition - REST
> ---
>
> Key: CAMEL-9129
> URL: https://issues.apache.org/jira/browse/CAMEL-9129
> Project: Camel
>  Issue Type: New Feature
>  Components: rest
>Affects Versions: 2.16.0
>Reporter: Charles Moulliard
>Assignee: Charles Moulliard
>
> Some API like Swagger sends HTTP OPTIONS method request 
> (http://restcookbook.com/HTTP%20Methods/options/) to get, when CORS is 
> enable, the CORS HTTP Headers (Access-Control-Allow-*) prior to run a 
> POST/PUT or DELETE operation
> A workaround has been proposed to pass using the verb("") method the 
> ("OPTIONS") (see camel-8373) - but it should be better that we propose also a 
> OptionsVerbDefinition.



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


[jira] [Created] (CAMEL-9129) Create OptionsVerbDefinition - REST

2015-09-13 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-9129:


 Summary: Create OptionsVerbDefinition - REST
 Key: CAMEL-9129
 URL: https://issues.apache.org/jira/browse/CAMEL-9129
 Project: Camel
  Issue Type: New Feature
Reporter: Charles Moulliard


Some API like Swagger sends HTTP OPTIONS method request 
(http://restcookbook.com/HTTP%20Methods/options/) to get, when CORS is enable, 
the CORS HTTP Headers (Access-Control-Allow-*) prior to run a POST/PUT or 
DELETE operation

A workaround has been proposed to pass using the verb("") method the 
("OPTIONS") (see camel-8373) - but it should be better that we propose also a 
OptionsVerbDefinition.



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


[jira] [Updated] (CAMEL-9129) Create OptionsVerbDefinition - REST

2015-09-13 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-9129:
-
Component/s: rest

> Create OptionsVerbDefinition - REST
> ---
>
> Key: CAMEL-9129
> URL: https://issues.apache.org/jira/browse/CAMEL-9129
> Project: Camel
>  Issue Type: New Feature
>  Components: rest
>Affects Versions: 2.16.0
>Reporter: Charles Moulliard
>Assignee: Charles Moulliard
>
> Some API like Swagger sends HTTP OPTIONS method request 
> (http://restcookbook.com/HTTP%20Methods/options/) to get, when CORS is 
> enable, the CORS HTTP Headers (Access-Control-Allow-*) prior to run a 
> POST/PUT or DELETE operation
> A workaround has been proposed to pass using the verb("") method the 
> ("OPTIONS") (see camel-8373) - but it should be better that we propose also a 
> OptionsVerbDefinition.



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


[jira] [Updated] (CAMEL-9129) Create OptionsVerbDefinition - REST

2015-09-13 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-9129:
-
Affects Version/s: 2.16.0

> Create OptionsVerbDefinition - REST
> ---
>
> Key: CAMEL-9129
> URL: https://issues.apache.org/jira/browse/CAMEL-9129
> Project: Camel
>  Issue Type: New Feature
>  Components: rest
>Affects Versions: 2.16.0
>Reporter: Charles Moulliard
>Assignee: Charles Moulliard
>
> Some API like Swagger sends HTTP OPTIONS method request 
> (http://restcookbook.com/HTTP%20Methods/options/) to get, when CORS is 
> enable, the CORS HTTP Headers (Access-Control-Allow-*) prior to run a 
> POST/PUT or DELETE operation
> A workaround has been proposed to pass using the verb("") method the 
> ("OPTIONS") (see camel-8373) - but it should be better that we propose also a 
> OptionsVerbDefinition.



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


[jira] [Commented] (CAMEL-8373) rest-dsl - CORS may have issue with non simple requests

2015-09-11 Thread Charles Moulliard (JIRA)

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

Charles Moulliard commented on CAMEL-8373:
--

Such option should be added for REST DSL. Otherwise we can't answer to CORS 
preflight requests of Swagger where OPTIONS requests are send

> rest-dsl - CORS may have issue with non simple requests
> ---
>
> Key: CAMEL-8373
> URL: https://issues.apache.org/jira/browse/CAMEL-8373
> Project: Camel
>  Issue Type: Task
>  Components: camel-core
>Affects Versions: 2.14.1
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>
> Look into reported on SO
> http://stackoverflow.com/questions/28562817/camel-rest-dsl-enablecors-only-working-for-get
> For non simple requests, such as PUT see
> http://www.w3.org/TR/cors/



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


[jira] [Created] (CAMEL-9057) Camel Example Servlet REST generates java.lang.NoClassDefFoundError: scala/xml/PrettyPrinter

2015-08-05 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-9057:


 Summary: Camel Example Servlet REST generates 
java.lang.NoClassDefFoundError: scala/xml/PrettyPrinter
 Key: CAMEL-9057
 URL: https://issues.apache.org/jira/browse/CAMEL-9057
 Project: Camel
  Issue Type: Bug
  Components: examples
Affects Versions: 2.16.0
Reporter: Charles Moulliard


After starting jetty:run maven goal and accessing the apiDoc of Swagger 
(http://localhost:8080/camel-example-servlet-rest-tomcat/api-docs/myCamel), the 
following error is reported

{code}
2015-08-05 17:42:18.053:INFO:oejs.Server:main: Started @18962ms
[INFO] Started Jetty Server
2015-08-05 17:42:26.619:WARN:oejs.ServletHandler:qtp1891031939-25: Error for 
/camel-example-servlet-rest-tomcat/api-docs/myCamel
java.lang.NoClassDefFoundError: scala/xml/PrettyPrinter
at 
com.wordnik.swagger.core.util.JsonSerializer$.init(JsonSerializer.scala:31)
at 
com.wordnik.swagger.core.util.JsonSerializer$.clinit(JsonSerializer.scala)
at 
org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.renderResourceListing(RestSwaggerApiDeclarationServlet.scala:225)
at 
org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.doGet(RestSwaggerApiDeclarationServlet.scala:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
at 
org.apache.camel.component.swagger.RestSwaggerCorsFilter.doFilter(RestSwaggerCorsFilter.scala:44)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
at 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:497)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
at 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
at 
org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:745)
Caused by: 
java.lang.ClassNotFoundException: scala.xml.PrettyPrinter
at 
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
at 
org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:450)
at 
org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:403)
at 
com.wordnik.swagger.core.util.JsonSerializer$.init(JsonSerializer.scala:31)
at 
com.wordnik.swagger.core.util.JsonSerializer$.clinit(JsonSerializer.scala)
at 
org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.renderResourceListing(RestSwaggerApiDeclarationServlet.scala:225)
at 
org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.doGet(RestSwaggerApiDeclarationServlet.scala:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
{code}



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


[jira] [Updated] (CAMEL-9057) Camel Example Servlet REST generates java.lang.NoClassDefFoundError: scala/xml/PrettyPrinter

2015-08-05 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-9057:
-
Description: 
After starting jetty:run maven goal and accessing the apiDoc of Swagger 
(http://localhost:8080/camel-example-servlet-rest-tomcat/api-docs/myCamel), the 
following error is reported

{code}
2015-08-05 17:42:18.053:INFO:oejs.Server:main: Started @18962ms
[INFO] Started Jetty Server
2015-08-05 17:42:26.619:WARN:oejs.ServletHandler:qtp1891031939-25: Error for 
/camel-example-servlet-rest-tomcat/api-docs/myCamel
java.lang.NoClassDefFoundError: scala/xml/PrettyPrinter
at 
com.wordnik.swagger.core.util.JsonSerializer$.init(JsonSerializer.scala:31)
at 
com.wordnik.swagger.core.util.JsonSerializer$.clinit(JsonSerializer.scala)
at 
org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.renderResourceListing(RestSwaggerApiDeclarationServlet.scala:225)
at 
org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.doGet(RestSwaggerApiDeclarationServlet.scala:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
at 
org.apache.camel.component.swagger.RestSwaggerCorsFilter.doFilter(RestSwaggerCorsFilter.scala:44)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
at 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:497)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
at 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
at 
org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:745)
Caused by: 
java.lang.ClassNotFoundException: scala.xml.PrettyPrinter
at 
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
at 
org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:450)
at 
org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:403)
at 
com.wordnik.swagger.core.util.JsonSerializer$.init(JsonSerializer.scala:31)
at 
com.wordnik.swagger.core.util.JsonSerializer$.clinit(JsonSerializer.scala)
at 
org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.renderResourceListing(RestSwaggerApiDeclarationServlet.scala:225)
at 
org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.doGet(RestSwaggerApiDeclarationServlet.scala:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
{code}

when the same url is called a second time, then we get another class not found 
error 

{code}
2015-08-05 17:47:33.803:WARN:oejs.ServletHandler:qtp1891031939-33: Error for 
/camel-example-servlet-rest-tomcat/api-docs/myCamel
java.lang.NoClassDefFoundError: Could not initialize class 
com.wordnik.swagger.core.util.JsonSerializer$
at 

[jira] [Commented] (CAMEL-9057) Camel Example Servlet REST generates java.lang.NoClassDefFoundError: scala/xml/PrettyPrinter

2015-08-05 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-9057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14658423#comment-14658423
 ] 

Charles Moulliard commented on CAMEL-9057:
--

This error also occurs when the war is deployed on Tomcat

 Camel Example Servlet REST generates java.lang.NoClassDefFoundError: 
 scala/xml/PrettyPrinter
 

 Key: CAMEL-9057
 URL: https://issues.apache.org/jira/browse/CAMEL-9057
 Project: Camel
  Issue Type: Bug
  Components: examples
Affects Versions: 2.16.0
Reporter: Charles Moulliard

 After starting jetty:run maven goal and accessing the apiDoc of Swagger 
 (http://localhost:8080/camel-example-servlet-rest-tomcat/api-docs/myCamel), 
 the following error is reported
 {code}
 2015-08-05 17:42:18.053:INFO:oejs.Server:main: Started @18962ms
 [INFO] Started Jetty Server
 2015-08-05 17:42:26.619:WARN:oejs.ServletHandler:qtp1891031939-25: Error for 
 /camel-example-servlet-rest-tomcat/api-docs/myCamel
 java.lang.NoClassDefFoundError: scala/xml/PrettyPrinter
 at 
 com.wordnik.swagger.core.util.JsonSerializer$.init(JsonSerializer.scala:31)
 at 
 com.wordnik.swagger.core.util.JsonSerializer$.clinit(JsonSerializer.scala)
 at 
 org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.renderResourceListing(RestSwaggerApiDeclarationServlet.scala:225)
 at 
 org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.doGet(RestSwaggerApiDeclarationServlet.scala:111)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
 at 
 org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808)
 at 
 org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
 at 
 org.apache.camel.component.swagger.RestSwaggerCorsFilter.doFilter(RestSwaggerCorsFilter.scala:44)
 at 
 org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
 at 
 org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
 at 
 org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
 at 
 org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
 at 
 org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
 at 
 org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
 at 
 org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
 at 
 org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
 at 
 org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
 at 
 org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
 at 
 org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
 at 
 org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)
 at 
 org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
 at org.eclipse.jetty.server.Server.handle(Server.java:497)
 at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
 at 
 org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
 at 
 org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
 at 
 org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
 at 
 org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
 at java.lang.Thread.run(Thread.java:745)
 Caused by: 
 java.lang.ClassNotFoundException: scala.xml.PrettyPrinter
 at 
 org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
 at 
 org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
 at 
 org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
 at 
 org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
 at 
 org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:450)
 at 
 org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:403)
 at 
 com.wordnik.swagger.core.util.JsonSerializer$.init(JsonSerializer.scala:31)
 at 
 com.wordnik.swagger.core.util.JsonSerializer$.clinit(JsonSerializer.scala)
 at 
 org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.renderResourceListing(RestSwaggerApiDeclarationServlet.scala:225)
 at 
 

[jira] [Resolved] (CAMEL-9057) Camel Example Servlet REST generates java.lang.NoClassDefFoundError: scala/xml/PrettyPrinter

2015-08-05 Thread Charles Moulliard (JIRA)

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

Charles Moulliard resolved CAMEL-9057.
--
Resolution: Fixed

Add missing scala deps

 Camel Example Servlet REST generates java.lang.NoClassDefFoundError: 
 scala/xml/PrettyPrinter
 

 Key: CAMEL-9057
 URL: https://issues.apache.org/jira/browse/CAMEL-9057
 Project: Camel
  Issue Type: Bug
  Components: examples
Affects Versions: 2.16.0
Reporter: Charles Moulliard
Assignee: Charles Moulliard

 After starting jetty:run maven goal and accessing the apiDoc of Swagger 
 (http://localhost:8080/camel-example-servlet-rest-tomcat/api-docs/myCamel), 
 the following error is reported
 {code}
 2015-08-05 17:42:18.053:INFO:oejs.Server:main: Started @18962ms
 [INFO] Started Jetty Server
 2015-08-05 17:42:26.619:WARN:oejs.ServletHandler:qtp1891031939-25: Error for 
 /camel-example-servlet-rest-tomcat/api-docs/myCamel
 java.lang.NoClassDefFoundError: scala/xml/PrettyPrinter
 at 
 com.wordnik.swagger.core.util.JsonSerializer$.init(JsonSerializer.scala:31)
 at 
 com.wordnik.swagger.core.util.JsonSerializer$.clinit(JsonSerializer.scala)
 at 
 org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.renderResourceListing(RestSwaggerApiDeclarationServlet.scala:225)
 at 
 org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.doGet(RestSwaggerApiDeclarationServlet.scala:111)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
 at 
 org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808)
 at 
 org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
 at 
 org.apache.camel.component.swagger.RestSwaggerCorsFilter.doFilter(RestSwaggerCorsFilter.scala:44)
 at 
 org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
 at 
 org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
 at 
 org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
 at 
 org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
 at 
 org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
 at 
 org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
 at 
 org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
 at 
 org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
 at 
 org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
 at 
 org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
 at 
 org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
 at 
 org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)
 at 
 org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
 at org.eclipse.jetty.server.Server.handle(Server.java:497)
 at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
 at 
 org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
 at 
 org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
 at 
 org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
 at 
 org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
 at java.lang.Thread.run(Thread.java:745)
 Caused by: 
 java.lang.ClassNotFoundException: scala.xml.PrettyPrinter
 at 
 org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
 at 
 org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
 at 
 org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
 at 
 org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
 at 
 org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:450)
 at 
 org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:403)
 at 
 com.wordnik.swagger.core.util.JsonSerializer$.init(JsonSerializer.scala:31)
 at 
 com.wordnik.swagger.core.util.JsonSerializer$.clinit(JsonSerializer.scala)
 at 
 org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.renderResourceListing(RestSwaggerApiDeclarationServlet.scala:225)
 at 
 

[jira] [Work started] (CAMEL-9057) Camel Example Servlet REST generates java.lang.NoClassDefFoundError: scala/xml/PrettyPrinter

2015-08-05 Thread Charles Moulliard (JIRA)

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

Work on CAMEL-9057 started by Charles Moulliard.

 Camel Example Servlet REST generates java.lang.NoClassDefFoundError: 
 scala/xml/PrettyPrinter
 

 Key: CAMEL-9057
 URL: https://issues.apache.org/jira/browse/CAMEL-9057
 Project: Camel
  Issue Type: Bug
  Components: examples
Affects Versions: 2.16.0
Reporter: Charles Moulliard
Assignee: Charles Moulliard

 After starting jetty:run maven goal and accessing the apiDoc of Swagger 
 (http://localhost:8080/camel-example-servlet-rest-tomcat/api-docs/myCamel), 
 the following error is reported
 {code}
 2015-08-05 17:42:18.053:INFO:oejs.Server:main: Started @18962ms
 [INFO] Started Jetty Server
 2015-08-05 17:42:26.619:WARN:oejs.ServletHandler:qtp1891031939-25: Error for 
 /camel-example-servlet-rest-tomcat/api-docs/myCamel
 java.lang.NoClassDefFoundError: scala/xml/PrettyPrinter
 at 
 com.wordnik.swagger.core.util.JsonSerializer$.init(JsonSerializer.scala:31)
 at 
 com.wordnik.swagger.core.util.JsonSerializer$.clinit(JsonSerializer.scala)
 at 
 org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.renderResourceListing(RestSwaggerApiDeclarationServlet.scala:225)
 at 
 org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.doGet(RestSwaggerApiDeclarationServlet.scala:111)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
 at 
 org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808)
 at 
 org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
 at 
 org.apache.camel.component.swagger.RestSwaggerCorsFilter.doFilter(RestSwaggerCorsFilter.scala:44)
 at 
 org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
 at 
 org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
 at 
 org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
 at 
 org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
 at 
 org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
 at 
 org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
 at 
 org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
 at 
 org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
 at 
 org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
 at 
 org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
 at 
 org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
 at 
 org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)
 at 
 org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
 at org.eclipse.jetty.server.Server.handle(Server.java:497)
 at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
 at 
 org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
 at 
 org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
 at 
 org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
 at 
 org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
 at java.lang.Thread.run(Thread.java:745)
 Caused by: 
 java.lang.ClassNotFoundException: scala.xml.PrettyPrinter
 at 
 org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
 at 
 org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
 at 
 org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
 at 
 org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
 at 
 org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:450)
 at 
 org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:403)
 at 
 com.wordnik.swagger.core.util.JsonSerializer$.init(JsonSerializer.scala:31)
 at 
 com.wordnik.swagger.core.util.JsonSerializer$.clinit(JsonSerializer.scala)
 at 
 org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.renderResourceListing(RestSwaggerApiDeclarationServlet.scala:225)
 at 
 

[jira] [Updated] (CAMEL-8917) camel-cxfrs doesn't use the resource classes handle the invocation directly

2015-06-29 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-8917:
-
Component/s: (was: el-cxfrs)
 camel-cxfrs

 camel-cxfrs doesn't use the resource classes handle the invocation directly
 ---

 Key: CAMEL-8917
 URL: https://issues.apache.org/jira/browse/CAMEL-8917
 Project: Camel
  Issue Type: Improvement
  Components: camel-cxfrs
Reporter: Charles Moulliard
  Labels: camel-cxfrs

 Here is the content of our discussion 
 As the camel-swagger get the ServiceModule from the Route definition which is 
 dumped to XML, it is quit different from the CXF-swagger who builds the 
 ServiceModule from the Resource Class.
 As camel-cxfrs doesn't use the resource classes handle the invocation 
 directly (it just delegates the request to the camel route), so it causes 
 some trouble if the CXF-swagger try to load the resource classes. To fix it, 
 we may need to find a way to generate the ServiceModule rightly.
 Issue : 
 {code}
 I try now to use Swagger as described here :
 https://github.com/swagger-api/swagger-core/wiki/Java-CXF-Quickstart and
 implemented as such :
 https://github.com/cmoulliard/use-cases/blob/master/fabric-camel-rest/src/main/resources/OSGI-INF/blueprint/camel.xml#L11-L40
 When we launch locally mvn camel:run but I get --
 No message body writer has been found for class
 org.apache.cxf.message.MessageContentsList, ContentType:
 application/json;charset=utf-8 at this address
 http://localhost:8080/cxf/rest/api-docs
 {code}



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


[jira] [Updated] (CAMEL-8917) camel-cxfrs doesn't use the resource classes handle the invocation directly

2015-06-29 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-8917:
-
Description: 
Here is the content of our discussion 
As the camel-swagger get the ServiceModule from the Route definition which is 
dumped to XML, it is quit different from the CXF-swagger who builds the 
ServiceModule from the Resource Class.

As camel-cxfrs doesn't use the resource classes handle the invocation directly 
(it just delegates the request to the camel route), so it causes some trouble 
if the CXF-swagger try to load the resource classes. To fix it, we may need to 
find a way to generate the ServiceModule rightly.

Issue : 
{code}
I try now to use Swagger as described here :
https://github.com/swagger-api/swagger-core/wiki/Java-CXF-Quickstart and
implemented as such :
https://github.com/cmoulliard/use-cases/blob/master/fabric-camel-rest/src/main/resources/OSGI-INF/blueprint/camel.xml#L11-L40

When we launch locally mvn camel:run but I get --

No message body writer has been found for class
org.apache.cxf.message.MessageContentsList, ContentType:
application/json;charset=utf-8 at this address
http://localhost:8080/cxf/rest/api-docs
{code}

  was:
Here is the content of our discussion 
As the camel-swagger get the ServiceModule from the Route definition which is 
dumped to XML, it is quit different from the CXF-swagger who builds the 
ServiceModule from the Resource Class.

As camel-cxfrs doesn't use the resource classes handle the invocation directly 
(it just delegates the request to the camel route), so it causes some trouble 
if the CXF-swagger try to load the resource classes. To fix it, we may need to 
find a way to generate the ServiceModule rightly.
- Original Message -
From: Charles Moulliard cmoulli...@redhat.com
Cc: Yue Fang yf...@redhat.com
Sent: Thursday, June 11, 2015 5:39:52 PM
Subject: Camel + CXF  Swagger

Issue -- 
{code}
I try now to use Swagger as described here :
https://github.com/swagger-api/swagger-core/wiki/Java-CXF-Quickstart and
implemented as such :
https://github.com/cmoulliard/use-cases/blob/master/fabric-camel-rest/src/main/resources/OSGI-INF/blueprint/camel.xml#L11-L40

When we launch locally mvn camel:run but I get --

No message body writer has been found for class
org.apache.cxf.message.MessageContentsList, ContentType:
application/json;charset=utf-8 at this address
http://localhost:8080/cxf/rest/api-docs
{code}


 camel-cxfrs doesn't use the resource classes handle the invocation directly
 ---

 Key: CAMEL-8917
 URL: https://issues.apache.org/jira/browse/CAMEL-8917
 Project: Camel
  Issue Type: Improvement
  Components: el-cxfrs
Reporter: Charles Moulliard

 Here is the content of our discussion 
 As the camel-swagger get the ServiceModule from the Route definition which is 
 dumped to XML, it is quit different from the CXF-swagger who builds the 
 ServiceModule from the Resource Class.
 As camel-cxfrs doesn't use the resource classes handle the invocation 
 directly (it just delegates the request to the camel route), so it causes 
 some trouble if the CXF-swagger try to load the resource classes. To fix it, 
 we may need to find a way to generate the ServiceModule rightly.
 Issue : 
 {code}
 I try now to use Swagger as described here :
 https://github.com/swagger-api/swagger-core/wiki/Java-CXF-Quickstart and
 implemented as such :
 https://github.com/cmoulliard/use-cases/blob/master/fabric-camel-rest/src/main/resources/OSGI-INF/blueprint/camel.xml#L11-L40
 When we launch locally mvn camel:run but I get --
 No message body writer has been found for class
 org.apache.cxf.message.MessageContentsList, ContentType:
 application/json;charset=utf-8 at this address
 http://localhost:8080/cxf/rest/api-docs
 {code}



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


[jira] [Created] (CAMEL-8917) camel-cxfrs doesn't use the resource classes handle the invocation directly

2015-06-29 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-8917:


 Summary: camel-cxfrs doesn't use the resource classes handle the 
invocation directly
 Key: CAMEL-8917
 URL: https://issues.apache.org/jira/browse/CAMEL-8917
 Project: Camel
  Issue Type: Improvement
  Components: el-cxfrs
Reporter: Charles Moulliard


Here is the content of our discussion 
As the camel-swagger get the ServiceModule from the Route definition which is 
dumped to XML, it is quit different from the CXF-swagger who builds the 
ServiceModule from the Resource Class.

As camel-cxfrs doesn't use the resource classes handle the invocation directly 
(it just delegates the request to the camel route), so it causes some trouble 
if the CXF-swagger try to load the resource classes. To fix it, we may need to 
find a way to generate the ServiceModule rightly.
- Original Message -
From: Charles Moulliard cmoulli...@redhat.com
Cc: Yue Fang yf...@redhat.com
Sent: Thursday, June 11, 2015 5:39:52 PM
Subject: Camel + CXF  Swagger

Issue -- 
{code}
I try now to use Swagger as described here :
https://github.com/swagger-api/swagger-core/wiki/Java-CXF-Quickstart and
implemented as such :
https://github.com/cmoulliard/use-cases/blob/master/fabric-camel-rest/src/main/resources/OSGI-INF/blueprint/camel.xml#L11-L40

When we launch locally mvn camel:run but I get --

No message body writer has been found for class
org.apache.cxf.message.MessageContentsList, ContentType:
application/json;charset=utf-8 at this address
http://localhost:8080/cxf/rest/api-docs
{code}



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


[jira] [Commented] (CAMEL-7942) Support Oauth, Ouath2 OpenID client to request token

2015-04-20 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14502403#comment-14502403
 ] 

Charles Moulliard commented on CAMEL-7942:
--

If you ned help to create the component, unit tests, ... please contact me 
Duncan

 Support Oauth, Ouath2  OpenID client to request token
 --

 Key: CAMEL-7942
 URL: https://issues.apache.org/jira/browse/CAMEL-7942
 Project: Camel
  Issue Type: New Feature
Reporter: Charles Moulliard

 Apache Camel does not provide any security layer to support OAuth, OAuth2 or 
 OpenID specifications to obtain a token, refresh it and maintain the existing 
 tokens in a cache. 
 Such a security layer should be interesting for the camel-cxf, camel-jetty, 
 camel-http, REST DSL components ... 
 The Apache OLTU project (https://oltu.apache.org/) could be used to support 
 OAuth, OAuth2 and OpenID4java (https://code.google.com/p/openid4java/) for 
 OpenID



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


[jira] [Updated] (CAMEL-8326) Project created from camel-blueprint-archetype does not work

2015-02-10 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-8326:
-
Attachment: test.zip

Project tested

 Project created from camel-blueprint-archetype does not work
 

 Key: CAMEL-8326
 URL: https://issues.apache.org/jira/browse/CAMEL-8326
 Project: Camel
  Issue Type: Bug
  Components: osgi, tooling
Affects Versions: 2.13.3, 2.14.1
Reporter: Charles Moulliard
 Attachments: test.zip


 When we launch the camel:run maven goal created from a project created using 
 the archetype :
 org.apache.camel.archetypes:camel-archetype-blueprint (Creates a new Camel 
 project with OSGi blueprint support. Ready to be deployed in OSGi.)
 then it fails
 {code}
 [mel.test.blueprint.Main.main()] MainSupportINFO  Apache 
 Camel 2.14.1 starting
 [mel.test.blueprint.Main.main()] Activator  INFO  Camel 
 activator starting
 [mel.test.blueprint.Main.main()] Activator  INFO  Camel 
 activator started
 [mel.test.blueprint.Main.main()] BlueprintExtender  INFO  No 
 quiesce support is available, so blueprint components will not participate in 
 quiesce operations
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  Test 
 bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle, 
 Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec, 
 Bundle-Version=0.2.1
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.packageadmin.PackageAdmin], bundle: 
 de.kalpatec.pojosr.framework [0], symbolicName: de.kalpatec.pojosr.framework
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.LanguageResolver], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer], 
 bundle: org.apache.camel.camel-blueprint [4], symbolicName: 
 org.apache.camel.camel-blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle: 
 org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle: 
 org.apache.felix.configadmin [25], symbolicName: org.apache.felix.configadmin
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.DataFormatResolver], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer], 
 bundle: org.apache.aries.blueprint [13], symbolicName: 
 org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.camel.camel-blueprint [4], symbolicName: 
 org.apache.camel.camel-blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.url.URLStreamHandlerService], bundle: 
 org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.cm.ConfigurationAdmin], bundle: 
 org.apache.felix.configadmin [25], 

[jira] [Commented] (CAMEL-8326) Project created from camel-blueprint-archetype does not work

2015-02-10 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14313880#comment-14313880
 ] 

Charles Moulliard commented on CAMEL-8326:
--

Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 
2014-08-11T22:58:10+02:00)
Java version: 1.7.0_51, vendor: Oracle Corporation

 Project created from camel-blueprint-archetype does not work
 

 Key: CAMEL-8326
 URL: https://issues.apache.org/jira/browse/CAMEL-8326
 Project: Camel
  Issue Type: Bug
  Components: osgi, tooling
Affects Versions: 2.13.3, 2.14.1
Reporter: Charles Moulliard
 Attachments: test.zip


 When we launch the camel:run maven goal created from a project created using 
 the archetype :
 org.apache.camel.archetypes:camel-archetype-blueprint (Creates a new Camel 
 project with OSGi blueprint support. Ready to be deployed in OSGi.)
 then it fails
 {code}
 [mel.test.blueprint.Main.main()] MainSupportINFO  Apache 
 Camel 2.14.1 starting
 [mel.test.blueprint.Main.main()] Activator  INFO  Camel 
 activator starting
 [mel.test.blueprint.Main.main()] Activator  INFO  Camel 
 activator started
 [mel.test.blueprint.Main.main()] BlueprintExtender  INFO  No 
 quiesce support is available, so blueprint components will not participate in 
 quiesce operations
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  Test 
 bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle, 
 Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec, 
 Bundle-Version=0.2.1
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.packageadmin.PackageAdmin], bundle: 
 de.kalpatec.pojosr.framework [0], symbolicName: de.kalpatec.pojosr.framework
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.LanguageResolver], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer], 
 bundle: org.apache.camel.camel-blueprint [4], symbolicName: 
 org.apache.camel.camel-blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle: 
 org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle: 
 org.apache.felix.configadmin [25], symbolicName: org.apache.felix.configadmin
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.DataFormatResolver], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer], 
 bundle: org.apache.aries.blueprint [13], symbolicName: 
 org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.camel.camel-blueprint [4], symbolicName: 
 org.apache.camel.camel-blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.url.URLStreamHandlerService], bundle: 
 org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
 

[jira] [Commented] (CAMEL-8326) Project created from camel-blueprint-archetype does not work

2015-02-10 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14314184#comment-14314184
 ] 

Charles Moulliard commented on CAMEL-8326:
--

I can't yet explain what is the issue but if we first, install the project 
before to launch camel:run, then it will work

1) Does not work
mvn clean compile camel:run

2) Work
mvn clean package camel:run

I suspect that the reason is that the MANIFEST.MF created by the felix maven 
bundle was not generated during compile phase !

{code}
dabouhost:~/Temp/test$ mvn install
[INFO] Scanning for projects...
[INFO]
[INFO] 
[INFO] Building A Camel Blueprint Route 1.0-SNAPSHOT
[INFO] 
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ test ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ test ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
test ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ test 
---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:2.13-SONATYPE:test (default-test) @ test ---
[INFO] Surefire report directory: 
/Users/chmoulli/Temp/test/target/surefire-reports

---
 T E S T S
---
Running org.apache.camel.RouteTest
[  main] CamelBlueprintHelper   INFO  Using 
Blueprint XML file: 
/Users/chmoulli/Temp/test/target/classes/OSGI-INF/blueprint/blueprint.xml
[  Thread-0] RawBuilder INFO  Copy 
thread finished.
[  main] Activator  INFO  Camel 
activator starting
[  main] Activator  INFO  Camel 
activator started
[  main] BlueprintExtender  INFO  No 
quiesce support is available, so blueprint components will not participate in 
quiesce operations
[  main] RouteTest  INFO  

[  main] RouteTest  INFO  Testing: 
testRoute(org.apache.camel.RouteTest)
[  main] RouteTest  INFO  

[ Blueprint Extender: 3] BlueprintContainerImpl INFO  Bundle 
RouteTest is waiting for namespace handlers 
[http://camel.apache.org/schema/blueprint]
[  main] RouteTest  INFO  Skipping 
starting CamelContext as system property skipStartingCamelContext is set to be 
true.
[  main] BlueprintCamelContext  INFO  Apache 
Camel 2.14.1 (CamelContext: blueprintContext) is starting
[  main] DefaultManagementStrategy  INFO  JMX is 
disabled
[  main] BlueprintCamelContext  INFO  
AllowUseOriginalMessage is enabled. If access to the original message is not 
needed, then its recommended to turn this option off as it may improve 
performance.
[  main] BlueprintCamelContext  INFO  
StreamCaching is not in use. If using streams then its recommended to enable 
stream caching. See more details at http://camel.apache.org/stream-caching.html
[  main] BlueprintCamelContext  INFO  Route: 
timerToLog started and consuming from: Endpoint[timer://foo?period=5000]
[  main] BlueprintCamelContext  INFO  Total 1 
routes, of which 1 is started.
[  main] BlueprintCamelContext  INFO  Apache 
Camel 2.14.1 (CamelContext: blueprintContext) started in 0.075 seconds
[  main] MockEndpoint   INFO  
Asserting: Endpoint[mock://result] is satisfied
[ntext) thread #0 - timer://foo] timerToLog INFO  The 
message contains Hi from Camel at 2015-02-10 14:37:32
[  main] RouteTest  INFO  

[  main] RouteTest  INFO  Testing 
done: testRoute(org.apache.camel.RouteTest)
[  main] RouteTest  INFO  Took: 
1.090 seconds (1090 millis)
[  main] 

[jira] [Commented] (CAMEL-8326) Project created from camel-blueprint-archetype does not work

2015-02-10 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14314191#comment-14314191
 ] 

Charles Moulliard commented on CAMEL-8326:
--

That works without issue if add an execution tag to the 
maven-bundle-plugin. I will update the archetype into the project to avoid 
such stupid behavior and problem.

{code}
executions
execution
  idbundle-manifest/id
  phaseprocess-classes/phase
  goals
goalmanifest/goal
  /goals
/execution
  /executions
{code}

 Project created from camel-blueprint-archetype does not work
 

 Key: CAMEL-8326
 URL: https://issues.apache.org/jira/browse/CAMEL-8326
 Project: Camel
  Issue Type: Bug
  Components: osgi, tooling
Affects Versions: 2.13.3, 2.14.1
Reporter: Charles Moulliard
 Attachments: test.zip


 When we launch the camel:run maven goal created from a project created using 
 the archetype :
 org.apache.camel.archetypes:camel-archetype-blueprint (Creates a new Camel 
 project with OSGi blueprint support. Ready to be deployed in OSGi.)
 then it fails
 {code}
 [mel.test.blueprint.Main.main()] MainSupportINFO  Apache 
 Camel 2.14.1 starting
 [mel.test.blueprint.Main.main()] Activator  INFO  Camel 
 activator starting
 [mel.test.blueprint.Main.main()] Activator  INFO  Camel 
 activator started
 [mel.test.blueprint.Main.main()] BlueprintExtender  INFO  No 
 quiesce support is available, so blueprint components will not participate in 
 quiesce operations
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  Test 
 bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle, 
 Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec, 
 Bundle-Version=0.2.1
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.packageadmin.PackageAdmin], bundle: 
 de.kalpatec.pojosr.framework [0], symbolicName: de.kalpatec.pojosr.framework
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.LanguageResolver], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer], 
 bundle: org.apache.camel.camel-blueprint [4], symbolicName: 
 org.apache.camel.camel-blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle: 
 org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle: 
 org.apache.felix.configadmin [25], symbolicName: org.apache.felix.configadmin
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.DataFormatResolver], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer], 
 bundle: org.apache.aries.blueprint [13], symbolicName: 
 org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.camel.camel-blueprint [4], symbolicName: 
 org.apache.camel.camel-blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] 

[jira] [Assigned] (CAMEL-8326) Project created from camel-blueprint-archetype does not work

2015-02-10 Thread Charles Moulliard (JIRA)

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

Charles Moulliard reassigned CAMEL-8326:


Assignee: Charles Moulliard

 Project created from camel-blueprint-archetype does not work
 

 Key: CAMEL-8326
 URL: https://issues.apache.org/jira/browse/CAMEL-8326
 Project: Camel
  Issue Type: Bug
  Components: osgi, tooling
Affects Versions: 2.13.3, 2.14.1
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Attachments: test.zip


 When we launch the camel:run maven goal created from a project created using 
 the archetype :
 org.apache.camel.archetypes:camel-archetype-blueprint (Creates a new Camel 
 project with OSGi blueprint support. Ready to be deployed in OSGi.)
 then it fails
 {code}
 [mel.test.blueprint.Main.main()] MainSupportINFO  Apache 
 Camel 2.14.1 starting
 [mel.test.blueprint.Main.main()] Activator  INFO  Camel 
 activator starting
 [mel.test.blueprint.Main.main()] Activator  INFO  Camel 
 activator started
 [mel.test.blueprint.Main.main()] BlueprintExtender  INFO  No 
 quiesce support is available, so blueprint components will not participate in 
 quiesce operations
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  Test 
 bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle, 
 Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec, 
 Bundle-Version=0.2.1
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.packageadmin.PackageAdmin], bundle: 
 de.kalpatec.pojosr.framework [0], symbolicName: de.kalpatec.pojosr.framework
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.LanguageResolver], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer], 
 bundle: org.apache.camel.camel-blueprint [4], symbolicName: 
 org.apache.camel.camel-blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle: 
 org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle: 
 org.apache.felix.configadmin [25], symbolicName: org.apache.felix.configadmin
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.DataFormatResolver], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer], 
 bundle: org.apache.aries.blueprint [13], symbolicName: 
 org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.camel.camel-blueprint [4], symbolicName: 
 org.apache.camel.camel-blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.url.URLStreamHandlerService], bundle: 
 org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.cm.ConfigurationAdmin], bundle: 
 

[jira] [Closed] (CAMEL-8326) Project created from camel-blueprint-archetype does not work

2015-02-10 Thread Charles Moulliard (JIRA)

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

Charles Moulliard closed CAMEL-8326.

Resolution: Fixed

code submitted : ed73023..c7cb9d3  master - master

 Project created from camel-blueprint-archetype does not work
 

 Key: CAMEL-8326
 URL: https://issues.apache.org/jira/browse/CAMEL-8326
 Project: Camel
  Issue Type: Bug
  Components: osgi, tooling
Affects Versions: 2.13.3, 2.14.1
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Attachments: test.zip


 When we launch the camel:run maven goal created from a project created using 
 the archetype :
 org.apache.camel.archetypes:camel-archetype-blueprint (Creates a new Camel 
 project with OSGi blueprint support. Ready to be deployed in OSGi.)
 then it fails
 {code}
 [mel.test.blueprint.Main.main()] MainSupportINFO  Apache 
 Camel 2.14.1 starting
 [mel.test.blueprint.Main.main()] Activator  INFO  Camel 
 activator starting
 [mel.test.blueprint.Main.main()] Activator  INFO  Camel 
 activator started
 [mel.test.blueprint.Main.main()] BlueprintExtender  INFO  No 
 quiesce support is available, so blueprint components will not participate in 
 quiesce operations
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  Test 
 bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle, 
 Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec, 
 Bundle-Version=0.2.1
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.packageadmin.PackageAdmin], bundle: 
 de.kalpatec.pojosr.framework [0], symbolicName: de.kalpatec.pojosr.framework
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.LanguageResolver], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer], 
 bundle: org.apache.camel.camel-blueprint [4], symbolicName: 
 org.apache.camel.camel-blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle: 
 org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle: 
 org.apache.felix.configadmin [25], symbolicName: org.apache.felix.configadmin
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.DataFormatResolver], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer], 
 bundle: org.apache.aries.blueprint [13], symbolicName: 
 org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.camel.camel-blueprint [4], symbolicName: 
 org.apache.camel.camel-blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.url.URLStreamHandlerService], bundle: 
 org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: 

[jira] [Commented] (CAMEL-8326) Project created from camel-blueprint-archetype does not work

2015-02-09 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14313757#comment-14313757
 ] 

Charles Moulliard commented on CAMEL-8326:
--

When camel:run is launched with the option use Blueprint, then the Camel Main 
class part of camel-test-blueprint project uses the PoJoSR framework and not 
Karaf with Pax WEB. Here is how the Main class of the project 
camel-test-blueprint calls the Camel to create the Bundle Context :

https://github.com/apache/camel/blob/master/components/camel-test-blueprint/src/main/java/org/apache/camel/test/blueprint/Main.java#L136
 
https://github.com/apache/camel/blob/master/components/camel-test-blueprint/src/main/java/org/apache/camel/test/blueprint/CamelBlueprintHelper.java#L105

 Project created from camel-blueprint-archetype does not work
 

 Key: CAMEL-8326
 URL: https://issues.apache.org/jira/browse/CAMEL-8326
 Project: Camel
  Issue Type: Bug
  Components: osgi, tooling
Affects Versions: 2.13.3, 2.14.1
Reporter: Charles Moulliard

 When we launch the camel:run maven goal created from a project created using 
 the archetype :
 org.apache.camel.archetypes:camel-archetype-blueprint (Creates a new Camel 
 project with OSGi blueprint support. Ready to be deployed in OSGi.)
 then it fails
 {code}
 [mel.test.blueprint.Main.main()] MainSupportINFO  Apache 
 Camel 2.14.1 starting
 [mel.test.blueprint.Main.main()] Activator  INFO  Camel 
 activator starting
 [mel.test.blueprint.Main.main()] Activator  INFO  Camel 
 activator started
 [mel.test.blueprint.Main.main()] BlueprintExtender  INFO  No 
 quiesce support is available, so blueprint components will not participate in 
 quiesce operations
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  Test 
 bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle, 
 Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec, 
 Bundle-Version=0.2.1
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.packageadmin.PackageAdmin], bundle: 
 de.kalpatec.pojosr.framework [0], symbolicName: de.kalpatec.pojosr.framework
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.LanguageResolver], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer], 
 bundle: org.apache.camel.camel-blueprint [4], symbolicName: 
 org.apache.camel.camel-blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle: 
 org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle: 
 org.apache.felix.configadmin [25], symbolicName: org.apache.felix.configadmin
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.DataFormatResolver], bundle: 
 org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer], 
 bundle: org.apache.aries.blueprint [13], symbolicName: 
 org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.camel.camel-blueprint [4], symbolicName: 
 org.apache.camel.camel-blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   

[jira] [Created] (CAMEL-8326) Project created from camel-blueprint-archetype does not work

2015-02-09 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-8326:


 Summary: Project created from camel-blueprint-archetype does not 
work
 Key: CAMEL-8326
 URL: https://issues.apache.org/jira/browse/CAMEL-8326
 Project: Camel
  Issue Type: Bug
Affects Versions: 2.14.1, 2.13.3
Reporter: Charles Moulliard


When we launch the camel:run maven goal created from a project created using 
the archetype :

org.apache.camel.archetypes:camel-archetype-blueprint (Creates a new Camel 
project with OSGi blueprint support. Ready to be deployed in OSGi.)

then it fails

{code}
[mel.test.blueprint.Main.main()] MainSupportINFO  Apache 
Camel 2.14.1 starting
[mel.test.blueprint.Main.main()] Activator  INFO  Camel 
activator starting
[mel.test.blueprint.Main.main()] Activator  INFO  Camel 
activator started
[mel.test.blueprint.Main.main()] BlueprintExtender  INFO  No 
quiesce support is available, so blueprint components will not participate in 
quiesce operations
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  Test 
bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle, 
Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec, 
Bundle-Version=0.2.1
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.osgi.service.packageadmin.PackageAdmin], bundle: 
de.kalpatec.pojosr.framework [0], symbolicName: de.kalpatec.pojosr.framework
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.camel.spi.LanguageResolver], bundle: 
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer], 
bundle: org.apache.camel.camel-blueprint [4], symbolicName: 
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle: 
org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle: 
org.apache.felix.configadmin [25], symbolicName: org.apache.felix.configadmin
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.camel.spi.DataFormatResolver], bundle: 
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer], 
bundle: org.apache.aries.blueprint [13], symbolicName: 
org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
org.apache.camel.camel-blueprint [4], symbolicName: 
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle: 
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.osgi.service.url.URLStreamHandlerService], bundle: 
org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.osgi.service.cm.ConfigurationAdmin], bundle: 
org.apache.felix.configadmin [25], symbolicName: org.apache.felix.configadmin
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.camel.spi.ComponentResolver], bundle: 
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  

[jira] [Commented] (CAMEL-8301) ClassNotFoundException: org.apache.aries.blueprint.NamespaceHandler not found by org.apache.camel.camel-cxf-transport

2015-01-30 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-8301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14298772#comment-14298772
 ] 

Charles Moulliard commented on CAMEL-8301:
--

I suspect that the problem comes from the fact that this version of the 
camel-cxf-transport is targeted for Aries Blueprint 1.1

{code}
camel-cxf-transport (300)
-
Manifest-Version = 1.0
Karaf-Info = Camel;camel-cxf-transport=2.14.0
Bnd-LastModified = 1410773615135
Tool = Bnd-1.50.0
Built-By = ubuntu
Implementation-Version = 2.14.0
Build-Jdk = 1.7.0_67
Implementation-Title = Apache Camel
Created-By = Apache Maven Bundle Plugin

Bundle-Vendor = The Apache Software Foundation
Bundle-Name = camel-cxf-transport
Bundle-DocURL = http://www.apache.org/
Bundle-Description = Camel Transport for CXF
Bundle-SymbolicName = org.apache.camel.camel-cxf-transport
Bundle-Version = 2.14.0
Bundle-License = http://www.apache.org/licenses/LICENSE-2.0.txt
Bundle-ManifestVersion = 2

Export-Service =

org.apache.aries.blueprint.NamespaceHandler;osgi.service.blueprint.namespace=http://cxf.apache.org/transports/camel/blueprint

Import-Package =
javax.xml.namespace,
org.apache.aries.blueprint;resolution:=optional;version=[1.1,2),
{code}

 ClassNotFoundException: org.apache.aries.blueprint.NamespaceHandler not found 
 by org.apache.camel.camel-cxf-transport
 -

 Key: CAMEL-8301
 URL: https://issues.apache.org/jira/browse/CAMEL-8301
 Project: Camel
  Issue Type: Bug
  Components: el-cxf-transport
Affects Versions: 2.14.0
 Environment: Karaf : 2.3.0.redhat-610379
Reporter: Charles Moulliard
Priority: Blocker

 The blueprint context of the bundle camel-cxf-transport (version 2.14) cannot 
 be started as this exception is generated :
 {code}
 2015-01-30 16:23:25,913 | ERROR | l Console Thread | BlueprintContainerImpl   
 | ?   ? | 9 - 
 org.apache.aries.blueprint.core - 1.0.1.redhat-610379 | Unable to start 
 blueprint container for bundle org.apache.camel.camel-cxf-transport
 org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to 
 instantiate components
   at 
 org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:680)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:374)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:261)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:270)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:233)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1103)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:696)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:484)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4650)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.Felix$4.run(Felix.java:2123)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 

[jira] [Updated] (CAMEL-8301) ClassNotFoundException: org.apache.aries.blueprint.NamespaceHandler not found by org.apache.camel.camel-cxf-transport

2015-01-30 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-8301:
-
Description: 
The blueprint context of the bundle camel-cxf-transport (version 2.14) cannot 
be started as this exception is generated :

{code}
2015-01-30 16:23:25,913 | ERROR | l Console Thread | BlueprintContainerImpl 
  | ?   ? | 9 - 
org.apache.aries.blueprint.core - 1.0.1.redhat-610379 | Unable to start 
blueprint container for bundle org.apache.camel.camel-cxf-transport
org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to 
instantiate components
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:680)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:374)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:261)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
at 
org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:270)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
at 
org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:233)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)[11:org.apache.aries.util:1.0.1.redhat-610379]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)[11:org.apache.aries.util:1.0.1.redhat-610379]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)[11:org.apache.aries.util:1.0.1.redhat-610379]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)[11:org.apache.aries.util:1.0.1.redhat-610379]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)[11:org.apache.aries.util:1.0.1.redhat-610379]
at 
org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1103)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:696)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:484)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4650)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.felix.framework.Felix$4.run(Felix.java:2123)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.felix.framework.Felix.runInContext(Felix.java:2147)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.felix.framework.Felix.startBundle(Felix.java:2121)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:474)[22:org.apache.karaf.features.core:2.3.0.redhat-610379]
at 
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:404)[22:org.apache.karaf.features.core:2.3.0.redhat-610379]
at 
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:400)[22:org.apache.karaf.features.core:2.3.0.redhat-610379]
at 
org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)[26:org.apache.karaf.features.command:2.3.0.redhat-610379]
at 
org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:41)[26:org.apache.karaf.features.command:2.3.0.redhat-610379]
at 
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)[17:org.apache.karaf.shell.console:2.3.0.redhat-610379]
at 
org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[17:org.apache.karaf.shell.console:2.3.0.redhat-610379]
at 
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[15:org.apache.felix.gogo.runtime:0.11.0.redhat-610379]
at 

[jira] [Created] (CAMEL-8301) ClassNotFoundException: org.apache.aries.blueprint.NamespaceHandler not found by org.apache.camel.camel-cxf-transport

2015-01-30 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-8301:


 Summary: ClassNotFoundException: 
org.apache.aries.blueprint.NamespaceHandler not found by 
org.apache.camel.camel-cxf-transport
 Key: CAMEL-8301
 URL: https://issues.apache.org/jira/browse/CAMEL-8301
 Project: Camel
  Issue Type: Bug
  Components: el-cxf-transport
 Environment: Karaf : 2.3.0.redhat-610379
Reporter: Charles Moulliard
Priority: Blocker


The blueprint context of the bundle camel-cxf-transport cannot be started as 
this exception is generated :

{code}
2015-01-30 16:23:25,913 | ERROR | l Console Thread | BlueprintContainerImpl 
  | ?   ? | 9 - 
org.apache.aries.blueprint.core - 1.0.1.redhat-610379 | Unable to start 
blueprint container for bundle org.apache.camel.camel-cxf-transport
org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to 
instantiate components
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:680)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:374)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:261)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
at 
org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:270)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
at 
org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:233)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)[11:org.apache.aries.util:1.0.1.redhat-610379]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)[11:org.apache.aries.util:1.0.1.redhat-610379]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)[11:org.apache.aries.util:1.0.1.redhat-610379]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)[11:org.apache.aries.util:1.0.1.redhat-610379]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)[11:org.apache.aries.util:1.0.1.redhat-610379]
at 
org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1103)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:696)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:484)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4650)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.felix.framework.Felix$4.run(Felix.java:2123)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.felix.framework.Felix.runInContext(Felix.java:2147)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.felix.framework.Felix.startBundle(Felix.java:2121)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
at 
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:474)[22:org.apache.karaf.features.core:2.3.0.redhat-610379]
at 
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:404)[22:org.apache.karaf.features.core:2.3.0.redhat-610379]
at 
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:400)[22:org.apache.karaf.features.core:2.3.0.redhat-610379]
at 
org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)[26:org.apache.karaf.features.command:2.3.0.redhat-610379]
at 
org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:41)[26:org.apache.karaf.features.command:2.3.0.redhat-610379]
at 
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)[17:org.apache.karaf.shell.console:2.3.0.redhat-610379]

[jira] [Updated] (CAMEL-8301) ClassNotFoundException: org.apache.aries.blueprint.NamespaceHandler not found by org.apache.camel.camel-cxf-transport

2015-01-30 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-8301:
-
Affects Version/s: 2.14.0

 ClassNotFoundException: org.apache.aries.blueprint.NamespaceHandler not found 
 by org.apache.camel.camel-cxf-transport
 -

 Key: CAMEL-8301
 URL: https://issues.apache.org/jira/browse/CAMEL-8301
 Project: Camel
  Issue Type: Bug
  Components: el-cxf-transport
Affects Versions: 2.14.0
 Environment: Karaf : 2.3.0.redhat-610379
Reporter: Charles Moulliard
Priority: Blocker

 The blueprint context of the bundle camel-cxf-transport (version 2.14) cannot 
 be started as this exception is generated :
 {code}
 2015-01-30 16:23:25,913 | ERROR | l Console Thread | BlueprintContainerImpl   
 | ?   ? | 9 - 
 org.apache.aries.blueprint.core - 1.0.1.redhat-610379 | Unable to start 
 blueprint container for bundle org.apache.camel.camel-cxf-transport
 org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to 
 instantiate components
   at 
 org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:680)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:374)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:261)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:270)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:233)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1103)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:696)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:484)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4650)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.Felix$4.run(Felix.java:2123)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.Felix.runInContext(Felix.java:2147)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.Felix.startBundle(Felix.java:2121)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:474)[22:org.apache.karaf.features.core:2.3.0.redhat-610379]
   at 
 org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:404)[22:org.apache.karaf.features.core:2.3.0.redhat-610379]
   at 
 org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:400)[22:org.apache.karaf.features.core:2.3.0.redhat-610379]
   at 
 org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)[26:org.apache.karaf.features.command:2.3.0.redhat-610379]
   at 
 

[jira] [Commented] (CAMEL-8301) ClassNotFoundException: org.apache.aries.blueprint.NamespaceHandler not found by org.apache.camel.camel-cxf-transport

2015-01-30 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-8301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14298769#comment-14298769
 ] 

Charles Moulliard commented on CAMEL-8301:
--

The class is well exported by the aries bliueprint bundle 

{code}
Apache Aries Blueprint Core (9)
...
org/apache/aries/blueprint/NamespaceHandler.class
...
{code}

and the package org/apache/aries/blueprint/ is well imported by 
camel-cxf-transport

{code}
packages:imports 300
System Bundle (0): org.osgi.framework; version=1.7.0
System Bundle (0): javax.xml.namespace; version=0.0.0
System Bundle (0): org.w3c.dom; version=0.0.0
OPS4J Pax Logging - API (4): org.slf4j; version=1.7.1
OPS4J Pax Logging - API (4): org.slf4j; version=1.6.6
OPS4J Pax Logging - API (4): org.slf4j; version=1.5.11
OPS4J Pax Logging - API (4): org.slf4j; version=1.4.3
Apache Aries Blueprint Core (9): org.apache.aries.blueprint.mutable; 
version=1.0.0
Apache Aries Blueprint Core (9): org.osgi.service.blueprint; version=1.0.0
Apache Aries Blueprint API (14): org.osgi.service.blueprint.reflect; 
version=1.0.1
{code}

 ClassNotFoundException: org.apache.aries.blueprint.NamespaceHandler not found 
 by org.apache.camel.camel-cxf-transport
 -

 Key: CAMEL-8301
 URL: https://issues.apache.org/jira/browse/CAMEL-8301
 Project: Camel
  Issue Type: Bug
  Components: el-cxf-transport
Affects Versions: 2.14.0
 Environment: Karaf : 2.3.0.redhat-610379
Reporter: Charles Moulliard
Priority: Blocker

 The blueprint context of the bundle camel-cxf-transport (version 2.14) cannot 
 be started as this exception is generated :
 {code}
 2015-01-30 16:23:25,913 | ERROR | l Console Thread | BlueprintContainerImpl   
 | ?   ? | 9 - 
 org.apache.aries.blueprint.core - 1.0.1.redhat-610379 | Unable to start 
 blueprint container for bundle org.apache.camel.camel-cxf-transport
 org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to 
 instantiate components
   at 
 org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:680)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:374)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:261)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:270)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:233)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1103)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:696)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:484)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4650)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.Felix$4.run(Felix.java:2123)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.Felix.runInContext(Felix.java:2147)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.Felix.startBundle(Felix.java:2121)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 

[jira] [Commented] (CAMEL-8301) ClassNotFoundException: org.apache.aries.blueprint.NamespaceHandler not found by org.apache.camel.camel-cxf-transport

2015-01-30 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-8301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14298768#comment-14298768
 ] 

Charles Moulliard commented on CAMEL-8301:
--

Only these classes are loaded

{code}
camel-cxf-transport (300)
org/apache/aries/blueprint/mutable/MutableBeanArgument.class
org/apache/aries/blueprint/mutable/MutableBeanMetadata.class
org/apache/aries/blueprint/mutable/MutableBeanProperty.class
org/apache/aries/blueprint/mutable/MutableCollectionMetadata.class
org/apache/aries/blueprint/mutable/MutableComponentMetadata.class
org/apache/aries/blueprint/mutable/MutableIdRefMetadata.class
org/apache/aries/blueprint/mutable/MutableMapEntry.class
org/apache/aries/blueprint/mutable/MutableMapMetadata.class
org/apache/aries/blueprint/mutable/MutablePassThroughMetadata.class
org/apache/aries/blueprint/mutable/MutablePropsMetadata.class
org/apache/aries/blueprint/mutable/MutableRefMetadata.class
org/apache/aries/blueprint/mutable/MutableReferenceListMetadata.class
org/apache/aries/blueprint/mutable/MutableReferenceListener.class
org/apache/aries/blueprint/mutable/MutableReferenceMetadata.class
org/apache/aries/blueprint/mutable/MutableRegistrationListener.class
org/apache/aries/blueprint/mutable/MutableServiceMetadata.class
org/apache/aries/blueprint/mutable/MutableServiceReferenceMetadata.class
org/apache/aries/blueprint/mutable/MutableValueMetadata.class
{code}

 ClassNotFoundException: org.apache.aries.blueprint.NamespaceHandler not found 
 by org.apache.camel.camel-cxf-transport
 -

 Key: CAMEL-8301
 URL: https://issues.apache.org/jira/browse/CAMEL-8301
 Project: Camel
  Issue Type: Bug
  Components: el-cxf-transport
Affects Versions: 2.14.0
 Environment: Karaf : 2.3.0.redhat-610379
Reporter: Charles Moulliard
Priority: Blocker

 The blueprint context of the bundle camel-cxf-transport (version 2.14) cannot 
 be started as this exception is generated :
 {code}
 2015-01-30 16:23:25,913 | ERROR | l Console Thread | BlueprintContainerImpl   
 | ?   ? | 9 - 
 org.apache.aries.blueprint.core - 1.0.1.redhat-610379 | Unable to start 
 blueprint container for bundle org.apache.camel.camel-cxf-transport
 org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to 
 instantiate components
   at 
 org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:680)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:374)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:261)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:270)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:233)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)[11:org.apache.aries.util:1.0.1.redhat-610379]
   at 
 org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1103)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:696)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:484)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4650)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
   at 
 

[jira] [Created] (CAMEL-8292) Log the HTTP query generated to call the Open Weather Web server

2015-01-28 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-8292:


 Summary: Log the HTTP query generated to call the Open Weather Web 
server
 Key: CAMEL-8292
 URL: https://issues.apache.org/jira/browse/CAMEL-8292
 Project: Camel
  Issue Type: Improvement
  Components: camel-weather
Reporter: Charles Moulliard
 Fix For: 2.14.2, 2.15.0


The query created by the WeatherConfiguration.getQuery() method is not logged 
(DEBUG mode)



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


[jira] [Closed] (CAMEL-8292) Log the HTTP query generated to call the Open Weather Web server

2015-01-28 Thread Charles Moulliard (JIRA)

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

Charles Moulliard closed CAMEL-8292.

Resolution: Fixed

DEBUG Log option already defined for the consumer/producer

 Log the HTTP query generated to call the Open Weather Web server
 

 Key: CAMEL-8292
 URL: https://issues.apache.org/jira/browse/CAMEL-8292
 Project: Camel
  Issue Type: Improvement
  Components: camel-weather
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.14.2, 2.15.0


 The query created by the WeatherConfiguration.getQuery() method is not logged 
 (DEBUG mode)



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


[jira] [Assigned] (CAMEL-8292) Log the HTTP query generated to call the Open Weather Web server

2015-01-28 Thread Charles Moulliard (JIRA)

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

Charles Moulliard reassigned CAMEL-8292:


Assignee: Charles Moulliard

 Log the HTTP query generated to call the Open Weather Web server
 

 Key: CAMEL-8292
 URL: https://issues.apache.org/jira/browse/CAMEL-8292
 Project: Camel
  Issue Type: Improvement
  Components: camel-weather
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.14.2, 2.15.0


 The query created by the WeatherConfiguration.getQuery() method is not logged 
 (DEBUG mode)



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


[jira] [Created] (CAMEL-8185) IllegalArgumentException: argument type mismatch

2014-12-26 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-8185:


 Summary: IllegalArgumentException: argument type mismatch
 Key: CAMEL-8185
 URL: https://issues.apache.org/jira/browse/CAMEL-8185
 Project: Camel
  Issue Type: Bug
  Components: camel-scr
Affects Versions: 2.15.0
Reporter: Charles Moulliard


When camel-scr (2.15-SNAPSHOT) is deployed and used with Apache Karaf - 
2.3.0.redhat-611412

The following errors are generated when SCR got the CamelComponent 
{code}
2014-12-26 11:13:49,453 | ERROR | r-1.0.0-thread-2 | osgi-camel-scr 
  | ?   ? | 255 - 
com.redhat.gpe.training.osgi-camel-scr - 1.0.0 | 
[com.redhat.gpe.training.osgi.camel.BootStrap(52)] The gotCamelComponent method 
has thrown an exception
java.lang.IllegalArgumentException: argument type mismatch
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)[:1.7.0_51]
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_51]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_51]
at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_51]
at 
org.apache.felix.scr.impl.helper.BaseMethod.invokeMethod(BaseMethod.java:231)[82:org.apache.felix.scr:1.8.0.redhat-611412]
at 
org.apache.felix.scr.impl.helper.BaseMethod.access$500(BaseMethod.java:39)[82:org.apache.felix.scr:1.8.0.redhat-611412]
{code}

Here is the code used as example :

{code}
import org.apache.camel.CamelContext;
import org.apache.camel.RoutesBuilder;
import org.apache.camel.scr.AbstractCamelRunner;
import org.apache.camel.spi.ComponentResolver;
import org.apache.felix.scr.annotations.*;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

import java.util.ArrayList;
import java.util.List;

@Component(label = BootStrap.COMPONENT_LABEL, description = 
BootStrap.COMPONENT_DESCRIPTION)
@Properties({
@Property(name = camelContextId, value = camel-scr-exercise),
@Property(name = active, value = true)
})
@References({
@Reference(name = camelComponent,referenceInterface = 
ComponentResolver.class,
cardinality = ReferenceCardinality.MANDATORY_MULTIPLE, policy = 
ReferencePolicy.DYNAMIC,
policyOption = ReferencePolicyOption.GREEDY, bind = 
gotCamelComponent, unbind = lostCamelComponent)
})
public class BootStrap extends AbstractCamelRunner {

public static final String COMPONENT_LABEL = bootstrap.CamelScrExercise;
public static final String COMPONENT_DESCRIPTION = This is the description 
for camel-scr-exercise.;

public static final Logger LOGGER = 
LoggerFactory.getLogger(BootStrap.class);

@Override
protected ListRoutesBuilder getRouteBuilders() {
LOGGER.info(Load Camel Routes definition);
ListRoutesBuilder routesBuilders = new ArrayList();
routesBuilders.add(new GreeterRoute());
return routesBuilders;
}
}

{code}



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


[jira] [Updated] (CAMEL-8185) IllegalArgumentException: argument type mismatch

2014-12-26 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-8185:
-
Description: 
When camel-scr (2.15-SNAPSHOT) is deployed and used with Apache Karaf - 
2.3.0.redhat-611412

The following errors are generated when SCR got the CamelComponent or lost the 
Component
{code}
2014-12-26 11:13:49,453 | ERROR | r-1.0.0-thread-2 | osgi-camel-scr 
  | ?   ? | 255 - 
com.redhat.gpe.training.osgi-camel-scr - 1.0.0 | 
[com.redhat.gpe.training.osgi.camel.BootStrap(52)] The gotCamelComponent method 
has thrown an exception
java.lang.IllegalArgumentException: argument type mismatch
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)[:1.7.0_51]
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_51]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_51]
at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_51]
at 
org.apache.felix.scr.impl.helper.BaseMethod.invokeMethod(BaseMethod.java:231)[82:org.apache.felix.scr:1.8.0.redhat-611412]
at 
org.apache.felix.scr.impl.helper.BaseMethod.access$500(BaseMethod.java:39)[82:org.apache.felix.scr:1.8.0.redhat-611412]
{code}

{code}
2014-12-26 11:22:50,355 | ERROR | l Console Thread | osgi-camel-scr 
  | ?   ? | 255 - 
com.redhat.gpe.training.osgi-camel-scr - 1.0.0 | 
[com.redhat.gpe.training.osgi.camel.BootStrap(52)] The lostCamelComponent 
method has thrown an exception
java.lang.IllegalArgumentException: argument type mismatch
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)[:1.7.0_51]
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_51]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_51]
at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_51]
at 
org.apache.felix.scr.impl.helper.BaseMethod.invokeMethod(BaseMethod.java:231)[82:org.apache.felix.scr:1.8.0.redhat-611412]
at 
org.apache.felix.scr.impl.helper.BaseMethod.access$500(BaseMethod.java:39)[82:org.apache.felix.scr:1.8.0.redhat-611412]
at 
org.apache.felix.scr.impl.helper.BaseMethod$Resolved.invoke(BaseMethod.java:624)[82:org.apache.felix.scr:1.8.0.redhat-611412]
at 
org.apache.felix.scr.impl.helper.BaseMethod.invoke(BaseMethod.java:508)[82:org.apache.felix.scr:1.8.0.redhat-611412]
at 
org.apache.felix.scr.impl.helper.BindMethod.invoke(BindMethod.java:37)[82:org.apache.felix.scr:1.8.0.redhat-611412]
at 
org.apache.felix.scr.impl.manager.DependencyManager.invokeUnbindMethod(DependencyManager.java:1711)[82:org.apache.felix.scr:1.8.0.redhat-611412]
{code}

Here is the code used as example :

{code}
import org.apache.camel.CamelContext;
import org.apache.camel.RoutesBuilder;
import org.apache.camel.scr.AbstractCamelRunner;
import org.apache.camel.spi.ComponentResolver;
import org.apache.felix.scr.annotations.*;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

import java.util.ArrayList;
import java.util.List;

@Component(label = BootStrap.COMPONENT_LABEL, description = 
BootStrap.COMPONENT_DESCRIPTION)
@Properties({
@Property(name = camelContextId, value = camel-scr-exercise),
@Property(name = active, value = true)
})
@References({
@Reference(name = camelComponent,referenceInterface = 
ComponentResolver.class,
cardinality = ReferenceCardinality.MANDATORY_MULTIPLE, policy = 
ReferencePolicy.DYNAMIC,
policyOption = ReferencePolicyOption.GREEDY, bind = 
gotCamelComponent, unbind = lostCamelComponent)
})
public class BootStrap extends AbstractCamelRunner {

public static final String COMPONENT_LABEL = bootstrap.CamelScrExercise;
public static final String COMPONENT_DESCRIPTION = This is the description 
for camel-scr-exercise.;

public static final Logger LOGGER = 
LoggerFactory.getLogger(BootStrap.class);

@Override
protected ListRoutesBuilder getRouteBuilders() {
LOGGER.info(Load Camel Routes definition);
ListRoutesBuilder routesBuilders = new ArrayList();
routesBuilders.add(new GreeterRoute());
return routesBuilders;
}
}

{code}

  was:
When camel-scr (2.15-SNAPSHOT) is deployed and used with Apache Karaf - 
2.3.0.redhat-611412

The following errors are generated when SCR got the CamelComponent 
{code}
2014-12-26 11:13:49,453 | ERROR | r-1.0.0-thread-2 | osgi-camel-scr 
  | ?   ? | 255 - 
com.redhat.gpe.training.osgi-camel-scr - 1.0.0 | 
[com.redhat.gpe.training.osgi.camel.BootStrap(52)] The gotCamelComponent method 
has thrown an exception
java.lang.IllegalArgumentException: argument type mismatch
  

[jira] [Resolved] (CAMEL-8122) camel:run using useBlueprint option does not launch camel example project

2014-12-05 Thread Charles Moulliard (JIRA)

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

Charles Moulliard resolved CAMEL-8122.
--
Resolution: Fixed

Issue not longer there after doing a mvn clean install of camel-2.15-SNAPSHOT 
project

 camel:run using useBlueprint option does not launch camel example project
 ---

 Key: CAMEL-8122
 URL: https://issues.apache.org/jira/browse/CAMEL-8122
 Project: Camel
  Issue Type: Bug
  Components: examples
Affects Versions: 2.15.0
Reporter: Charles Moulliard

 When we launch the maven camel:run goal with the camel-example-sql-blueprint, 
 the camel project is not started and this OSGI Service error is reported.
 I suspect that some bundles are missing and not loaded by the PoJoSr 
 classloader when the project is started/launched by the camel-maven-plugin 
 See line of code 
 {code}
 package org.apache.camel.maven;
 ...
 public class RunMojo extends AbstractExecMojo {
 ...
 } else if (usingBlueprintMain) {
 mainClass = org.apache.camel.test.blueprint.Main;
 // must include plugin dependencies for blueprint
 extraPluginDependencyArtifactId = camel-test-blueprint;
 {code}
 Error reported on the console
 {code}
 Caused by: java.lang.RuntimeException: Gave up waiting for service 
 (objectClass=org.apache.camel.CamelContext)
 [INFO] --- camel-maven-plugin:2.15-SNAPSHOT:run (default-cli) @ 
 camel-example-sql-blueprint ---
 [INFO] Using org.apache.camel.test.blueprint.Main to initiate a CamelContext
 [INFO] Starting Camel ...
 [mel.test.blueprint.Main.main()] MainSupportINFO  Apache 
 Camel 2.15-SNAPSHOT starting
 [mel.test.blueprint.Main.main()] Activator  INFO  Camel 
 activator starting
 [mel.test.blueprint.Main.main()] Activator  INFO  Camel 
 activator started
 [mel.test.blueprint.Main.main()] BlueprintExtender  INFO  No 
 quiesce support is available, so blueprint components will not participate in 
 quiesce operations
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  Test 
 bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle, 
 Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec, 
 Bundle-Version=0.2.1
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle: 
 org.apache.camel.camel-core [3], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [17], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [17], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.camel.camel-blueprint [2], symbolicName: 
 org.apache.camel.camel-blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.proxy.ProxyManager], bundle: 
 org.apache.aries.proxy.impl [19], symbolicName: org.apache.aries.proxy.impl
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.cm.ConfigurationAdmin], bundle: 
 org.apache.felix.configadmin [28], symbolicName: org.apache.felix.configadmin
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [17], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle: 
 org.apache.felix.configadmin [28], symbolicName: org.apache.felix.configadmin
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle: 
 org.apache.felix.fileinstall [29], symbolicName: org.apache.felix.fileinstall
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.cm.ConfigurationListener, 
 org.apache.felix.fileinstall.ArtifactListener, 
 org.apache.felix.fileinstall.ArtifactInstaller], bundle: 
 org.apache.felix.fileinstall [29], symbolicName: org.apache.felix.fileinstall
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.url.URLStreamHandlerService], bundle: 
 org.apache.felix.fileinstall [29], 

[jira] [Assigned] (CAMEL-8122) camel:run using useBlueprint option does not launch camel example project

2014-12-05 Thread Charles Moulliard (JIRA)

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

Charles Moulliard reassigned CAMEL-8122:


Assignee: Charles Moulliard

 camel:run using useBlueprint option does not launch camel example project
 ---

 Key: CAMEL-8122
 URL: https://issues.apache.org/jira/browse/CAMEL-8122
 Project: Camel
  Issue Type: Bug
  Components: examples
Affects Versions: 2.15.0
Reporter: Charles Moulliard
Assignee: Charles Moulliard

 When we launch the maven camel:run goal with the camel-example-sql-blueprint, 
 the camel project is not started and this OSGI Service error is reported.
 I suspect that some bundles are missing and not loaded by the PoJoSr 
 classloader when the project is started/launched by the camel-maven-plugin 
 See line of code 
 {code}
 package org.apache.camel.maven;
 ...
 public class RunMojo extends AbstractExecMojo {
 ...
 } else if (usingBlueprintMain) {
 mainClass = org.apache.camel.test.blueprint.Main;
 // must include plugin dependencies for blueprint
 extraPluginDependencyArtifactId = camel-test-blueprint;
 {code}
 Error reported on the console
 {code}
 Caused by: java.lang.RuntimeException: Gave up waiting for service 
 (objectClass=org.apache.camel.CamelContext)
 [INFO] --- camel-maven-plugin:2.15-SNAPSHOT:run (default-cli) @ 
 camel-example-sql-blueprint ---
 [INFO] Using org.apache.camel.test.blueprint.Main to initiate a CamelContext
 [INFO] Starting Camel ...
 [mel.test.blueprint.Main.main()] MainSupportINFO  Apache 
 Camel 2.15-SNAPSHOT starting
 [mel.test.blueprint.Main.main()] Activator  INFO  Camel 
 activator starting
 [mel.test.blueprint.Main.main()] Activator  INFO  Camel 
 activator started
 [mel.test.blueprint.Main.main()] BlueprintExtender  INFO  No 
 quiesce support is available, so blueprint components will not participate in 
 quiesce operations
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  Test 
 bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle, 
 Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec, 
 Bundle-Version=0.2.1
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle: 
 org.apache.camel.camel-core [3], symbolicName: org.apache.camel.camel-core
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [17], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [17], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.camel.camel-blueprint [2], symbolicName: 
 org.apache.camel.camel-blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.proxy.ProxyManager], bundle: 
 org.apache.aries.proxy.impl [19], symbolicName: org.apache.aries.proxy.impl
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.cm.ConfigurationAdmin], bundle: 
 org.apache.felix.configadmin [28], symbolicName: org.apache.felix.configadmin
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
 org.apache.aries.blueprint [17], symbolicName: org.apache.aries.blueprint
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle: 
 org.apache.felix.configadmin [28], symbolicName: org.apache.felix.configadmin
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle: 
 org.apache.felix.fileinstall [29], symbolicName: org.apache.felix.fileinstall
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.cm.ConfigurationListener, 
 org.apache.felix.fileinstall.ArtifactListener, 
 org.apache.felix.fileinstall.ArtifactInstaller], bundle: 
 org.apache.felix.fileinstall [29], symbolicName: org.apache.felix.fileinstall
 [mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
 ServiceReference: [org.osgi.service.url.URLStreamHandlerService], bundle: 
 org.apache.felix.fileinstall [29], symbolicName: org.apache.felix.fileinstall
 

[jira] [Commented] (CAMEL-7925) groovy and osgi - Could not initialize class script1413536396719697720774

2014-12-05 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14235338#comment-14235338
 ] 

Charles Moulliard commented on CAMEL-7925:
--

Unfortunately no. I'm not even sure that a ticket has been logged.

 groovy and osgi - Could not initialize class script1413536396719697720774
 -

 Key: CAMEL-7925
 URL: https://issues.apache.org/jira/browse/CAMEL-7925
 Project: Camel
  Issue Type: Bug
  Components: camel-groovy
 Environment: Apache Karaf 2.2.x
Reporter: Charles Moulliard
Assignee: Charles Moulliard
Priority: Minor

 When a camel route is deployed on apache Karaf using a groovy expression to 
 be evaluated we get this error 
 https://gist.github.com/cmoulliard/7294122c47e9c18df399
 Route
 {code}
   from(direct:launch).routeId(request-token)
   
   .onException(HttpOperationFailedException.class)
   .handled(true)
   .log(An error occurred)
   .to(direct:interface-status)
   .end()
   
   .setHeader(Exchange.HTTP_URI, constant(wayneUriGetSession))
   .setHeader(Exchange.HTTP_QUERY, constant(User= + UserName + 
  + Pass= + Password))
   .setHeader(Exchange.HTTP_METHOD, constant(GET))
   
   .to(https4://token-service)
   .convertBodyTo(String.class)
   .setHeader(token).groovy(body.replaceAll('\',''))
 {code}
 {code}
 Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
 script1413536396719697720774
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
 Method)[:1.7.0_51]
   at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)[:1.7.0_51]
   at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.7.0_51]
   at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)[:1.7.0_51]
   at java.lang.Class.newInstance(Class.java:374)[:1.7.0_51]
   at 
 org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)
 {code}



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


[jira] [Commented] (CAMEL-7925) groovy and osgi - Could not initialize class script1413536396719697720774

2014-12-05 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14235402#comment-14235402
 ] 

Charles Moulliard commented on CAMEL-7925:
--

You will solve a part of the problem if you restrict the packages to be 
imported (as you propose). But as Groovy will generate class dynamically under 
the name script123456789, they will not be loaded and a classloading exception 
will take place for these classes. This is why until now, the trick to import 
dynamically everything. For sure, this is not a good thing as it breaks the 
OSGI modularity.

 groovy and osgi - Could not initialize class script1413536396719697720774
 -

 Key: CAMEL-7925
 URL: https://issues.apache.org/jira/browse/CAMEL-7925
 Project: Camel
  Issue Type: Bug
  Components: camel-groovy
 Environment: Apache Karaf 2.2.x
Reporter: Charles Moulliard
Assignee: Charles Moulliard
Priority: Minor

 When a camel route is deployed on apache Karaf using a groovy expression to 
 be evaluated we get this error 
 https://gist.github.com/cmoulliard/7294122c47e9c18df399
 Route
 {code}
   from(direct:launch).routeId(request-token)
   
   .onException(HttpOperationFailedException.class)
   .handled(true)
   .log(An error occurred)
   .to(direct:interface-status)
   .end()
   
   .setHeader(Exchange.HTTP_URI, constant(wayneUriGetSession))
   .setHeader(Exchange.HTTP_QUERY, constant(User= + UserName + 
  + Pass= + Password))
   .setHeader(Exchange.HTTP_METHOD, constant(GET))
   
   .to(https4://token-service)
   .convertBodyTo(String.class)
   .setHeader(token).groovy(body.replaceAll('\',''))
 {code}
 {code}
 Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
 script1413536396719697720774
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
 Method)[:1.7.0_51]
   at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)[:1.7.0_51]
   at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.7.0_51]
   at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)[:1.7.0_51]
   at java.lang.Class.newInstance(Class.java:374)[:1.7.0_51]
   at 
 org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)
 {code}



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


[jira] [Created] (CAMEL-8122) camel:run using useBlueprint option does not launch camel example project

2014-12-04 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-8122:


 Summary: camel:run using useBlueprint option does not launch 
camel example project
 Key: CAMEL-8122
 URL: https://issues.apache.org/jira/browse/CAMEL-8122
 Project: Camel
  Issue Type: Bug
  Components: examples
Affects Versions: 2.15.0
Reporter: Charles Moulliard


When we launch the maven camel:run goal with the camel-example-sql-blueprint, 
the camel project is not started and this OSGI Service error is reported.

I suspect that some bundles are missing and not loaded by the PoJoSr 
classloader when the project is started/launched by the camel-maven-plugin 

See line of code 

{code}
package org.apache.camel.maven;
...
public class RunMojo extends AbstractExecMojo {
...

} else if (usingBlueprintMain) {
mainClass = org.apache.camel.test.blueprint.Main;
// must include plugin dependencies for blueprint
extraPluginDependencyArtifactId = camel-test-blueprint;
{code}
{code}

Caused by: java.lang.RuntimeException: Gave up waiting for service 
(objectClass=org.apache.camel.CamelContext)


[INFO] --- camel-maven-plugin:2.15-SNAPSHOT:run (default-cli) @ 
camel-example-sql-blueprint ---
[INFO] Using org.apache.camel.test.blueprint.Main to initiate a CamelContext
[INFO] Starting Camel ...
[mel.test.blueprint.Main.main()] MainSupportINFO  Apache 
Camel 2.15-SNAPSHOT starting
[mel.test.blueprint.Main.main()] Activator  INFO  Camel 
activator starting
[mel.test.blueprint.Main.main()] Activator  INFO  Camel 
activator started
[mel.test.blueprint.Main.main()] BlueprintExtender  INFO  No 
quiesce support is available, so blueprint components will not participate in 
quiesce operations
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  Test 
bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle, 
Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec, 
Bundle-Version=0.2.1
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle: 
org.apache.camel.camel-core [3], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
org.apache.aries.blueprint [17], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
org.apache.aries.blueprint [17], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
org.apache.camel.camel-blueprint [2], symbolicName: 
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.proxy.ProxyManager], bundle: 
org.apache.aries.proxy.impl [19], symbolicName: org.apache.aries.proxy.impl
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.osgi.service.cm.ConfigurationAdmin], bundle: 
org.apache.felix.configadmin [28], symbolicName: org.apache.felix.configadmin
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
org.apache.aries.blueprint [17], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle: 
org.apache.felix.configadmin [28], symbolicName: org.apache.felix.configadmin
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle: 
org.apache.felix.fileinstall [29], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.osgi.service.cm.ConfigurationListener, 
org.apache.felix.fileinstall.ArtifactListener, 
org.apache.felix.fileinstall.ArtifactInstaller], bundle: 
org.apache.felix.fileinstall [29], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.osgi.service.url.URLStreamHandlerService], bundle: 
org.apache.felix.fileinstall [29], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.blueprint.services.ParserService], bundle: 
org.apache.aries.blueprint [17], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: 

[jira] [Updated] (CAMEL-8122) camel:run using useBlueprint option does not launch camel example project

2014-12-04 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-8122:
-
Description: 
When we launch the maven camel:run goal with the camel-example-sql-blueprint, 
the camel project is not started and this OSGI Service error is reported.

I suspect that some bundles are missing and not loaded by the PoJoSr 
classloader when the project is started/launched by the camel-maven-plugin 

See line of code 

{code}
package org.apache.camel.maven;
...
public class RunMojo extends AbstractExecMojo {
...

} else if (usingBlueprintMain) {
mainClass = org.apache.camel.test.blueprint.Main;
// must include plugin dependencies for blueprint
extraPluginDependencyArtifactId = camel-test-blueprint;
{code}

Error reported on the console

{code}

Caused by: java.lang.RuntimeException: Gave up waiting for service 
(objectClass=org.apache.camel.CamelContext)


[INFO] --- camel-maven-plugin:2.15-SNAPSHOT:run (default-cli) @ 
camel-example-sql-blueprint ---
[INFO] Using org.apache.camel.test.blueprint.Main to initiate a CamelContext
[INFO] Starting Camel ...
[mel.test.blueprint.Main.main()] MainSupportINFO  Apache 
Camel 2.15-SNAPSHOT starting
[mel.test.blueprint.Main.main()] Activator  INFO  Camel 
activator starting
[mel.test.blueprint.Main.main()] Activator  INFO  Camel 
activator started
[mel.test.blueprint.Main.main()] BlueprintExtender  INFO  No 
quiesce support is available, so blueprint components will not participate in 
quiesce operations
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  Test 
bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle, 
Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec, 
Bundle-Version=0.2.1
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle: 
org.apache.camel.camel-core [3], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
org.apache.aries.blueprint [17], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
org.apache.aries.blueprint [17], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
org.apache.camel.camel-blueprint [2], symbolicName: 
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.proxy.ProxyManager], bundle: 
org.apache.aries.proxy.impl [19], symbolicName: org.apache.aries.proxy.impl
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.osgi.service.cm.ConfigurationAdmin], bundle: 
org.apache.felix.configadmin [28], symbolicName: org.apache.felix.configadmin
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
org.apache.aries.blueprint [17], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle: 
org.apache.felix.configadmin [28], symbolicName: org.apache.felix.configadmin
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle: 
org.apache.felix.fileinstall [29], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.osgi.service.cm.ConfigurationListener, 
org.apache.felix.fileinstall.ArtifactListener, 
org.apache.felix.fileinstall.ArtifactInstaller], bundle: 
org.apache.felix.fileinstall [29], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.osgi.service.url.URLStreamHandlerService], bundle: 
org.apache.felix.fileinstall [29], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.blueprint.services.ParserService], bundle: 
org.apache.aries.blueprint [17], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle: 
org.apache.aries.blueprint [17], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper   WARN  
ServiceReference: 

[jira] [Commented] (CAMEL-7925) groovy and osgi - Could not initialize class script1413536396719697720774

2014-12-04 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234041#comment-14234041
 ] 

Charles Moulliard commented on CAMEL-7925:
--

I have redeployed my project on Apache Karaf 3.0.2 using Apache Camel 2.14.0 
with Groovy 2.3.6 and another classloading issue is reported even if the class 
groovy.lang.SCript is well packaged with the bundle Grrovy Runtime 

Error 

{code}
Caused by: java.lang.ClassNotFoundException: groovy.lang.Script
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:655)
at 
groovy.lang.GroovyClassLoader$InnerLoader.loadClass(GroovyClassLoader.java:408)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:765)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:753)
... 31 more

1 error

at 
org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:309)[122:groovy-all:2.3.6]
at 
org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1067)[122:groovy-all:2.3.6]
at 
org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:583)[122:groovy-all:2.3.6]
at 
org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:561)[122:groovy-all:2.3.6]
at 
org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:538)[122:groovy-all:2.3.6]
at 
groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:286)[122:groovy-all:2.3.6]
at 
groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:259)[122:groovy-all:2.3.6]
at 
groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:245)[122:groovy-all:2.3.6]
at 
groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:203)[122:groovy-all:2.3.6]
at 
groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:213)[122:groovy-all:2.3.6]
at 
org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:65)[123:org.apache.camel.camel-groovy:2.14.0]
at 
org.apache.camel.language.groovy.GroovyExpression.evaluate(GroovyExpression.java:50)[123:org.apache.camel.camel-groovy:2.14.0]
at 
org.apache.camel.builder.ProcessorBuilder$4.process(ProcessorBuilder.java:103)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:398)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.Pipeline.process(Pipeline.java:118)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.Pipeline.process(Pipeline.java:80)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.component.timer.TimerConsumer.sendTimerExchange(TimerConsumer.java:157)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.component.timer.TimerConsumer$1.run(TimerConsumer.java:68)[92:org.apache.camel.camel-core:2.14.0]
at java.util.TimerThread.mainLoop(Timer.java:555)[:1.7.0_51]
at java.util.TimerThread.run(Timer.java:505)[:1.7.0_51]
{code}

What is deployed on Karaf 

{code}
 92 | Active   |  50 | 2.14.0 | mvn:org.apache.camel/camel-core/2.14.0
 93 | Active   |  50 | 2.14.0 | 
mvn:org.apache.camel.karaf/camel-karaf-commands/2.14.0
108 | Active   |  50 | 1.1.1  | 
mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/1.1.1
109 | Active   |  50 | 2.14.0 | mvn:org.apache.camel/camel-spring/2.14.0
110 | Active   |  50 | 2.14.0 | 
mvn:org.apache.camel/camel-blueprint/2.14.0
120 | Active   |  50 | 1.7.0.6| 
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.ant/1.7.0_6
121 | Active   |  50 | 2.2.0  | 
mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/2.2.0
122 | Active   |  50 | 2.3.6  | mvn:org.codehaus.groovy/groovy-all/2.3.6
123 | 

[jira] [Comment Edited] (CAMEL-7925) groovy and osgi - Could not initialize class script1413536396719697720774

2014-12-04 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234041#comment-14234041
 ] 

Charles Moulliard edited comment on CAMEL-7925 at 12/4/14 9:06 AM:
---

I have redeployed my project on Apache Karaf 3.0.2 using Apache Camel 2.14.0 
with Groovy 2.3.6 and another classloading issue is reported even if the class 
groovy.lang.Script is well packaged with the bundle Groovy Runtime 

Error 

{code}
Caused by: java.lang.ClassNotFoundException: groovy.lang.Script
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:655)
at 
groovy.lang.GroovyClassLoader$InnerLoader.loadClass(GroovyClassLoader.java:408)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:765)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:753)
... 31 more

1 error

at 
org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:309)[122:groovy-all:2.3.6]
at 
org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1067)[122:groovy-all:2.3.6]
at 
org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:583)[122:groovy-all:2.3.6]
at 
org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:561)[122:groovy-all:2.3.6]
at 
org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:538)[122:groovy-all:2.3.6]
at 
groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:286)[122:groovy-all:2.3.6]
at 
groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:259)[122:groovy-all:2.3.6]
at 
groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:245)[122:groovy-all:2.3.6]
at 
groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:203)[122:groovy-all:2.3.6]
at 
groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:213)[122:groovy-all:2.3.6]
at 
org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:65)[123:org.apache.camel.camel-groovy:2.14.0]
at 
org.apache.camel.language.groovy.GroovyExpression.evaluate(GroovyExpression.java:50)[123:org.apache.camel.camel-groovy:2.14.0]
at 
org.apache.camel.builder.ProcessorBuilder$4.process(ProcessorBuilder.java:103)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:398)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.Pipeline.process(Pipeline.java:118)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.Pipeline.process(Pipeline.java:80)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.component.timer.TimerConsumer.sendTimerExchange(TimerConsumer.java:157)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.component.timer.TimerConsumer$1.run(TimerConsumer.java:68)[92:org.apache.camel.camel-core:2.14.0]
at java.util.TimerThread.mainLoop(Timer.java:555)[:1.7.0_51]
at java.util.TimerThread.run(Timer.java:505)[:1.7.0_51]
{code}

What is deployed on Karaf 

{code}
 92 | Active   |  50 | 2.14.0 | mvn:org.apache.camel/camel-core/2.14.0
 93 | Active   |  50 | 2.14.0 | 
mvn:org.apache.camel.karaf/camel-karaf-commands/2.14.0
108 | Active   |  50 | 1.1.1  | 
mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/1.1.1
109 | Active   |  50 | 2.14.0 | mvn:org.apache.camel/camel-spring/2.14.0
110 | Active   |  50 | 2.14.0 | 
mvn:org.apache.camel/camel-blueprint/2.14.0
120 | Active   |  50 | 1.7.0.6| 
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.ant/1.7.0_6
121 | Active   |  50 | 2.2.0  | 
mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/2.2.0
122 | Active   |  50 | 2.3.6  | 

[jira] [Comment Edited] (CAMEL-7925) groovy and osgi - Could not initialize class script1413536396719697720774

2014-12-04 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234041#comment-14234041
 ] 

Charles Moulliard edited comment on CAMEL-7925 at 12/4/14 9:07 AM:
---

I have redeployed my project on Apache Karaf 3.0.2 using Apache Camel 2.14.0 
with Groovy 2.3.6 and another classloading issue is reported even if the class 
groovy.lang.Script is well packaged with the bundle Groovy Runtime 

Error 

{code}
Caused by: java.lang.ClassNotFoundException: groovy.lang.Script
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:655)
at 
groovy.lang.GroovyClassLoader$InnerLoader.loadClass(GroovyClassLoader.java:408)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:765)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:753)
... 31 more

1 error

at 
org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:309)[122:groovy-all:2.3.6]
at 
org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1067)[122:groovy-all:2.3.6]
at 
org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:583)[122:groovy-all:2.3.6]
at 
org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:561)[122:groovy-all:2.3.6]
at 
org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:538)[122:groovy-all:2.3.6]
at 
groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:286)[122:groovy-all:2.3.6]
at 
groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:259)[122:groovy-all:2.3.6]
at 
groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:245)[122:groovy-all:2.3.6]
at 
groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:203)[122:groovy-all:2.3.6]
at 
groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:213)[122:groovy-all:2.3.6]
at 
org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:65)[123:org.apache.camel.camel-groovy:2.14.0]
at 
org.apache.camel.language.groovy.GroovyExpression.evaluate(GroovyExpression.java:50)[123:org.apache.camel.camel-groovy:2.14.0]
at 
org.apache.camel.builder.ProcessorBuilder$4.process(ProcessorBuilder.java:103)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:398)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.Pipeline.process(Pipeline.java:118)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.Pipeline.process(Pipeline.java:80)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.component.timer.TimerConsumer.sendTimerExchange(TimerConsumer.java:157)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.component.timer.TimerConsumer$1.run(TimerConsumer.java:68)[92:org.apache.camel.camel-core:2.14.0]
at java.util.TimerThread.mainLoop(Timer.java:555)[:1.7.0_51]
at java.util.TimerThread.run(Timer.java:505)[:1.7.0_51]
{code}

What is deployed on Karaf 

{code}
 92 | Active   |  50 | 2.14.0 | mvn:org.apache.camel/camel-core/2.14.0
 93 | Active   |  50 | 2.14.0 | 
mvn:org.apache.camel.karaf/camel-karaf-commands/2.14.0
108 | Active   |  50 | 1.1.1  | 
mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/1.1.1
109 | Active   |  50 | 2.14.0 | mvn:org.apache.camel/camel-spring/2.14.0
110 | Active   |  50 | 2.14.0 | 
mvn:org.apache.camel/camel-blueprint/2.14.0
120 | Active   |  50 | 1.7.0.6| 
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.ant/1.7.0_6
121 | Active   |  50 | 2.2.0  | 
mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/2.2.0
122 | Active   |  50 | 2.3.6  | 

[jira] [Commented] (CAMEL-7925) groovy and osgi - Could not initialize class script1413536396719697720774

2014-12-04 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234051#comment-14234051
 ] 

Charles Moulliard commented on CAMEL-7925:
--

Example is available here 
:https://github.com/cmoulliard/use-cases/blob/master/camel-osgi-groovy/README.md

 groovy and osgi - Could not initialize class script1413536396719697720774
 -

 Key: CAMEL-7925
 URL: https://issues.apache.org/jira/browse/CAMEL-7925
 Project: Camel
  Issue Type: Bug
  Components: camel-groovy
 Environment: Apache Karaf 2.2.x
Reporter: Charles Moulliard
Priority: Minor

 When a camel route is deployed on apache Karaf using a groovy expression to 
 be evaluated we get this error 
 https://gist.github.com/cmoulliard/7294122c47e9c18df399
 Route
 {code}
   from(direct:launch).routeId(request-token)
   
   .onException(HttpOperationFailedException.class)
   .handled(true)
   .log(An error occurred)
   .to(direct:interface-status)
   .end()
   
   .setHeader(Exchange.HTTP_URI, constant(wayneUriGetSession))
   .setHeader(Exchange.HTTP_QUERY, constant(User= + UserName + 
  + Pass= + Password))
   .setHeader(Exchange.HTTP_METHOD, constant(GET))
   
   .to(https4://token-service)
   .convertBodyTo(String.class)
   .setHeader(token).groovy(body.replaceAll('\',''))
 {code}
 {code}
 Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
 script1413536396719697720774
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
 Method)[:1.7.0_51]
   at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)[:1.7.0_51]
   at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.7.0_51]
   at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)[:1.7.0_51]
   at java.lang.Class.newInstance(Class.java:374)[:1.7.0_51]
   at 
 org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)
 {code}



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


[jira] [Commented] (CAMEL-7925) groovy and osgi - Could not initialize class script1413536396719697720774

2014-12-04 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234098#comment-14234098
 ] 

Charles Moulliard commented on CAMEL-7925:
--

If I add dynamic-import package to the demo example, the classloading issue 
with groovy.lang.script is gone and I get a similar error :

{code}
2014-12-04 11:22:36,696 | WARN  | - timer://groovy | TimerConsumer  
  | 92 - org.apache.camel.camel-core - 2.14.0 | Error processing exchange. 
Exchange[Message: This is a message containing double quotes. Example -- 
Hello.]. Caused by: [java.lang.ClassCastException - 
script1417688554694697720774 cannot be cast to groovy.lang.Script]
java.lang.ClassCastException: script1417688554694697720774 cannot be cast to 
groovy.lang.Script
at 
org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)[123:org.apache.camel.camel-groovy:2.14.0]
at 
org.apache.camel.language.groovy.GroovyExpression.evaluate(GroovyExpression.java:50)[123:org.apache.camel.camel-groovy:2.14.0]
at 
org.apache.camel.builder.ProcessorBuilder$4.process(ProcessorBuilder.java:103)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:398)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.Pipeline.process(Pipeline.java:118)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.Pipeline.process(Pipeline.java:80)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.component.timer.TimerConsumer.sendTimerExchange(TimerConsumer.java:157)[92:org.apache.camel.camel-core:2.14.0]
at 
org.apache.camel.component.timer.TimerConsumer$1.run(TimerConsumer.java:68)[92:org.apache.camel.camel-core:2.14.0]
at java.util.TimerThread.mainLoop(Timer.java:555)[:1.7.0_51]
at java.util.TimerThread.run(Timer.java:505)[:1.7.0_51]
{code}

 groovy and osgi - Could not initialize class script1413536396719697720774
 -

 Key: CAMEL-7925
 URL: https://issues.apache.org/jira/browse/CAMEL-7925
 Project: Camel
  Issue Type: Bug
  Components: camel-groovy
 Environment: Apache Karaf 2.2.x
Reporter: Charles Moulliard
Priority: Minor

 When a camel route is deployed on apache Karaf using a groovy expression to 
 be evaluated we get this error 
 https://gist.github.com/cmoulliard/7294122c47e9c18df399
 Route
 {code}
   from(direct:launch).routeId(request-token)
   
   .onException(HttpOperationFailedException.class)
   .handled(true)
   .log(An error occurred)
   .to(direct:interface-status)
   .end()
   
   .setHeader(Exchange.HTTP_URI, constant(wayneUriGetSession))
   .setHeader(Exchange.HTTP_QUERY, constant(User= + UserName + 
  + Pass= + Password))
   .setHeader(Exchange.HTTP_METHOD, constant(GET))
   
   .to(https4://token-service)
   .convertBodyTo(String.class)
   .setHeader(token).groovy(body.replaceAll('\',''))
 {code}
 {code}
 Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
 script1413536396719697720774
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
 Method)[:1.7.0_51]
   at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)[:1.7.0_51]
   at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.7.0_51]
   at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)[:1.7.0_51]
   at java.lang.Class.newInstance(Class.java:374)[:1.7.0_51]
   at 
 org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)
 {code}



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


[jira] [Commented] (CAMEL-7925) groovy and osgi - Could not initialize class script1413536396719697720774

2014-12-04 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234100#comment-14234100
 ] 

Charles Moulliard commented on CAMEL-7925:
--

It seems that the problem reported is related to Felix issue - 
https://issues.apache.org/jira/browse/CAMEL-5493

 groovy and osgi - Could not initialize class script1413536396719697720774
 -

 Key: CAMEL-7925
 URL: https://issues.apache.org/jira/browse/CAMEL-7925
 Project: Camel
  Issue Type: Bug
  Components: camel-groovy
 Environment: Apache Karaf 2.2.x
Reporter: Charles Moulliard
Priority: Minor

 When a camel route is deployed on apache Karaf using a groovy expression to 
 be evaluated we get this error 
 https://gist.github.com/cmoulliard/7294122c47e9c18df399
 Route
 {code}
   from(direct:launch).routeId(request-token)
   
   .onException(HttpOperationFailedException.class)
   .handled(true)
   .log(An error occurred)
   .to(direct:interface-status)
   .end()
   
   .setHeader(Exchange.HTTP_URI, constant(wayneUriGetSession))
   .setHeader(Exchange.HTTP_QUERY, constant(User= + UserName + 
  + Pass= + Password))
   .setHeader(Exchange.HTTP_METHOD, constant(GET))
   
   .to(https4://token-service)
   .convertBodyTo(String.class)
   .setHeader(token).groovy(body.replaceAll('\',''))
 {code}
 {code}
 Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
 script1413536396719697720774
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
 Method)[:1.7.0_51]
   at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)[:1.7.0_51]
   at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.7.0_51]
   at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)[:1.7.0_51]
   at java.lang.Class.newInstance(Class.java:374)[:1.7.0_51]
   at 
 org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)
 {code}



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


[jira] [Commented] (CAMEL-7925) groovy and osgi - Could not initialize class script1413536396719697720774

2014-12-04 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234121#comment-14234121
 ] 

Charles Moulliard commented on CAMEL-7925:
--

Problem resolved using DynamicImport-Package*/DynamicImport-Package  
features camel-script, camel-script-groovy

 groovy and osgi - Could not initialize class script1413536396719697720774
 -

 Key: CAMEL-7925
 URL: https://issues.apache.org/jira/browse/CAMEL-7925
 Project: Camel
  Issue Type: Bug
  Components: camel-groovy
 Environment: Apache Karaf 2.2.x
Reporter: Charles Moulliard
Priority: Minor

 When a camel route is deployed on apache Karaf using a groovy expression to 
 be evaluated we get this error 
 https://gist.github.com/cmoulliard/7294122c47e9c18df399
 Route
 {code}
   from(direct:launch).routeId(request-token)
   
   .onException(HttpOperationFailedException.class)
   .handled(true)
   .log(An error occurred)
   .to(direct:interface-status)
   .end()
   
   .setHeader(Exchange.HTTP_URI, constant(wayneUriGetSession))
   .setHeader(Exchange.HTTP_QUERY, constant(User= + UserName + 
  + Pass= + Password))
   .setHeader(Exchange.HTTP_METHOD, constant(GET))
   
   .to(https4://token-service)
   .convertBodyTo(String.class)
   .setHeader(token).groovy(body.replaceAll('\',''))
 {code}
 {code}
 Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
 script1413536396719697720774
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
 Method)[:1.7.0_51]
   at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)[:1.7.0_51]
   at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.7.0_51]
   at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)[:1.7.0_51]
   at java.lang.Class.newInstance(Class.java:374)[:1.7.0_51]
   at 
 org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)
 {code}



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


[jira] [Resolved] (CAMEL-7925) groovy and osgi - Could not initialize class script1413536396719697720774

2014-12-04 Thread Charles Moulliard (JIRA)

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

Charles Moulliard resolved CAMEL-7925.
--
Resolution: Fixed

See last comment

 groovy and osgi - Could not initialize class script1413536396719697720774
 -

 Key: CAMEL-7925
 URL: https://issues.apache.org/jira/browse/CAMEL-7925
 Project: Camel
  Issue Type: Bug
  Components: camel-groovy
 Environment: Apache Karaf 2.2.x
Reporter: Charles Moulliard
Priority: Minor

 When a camel route is deployed on apache Karaf using a groovy expression to 
 be evaluated we get this error 
 https://gist.github.com/cmoulliard/7294122c47e9c18df399
 Route
 {code}
   from(direct:launch).routeId(request-token)
   
   .onException(HttpOperationFailedException.class)
   .handled(true)
   .log(An error occurred)
   .to(direct:interface-status)
   .end()
   
   .setHeader(Exchange.HTTP_URI, constant(wayneUriGetSession))
   .setHeader(Exchange.HTTP_QUERY, constant(User= + UserName + 
  + Pass= + Password))
   .setHeader(Exchange.HTTP_METHOD, constant(GET))
   
   .to(https4://token-service)
   .convertBodyTo(String.class)
   .setHeader(token).groovy(body.replaceAll('\',''))
 {code}
 {code}
 Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
 script1413536396719697720774
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
 Method)[:1.7.0_51]
   at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)[:1.7.0_51]
   at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.7.0_51]
   at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)[:1.7.0_51]
   at java.lang.Class.newInstance(Class.java:374)[:1.7.0_51]
   at 
 org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)
 {code}



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


[jira] [Assigned] (CAMEL-7925) groovy and osgi - Could not initialize class script1413536396719697720774

2014-12-04 Thread Charles Moulliard (JIRA)

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

Charles Moulliard reassigned CAMEL-7925:


Assignee: Charles Moulliard

 groovy and osgi - Could not initialize class script1413536396719697720774
 -

 Key: CAMEL-7925
 URL: https://issues.apache.org/jira/browse/CAMEL-7925
 Project: Camel
  Issue Type: Bug
  Components: camel-groovy
 Environment: Apache Karaf 2.2.x
Reporter: Charles Moulliard
Assignee: Charles Moulliard
Priority: Minor

 When a camel route is deployed on apache Karaf using a groovy expression to 
 be evaluated we get this error 
 https://gist.github.com/cmoulliard/7294122c47e9c18df399
 Route
 {code}
   from(direct:launch).routeId(request-token)
   
   .onException(HttpOperationFailedException.class)
   .handled(true)
   .log(An error occurred)
   .to(direct:interface-status)
   .end()
   
   .setHeader(Exchange.HTTP_URI, constant(wayneUriGetSession))
   .setHeader(Exchange.HTTP_QUERY, constant(User= + UserName + 
  + Pass= + Password))
   .setHeader(Exchange.HTTP_METHOD, constant(GET))
   
   .to(https4://token-service)
   .convertBodyTo(String.class)
   .setHeader(token).groovy(body.replaceAll('\',''))
 {code}
 {code}
 Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
 script1413536396719697720774
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
 Method)[:1.7.0_51]
   at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)[:1.7.0_51]
   at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.7.0_51]
   at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)[:1.7.0_51]
   at java.lang.Class.newInstance(Class.java:374)[:1.7.0_51]
   at 
 org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)
 {code}



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


[jira] [Commented] (CAMEL-8066) Add swagger ui to the camel swagger rest example

2014-11-24 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223202#comment-14223202
 ] 

Charles Moulliard commented on CAMEL-8066:
--

Project has been updated to avoid to include into the src/main/webapp all the 
swagger-ui resources.
3 plugins have been added to the project :
- Step 1. - Download Swagger UI project from GitHub
- Step 2. - Decompress content and move it to target/swagger-ui folder
- Step 3. - Copy Web Resources to target/classes but also to target/swagger-ui
- Step 4.  Add Swagger-ui Resources to the WAR

 Add swagger ui to the camel swagger rest example
 

 Key: CAMEL-8066
 URL: https://issues.apache.org/jira/browse/CAMEL-8066
 Project: Camel
  Issue Type: Improvement
  Components: examples
Affects Versions: 2.14.0
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.15.0


 The example camel-example-servlet-rest-tomcat uses the camel swagger 
 component to register the swagger servlet able to discover and generates json 
 files for the REST service.
 The goal of this improvement is to add the swagger-ui resources (html, css, 
 js, ...) to allow the user to discover the operations of the REST services 
 and play with them.



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


[jira] [Commented] (CAMEL-8066) Add swagger ui to the camel swagger rest example

2014-11-22 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221902#comment-14221902
 ] 

Charles Moulliard commented on CAMEL-8066:
--

I will have a look monday to include the JAR generated from swagger-ui github 
repository. This could be achieved with 2 maven plugin and some ant tasks to 
unzip the content into the webapp directory

 Add swagger ui to the camel swagger rest example
 

 Key: CAMEL-8066
 URL: https://issues.apache.org/jira/browse/CAMEL-8066
 Project: Camel
  Issue Type: Improvement
  Components: examples
Affects Versions: 2.14.0
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.15.0


 The example camel-example-servlet-rest-tomcat uses the camel swagger 
 component to register the swagger servlet able to discover and generates json 
 files for the REST service.
 The goal of this improvement is to add the swagger-ui resources (html, css, 
 js, ...) to allow the user to discover the operations of the REST services 
 and play with them.



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


[jira] [Assigned] (CAMEL-8066) Add swagger ui to the camel swagger rest example

2014-11-21 Thread Charles Moulliard (JIRA)

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

Charles Moulliard reassigned CAMEL-8066:


Assignee: Charles Moulliard

 Add swagger ui to the camel swagger rest example
 

 Key: CAMEL-8066
 URL: https://issues.apache.org/jira/browse/CAMEL-8066
 Project: Camel
  Issue Type: Improvement
  Components: examples
Affects Versions: 2.14.0
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.15.0


 The example camel-example-servlet-rest-tomcat uses the camel swagger 
 component to register the swagger servlet able to discover and generates json 
 files for the REST service.
 The goal of this improvement is to add the swagger-ui resources (html, css, 
 js, ...) to allow the user to discover the operations of the REST services 
 and play with them.



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


[jira] [Created] (CAMEL-8066) Add swagger ui to the camel swagger rest example

2014-11-21 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-8066:


 Summary: Add swagger ui to the camel swagger rest example
 Key: CAMEL-8066
 URL: https://issues.apache.org/jira/browse/CAMEL-8066
 Project: Camel
  Issue Type: Improvement
  Components: examples
Affects Versions: 2.14.0
Reporter: Charles Moulliard
 Fix For: 2.15.0


The example camel-example-servlet-rest-tomcat uses the camel swagger 
component to register the swagger servlet able to discover and generates json 
files for the REST service.

The goal of this improvement is to add the swagger-ui resources (html, css, js, 
...) to allow the user to discover the operations of the REST services and play 
with them.




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


[jira] [Resolved] (CAMEL-8066) Add swagger ui to the camel swagger rest example

2014-11-21 Thread Charles Moulliard (JIRA)

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

Charles Moulliard resolved CAMEL-8066.
--
Resolution: Fixed

 Add swagger ui to the camel swagger rest example
 

 Key: CAMEL-8066
 URL: https://issues.apache.org/jira/browse/CAMEL-8066
 Project: Camel
  Issue Type: Improvement
  Components: examples
Affects Versions: 2.14.0
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.15.0


 The example camel-example-servlet-rest-tomcat uses the camel swagger 
 component to register the swagger servlet able to discover and generates json 
 files for the REST service.
 The goal of this improvement is to add the swagger-ui resources (html, css, 
 js, ...) to allow the user to discover the operations of the REST services 
 and play with them.



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


[jira] [Commented] (CAMEL-7925) groovy and osgi - Could not initialize class script1413536396719697720774

2014-10-27 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14184908#comment-14184908
 ] 

Charles Moulliard commented on CAMEL-7925:
--

- Version of camel used : 2.12
- The version of Karaf does not affect this issue which is a classloading 
problem

 groovy and osgi - Could not initialize class script1413536396719697720774
 -

 Key: CAMEL-7925
 URL: https://issues.apache.org/jira/browse/CAMEL-7925
 Project: Camel
  Issue Type: Bug
  Components: camel-groovy
 Environment: Apache Karaf 2.2.x
Reporter: Charles Moulliard
Priority: Minor

 When a camel route is deployed on apache Karaf using a groovy expression to 
 be evaluated we get this error 
 https://gist.github.com/cmoulliard/7294122c47e9c18df399
 Route
 {code}
   from(direct:launch).routeId(request-token)
   
   .onException(HttpOperationFailedException.class)
   .handled(true)
   .log(An error occurred)
   .to(direct:interface-status)
   .end()
   
   .setHeader(Exchange.HTTP_URI, constant(wayneUriGetSession))
   .setHeader(Exchange.HTTP_QUERY, constant(User= + UserName + 
  + Pass= + Password))
   .setHeader(Exchange.HTTP_METHOD, constant(GET))
   
   .to(https4://token-service)
   .convertBodyTo(String.class)
   .setHeader(token).groovy(body.replaceAll('\',''))
 {code}
 {code}
 Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
 script1413536396719697720774
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
 Method)[:1.7.0_51]
   at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)[:1.7.0_51]
   at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.7.0_51]
   at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)[:1.7.0_51]
   at java.lang.Class.newInstance(Class.java:374)[:1.7.0_51]
   at 
 org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)
 {code}



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


[jira] [Created] (CAMEL-7942) Support Oauth, Ouath2 OpenID client to request token

2014-10-22 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-7942:


 Summary: Support Oauth, Ouath2  OpenID client to request token
 Key: CAMEL-7942
 URL: https://issues.apache.org/jira/browse/CAMEL-7942
 Project: Camel
  Issue Type: New Feature
Reporter: Charles Moulliard


Apache Camel does not provide any security layer to support OAuth, OAuth2 or 
OpenID specifications to obtain a token, refresh it and maintain the existing 
tokens in a cache. 

Such a security layer should be interesting for the camel-cxf, camel-jetty, 
camel-http, REST DSL components ... 

The Apache OLTU project (https://oltu.apache.org/) could be used to support 
OAuth, OAuth2 and OpenID4java (https://code.google.com/p/openid4java/)



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


[jira] [Updated] (CAMEL-7942) Support Oauth, Ouath2 OpenID client to request token

2014-10-22 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-7942:
-
Description: 
Apache Camel does not provide any security layer to support OAuth, OAuth2 or 
OpenID specifications to obtain a token, refresh it and maintain the existing 
tokens in a cache. 

Such a security layer should be interesting for the camel-cxf, camel-jetty, 
camel-http, REST DSL components ... 

The Apache OLTU project (https://oltu.apache.org/) could be used to support 
OAuth, OAuth2 and OpenID4java (https://code.google.com/p/openid4java/) for 
OpenID

  was:
Apache Camel does not provide any security layer to support OAuth, OAuth2 or 
OpenID specifications to obtain a token, refresh it and maintain the existing 
tokens in a cache. 

Such a security layer should be interesting for the camel-cxf, camel-jetty, 
camel-http, REST DSL components ... 

The Apache OLTU project (https://oltu.apache.org/) could be used to support 
OAuth, OAuth2 and OpenID4java (https://code.google.com/p/openid4java/)


 Support Oauth, Ouath2  OpenID client to request token
 --

 Key: CAMEL-7942
 URL: https://issues.apache.org/jira/browse/CAMEL-7942
 Project: Camel
  Issue Type: New Feature
Reporter: Charles Moulliard

 Apache Camel does not provide any security layer to support OAuth, OAuth2 or 
 OpenID specifications to obtain a token, refresh it and maintain the existing 
 tokens in a cache. 
 Such a security layer should be interesting for the camel-cxf, camel-jetty, 
 camel-http, REST DSL components ... 
 The Apache OLTU project (https://oltu.apache.org/) could be used to support 
 OAuth, OAuth2 and OpenID4java (https://code.google.com/p/openid4java/) for 
 OpenID



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


[jira] [Resolved] (CAMEL-7924) java.lang.ClassNotFoundException: org.codehaus.groovy.runtime.callsite.CallSiteArray

2014-10-20 Thread Charles Moulliard (JIRA)

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

Charles Moulliard resolved CAMEL-7924.
--
Resolution: Fixed

 java.lang.ClassNotFoundException: 
 org.codehaus.groovy.runtime.callsite.CallSiteArray
 

 Key: CAMEL-7924
 URL: https://issues.apache.org/jira/browse/CAMEL-7924
 Project: Camel
  Issue Type: Bug
  Components: camel-groovy
Affects Versions: 2.12.3, 2.13.2, 2.14.0
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.13.3, 2.14.1, 2.15.0


 When a camelRoute using the camel-groovy component is deployed on Karaf, we 
 get this class not found exception. Apparently, the class is not imported and 
 the package is not declared in the MANIFEST file of the component.
 {code}
 Caused by: java.lang.NoClassDefFoundError: 
 org/codehaus/groovy/runtime/callsite/CallSiteArray
   at 
 script1413531356181697720774.$createCallSiteArray(script1413531356181697720774.groovy)
   at 
 script1413531356181697720774.$getCallSiteArray(script1413531356181697720774.groovy)
   at 
 script1413531356181697720774.__$swapInit(script1413531356181697720774.groovy)
   at 
 script1413531356181697720774.clinit(script1413531356181697720774.groovy)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
 Method)[:1.7.0_51]
   at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)[:1.7.0_51]
   at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.7.0_51]
   at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)[:1.7.0_51]
   at java.lang.Class.newInstance(Class.java:374)[:1.7.0_51]
   at 
 org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)
   at 
 org.apache.camel.language.groovy.GroovyExpression.evaluate(GroovyExpression.java:50)
   at 
 org.apache.camel.builder.ProcessorBuilder$4.process(ProcessorBuilder.java:103)
   at 
 org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
   ... 89 more
 Caused by: java.lang.ClassNotFoundException: 
 org.codehaus.groovy.runtime.callsite.CallSiteArray
   at java.net.URLClassLoader$1.run(URLClassLoader.java:366)[:1.7.0_51]
   at java.net.URLClassLoader$1.run(URLClassLoader.java:355)[:1.7.0_51]
   at java.security.AccessController.doPrivileged(Native Method)[:1.7.0_51]
   at java.net.URLClassLoader.findClass(URLClassLoader.java:354)[:1.7.0_51]
   at java.lang.ClassLoader.loadClass(ClassLoader.java:425)[:1.7.0_51]
   at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:648)
   at 
 groovy.lang.GroovyClassLoader$InnerLoader.loadClass(GroovyClassLoader.java:401)
   at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:758)
   at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:746)
   ... 102 more
 {code}



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


[jira] [Created] (CAMEL-7924) java.lang.ClassNotFoundException: org.codehaus.groovy.runtime.callsite.CallSiteArray

2014-10-17 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-7924:


 Summary: java.lang.ClassNotFoundException: 
org.codehaus.groovy.runtime.callsite.CallSiteArray
 Key: CAMEL-7924
 URL: https://issues.apache.org/jira/browse/CAMEL-7924
 Project: Camel
  Issue Type: Bug
  Components: camel-groovy
Affects Versions: 2.14.0, 2.13.2, 2.12.3
Reporter: Charles Moulliard
 Fix For: 2.14.1


When a camelRoute using the camel-groovy component is deployed on Karaf, we get 
this class not found exception. Apparently, the class is not imported and the 
package is not declared in the MANIFEST file of the component.

{code}
Caused by: java.lang.NoClassDefFoundError: 
org/codehaus/groovy/runtime/callsite/CallSiteArray
at 
script1413531356181697720774.$createCallSiteArray(script1413531356181697720774.groovy)
at 
script1413531356181697720774.$getCallSiteArray(script1413531356181697720774.groovy)
at 
script1413531356181697720774.__$swapInit(script1413531356181697720774.groovy)
at 
script1413531356181697720774.clinit(script1413531356181697720774.groovy)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
Method)[:1.7.0_51]
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)[:1.7.0_51]
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.7.0_51]
at 
java.lang.reflect.Constructor.newInstance(Constructor.java:526)[:1.7.0_51]
at java.lang.Class.newInstance(Class.java:374)[:1.7.0_51]
at 
org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)
at 
org.apache.camel.language.groovy.GroovyExpression.evaluate(GroovyExpression.java:50)
at 
org.apache.camel.builder.ProcessorBuilder$4.process(ProcessorBuilder.java:103)
at 
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
... 89 more
Caused by: java.lang.ClassNotFoundException: 
org.codehaus.groovy.runtime.callsite.CallSiteArray
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)[:1.7.0_51]
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)[:1.7.0_51]
at java.security.AccessController.doPrivileged(Native Method)[:1.7.0_51]
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)[:1.7.0_51]
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)[:1.7.0_51]
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:648)
at 
groovy.lang.GroovyClassLoader$InnerLoader.loadClass(GroovyClassLoader.java:401)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:758)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:746)
... 102 more
{code}



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


[jira] [Assigned] (CAMEL-7924) java.lang.ClassNotFoundException: org.codehaus.groovy.runtime.callsite.CallSiteArray

2014-10-17 Thread Charles Moulliard (JIRA)

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

Charles Moulliard reassigned CAMEL-7924:


Assignee: Charles Moulliard

 java.lang.ClassNotFoundException: 
 org.codehaus.groovy.runtime.callsite.CallSiteArray
 

 Key: CAMEL-7924
 URL: https://issues.apache.org/jira/browse/CAMEL-7924
 Project: Camel
  Issue Type: Bug
  Components: camel-groovy
Affects Versions: 2.12.3, 2.13.2, 2.14.0
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.14.1


 When a camelRoute using the camel-groovy component is deployed on Karaf, we 
 get this class not found exception. Apparently, the class is not imported and 
 the package is not declared in the MANIFEST file of the component.
 {code}
 Caused by: java.lang.NoClassDefFoundError: 
 org/codehaus/groovy/runtime/callsite/CallSiteArray
   at 
 script1413531356181697720774.$createCallSiteArray(script1413531356181697720774.groovy)
   at 
 script1413531356181697720774.$getCallSiteArray(script1413531356181697720774.groovy)
   at 
 script1413531356181697720774.__$swapInit(script1413531356181697720774.groovy)
   at 
 script1413531356181697720774.clinit(script1413531356181697720774.groovy)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
 Method)[:1.7.0_51]
   at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)[:1.7.0_51]
   at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.7.0_51]
   at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)[:1.7.0_51]
   at java.lang.Class.newInstance(Class.java:374)[:1.7.0_51]
   at 
 org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)
   at 
 org.apache.camel.language.groovy.GroovyExpression.evaluate(GroovyExpression.java:50)
   at 
 org.apache.camel.builder.ProcessorBuilder$4.process(ProcessorBuilder.java:103)
   at 
 org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
   ... 89 more
 Caused by: java.lang.ClassNotFoundException: 
 org.codehaus.groovy.runtime.callsite.CallSiteArray
   at java.net.URLClassLoader$1.run(URLClassLoader.java:366)[:1.7.0_51]
   at java.net.URLClassLoader$1.run(URLClassLoader.java:355)[:1.7.0_51]
   at java.security.AccessController.doPrivileged(Native Method)[:1.7.0_51]
   at java.net.URLClassLoader.findClass(URLClassLoader.java:354)[:1.7.0_51]
   at java.lang.ClassLoader.loadClass(ClassLoader.java:425)[:1.7.0_51]
   at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:648)
   at 
 groovy.lang.GroovyClassLoader$InnerLoader.loadClass(GroovyClassLoader.java:401)
   at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:758)
   at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:746)
   ... 102 more
 {code}



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


[jira] [Updated] (CAMEL-7924) java.lang.ClassNotFoundException: org.codehaus.groovy.runtime.callsite.CallSiteArray

2014-10-17 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-7924:
-
Fix Version/s: 2.15.0
   2.13.3
   2.12.5

 java.lang.ClassNotFoundException: 
 org.codehaus.groovy.runtime.callsite.CallSiteArray
 

 Key: CAMEL-7924
 URL: https://issues.apache.org/jira/browse/CAMEL-7924
 Project: Camel
  Issue Type: Bug
  Components: camel-groovy
Affects Versions: 2.12.3, 2.13.2, 2.14.0
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.12.5, 2.13.3, 2.14.1, 2.15.0


 When a camelRoute using the camel-groovy component is deployed on Karaf, we 
 get this class not found exception. Apparently, the class is not imported and 
 the package is not declared in the MANIFEST file of the component.
 {code}
 Caused by: java.lang.NoClassDefFoundError: 
 org/codehaus/groovy/runtime/callsite/CallSiteArray
   at 
 script1413531356181697720774.$createCallSiteArray(script1413531356181697720774.groovy)
   at 
 script1413531356181697720774.$getCallSiteArray(script1413531356181697720774.groovy)
   at 
 script1413531356181697720774.__$swapInit(script1413531356181697720774.groovy)
   at 
 script1413531356181697720774.clinit(script1413531356181697720774.groovy)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
 Method)[:1.7.0_51]
   at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)[:1.7.0_51]
   at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.7.0_51]
   at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)[:1.7.0_51]
   at java.lang.Class.newInstance(Class.java:374)[:1.7.0_51]
   at 
 org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)
   at 
 org.apache.camel.language.groovy.GroovyExpression.evaluate(GroovyExpression.java:50)
   at 
 org.apache.camel.builder.ProcessorBuilder$4.process(ProcessorBuilder.java:103)
   at 
 org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
   ... 89 more
 Caused by: java.lang.ClassNotFoundException: 
 org.codehaus.groovy.runtime.callsite.CallSiteArray
   at java.net.URLClassLoader$1.run(URLClassLoader.java:366)[:1.7.0_51]
   at java.net.URLClassLoader$1.run(URLClassLoader.java:355)[:1.7.0_51]
   at java.security.AccessController.doPrivileged(Native Method)[:1.7.0_51]
   at java.net.URLClassLoader.findClass(URLClassLoader.java:354)[:1.7.0_51]
   at java.lang.ClassLoader.loadClass(ClassLoader.java:425)[:1.7.0_51]
   at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:648)
   at 
 groovy.lang.GroovyClassLoader$InnerLoader.loadClass(GroovyClassLoader.java:401)
   at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:758)
   at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:746)
   ... 102 more
 {code}



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


[jira] [Created] (CAMEL-7925) Could not initialize class script1413536396719697720774

2014-10-17 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-7925:


 Summary: Could not initialize class script1413536396719697720774
 Key: CAMEL-7925
 URL: https://issues.apache.org/jira/browse/CAMEL-7925
 Project: Camel
  Issue Type: Bug
  Components: el-groovy, camel-groovy
 Environment: Apache Karaf 2.2.x
Reporter: Charles Moulliard


When a camel route is deployed on apache Karaf using a groovy expression to be 
evaluated we get this error 

https://gist.github.com/cmoulliard/7294122c47e9c18df399

Route

{code}
from(direct:launch).routeId(request-token)

.onException(HttpOperationFailedException.class)
.handled(true)
.log(An error occurred)
.to(direct:interface-status)
.end()

.setHeader(Exchange.HTTP_URI, constant(wayneUriGetSession))
.setHeader(Exchange.HTTP_QUERY, constant(User= + UserName + 
 + Pass= + Password))
.setHeader(Exchange.HTTP_METHOD, constant(GET))

.to(https4://token-service)
.convertBodyTo(String.class)
.setHeader(token).groovy(body.replaceAll('\',''))
{code}

{code}
Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
script1413536396719697720774
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
Method)[:1.7.0_51]
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)[:1.7.0_51]
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.7.0_51]
at 
java.lang.reflect.Constructor.newInstance(Constructor.java:526)[:1.7.0_51]
at java.lang.Class.newInstance(Class.java:374)[:1.7.0_51]
at 
org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)
{code}




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


[jira] [Created] (CAMEL-7837) Support json2json data transformation

2014-09-19 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-7837:


 Summary: Support json2json data transformation
 Key: CAMEL-7837
 URL: https://issues.apache.org/jira/browse/CAMEL-7837
 Project: Camel
  Issue Type: New Feature
Affects Versions: 2.14.0
Reporter: Charles Moulliard


We should support json2json data transformation.
A good candidate project exists which is Apache Licensed 2 : 
- http://chunqishi.github.io/json2json/
- https://github.com/chunqishi/json2json



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


[jira] [Updated] (CAMEL-7754) Property Trigger.timerZone is declared as constant but not implemented

2014-09-01 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-7754:
-
Summary: Property Trigger.timerZone is declared as constant but not 
implemented  (was: Property Trigger.timerZone is declared as contant but not 
implemented)

 Property Trigger.timerZone is declared as constant but not implemented
 --

 Key: CAMEL-7754
 URL: https://issues.apache.org/jira/browse/CAMEL-7754
 Project: Camel
  Issue Type: Bug
  Components: camel-quartz, camel-quartz2
Affects Versions: 2.12.1, 2.13.2
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.14.0


 Seems that we have a problem with Quartz/Quartz2 components. The doc claims 
 that we can setup this property in the URI trigger.timeZone 
 (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz 
 don't use it even if a constant is defined 
 :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0
 We have the same issue too with quartz2 -- 
 https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0



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


[jira] [Updated] (CAMEL-7742) Support grouping separator for Camel Bindy (BigDecimal)

2014-09-01 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-7742:
-
Summary: Support grouping separator for Camel Bindy (BigDecimal)  (was: 
Support grouping separtor for Camel Bindy (BigDecimal))

 Support grouping separator for Camel Bindy (BigDecimal)
 ---

 Key: CAMEL-7742
 URL: https://issues.apache.org/jira/browse/CAMEL-7742
 Project: Camel
  Issue Type: Improvement
  Components: camel-bindy
Affects Versions: 2.13.2
Reporter: Charles Moulliard
Assignee: Charles Moulliard

 Issue 
 {code}
 I currently have a problem concerning Camel Bindy. I have a csv file that
 should be parsed with Camel Bindy using a given model class. This csv file
 contains a number that should be parsed as a BigDecimal. The problem is that
 this number contains a comma as a grouping separator and a point as the
 decimal separator.
 If I start the camel route the unmarshal process will throw a
 NumberFormatException mentioning the invalid format of that number. So I
 tried to add a pattern to the DataField annotation, but the error stays.
 After digging throw the documentation (http://camel.apache.org/bindy.html)
 and the source code of FormatFactory
 (http://grepcode.com/file_/repo1.maven.org/maven2/org.apache.camel/camel-bindy/2.13.1/org/apache/camel/dataformat/bindy/FormatFactory.java/?v=source)
 I'm a little bit confused, because the documentation mentions the ability to
 specify a grouping separator, but the source code shows that the pattern is
 ignored for BigDecimal data types.
 Does anyone know how to specify that grouping separator? Or is this not
 implemented yet?
 {code}
 Solution
 {code}
 public void parsePattern(String formattedString,
   Locale locale,
   String pattern,
   char groupingSeparator,
   char decimalSeparator) throws ParseException {
 DecimalFormatSymbols symbols = new DecimalFormatSymbols(locale);
 symbols.setGroupingSeparator(groupingSeparator);
 symbols.setDecimalSeparator(decimalSeparator);
 DecimalFormat decimalFormat = new DecimalFormat(pattern, symbols);
 decimalFormat.setParseBigDecimal(true);
 // parse the string
 BigDecimal bigDecimal = (BigDecimal) 
 decimalFormat.parse(formattedString);
 bigDecimal.setScale(precision);
 System.out.println(bigDecimal);
 }
 {code}



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


[jira] [Commented] (CAMEL-7754) Property Trigger.timerZone is declared as constant but not implemented

2014-09-01 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14117108#comment-14117108
 ] 

Charles Moulliard commented on CAMEL-7754:
--

There is a bug with Quartz Scheduler as the TIMEZONE which is well used by the 
calendar is not taken into consideration when the nextFiredTime is calculated 
by the CronExpression class

{code}
protected Date getTimeAfter(Date afterTime) {

// Computation is based on Gregorian year only.
Calendar cl = new java.util.GregorianCalendar(getTimeZone()); 

// move ahead one second, since we're computing the time *after* the
// given time
afterTime = new Date(afterTime.getTime() + 1000); // CALENDAR SYSTEM IS 
USED
{code}

See screenshots 

 Property Trigger.timerZone is declared as constant but not implemented
 --

 Key: CAMEL-7754
 URL: https://issues.apache.org/jira/browse/CAMEL-7754
 Project: Camel
  Issue Type: Bug
  Components: camel-quartz, camel-quartz2
Affects Versions: 2.12.1, 2.13.2
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.14.0


 Seems that we have a problem with Quartz/Quartz2 components. The doc claims 
 that we can setup this property in the URI trigger.timeZone 
 (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz 
 don't use it even if a constant is defined 
 :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0
 We have the same issue too with quartz2 -- 
 https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0



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


[jira] [Updated] (CAMEL-7754) Property Trigger.timerZone is declared as constant but not implemented

2014-09-01 Thread Charles Moulliard (JIRA)

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

Charles Moulliard updated CAMEL-7754:
-
Attachment: before.png
after.png

 Property Trigger.timerZone is declared as constant but not implemented
 --

 Key: CAMEL-7754
 URL: https://issues.apache.org/jira/browse/CAMEL-7754
 Project: Camel
  Issue Type: Bug
  Components: camel-quartz, camel-quartz2
Affects Versions: 2.12.1, 2.13.2
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.14.0

 Attachments: after.png, before.png


 Seems that we have a problem with Quartz/Quartz2 components. The doc claims 
 that we can setup this property in the URI trigger.timeZone 
 (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz 
 don't use it even if a constant is defined 
 :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0
 We have the same issue too with quartz2 -- 
 https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0



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


[jira] [Comment Edited] (CAMEL-7754) Property Trigger.timerZone is declared as constant but not implemented

2014-09-01 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14117108#comment-14117108
 ] 

Charles Moulliard edited comment on CAMEL-7754 at 9/1/14 7:24 AM:
--

There is a bug with Quartz Scheduler as the TIMEZONE which is well used by the 
calendar is not taken into consideration when the nextFiredTime is calculated 
by the CronExpression class

{code}
protected Date getTimeAfter(Date afterTime) {

// Computation is based on Gregorian year only.
Calendar cl = new java.util.GregorianCalendar(getTimeZone()); 

// move ahead one second, since we're computing the time *after* the
// given time
afterTime = new Date(afterTime.getTime() + 1000); // CALENDAR SYSTEM IS 
USED AS WE DON'T USE THE cl object
{code}

See screenshots 


was (Author: cmoulliard):
There is a bug with Quartz Scheduler as the TIMEZONE which is well used by the 
calendar is not taken into consideration when the nextFiredTime is calculated 
by the CronExpression class

{code}
protected Date getTimeAfter(Date afterTime) {

// Computation is based on Gregorian year only.
Calendar cl = new java.util.GregorianCalendar(getTimeZone()); 

// move ahead one second, since we're computing the time *after* the
// given time
afterTime = new Date(afterTime.getTime() + 1000); // CALENDAR SYSTEM IS 
USED
{code}

See screenshots 

 Property Trigger.timerZone is declared as constant but not implemented
 --

 Key: CAMEL-7754
 URL: https://issues.apache.org/jira/browse/CAMEL-7754
 Project: Camel
  Issue Type: Bug
  Components: camel-quartz, camel-quartz2
Affects Versions: 2.12.1, 2.13.2
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.14.0

 Attachments: after.png, before.png


 Seems that we have a problem with Quartz/Quartz2 components. The doc claims 
 that we can setup this property in the URI trigger.timeZone 
 (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz 
 don't use it even if a constant is defined 
 :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0
 We have the same issue too with quartz2 -- 
 https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0



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


[jira] [Created] (CAMEL-7754) Property Trigger.timerZone is declared as contant but not implemented

2014-08-27 Thread Charles Moulliard (JIRA)
Charles Moulliard created CAMEL-7754:


 Summary: Property Trigger.timerZone is declared as contant but not 
implemented
 Key: CAMEL-7754
 URL: https://issues.apache.org/jira/browse/CAMEL-7754
 Project: Camel
  Issue Type: Bug
  Components: camel-quartz, camel-quartz2
Affects Versions: 2.13.2, 2.12.1
Reporter: Charles Moulliard
 Fix For: 2.14.0


Seems that we have a problem with Quartz/Quartz2 components. The doc claims 
that we can setup this property in the URI trigger.timeZone 
(http://camel.apache.org/quartz.html - see specifying timezone ) but quartz 
don't use it even if a constant is defined 
:https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0

We have the same issue too with quartz2 -- 
https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CAMEL-7754) Property Trigger.timerZone is declared as contant but not implemented

2014-08-27 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112037#comment-14112037
 ] 

Charles Moulliard commented on CAMEL-7754:
--

Test case used

{code}
public class CamelQuartzTest extends CamelTestSupport {

@Test
public void testQuartzCronRoute() throws Exception {
MockEndpoint mock = getMockEndpoint(mock:result);
mock.expectedMinimumMessageCount(3);

assertMockEndpointsSatisfied();

JobDetail job = 
mock.getReceivedExchanges().get(0).getIn().getHeader(jobDetail, 
JobDetail.class);
assertNotNull(job);

assertEquals(cron, 
job.getJobDataMap().get(QuartzConstants.QUARTZ_TRIGGER_TYPE));
assertEquals(UTC, 
job.getJobDataMap().get(QuartzConstants.QUARTZ_TRIGGER_CRON_TIMEZONE)); // ERROR
assertEquals(0/2 * * * * ?trigger.timeZone=UTC, 
job.getJobDataMap().get(QuartzConstants.QUARTZ_TRIGGER_CRON_EXPRESSION));
}

@Override
protected RouteBuilder createRouteBuilder() {
return new RouteBuilder() {
public void configure() {

from(quartz2://myGroup/myTimerName?cron=0/2+*+*+*+*+?trigger.timeZone=UTC).to(mock:result);
}
};
}
}
{code}

 Property Trigger.timerZone is declared as contant but not implemented
 -

 Key: CAMEL-7754
 URL: https://issues.apache.org/jira/browse/CAMEL-7754
 Project: Camel
  Issue Type: Bug
  Components: camel-quartz, camel-quartz2
Affects Versions: 2.12.1, 2.13.2
Reporter: Charles Moulliard
 Fix For: 2.14.0


 Seems that we have a problem with Quartz/Quartz2 components. The doc claims 
 that we can setup this property in the URI trigger.timeZone 
 (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz 
 don't use it even if a constant is defined 
 :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0
 We have the same issue too with quartz2 -- 
 https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Assigned] (CAMEL-7754) Property Trigger.timerZone is declared as contant but not implemented

2014-08-27 Thread Charles Moulliard (JIRA)

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

Charles Moulliard reassigned CAMEL-7754:


Assignee: Charles Moulliard

 Property Trigger.timerZone is declared as contant but not implemented
 -

 Key: CAMEL-7754
 URL: https://issues.apache.org/jira/browse/CAMEL-7754
 Project: Camel
  Issue Type: Bug
  Components: camel-quartz, camel-quartz2
Affects Versions: 2.12.1, 2.13.2
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.14.0


 Seems that we have a problem with Quartz/Quartz2 components. The doc claims 
 that we can setup this property in the URI trigger.timeZone 
 (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz 
 don't use it even if a constant is defined 
 :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0
 We have the same issue too with quartz2 -- 
 https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CAMEL-7754) Property Trigger.timerZone is declared as contant but not implemented

2014-08-27 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112090#comment-14112090
 ] 

Charles Moulliard commented on CAMEL-7754:
--

For Quartz 1, we should improve the QuartzComponent class to add the 
CamelProperty QUARTZ_TRIGGER_CRON_TIMEZONE

{code}
// enrich job data map with trigger information
if (cron != null) {

answer.getJobDetail().getJobDataMap().put(QuartzConstants.QUARTZ_TRIGGER_TYPE, 
cron);

answer.getJobDetail().getJobDataMap().put(QuartzConstants.QUARTZ_TRIGGER_CRON_EXPRESSION,
 cron);
String timeZone = 
EndpointHelper.resloveStringParameter(getCamelContext(), 
(String)triggerParameters.get(timeZone), String.class);
if (timeZone != null) {

answer.getJobDetail().getJobDataMap().put(QuartzConstants.QUARTZ_TRIGGER_CRON_TIMEZONE,
 timeZone);
}
} 
{code}

 Property Trigger.timerZone is declared as contant but not implemented
 -

 Key: CAMEL-7754
 URL: https://issues.apache.org/jira/browse/CAMEL-7754
 Project: Camel
  Issue Type: Bug
  Components: camel-quartz, camel-quartz2
Affects Versions: 2.12.1, 2.13.2
Reporter: Charles Moulliard
 Fix For: 2.14.0


 Seems that we have a problem with Quartz/Quartz2 components. The doc claims 
 that we can setup this property in the URI trigger.timeZone 
 (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz 
 don't use it even if a constant is defined 
 :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0
 We have the same issue too with quartz2 -- 
 https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Work started] (CAMEL-7754) Property Trigger.timerZone is declared as contant but not implemented

2014-08-27 Thread Charles Moulliard (JIRA)

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

Work on CAMEL-7754 started by Charles Moulliard.

 Property Trigger.timerZone is declared as contant but not implemented
 -

 Key: CAMEL-7754
 URL: https://issues.apache.org/jira/browse/CAMEL-7754
 Project: Camel
  Issue Type: Bug
  Components: camel-quartz, camel-quartz2
Affects Versions: 2.12.1, 2.13.2
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.14.0


 Seems that we have a problem with Quartz/Quartz2 components. The doc claims 
 that we can setup this property in the URI trigger.timeZone 
 (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz 
 don't use it even if a constant is defined 
 :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0
 We have the same issue too with quartz2 -- 
 https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CAMEL-7754) Property Trigger.timerZone is declared as contant but not implemented

2014-08-27 Thread Charles Moulliard (JIRA)

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

Charles Moulliard resolved CAMEL-7754.
--

Resolution: Fixed

 Property Trigger.timerZone is declared as contant but not implemented
 -

 Key: CAMEL-7754
 URL: https://issues.apache.org/jira/browse/CAMEL-7754
 Project: Camel
  Issue Type: Bug
  Components: camel-quartz, camel-quartz2
Affects Versions: 2.12.1, 2.13.2
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.14.0


 Seems that we have a problem with Quartz/Quartz2 components. The doc claims 
 that we can setup this property in the URI trigger.timeZone 
 (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz 
 don't use it even if a constant is defined 
 :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0
 We have the same issue too with quartz2 -- 
 https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CAMEL-7754) Property Trigger.timerZone is declared as contant but not implemented

2014-08-27 Thread Charles Moulliard (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112116#comment-14112116
 ] 

Charles Moulliard commented on CAMEL-7754:
--

For Quartz2, the TimeZone property must be pass as parameter to the 
Trigger.newBuilder()

 Property Trigger.timerZone is declared as contant but not implemented
 -

 Key: CAMEL-7754
 URL: https://issues.apache.org/jira/browse/CAMEL-7754
 Project: Camel
  Issue Type: Bug
  Components: camel-quartz, camel-quartz2
Affects Versions: 2.12.1, 2.13.2
Reporter: Charles Moulliard
Assignee: Charles Moulliard
 Fix For: 2.14.0


 Seems that we have a problem with Quartz/Quartz2 components. The doc claims 
 that we can setup this property in the URI trigger.timeZone 
 (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz 
 don't use it even if a constant is defined 
 :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0
 We have the same issue too with quartz2 -- 
 https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Work started] (CAMEL-7742) Support grouping separtor for Camel Bindy (BigDecimal)

2014-08-26 Thread Charles Moulliard (JIRA)

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

Work on CAMEL-7742 started by Charles Moulliard.

 Support grouping separtor for Camel Bindy (BigDecimal)
 --

 Key: CAMEL-7742
 URL: https://issues.apache.org/jira/browse/CAMEL-7742
 Project: Camel
  Issue Type: Improvement
  Components: camel-bindy
Affects Versions: 2.13.2
Reporter: Charles Moulliard
Assignee: Charles Moulliard

 Issue 
 {code}
 I currently have a problem concerning Camel Bindy. I have a csv file that
 should be parsed with Camel Bindy using a given model class. This csv file
 contains a number that should be parsed as a BigDecimal. The problem is that
 this number contains a comma as a grouping separator and a point as the
 decimal separator.
 If I start the camel route the unmarshal process will throw a
 NumberFormatException mentioning the invalid format of that number. So I
 tried to add a pattern to the DataField annotation, but the error stays.
 After digging throw the documentation (http://camel.apache.org/bindy.html)
 and the source code of FormatFactory
 (http://grepcode.com/file_/repo1.maven.org/maven2/org.apache.camel/camel-bindy/2.13.1/org/apache/camel/dataformat/bindy/FormatFactory.java/?v=source)
 I'm a little bit confused, because the documentation mentions the ability to
 specify a grouping separator, but the source code shows that the pattern is
 ignored for BigDecimal data types.
 Does anyone know how to specify that grouping separator? Or is this not
 implemented yet?
 {code}
 Solution
 {code}
 public void parsePattern(String formattedString,
   Locale locale,
   String pattern,
   char groupingSeparator,
   char decimalSeparator) throws ParseException {
 DecimalFormatSymbols symbols = new DecimalFormatSymbols(locale);
 symbols.setGroupingSeparator(groupingSeparator);
 symbols.setDecimalSeparator(decimalSeparator);
 DecimalFormat decimalFormat = new DecimalFormat(pattern, symbols);
 decimalFormat.setParseBigDecimal(true);
 // parse the string
 BigDecimal bigDecimal = (BigDecimal) 
 decimalFormat.parse(formattedString);
 bigDecimal.setScale(precision);
 System.out.println(bigDecimal);
 }
 {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CAMEL-7742) Support grouping separtor for Camel Bindy (BigDecimal)

2014-08-26 Thread Charles Moulliard (JIRA)

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

Charles Moulliard resolved CAMEL-7742.
--

Resolution: Fixed

 Support grouping separtor for Camel Bindy (BigDecimal)
 --

 Key: CAMEL-7742
 URL: https://issues.apache.org/jira/browse/CAMEL-7742
 Project: Camel
  Issue Type: Improvement
  Components: camel-bindy
Affects Versions: 2.13.2
Reporter: Charles Moulliard
Assignee: Charles Moulliard

 Issue 
 {code}
 I currently have a problem concerning Camel Bindy. I have a csv file that
 should be parsed with Camel Bindy using a given model class. This csv file
 contains a number that should be parsed as a BigDecimal. The problem is that
 this number contains a comma as a grouping separator and a point as the
 decimal separator.
 If I start the camel route the unmarshal process will throw a
 NumberFormatException mentioning the invalid format of that number. So I
 tried to add a pattern to the DataField annotation, but the error stays.
 After digging throw the documentation (http://camel.apache.org/bindy.html)
 and the source code of FormatFactory
 (http://grepcode.com/file_/repo1.maven.org/maven2/org.apache.camel/camel-bindy/2.13.1/org/apache/camel/dataformat/bindy/FormatFactory.java/?v=source)
 I'm a little bit confused, because the documentation mentions the ability to
 specify a grouping separator, but the source code shows that the pattern is
 ignored for BigDecimal data types.
 Does anyone know how to specify that grouping separator? Or is this not
 implemented yet?
 {code}
 Solution
 {code}
 public void parsePattern(String formattedString,
   Locale locale,
   String pattern,
   char groupingSeparator,
   char decimalSeparator) throws ParseException {
 DecimalFormatSymbols symbols = new DecimalFormatSymbols(locale);
 symbols.setGroupingSeparator(groupingSeparator);
 symbols.setDecimalSeparator(decimalSeparator);
 DecimalFormat decimalFormat = new DecimalFormat(pattern, symbols);
 decimalFormat.setParseBigDecimal(true);
 // parse the string
 BigDecimal bigDecimal = (BigDecimal) 
 decimalFormat.parse(formattedString);
 bigDecimal.setScale(precision);
 System.out.println(bigDecimal);
 }
 {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)


  1   2   >