On Tue, May 8, 2012 at 3:26 PM, Daniel Kulp <dk...@apache.org> wrote: > On Tuesday, May 08, 2012 07:12:28 AM Daniel Kulp wrote: >> On Tuesday, May 08, 2012 09:24:43 AM Claus Ibsen wrote: >> > For the fix in XStreamDataFormat.java, i wonder if the hardcoded >> > namespace to @XmlType(name = "converterList", namespace = >> > "http://camel.apache.org/schema/spring";) >> > >> > would be an issue for Blueprint XML, as we have the schema as: >> > "http://camel.apache.org/schema/blueprint"; instead >> >> Hmm... Good point. I'll try moving them out from being nested classes >> and seeing if that helps. > > Actually, this turns out to be the correct thing. Internally, everything > is in the "spring" namespace. The package-info.java uses the spring > namespace and the XmlType namespaces need to match that. > > The blueprint namespace handler renames all the blueprint namespaces in the > blueprint DOM to the spring namespace prior to parsing so the parsing will > work. Kind of a hack, but works. >
Ah perfect. Yeah I thought that as well, but didn't realize how far the "hack" goes with the rename. But better raise a concern that none. The Camel Karaf commands which spit out the routes in XML, actually uses the spring namespace, also if the route is from Blueprint. But that is what the JAXB model namespaces was designed with in the first place, when it was created about 5 years ago. We could do a hack in the Karaf commands and spit out the namespace as blueprint if its a blueprint route. That would probably be nicer. > > -- > Daniel Kulp > dk...@apache.org - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com > -- Claus Ibsen ----------------- CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
