Grokbase Groups Camel dev April 2010
FAQ
Preserve streaming behavior in camel-cxf PAYLOAD mode
-----------------------------------------------------

Key: CAMEL-2620
URL: https://issues.apache.org/activemq/browse/CAMEL-2620
Project: Apache Camel
Issue Type: Improvement
Components: camel-cxf
Reporter: William Tam
Assignee: William Tam
Fix For: 2.3.0


Dan Kulp pointed out in https://issues.apache.org/jira/browse/CXF-2753 that Camel should preserve the streaming behavior by setting message part type class to Source.class (so the payload object becomes a SAXSource that wraps around a XMLStreamReader). The camel-cxf component currently exposes to the user a List of DOM Elements as payload. Basically, streaming behavior stops there anyway. We probably should provide a parameter to configure the camel-cxf endpoint to opt out of DOM and get a SAXSource as payload and add a converter if the user needs to go from SAXSource to DOM.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Search Discussions

  • William Tam (JIRA) at May 6, 2010 at 6:15 pm
    [ https://issues.apache.org/activemq/browse/CAMEL-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    William Tam updated CAMEL-2620:
    -------------------------------

    Fix Version/s: (was: 2.3.0)
    2.4.0
    Preserve streaming behavior in camel-cxf PAYLOAD mode
    -----------------------------------------------------

    Key: CAMEL-2620
    URL: https://issues.apache.org/activemq/browse/CAMEL-2620
    Project: Apache Camel
    Issue Type: Improvement
    Components: camel-cxf
    Reporter: William Tam
    Assignee: William Tam
    Fix For: 2.4.0


    Dan Kulp pointed out in https://issues.apache.org/jira/browse/CXF-2753 that Camel should preserve the streaming behavior by setting message part type class to Source.class (so the payload object becomes a SAXSource that wraps around a XMLStreamReader). The camel-cxf component currently exposes to the user a List of DOM Elements as payload. Basically, streaming behavior stops there anyway. We probably should provide a parameter to configure the camel-cxf endpoint to opt out of DOM and get a SAXSource as payload and add a converter if the user needs to go from SAXSource to DOM.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Willem Jiang (JIRA) at Jun 22, 2010 at 8:07 am
    [ https://issues.apache.org/activemq/browse/CAMEL-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Willem Jiang reassigned CAMEL-2620:
    -----------------------------------

    Assignee: Willem Jiang (was: William Tam)
    Preserve streaming behavior in camel-cxf PAYLOAD mode
    -----------------------------------------------------

    Key: CAMEL-2620
    URL: https://issues.apache.org/activemq/browse/CAMEL-2620
    Project: Apache Camel
    Issue Type: Improvement
    Components: camel-cxf
    Reporter: William Tam
    Assignee: Willem Jiang
    Fix For: 2.4.0


    Dan Kulp pointed out in https://issues.apache.org/jira/browse/CXF-2753 that Camel should preserve the streaming behavior by setting message part type class to Source.class (so the payload object becomes a SAXSource that wraps around a XMLStreamReader). The camel-cxf component currently exposes to the user a List of DOM Elements as payload. Basically, streaming behavior stops there anyway. We probably should provide a parameter to configure the camel-cxf endpoint to opt out of DOM and get a SAXSource as payload and add a converter if the user needs to go from SAXSource to DOM.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Willem Jiang (JIRA) at Jun 30, 2010 at 8:51 am
    [ https://issues.apache.org/activemq/browse/CAMEL-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60357#action_60357 ]

    Willem Jiang commented on CAMEL-2620:
    -------------------------------------

    @William,
    If the user want's keep the pay load stream as possible as he want , he could use the Message DataFormat.
    It's a good idea to store the payload message as a SAXSource, as it's not easy to convert it back to DOM unless we know about the message part info.

    Maybe we can move this feature into future, to see if there are some real request about it.

    Preserve streaming behavior in camel-cxf PAYLOAD mode
    -----------------------------------------------------

    Key: CAMEL-2620
    URL: https://issues.apache.org/activemq/browse/CAMEL-2620
    Project: Apache Camel
    Issue Type: Improvement
    Components: camel-cxf
    Reporter: William Tam
    Assignee: Willem Jiang
    Fix For: 2.4.0


    Dan Kulp pointed out in https://issues.apache.org/jira/browse/CXF-2753 that Camel should preserve the streaming behavior by setting message part type class to Source.class (so the payload object becomes a SAXSource that wraps around a XMLStreamReader). The camel-cxf component currently exposes to the user a List of DOM Elements as payload. Basically, streaming behavior stops there anyway. We probably should provide a parameter to configure the camel-cxf endpoint to opt out of DOM and get a SAXSource as payload and add a converter if the user needs to go from SAXSource to DOM.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Willem Jiang (JIRA) at Jun 30, 2010 at 8:58 am
    [ https://issues.apache.org/activemq/browse/CAMEL-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60357#action_60357 ]

    Willem Jiang edited comment on CAMEL-2620 at 6/30/10 4:50 AM:
    --------------------------------------------------------------

    @William,
    If the user want to keep the pay load stream as possible as he want , he could use the Message DataFormat.
    It's not a good idea to store the payload message as a SAXSource, as it's not easy to convert it back to DOM unless we know about the message part info.

    Maybe we can move this feature into future, to see if there are some real request about it.


    was (Author: njiang):
    @William,
    If the user want's keep the pay load stream as possible as he want , he could use the Message DataFormat.
    It's a good idea to store the payload message as a SAXSource, as it's not easy to convert it back to DOM unless we know about the message part info.

    Maybe we can move this feature into future, to see if there are some real request about it.

    Preserve streaming behavior in camel-cxf PAYLOAD mode
    -----------------------------------------------------

    Key: CAMEL-2620
    URL: https://issues.apache.org/activemq/browse/CAMEL-2620
    Project: Apache Camel
    Issue Type: Improvement
    Components: camel-cxf
    Reporter: William Tam
    Assignee: Willem Jiang
    Fix For: 2.4.0


    Dan Kulp pointed out in https://issues.apache.org/jira/browse/CXF-2753 that Camel should preserve the streaming behavior by setting message part type class to Source.class (so the payload object becomes a SAXSource that wraps around a XMLStreamReader). The camel-cxf component currently exposes to the user a List of DOM Elements as payload. Basically, streaming behavior stops there anyway. We probably should provide a parameter to configure the camel-cxf endpoint to opt out of DOM and get a SAXSource as payload and add a converter if the user needs to go from SAXSource to DOM.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Willem Jiang (JIRA) at Jun 30, 2010 at 9:00 am
    [ https://issues.apache.org/activemq/browse/CAMEL-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Willem Jiang reassigned CAMEL-2620:
    -----------------------------------

    Assignee: (was: Willem Jiang)
    Preserve streaming behavior in camel-cxf PAYLOAD mode
    -----------------------------------------------------

    Key: CAMEL-2620
    URL: https://issues.apache.org/activemq/browse/CAMEL-2620
    Project: Apache Camel
    Issue Type: Improvement
    Components: camel-cxf
    Reporter: William Tam
    Fix For: Future


    Dan Kulp pointed out in https://issues.apache.org/jira/browse/CXF-2753 that Camel should preserve the streaming behavior by setting message part type class to Source.class (so the payload object becomes a SAXSource that wraps around a XMLStreamReader). The camel-cxf component currently exposes to the user a List of DOM Elements as payload. Basically, streaming behavior stops there anyway. We probably should provide a parameter to configure the camel-cxf endpoint to opt out of DOM and get a SAXSource as payload and add a converter if the user needs to go from SAXSource to DOM.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Willem Jiang (JIRA) at Jun 30, 2010 at 9:00 am
    [ https://issues.apache.org/activemq/browse/CAMEL-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Willem Jiang updated CAMEL-2620:
    --------------------------------

    Fix Version/s: Future
    (was: 2.4.0)
    Preserve streaming behavior in camel-cxf PAYLOAD mode
    -----------------------------------------------------

    Key: CAMEL-2620
    URL: https://issues.apache.org/activemq/browse/CAMEL-2620
    Project: Apache Camel
    Issue Type: Improvement
    Components: camel-cxf
    Reporter: William Tam
    Fix For: Future


    Dan Kulp pointed out in https://issues.apache.org/jira/browse/CXF-2753 that Camel should preserve the streaming behavior by setting message part type class to Source.class (so the payload object becomes a SAXSource that wraps around a XMLStreamReader). The camel-cxf component currently exposes to the user a List of DOM Elements as payload. Basically, streaming behavior stops there anyway. We probably should provide a parameter to configure the camel-cxf endpoint to opt out of DOM and get a SAXSource as payload and add a converter if the user needs to go from SAXSource to DOM.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupdev @
categoriescamel
postedApr 6, '10 at 7:17p
activeJun 30, '10 at 9:00a
posts7
users1
websitecamel.apache.org

1 user in discussion

Willem Jiang (JIRA): 7 posts

People

Translate

site design / logo © 2022 Grokbase