Skip to content
This repository has been archived by the owner on Jun 3, 2020. It is now read-only.

How to handle pruned technologies? #79

Open
scottmarlow opened this issue Apr 3, 2020 · 1 comment
Open

How to handle pruned technologies? #79

scottmarlow opened this issue Apr 3, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@scottmarlow
Copy link

What is the requirement around handling application bytecode that contains a pruned technology (e.g. javax.xml.rpc or javax.management.j2ee)?

If transformers ignores pruned classes being referenced, the application will likely not work on an EE 9 implementation (likely failing to deploy with a ClassNotFoundException.)

If transformers detect pruned classes being referenced and produce error or failures, then at least users will know that they need to remove the pruned classes from their application first.

In terms of application bytecode modification strategies, if anyone has one, please add a comment to this issue. For example, replacing javax.xml.rpc references to a different class that is added to the application that throws a RuntimeException, if the code that depends on javax.xml.rpc is reached. I'm not sure if this is possible or would help enough, but am just mentioning as a possible (not really thought out) idea.

@tbitonti
Copy link
Owner

tbitonti commented Apr 7, 2020

Most simply, we could add a 'disallowPackage' option, which could be looked for and produce transformation exceptions.

@tbitonti tbitonti changed the title How to handle pruned technlogies? How to handle pruned technologies? Apr 14, 2020
@tbitonti tbitonti added the enhancement New feature or request label Apr 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants