[
https://issues.apache.org/activemq/browse/CAMEL-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48099#action_48099
]
James Strachan commented on CAMEL-1184:
---------------------------------------
great work Ramon!
BTW the trickiest bit extending camel is the JAXB part for the XML version of
things; it always bites you in the ass! I had a few hours banging my head
against it. One thing that looks missing is when adding a class into
org.apache.camel.model.* it typically needs to be added to the corresponding
jaxb.index file in camel-core/src/main/resources. Also sometimes changing these
classes leads to schema gen build failures in camel-spring - I had them
yesterday!
This looks great!
> Add a new Dataformat - tidyMarkup - which allows us to unmarshal bad HTML to
> good (XML) Html.
> ---------------------------------------------------------------------------------------------
>
> Key: CAMEL-1184
> URL: https://issues.apache.org/activemq/browse/CAMEL-1184
> Project: Apache Camel
> Issue Type: New Feature
> Reporter: Ramon Buckland
> Assignee: Ramon Buckland
> Priority: Minor
> Fix For: 1.5.1, 2.0.0
>
> Attachments: tidyMarkup-sourcefiles.tgz
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Using TagSoup, a competent 'bad html' to good well formed (xml) Html, we can
> create a new dataformat such that ..
> from("direct:fromSomeHttpSite")
> .unmarshal().tidyMarkup()
> .setBody().xpath("//table/tr/td[1]")
> .to("direct:foo")
> we get to turn the nasty HTML into goody HTML which can go through XSLT
> components and be xpathed and all the goodness we love.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
