Hello,
I've copied the e-mail over to the users mailing list if someone has
better idea or has similar issues.
We have made a few changes as to how the Camel started and stopped in
version 2.20, which in turn might make a difference in you case (I'm
not 100% sure on that). You can test your code with 2.20 snapshots
available from the Apache snapshots repository[1] .
That being said, I'm pretty sure that you could register the custom
type converter even after SpringCamelContext has been
initialized/started. For instance you could do something like:
@PostConstruct
public void setupCustomTypeConverter(CamelContext camelContext) {
camelContext.getTypeConverterRegistry().addTypeConverter(...);
}
Oh, and you can subscribe to the users mailing list the old school way
by sending an e-mail to: [email protected] (see [2]) we
switched off posting via Nabble as there was too much spam on there.
Also you can find us at IRC on freenode and via Gitter (a web based
chat), see [3].
zoran
[1] https://repository.apache.org/content/groups/snapshots/
[2] https://camel.apache.org/mailing-lists.html
[3] https://camel.apache.org/irc-room.html
On Wed, Oct 4, 2017 at 9:29 AM, <[email protected]> wrote:
> Hi,
>
> I can not post a new topic to the mailinglist.
>
> You helped me before with a problem with SpringBoot and Camel so I was
> wondering if you had time to help me again.
>
> We are using CamelAutoConfiguration to create the SpringCamelContext.
> In the code (line 229) afterPropertiesSet is called manually after the bean
> as been created (not by @PostConstruct).
>
> But sometimes the bean creation order change and our @Converter bean is
> created AFTER the CamelContext. Thus resulting in having a CamelContext
> without our Converter. (The converter being registered in afterPropertiesSet
> but applicationContext.getBeansOfType(TypeConverters.class) is empty since
> not created yet).
>
>
> Could you help me to find a solution for this ? I could disable
> CamelAutoConfiguration and make a copy of it calling afterPropertiesSet in
> @PostConstruct but I'm not sure if it is safe. There should be a reason why
> this have not been done.
>
> _____________________________________
> Sent from http://camel.465427.n5.nabble.com
>
--
Zoran Regvart
