apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Munagala V. Ramanath (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXMALHAR-2083) Revert breaking changes to XmlParser in release 3.3
Date Tue, 10 May 2016 19:34:12 GMT

    [ https://issues.apache.org/jira/browse/APEXMALHAR-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278720#comment-15278720
] 

Munagala V. Ramanath commented on APEXMALHAR-2083:
--------------------------------------------------

There are several issues w.r.t. this operator:

1. Operator moved from 'contrib' to 'library' in 3.3; this is a breaking change since
   apps using it with 3.2 will not even compile with 3.3.
2. The 3.3 version now uses JAXB and causes an exception if Parser.clazz field
   is null.
3. Parser.clazz is transient and is initialized from the setup call of the output port.
   This will not work if the main operator class setup() expects this field to be
   defined since it is called before port setup(). Does it even belong here since it
   is unused ? Subclasses can define it if necessary.

While reverting, need to verify that the new code is not used or depended on elsewhere

> Revert breaking changes to XmlParser in release 3.3
> ---------------------------------------------------
>
>                 Key: APEXMALHAR-2083
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2083
>             Project: Apache Apex Malhar
>          Issue Type: Bug
>          Components: utilities
>    Affects Versions: 3.3.1
>            Reporter: Munagala V. Ramanath
>
> XmlParser was changed in 3.3 in a way that is not backwards compatible. We need to revert
this change in both 3.3 and 3.4.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message