Hi, Marina, Tom and Sanjeeb.
The problem with generated weaved classes was my fault.
I didn't properly use the ant task (I used taskdef attribute classpath).
So now my testcase is working and there is no need to deploy weaved classes on server.
But I tried to deploy weaved classes using Admin Console and got the same exception.
Deployed jar contains PU classes and also EJB Session Bean.
So may be there is no real need to discover the problem of redeploying of weaved classes, but may be this can
concern some other issues.
Thank you.
Best regards, Alexey Kostylev.
> Tom, Alexey,
>
> Why does anybody need to deploy a statically weaved jar?
>
> Alexey,
> Are you deploying a jar with only PU classes or is it a Java EE module that
> contains a PU in addition to the Java EE components (like an EJB or a Web
> component)?
>
> thanks,
> -marina
>
> Tom Ware wrote:
>> Hi Alexey,
>>
>> I am moving this discussion to the persistence mailing list because I
>> think some of the other folks on the list are more likely than me to be
>> able to help with the packaging issue you are seeing. Are you
>> subscribed to that list?
>>
>> When I ran your original jar through the static weaver, I saw the same
>> problem you were seeing. With my changes, I got the attached jar. As
>> you can see it is different. When I decompile City.class, I can see
>> constructs TopLink Essentials has added for static weaving. I run the
>> static weaver as follows on my windows machine:
>>
>> --
>> set
>> classpath=.;C:\cvsworkspace\publish\glassfish\lib\toplink-essentials.jar;%classpath%
>>
>>
>> java oracle.toplink.essentials.weaving.StaticWeave -loglevel FINEST
>> Issue1081.jar Issue1081Weaved.jar
>> --
>>
>> If you with logging turned on (-loglevel FINEST) how much logging do
>> you get?
>>
>> To The Sun folks,
>>
>> Alexey is getting an exception in autodeployment with a jar generated by
>> our static weaver. The exception is below. Do you have any idea why
>> this might be happening.
>>
>> -Tom
>>
>>