[jboss-jira] [JBoss JIRA] (WFLY-4597) Remove classname Strings from XTS subsystem
Gytis Trikleris (JIRA)
issues at jboss.org
Wed May 6 11:15:49 EDT 2015
[ https://issues.jboss.org/browse/WFLY-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gytis Trikleris moved JBTM-1859 to WFLY-4597:
---------------------------------------------
Project: WildFly (was: JBoss Transaction Manager)
Key: WFLY-4597 (was: JBTM-1859)
Component/s: XTS
(was: XTS)
(was: Application Server Integration)
Fix Version/s: 10.0.0.Alpha1
(was: 6.later)
> Remove classname Strings from XTS subsystem
> -------------------------------------------
>
> Key: WFLY-4597
> URL: https://issues.jboss.org/browse/WFLY-4597
> Project: WildFly
> Issue Type: Task
> Components: XTS
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> Priority: Minor
> Fix For: 10.0.0.Alpha1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> THe XTS SubSystem has many classnames passed to Jandex as raw Strings. It would be better to use Class#getName as it is type-safe.
> When this code was written, this was not possible, due to the nature of the order in which class-loading was done and the fact that the code in question was executed very early in the server boot. I don't remember the specific details.
> However, something seems to have changed in WildFly, such that we can now use Class#getName on the classes we require. This issue it to replace all the classname Strings with Class#getName() and to also simplify the code under org.jboss.as.xts.jandex, as a lot of that verbose code was added to to cope with the limitation of not being able to use Class#getName().
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list