Re: [Bug?] hl7dataformat hapicontext&parser not in camel-blueprint.xsd

[Walzer, Thomas]

Quinn, 

Your blueprint works fine (the factory method should be named getContext but 
that was an easy one).
Spares me one additional CamelContext :-)

Cheers, Thomas.

-----Ursprüngliche Nachricht-----
Von: Quinn Stevenson [mailto:qu...@pronoia-solutions.com] 
Gesendet: Freitag, 08. April 2016 17:03
An: users@camel.apache.org
Betreff: Re: [Bug?] hl7dataformat hapicontext&parser not in camel-blueprint.xsd

Something like this should work

<bean id="hapi-context-factory" class="net.integratix.demo.HapiContextFactory" >
    <!-- Initialization properties here if needed --> </bean>

<bean id="hapi-context" class="ca.uhn.hl7v2.DefaultHapiContext"
      factory-ref="hapi-context-factory" factory-method="getContext"/>

<bean id="my-hl7-format" class=" org.apache.camel.component.hl7.HL7DataFormat" >
    <property name="parser">
        <bean class="ca.uhn.hl7v2.parser.GenericParser">
            <argument ref="hapi-context"/>
        </bean>
    </property>
</bean>
You probably noticed I cheated a little - I didn’t want to work through all the 
Blueprint stuff to initialize the HapiContext so I created a factory to do it 
for me :-) import ca.uhn.hl7v2.DefaultHapiContext; import 
ca.uhn.hl7v2.HapiContext; import ca.uhn.hl7v2.parser.ParserConfiguration;

public class HapiContextFactory {

    public HapiContext createContext() {
        HapiContext answer = new DefaultHapiContext();

        ParserConfiguration pc = answer.getParserConfiguration();

        pc.addForcedEncode("NK1-2-1");
        pc.addForcedEncode("NK1-2-2");
        pc.addForcedEncode("NK1-3-1");
        pc.addForcedEncode("NK1-4-1");
        pc.addForcedEncode("NK1-4-3");
        pc.addForcedEncode("NK1-4-5");
        pc.addForcedEncode("NK1-4-6");

        pc.addForcedEncode("PID-21-1");
        pc.addForcedEncode("PID-22-1");
        pc.addForcedEncode("PID-23-1");
        pc.addForcedEncode("PID-24-1");
        pc.addForcedEncode("PID-25-1");
        pc.addForcedEncode("PID-26-1");

        return answer;
    }
}
I didn’t run any of this, but it compiles/validates :-)

Hope that helps ...

> On Apr 8, 2016, at 7:50 AM, Walzer, Thomas <thomas.wal...@integratix.net> 
> wrote:
> 
> HapiContext hapiContext = new DefaultHapiContext();
>               
>               ParserConfiguration pc = hapiContext.getParserConfiguration();
>               
>               pc.addForcedEncode("NK1-2-1");
>               pc.addForcedEncode("NK1-2-2");
>               pc.addForcedEncode("NK1-3-1");
>               pc.addForcedEncode("NK1-4-1");
>               pc.addForcedEncode("NK1-4-3");
>               pc.addForcedEncode("NK1-4-5");
>               pc.addForcedEncode("NK1-4-6");
>               
>               pc.addForcedEncode("PID-21-1");
>               pc.addForcedEncode("PID-22-1");
>               pc.addForcedEncode("PID-23-1");
>               pc.addForcedEncode("PID-24-1");
>               pc.addForcedEncode("PID-25-1");
>               pc.addForcedEncode("PID-26-1");