Hello Aki,
Thanks for your reply.
I understand from your explanation that this limitation might stay for some
time.
To avoid disabling Blueprint XSD validation entirely, I patched the
Blueprint core XSD to allow "id" attributes starting with "*.". This is of
course not an elegant solution, but it is less ugly to relax validation for
a single attribute than for the entire XML.
Regards,
metatech
---
blueprint-core/src/main/resources/org/apache/aries/blueprint/blueprint.xsd
2015-08-27 10:38:55.329361900 +0200
+++
blueprint-core/src/main/resources/org/apache/aries/blueprint/blueprint.xsd
2015-08-27 10:43:14.818203800 +0200
@@ -41,6 +41,13 @@
+ <xsd:simpleType name="IDwithWildcard" id="IDwithWildcard">
+ <xsd:restriction base="xsd:string">
+ <xsd:pattern value="([*][.])?[\i-[:]][\c-[:]]*"
id="IDwithWildcard.pattern">
+ </xsd:pattern>
+ </xsd:restriction>
+ </xsd:simpleType>
+
<xsd:complexType name="Tcomponent" abstract="true">
<xsd:annotation>
<xsd:documentation>
@@ -56,7 +63,7 @@
</xsd:documentation>
</xsd:annotation>
- <xsd:attribute name="id" type="xsd:ID" />
+ <xsd:attribute name="id" type="IDwithWildcard" />
<xsd:attribute name="activation" type="Tactivation">
<xsd:annotation>
Aki Yoshida-3 wrote
> I think I suggested
> adding another option of only disabling the primitive-type check some
> years ago at the aries mailing list.
>
> http://mail-archives.apache.org/mod_mbox/aries-user/201212.mbox/%
> [email protected]
> %3E
>
> but I think there is no such option and I also didn't pursue this issue.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-Transport-works-within-Blueprint-only-when-XSD-validation-is-disabled-tp5770593p5771007.html
Sent from the Camel - Users mailing list archive at Nabble.com.
