You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2020/06/22 04:12:00 UTC

[jira] [Resolved] (CAMEL-15204) Need to fix terminology within JT400 component

     [ https://issues.apache.org/jira/browse/CAMEL-15204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-15204.
---------------------------------
    Fix Version/s: 3.5.0
       Resolution: Fixed

> Need to fix terminology within JT400 component
> ----------------------------------------------
>
>                 Key: CAMEL-15204
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15204
>             Project: Camel
>          Issue Type: Task
>          Components: camel-jt400
>            Reporter: Jesse Gorzinski
>            Priority: Trivial
>             Fix For: 3.5.0
>
>
>  
> The JT400 component references "AS/400" in several places. 
> IBM hasn't marketed AS/400 in 20 years. It has since been completely replaced by IBM i on Power Systems (a completely different hardware set) in 2008. IBM i supports AS/400 methodologies (such as program calls, data queues, etc), so that commonly causes confusion with branding and terminology. It doesn't help that IBM's connector module for Java still has "400" in the name (for compatibility purposes). 
>  
> Anyway, we should change the doc of the JT400 component to properly reflect what it can be used for. I intend to PR these changes on GitHub, so you can assign me. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)