Abstract: Methods to perform an operation comprising receiving a first subset of keystroke inputs, of a plurality of keystroke inputs, in a first text input area in a first window, determining that a second window has changed a system focus from the first window to the second window in the absence of an explicit user request to change the system focus, wherein the second window does not include a text input area, wherein a second subset of keystroke inputs of the plurality of keystroke inputs are not received by the first text input area subsequent to changing the system focus, configuring the second window to include a safe-capture area, and capturing the second subset of keystroke inputs in the safe-capture input area while the system focus remains on the second window.

Abstract: Methods to perform an operation comprising receiving a first subset of keystroke inputs, of a plurality of keystroke inputs, in a first text input area in a first window, determining that a second window has changed a system focus from the first window to the second window in the absence of an explicit user request to change the system focus, wherein the second window does not include a text input area, wherein a second subset of keystroke inputs of the plurality of keystroke inputs are not received by the first text input area subsequent to changing the system focus, configuring the second window to include a safe-capture area, and capturing the second subset of keystroke inputs in the safe-capture input area while the system focus remains on the second window.

Abstract: Systems, methods, and computer program products to perform an operation comprising receiving a first subset of keystroke inputs, of a plurality of keystroke inputs, in a first text input area in a first window, determining that a second window has changed a system focus from the first window to the second window in the absence of an explicit user request to change the system focus, wherein the second window does not include a text input area, wherein a second subset of keystroke inputs of the plurality of keystroke inputs are not received by the first text input area subsequent to changing the system focus, configuring the second window to include a safe-capture area, and capturing the second subset of keystroke inputs in the safe-capture input area while the system focus remains on the second window.

Abstract: Arrangements described herein relate to managing versions of artifacts stored across disparate tools. In a multi-dimensional configuration space, dimensions can be defined. The dimensions can represent respective variations of respective versions of a plurality of artifacts for at least a first configuration of a system. Via the dimensions, versions of the plurality of artifacts can be mapped to at least a corresponding first configuration of the system, the mapped versions of the plurality of artifacts corresponding to the versions of the artifacts used in the first configuration. The first configuration can be identified by a point in the multi-dimensional configuration space defined by the respective dimensions. At least a first of the plurality of artifacts can be stored by a first tool, and at least a second of the plurality of artifacts can be stored by a second tool disparate from the first tool.

Abstract: Arrangements described herein relate to managing versions of artifacts stored across disparate tools. In a multi-dimensional configuration space, dimensions can be defined. The dimensions can represent respective variations of respective versions of a plurality of artifacts for at least a first configuration of a system. Via the dimensions, versions of the plurality of artifacts can be mapped to at least a corresponding first configuration of the system, the mapped versions of the plurality of artifacts corresponding to the versions of the artifacts used in the first configuration. The first configuration can be identified by a point in the multi-dimensional configuration space defined by the respective dimensions. At least a first of the plurality of artifacts can be stored by a first tool, and at least a second of the plurality of artifacts can be stored by a second tool disparate from the first tool.

Abstract: Arrangements described herein relate to managing versions of artifacts stored across disparate tools. In a multi-dimensional configuration space, dimensions can be defined. The dimensions can represent respective variations of respective versions of a plurality of artifacts for at least a first configuration of a system. Via the dimensions, versions of the plurality of artifacts can be mapped to at least a corresponding first configuration of the system, the mapped versions of the plurality of artifacts corresponding to the versions of the artifacts used in the first configuration. The first configuration can be identified by a point in the multi-dimensional configuration space defined by the respective dimensions. At least a first of the plurality of artifacts can be stored by a first tool, and at least a second of the plurality of artifacts can be stored by a second tool disparate from the first tool.

Abstract: Arrangements described herein relate to managing versions of artifacts stored across disparate tools. In a multi-dimensional configuration space, dimensions can be defined. The dimensions can represent respective variations of respective versions of a plurality of artifacts for at least a first configuration of a system. Via the dimensions, versions of the plurality of artifacts can be mapped to at least a corresponding first configuration of the system, the mapped versions of the plurality of artifacts corresponding to the versions of the artifacts used in the first configuration. The first configuration can be identified by a point in the multi-dimensional configuration space defined by the respective dimensions. At least a first of the plurality of artifacts can be stored by a first tool, and at least a second of the plurality of artifacts can be stored by a second tool disparate from the first tool.

Abstract: A system and method for legacy system component incremental migration from a legacy system to a new system comprises a read-only ghost or shadow in the new system. When changes are made in the legacy system, the changes are incrementally and automatically migrated to the new system allowing the legacy system and the new system to maintain availability during the migration. The concept of “mastership” is used where a component exists in the “New System”, but is actually mastered in the “Legacy System”. By allowing a sub-component to exist as a read-only ghost or shadow in the new system, and still be mastered/edited in the legacy system, a one-way bridge is provided so that the two systems can interact. The synchronization of the legacy system component is managed so that the ghost component is automatically updated when changes are made to the legacy system component and there is little maintenance that the user needs to do to create the bridge between the two systems.

Abstract: A system and method for legacy system component incremental migration from a legacy system to a new system comprises a read-only ghost or shadow in the new system. When changes are made in the legacy system, the changes are incrementally and automatically migrated to the new system allowing the legacy system and the new system to maintain availability during the migration. The concept of “mastership” is used where a component exists in the “New System”, but is actually mastered in the “Legacy System”. By allowing a sub-component to exist as a read-only ghost or shadow in the new system, and still be mastered/edited in the legacy system, a one-way bridge is provided so that the two systems can interact. The synchronization of the legacy system component is managed so that the ghost component is automatically updated when changes are made to the legacy system component and there is little maintenance that the user needs to do to create the bridge between the two systems.

Abstract: A way to define an access control that scales to component architectures. Specifically, the present invention allows annotations to be added to objects, for example in the javadoc section of a Java object, to restrict access to that object. Each annotation comprises a tag that specifies a designated privilege and one or more designees to which the privilege applies. The annotations may designate access options such as which packages, classes, interfaces, fields and/or operations may be visible to another package, class, interface, field and/or operation; which classes are allowed to implement a particular interface; which classes are allowed to instantiate a particular class; and/or which classes/interfaces are allowed to extend a particular class/interface. The annotation may refer to allowed objects directly, may refer to a group of classes having similar names, and/or may use an alias, which refers to an external object designation.