Alan, my only thought was that adding the processor to the JPA Entity Bean seems odd to me (for some reason - I'm pretty new to JPA, but the beans I've used thus far have been very clean). It seems like there should be a way in Spring DSL to request that values in the header get passed to the constructor for the JPA bean, like:
<from uri="servlet:///hello"/> <camel:to uri="jpa:MsgOutEntityBean?name=$(in.name)&employeetype=$(in.employeetype)/> So, then camel would create the MsgOutEntityBean, set those variables and persist....automagically. :) Thanks though - looks like the processor is the answer. -- View this message in context: http://camel.465427.n5.nabble.com/Transform-header-values-into-jpa-bean-body-tp4841535p4841761.html Sent from the Camel - Users mailing list archive at Nabble.com.
