You are viewing a plain text version of this content. The canonical link for it is here.
Posted to droids-dev@incubator.apache.org by "Mingfai Ma (JIRA)" <ji...@apache.org> on 2009/03/31 19:28:50 UTC
[jira] Updated: (DROIDS-44) Refactor Parse and ParseData
[ https://issues.apache.org/jira/browse/DROIDS-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mingfai Ma updated DROIDS-44:
-----------------------------
Attachment: DROIDS-44.patch
I attempt to make the change to get a feeling of how it looks like. Attached is a patch that do:
- Parse and ParseImpl
- changed ParseData getData to Object getData
- added getOutlinks()
- ParseImpl, changed to match Parse' new interface, and added a no argument constructor. when use as a JavaBean, it's better to have a no-argument constructor. e.g. if we use Spring to construct the ParseImpl, it's easier to set every attribute like JavaBean and not to use constructor. The attributes are not final anyway.
- renamed Parser.getParse() to Parser.parse() to better reflect the action
- changed other classes that are affected by the above changes.
> Refactor Parse and ParseData
> ----------------------------
>
> Key: DROIDS-44
> URL: https://issues.apache.org/jira/browse/DROIDS-44
> Project: Droids
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.01
> Reporter: Mingfai Ma
> Fix For: 0.01
>
> Attachments: DROIDS-44.patch
>
>
> this issue has been mentioned a couple of times in the mail list and another JIRA issue (DROIDS-11). It seems there is no actual issue for this, so i create one.
> issues:
> - reduce number of depth in the API
> - Parse should support holding custom data or a parsed DOM document or whatever parsing result other than outlinks
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.