openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Logemann ...@logemann.org>
Subject Re: strange JPA Enhance stack
Date Tue, 19 May 2009 22:14:24 GMT
Craig,

my intention was not  to rant against SERP :-)

I already filed a JIRA. I will report things there if i see something  
new during my tests...

---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de




Am 19.05.2009 um 21:57 schrieb Craig L Russell:

> Hi Marc,
>
> As Mike says, we could be a bit more friendly. By the way, SERP has  
> been very reliable so this hasn't been much of an issue to date.
>
> Could you please file a JIRA so we don't forget about it?
>
> Thanks,
>
> Craig
>
> On May 19, 2009, at 5:53 AM, Michael Dick wrote:
>
>> Hi Marc,
>>
>> Sounds like an unchecked exception thrown by Serp and we could be a  
>> bit
>> friendlier about how we handle it. At least dumping the classname  
>> that we're
>> trying to load would help. Adding a try / catch might be helpful.  
>> Which
>> version of OpenJPA are you using?
>>
>> My guess is that it is OpenJDK related and the compiled class is not
>> matching Serp's expectation. I haven't seen this exception before  
>> though and
>> I can't tell you why you're getting it.
>>
>> -mike
>>
>> On Tue, May 19, 2009 at 3:46 AM, Marc Logemann <li@logemann.org>  
>> wrote:
>>
>>> David,
>>>
>>> no, have not done this. Its quite a hughe effort to create a  
>>> project from
>>> scratch and deploy it to SCM and configure TeamCity to "compile/ 
>>> test" it. I
>>> still think its not a library issue because i use ivy within ANT  
>>> and the
>>> build system resolves libs the same way as its done on each  
>>> developer
>>> machine. The stack doesnt look like a missing lib to me. And its  
>>> definitely
>>> also not an ANT issue because i am using the same ANT Target on  
>>> the dev
>>> machines.
>>>
>>> I hoped somebody who developed the enhancer can tell something  
>>> about the
>>> stack. I mean something like "this problem can only occur under  
>>> this or that
>>> condition".
>>>
>>> In any way... do we agree that an IllegalArgumentException in SERP  
>>> shouldnt
>>> be the first Exception on the stack ? I definitely would expect an  
>>> Enhancer
>>> Exception saying whats wrong on an upper level. Something like  
>>> "Enhancement
>>> failed on Class X" or something. The root cause would be of course  
>>> the SERP
>>> exception.
>>>
>>> ---
>>> regards
>>> Marc Logemann
>>> http://www.logemann.org
>>> http://www.logentis.de
>>>
>>>
>>>
>>>
>>> Am 18.05.2009 um 16:29 schrieb Rick Curtis:
>>>
>>>
>>>
>>>> -Marc
>>>>
>>>> Any luck with the suggestion that David made?
>>>>
>>>>
>>>> David Beer-2 wrote:
>>>>
>>>>>
>>>>> On Sat, 16 May 2009 15:32:36 +0200
>>>>> Marc Logemann <li@logemann.org> wrote:
>>>>>
>>>>> Hi Marc
>>>>>
>>>>> Can't seem that it is OpenJDK 6 related as I use it here for  
>>>>> both my
>>>>> development and continous build system (hudson under tomcat).
>>>>>
>>>>> Are you using Ant or Maven with the build process. I have seen  
>>>>> on lists
>>>>> that this can sometimes be a problem. Can you create a small  
>>>>> project
>>>>> which has say just one class to enhance and see if that works  
>>>>> through
>>>>> you build system. I am thinking that it may be a classpath or  
>>>>> library
>>>>> problem.
>>>>>
>>>>> David
>>>>>
>>>>>
>>>>>
>>>> --
>>>> View this message in context:
>>>> http://n2.nabble.com/strange-JPA-Enhance-stack-tp2912505p2933425.html
>>>> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>>>>
>>>>
>>>
>
> Craig L Russell
> Architect, Sun Java Enterprise System http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>


Mime
View raw message