[
https://issues.apache.org/jira/browse/GERONIMO-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shrey Banga updated GERONIMO-4197:
----------------------------------
Attachment: GEP_JAXB_1.patch
Apply GEP_JAXB_1.patch to gep trunk.
This includes minor changes to jaxb classes to support exposing through DWR. A
dependency to the jar will be added to PlanCreator. Later when JAXB classes are
moved to the geronimo trunk (as geronimo-jaxb_spec) this dependency can be
changed and a dependency added to GEP.
> Use JAXB+DWR to eliminate ConfigData overhead
> ---------------------------------------------
>
> Key: GERONIMO-4197
> URL: https://issues.apache.org/jira/browse/GERONIMO-4197
> Project: Geronimo
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: PlanCreator
> Affects Versions: 2.2
> Reporter: Shrey Banga
> Assignee: Shrey Banga
> Fix For: 2.2
>
> Attachments: GEP_JAXB_1.patch
>
>
> Presently PlanCreator uses a set of ConfigData classes which basically wrap
> around xmlbean classes to create the deployment plans. These classes are
> exposed to DWR through EARHelper. As a result, a lot of code needs to be
> written to transfer data between multiple formats, ie from JSON to Java
> objects to XML.
> The idea is to use DWR to expose JAXB classes directly so that the xml can be
> generated using calls directly from the javascript, eliminating the
> ConfigData and EARHelper classes. This will ease the process of generating
> deployment plans, like that used by GEP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
