While 3.0 is in early stages it is a good time to do the testing. The
entire thing works fine in my environment, but I don't have access to
WebSphere and many other servers. I'd love to hear if it breaks. (BTW
the POM is setup to be built against commons-logging v.1.1)
Andrus
On Aug 16, 2006, at 7:21 PM, Malcolm Edgar wrote:
> I don't know what the current state of play is with commons-logging
> but there have been a number of class loader issues related to this
> library, especially with WebSphere.
>
> I believe the latest commons logging release has attempted to address
> many of these problems:
>
> http://jakarta.apache.org/commons/logging/commons-logging-1.1/
> troubleshooting.html
>
> I think this is something that should be looked at carefully.
>
> regards Malcolm Edgar
>
> On 8/17/06, Andrus Adamchik <andru..bjectstyle.org> wrote:
>> Just checked in the code removing Log4J dependency. May need to do
>> more cleanup. I'd encourage everybody who can use 3.0 in their
>> environment to try it out and report any problems you may find.
>>
>> Leftovers (from my CAY-631 comment):
>>
>> 1. Use Java logging factory for the modeler; figure out how to
>> redirect it to the Modeler.log
>> 2. Document methods that could not be deprecated and were simply
>> removed:
>>
>> QueryLogger.set/getLoggingLevel
>> Configuration.isLoggingConfigured()
>> Configuration.configureLogging()
>> Configuration.configureCommonLogging()
>>
>> 3. Any reasonable substitute for cayenne-logging.properties?
>>
>>
>> Andrus
>>
>>
>> On Aug 16, 2006, at 3:41 PM, Andrus Adamchik wrote:
>>
>> > Any objections to kicking out Log4J and replacing it with commons-
>> > logging throughout the framework?
>> >
>> > Refactoring and deprecation in 1.2 cleaned the path for doing that.
>> > So I think we should do that now.
>> >
>> > Andrus
>> >
>>
>>
>
This archive was generated by hypermail 2.0.0 : Wed Aug 16 2006 - 21:28:40 EDT