openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Woods <dwo...@apache.org>
Subject Re: Dynamic class enhancer and Java 5
Date Fri, 05 Jun 2009 18:49:16 GMT


Donald Woods wrote:
> 
> 
> Pinaki Poddar wrote:
>> Hi,
>>> and not the Enhancer.
>>   Yeah got that -- was too lazy to post a separate message :)
>>
>>   I had added Bean Validation API to get rid of compiler error I was 
>> seeing
>> earlier. And I have no provider (unless now there is some 'default 
>> provider'
>> within OpenJPA itself).
>>
>>   Just now removed the Bean Validation API library. Compiles alright. The
>> warning message still appears. 
> 
> OK, I'll take a look at that.
> 
>>
>>> Eclipse classpath setup correctly.
>> What is "correctly" in this case?
>>
> 
> Whatever mvn eclipse:eclipse generates, which should no longer include 
> the geronimo-validation api on the classpath for build, runtime or tests 
> (as it was removed as a dependency earlier this week.)
> 

Its still required as a build time depend on openjpa-persistence, but no 
where else right now (will get added into openjpa-integration soon...)

> 
>>
>> DWoods wrote:
>>>
>>>
>>> Pinaki Poddar wrote:
>>>> I am suddenly seeing a lot of these (on the trunk):
>>>> 31  WARN   [main] openjpa.Runtime - Could not create the optional
>>>> validation
>>>> provider. Reason returned: "No default ValidatorFactory"
>>>>
>>> This is related to the new Bean Validation support that we are still 
>>> adding and not the Enhancer.  This is the current warning message for 
>>> the scenario that you have a Bean Validation API on the classpath, 
>>> but no provider, which you should no longer be seeing with the latest 
>>> trunk source since Tuesday, if you're using maven or have your 
>>> Eclipse classpath setup correctly.
>>>
>>>
>>>> and few of these even when Domain classes are in the persistence.xml:
>>>> 31  INFO   [main] openjpa.Enhance - You have enabled runtime 
>>>> enhancement,
>>>> but have not specified the set of persistent classes.  OpenJPA must 
>>>> look
>>>> for
>>>> metadata for every loaded class, which might increase class load times
>>>> significantly.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Rick Curtis wrote:
>>>>> Milosz -
>>>>>
>>>>> The docs are correct that the enhancer is loaded when running only on
>>>>> Sun
>>>>> JDK 6. The message is logged incorrectly, but it shouldn't affect your
>>>>> code. I'll open a JIRA for the issue.
>>>>>
>>>>> -Rick
>>>>>
>>>>> MiƂosz Tylenda wrote:
>>>>>> Hi All!
>>>>>>
>>>>>> I have noticed that when I run a test against Sun JRE 5 or 6 with
a
>>>>>> -javaagent option, OpenJPA issues the following:
>>>>>>
>>>>>> INFO   [main] openjpa.Runtime - OpenJPA dynamically loaded the class
>>>>>> enhancer. Any classes that were not enhanced at build time will be
>>>>>> enhanced when the are loaded by the JVM.
>>>>>>
>>>>>> On the other hand, our manual suggests me this message should be

>>>>>> output
>>>>>> only with Sun JDK 6 and without -javaagent [1]. Is this behavior
>>>>>> correct?
>>>>>>
>>>>>> Cheers,
>>>>>> Milosz
>>>>>>
>>>>>> [1]
>>>>>> http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_pc_enhance_dynamic

>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>> -----
>>>> Pinaki Poddar                      http://ppoddar.blogspot.com/
>>>>                                       
>>>> http://www.linkedin.com/in/pinakipoddar
>>>> OpenJPA PMC Member/Committer
>>>> JPA Expert Group Member
>>>
>>
>>
>> -----
>> Pinaki Poddar                      http://ppoddar.blogspot.com/
>>                                       
>> http://www.linkedin.com/in/pinakipoddar
>> OpenJPA PMC Member/Committer
>> JPA Expert Group Member
> 

Mime
View raw message