I got it to work without blueprint (in java). Blueprint wiring was a bit too complex for me. If anyone has a working example I will gladly add it to the docs.
Should we add those elements to the xsd? Cheers, Thomas. > Am 05.04.2016 um 16:36 schrieb Quinn Stevenson <qu...@pronoia-solutions.com>: > > I learned something new - I’ve never used the camel:dataFormats element > before. > > I normally do something like this > <bean id="my-data-format" > class="org.apache.camel.component.hl7.HL7DataFormat" > > <property name="validate" value="true" /> > <property name="parser" ref="my-parser" /> > </bean> > > You’d have to define “my-parser” as well, but I think this will work. > > > >> On Apr 5, 2016, at 12:03 AM, Walzer, Thomas <thomas.wal...@integratix.net> >> wrote: >> >> When I write the blueprint xml I have a reference to camel-blueprint.xsd in >> it. So that the tooling can check my xml against the xsd. >> >> --snip from camel-blueprint.xsd --- >> >> <xs:complexType name="hl7DataFormat"> >> <xs:complexContent> >> <xs:extension base="tns:dataFormat"> >> <xs:sequence/> >> <xs:attribute name="validate" type="xs:boolean"> >> <xs:annotation> >> <xs:documentation xml:lang="en">Whether to validate the HL7 >> message Is by default true.</xs:documentation> >> </xs:annotation> >> </xs:attribute> >> </xs:extension> >> </xs:complexContent> >> </xs:complexType> >> >> --end snip ---- >> >> From the docs it should be more like >> >> <xs:complexType name="hl7DataFormat"> >> <xs:complexContent> >> <xs:extension base="tns:dataFormat"> >> <xs:sequence/> >> <xs:attribute name="validate" type="xs:boolean"> >> <xs:annotation> >> <xs:documentation xml:lang="en">Whether to validate the HL7 >> message Is by default true.</xs:documentation> >> </xs:annotation> >> </xs:attribute> >> <xs:attribute name="hapiContext" type="xs:string"> >> <xs:annotation> >> <xs:documentation xml:lang="en">The hapiContext to >> use</xs:documentation> >> </xs:annotation> >> </xs:attribute> >> <xs:attribute name="parser" type="xs:string"> >> <xs:annotation> >> <xs:documentation xml:lang="en">The parser to >> use</xs:documentation> >> </xs:annotation> >> </xs:attribute> >> </xs:extension> >> </xs:complexContent> >> >> >> So for instance the following snippet in my blueprint >> <camel:dataFormats> >> <camel:hl7 validate="true" parser="hl7Parser"/> >> </camel:dataFormats> >> >> yields: >> >> cvc-complex-type.3.2.2: Attribute 'parser' is not allowed to appear in >> element 'camel:hl7'. >> >> This happens not only when validating the source but also when starting up, >> as the blueprint gets validated again. >> >> Cheers, Thomas. >> >> -----Ursprüngliche Nachricht----- >> Von: Quinn Stevenson [mailto:qu...@pronoia-solutions.com] >> Gesendet: Montag, 04. April 2016 17:17 >> An: users@camel.apache.org >> Betreff: Re: [Bug?] hl7dataformat hapicontext&parser not in >> camel-blueprint.xsd >> >> As far as I know, Blueprint uses reflection to set properties so there >> wouldn’t be any need for any changes in camel-blueprint when a >> component/dataformat gets new properties. >> >> What exactly is your issue? >> >>> On Apr 4, 2016, at 2:19 AM, Walzer, Thomas <thomas.wal...@integratix.net> >>> wrote: >>> >>> Hi, >>> >>> is it possible that >>> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd does not >>> contain the new properties hapiContext & parser? >>> Makes it hard to use the features from 2.14.1 in blueprint ;-) >>> >>> Jira? >>> >>> Cheers, Thomas. >> >
