You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by carlo cancellieri <ge...@gmail.com> on 2014/05/23 13:02:07 UTC
Why tokenize (and some others) does not support properties substitution?
Hi,
I'm trying to use the properties substitution in my tokenizer with no
success.
I've also just seen that the camel-spring.xsd definition does not declare:
<xs:anyAttribute namespace="##other" processContents="skip"/>
In many complex types, so spring is not able to use the defined 'prop'
namespace as prefix for the tokenizer and csv parser.
This is my route and I'd like the substitute the 'csv.row.delimiter',
'csv.row.group' (in the tokenizer) and csv.row.delimiter (in the csv)
<route>
<!-- ACTUALLY READ THE CSV stream -->
<from uri="seda:splitting" />
<split parallelProcessing="false" stopOnException="false"
streaming="true">
<tokenize prop:token="csv.row.delimiter" prop:group="csv.row.group" />
<unmarshal>
<csv autogenColumns="true" prop:delimiter="csv.row.delimiter"
skipFirstLine="false" useMaps="true" configRef="csvConfig"
lazyLoad="false" />
</unmarshal>
<to uri="seda:processing" />
</split>
</route>
Is there a concrete need for this situation? If ther's not, you'll consider
to merge a contribution patch on this?
Cheers,
Carlo
--
Dott. Carlo Cancellieri
*skype*: ccancellieri
*Twitter*: @cancellieric
*LinkedIn*: http://it.linkedin.com/in/ccancellieri/
Re: Why tokenize (and some others) does not support properties substitution?
Posted by carlo cancellieri <c....@proximainformatica.com>.
Hi,
Apologize, I've just fwdd to the User list.
I posted here since my intention was to start a discussion with the dev
team since essentially this may not be an usage question.
It could be a possible improvement on the properties substitution.
Cheers,
Carlo
2014-05-23 13:11 GMT+02:00 Claus Ibsen <cl...@gmail.com>:
> Hi
>
> Use the @user mailing list for your Camel questions please
>
> On Fri, May 23, 2014 at 1:02 PM, carlo cancellieri
> <ge...@gmail.com> wrote:
> > Hi,
> > I'm trying to use the properties substitution in my tokenizer with no
> > success.
> > I've also just seen that the camel-spring.xsd definition does not
> declare:
> >
> > <xs:anyAttribute namespace="##other" processContents="skip"/>
> >
> > In many complex types, so spring is not able to use the defined 'prop'
> > namespace as prefix for the tokenizer and csv parser.
> >
> > This is my route and I'd like the substitute the 'csv.row.delimiter',
> > 'csv.row.group' (in the tokenizer) and csv.row.delimiter (in the csv)
> >
> > <route>
> > <!-- ACTUALLY READ THE CSV stream -->
> > <from uri="seda:splitting" />
> > <split parallelProcessing="false" stopOnException="false"
> > streaming="true">
> > <tokenize prop:token="csv.row.delimiter" prop:group="csv.row.group" />
> > <unmarshal>
> > <csv autogenColumns="true" prop:delimiter="csv.row.delimiter"
> > skipFirstLine="false" useMaps="true" configRef="csvConfig"
> > lazyLoad="false" />
> > </unmarshal>
> >
> > <to uri="seda:processing" />
> > </split>
> > </route>
> >
> > Is there a concrete need for this situation? If ther's not, you'll
> consider
> > to merge a contribution patch on this?
> >
> > Cheers,
> > Carlo
> >
> > --
> > Dott. Carlo Cancellieri
> > *skype*: ccancellieri
> > *Twitter*: @cancellieric
> > *LinkedIn*: http://it.linkedin.com/in/ccancellieri/
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cibsen@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
> hawtio: http://hawt.io/
> fabric8: http://fabric8.io/
>
--
Dott. Carlo Cancellieri
*skype*: ccancellieri
*Twitter*: @cancellieric
*LinkedIn*: http://it.linkedin.com/in/ccancellieri/
Re: Why tokenize (and some others) does not support properties substitution?
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Use the @user mailing list for your Camel questions please
On Fri, May 23, 2014 at 1:02 PM, carlo cancellieri
<ge...@gmail.com> wrote:
> Hi,
> I'm trying to use the properties substitution in my tokenizer with no
> success.
> I've also just seen that the camel-spring.xsd definition does not declare:
>
> <xs:anyAttribute namespace="##other" processContents="skip"/>
>
> In many complex types, so spring is not able to use the defined 'prop'
> namespace as prefix for the tokenizer and csv parser.
>
> This is my route and I'd like the substitute the 'csv.row.delimiter',
> 'csv.row.group' (in the tokenizer) and csv.row.delimiter (in the csv)
>
> <route>
> <!-- ACTUALLY READ THE CSV stream -->
> <from uri="seda:splitting" />
> <split parallelProcessing="false" stopOnException="false"
> streaming="true">
> <tokenize prop:token="csv.row.delimiter" prop:group="csv.row.group" />
> <unmarshal>
> <csv autogenColumns="true" prop:delimiter="csv.row.delimiter"
> skipFirstLine="false" useMaps="true" configRef="csvConfig"
> lazyLoad="false" />
> </unmarshal>
>
> <to uri="seda:processing" />
> </split>
> </route>
>
> Is there a concrete need for this situation? If ther's not, you'll consider
> to merge a contribution patch on this?
>
> Cheers,
> Carlo
>
> --
> Dott. Carlo Cancellieri
> *skype*: ccancellieri
> *Twitter*: @cancellieric
> *LinkedIn*: http://it.linkedin.com/in/ccancellieri/
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/