Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Date: Wed, 20 Feb 2013 23:03:12 +0000 (UTC)
From: "Romain Manni-Bucau (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Message-ID: <JIRA.12633266.1361390219936.313478.1361401392842@arcas>
In-Reply-To: <JIRA.12633266.1361390219936@arcas>
References: <JIRA.12633266.1361390219936@arcas>
Subject: [jira] [Commented] (OPENJPA-2337) ClassFileTransformer modifies
 bytecode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/OPENJPA-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582633#comment-13582633 ] 

Romain Manni-Bucau commented on OPENJPA-2337:
---------------------------------------------

i know but it is used, there no warning logged or anything letting think the classes are modified
                
> ClassFileTransformer modifies bytecode
> --------------------------------------
>
>                 Key: OPENJPA-2337
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2337
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: Enhance
>    Affects Versions: 2.2.0, 2.2.1
>            Reporter: Romain Manni-Bucau
>            Priority: Blocker
>
> When using the JPA ClassFileTransformer from a javaagent the expected workflow is to simply convert in memory original class byte[] to an enhanced byte[].
> However since the code is shared with ant task, mvn plugin and main() enhancer it also updates the file physically.
> That's a pain for load time weaving.
> Could it be skipped when using the ClassFileTransformer?
> sounds like a bug for me, wdyt?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira