commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Bourg (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BCEL-76) Add parent type processing for ClassPath class.
Date Thu, 24 Apr 2014 12:21:16 GMT

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

Emmanuel Bourg updated BCEL-76:
-------------------------------

          Description: 
We have developed an application that byte-code enhances classes using BCEL. The application
allows for users to pass additional classpath entries on top of the current system class path
settings. When we use the ClassPath instance to create a SyntheticRepository instance. We
are unable to include a parent type ClassPath. It is possible that some of the classes are
referenced by the system class path. While others are only contained within the passed classpath.
To get around this issue. We would have to prepend or append the setting of the java.class.path
properties. This can be troublesome since we do not know if the system classpath should be
prepended or appended. The other issue is that this can be used within a running application
and users might enhance classes not contained within the system class path before using them.
These classes can not be loaded by the system ClassLoader. If they are then the byte-code
enhanced class can not be used.

I have a fix that extends the ClassPath class to include the concept of a parent ClassPath.
The parent instance is used exactly like the parent concept for a class loader.

  was:
We have developed an application that byte-code enhances classes using BCEL. The
application allows for users to pass additional classpath entries on top of the
current system class path settings. When we use the ClassPath instance to create
a SyntheticRepository instance. We are unable to include a parent type
ClassPath. It is possible that some of the classes are referenced by the system
class path. While others are only contained within the passed classpath. To get
around this issue. We would have to prepend or append the setting of the
java.class.path properties. This can be troublesome since we do not know if the
system classpath should be prepended or appended. The other issue is that this
can be used within a running application and users might enhance classes not
contained within the system class path before using them. These classes can not
be loaded by the system ClassLoader. If they are then the byte-code enhanced
class can not be used.

I have a fix that extends the ClassPath class to include the concept of a parent
ClassPath. The parent instance is used exactly like the parent concept for a
class loader.

             Priority: Minor
          Environment:     (was: Operating System: All
Platform: All)
    Affects Version/s:     (was: unspecified)
        Fix Version/s: 6.0
             Priority:   (was: P5)
             Severity:   (was: enhancement)

> Add parent type processing for ClassPath class.
> -----------------------------------------------
>
>                 Key: BCEL-76
>                 URL: https://issues.apache.org/jira/browse/BCEL-76
>             Project: Commons BCEL
>          Issue Type: Improvement
>          Components: Main
>            Reporter: Claudio Corsi
>            Assignee: Apache Commons Developers
>            Priority: Minor
>             Fix For: 6.0
>
>         Attachments: patch.txt
>
>
> We have developed an application that byte-code enhances classes using BCEL. The application
allows for users to pass additional classpath entries on top of the current system class path
settings. When we use the ClassPath instance to create a SyntheticRepository instance. We
are unable to include a parent type ClassPath. It is possible that some of the classes are
referenced by the system class path. While others are only contained within the passed classpath.
To get around this issue. We would have to prepend or append the setting of the java.class.path
properties. This can be troublesome since we do not know if the system classpath should be
prepended or appended. The other issue is that this can be used within a running application
and users might enhance classes not contained within the system class path before using them.
These classes can not be loaded by the system ClassLoader. If they are then the byte-code
enhanced class can not be used.
> I have a fix that extends the ClassPath class to include the concept of a parent ClassPath.
The parent instance is used exactly like the parent concept for a class loader.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message