Another option is to configure Eclipse when to wrap lines of XML files.
This is what we did...

Best,

Christian Müller
-----------------

Software Integration Specialist

Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html

https://www.linkedin.com/pub/christian-mueller/11/551/642


On Wed, May 29, 2013 at 10:41 AM, Cristiano Costantini <
cristiano.costant...@gmail.com> wrote:

> Hi,
> yes, I need to use 2.10.4 as it is the version of camel available in latest
> version of Servicemix.
>
> For now we will avoid manually to format it.
>
> I've added a junit test which open the routes and if the XML is formatted
> by someone on the team at least the build will fail so I keep under control
> the issue and we prevent to break the application.
>
> Thank you,
> Cristiano
>
>
>
>
>
>
> 2013/5/28 Babak Vahdat <babak.vah...@swissonline.ch>
>
> >
> >
> > Am 28.05.13 22:22 schrieb "Cristiano Costantini" unter
> > <cristiano.costant...@gmail.com>:
> >
> > >Hi All,
> > >
> > >if I have a new line in a Simple expression like the following
> > >
> > ><when>
> > ><simple>${header.myHeader} in
> > >'aLongValueOne,aLongValueTo,aLongValueThree,aLongValueFour'
> > ></simple>
> > ><to uri="bean:myBean" />
> > ></when>
> > >
> > >I get a
> > >org.apache.camel.language.simple.types.SimpleIllegalSyntaxException:
> > >Unexpected token at location...
> > >
> > >
> > >The route works fine if I write the expression without new lines to the
> > >left or the right of the 'in' operator:
> > ><simple>
> > >   ${header.myHeader} in
> > >'aLongValueOne,aLongValueTo,aLongValueThree,aLongValueFour'
> > ></simple>
> > >
> > >As I'm required to format XML in Eclipse, can you suggest me a way to
> make
> > >the simple language tolerate new lines ?
> >
> > Hi
> >
> > I assume you make use of a Camel version lower than 2.11.0 as since then
> > this issue has been fixed.
> >
> > Babak
> >
> > >
> > >thank you,
> > >Cristiano
> >
> >
> >
>

Reply via email to