[I am cc'ing to Malcolm, as he does not appear to be on cayenne-devel]
I suggest we continue this discussion on the mailing list, as this is
not an action item that would be appropriate to keep in JIRA.
Log4J -> commons-logging. I thought of that switch as long term plan
and we definitely need to investigate how most common containers
behave. I remember Cris also voiced some concerns over it. And the
longer we drag the foot on it, the higher the chance that that people
find solutions to the current bugs :-) In 1.2 (a) client stuff will
be Log4J-free and (b) we deprecated all public references to Log4J in
the API - this makes me happy for the time being... I don't know if
we have any reason to pursue the switch immediately.
JDOM: Yes, XML features depend on that. DVModeler dependency doesn't
bother me... not like the users don't have an option to run another
JVM on their *desktop*, besides I was thinking of splitting DVModeler
out of Cayenne into some extensions package after 1.2 - with Andriy
not supporting it and myself using different Swing methodologies,
keeping it in the core is no longer feasible.
Still... I like JDOM and in the past I voted for including it in
Cayenne. But now that I want to use XML features on the client, and
keep client library light at the same time, I wouldn't mind if we rid
of this dependency and stick with JDK. Kevin, how bad do you think
this is (even if it means that we copy/paste a *few* JDOM utility
classes to Cayenne utilities)? I am not pushing for this, just wanted
to get a feel...
Andrus
On Oct 7, 2005, at 12:47 AM, jira-norepl..bjectstyle.org wrote:
> Message:
>
> A new issue has been created in JIRA.
>
> ---------------------------------------------------------------------
> View the issue:
>
> http://objectstyle.org/jira/secure/ViewIssue.jspa?key=CAY-389
>
>
> Here is an overview of the issue:
> ---------------------------------------------------------------------
> Key: CAY-389
> Summary: WebSphere and Commons Logging
> Type: Task
>
> Status: Assigned
> Priority: Major
>
> Project: Cayenne
> Components:
> Cayenne Core Library
> Versions:
> AFTER 1.2
>
> Assignee: Andrus Adamchik
> Reporter: Malcolm Edgar
>
> Created: Fri, 7 Oct 2005 12:47 AM
> Updated: Fri, 7 Oct 2005 12:47 AM
> Environment: WebSphere 5-6
>
> Description:
> The 1.2 M6 release notes discuss the option of depreciating Log4J
> and moving to Apache Commons Logging.
>
> WebSphere apparently uses Commons Logging internally, and
> applications attempting to use this library as well frequently have
> problems. IBM has proivded work around notes for these issues but I
> am told they are non-trivial to implement.
>
> One friend who had worked on implementing these work arounds on
> WebSphere 6 installation gave up after a couple of days of effort.
> This guy was no idiot either. They reverted to using Log4J to avoid
> these issues.
>
> On a related issue WebSphere 6 also includes JDOM 0.7 beta in its
> classpath. I know the Cayenne core does not use the JDOM 1.0
> library, but people using the DVModeller on an IBM JRE installation
> may have issues.
>
> http://www.openlaszlo.org/pipermail/laszlo-user/2004-November/
> 000000.html
>
>
> ---------------------------------------------------------------------
> JIRA INFORMATION:
> This message is automatically generated by JIRA.
>
> If you think it was sent incorrectly contact one of the
> administrators:
> http://objectstyle.org/jira/secure/Administrators.jspa
>
> If you want more information on JIRA, or have a bug to report see:
> http://www.atlassian.com/software/jira
>
>
>
This archive was generated by hypermail 2.0.0 : Fri Oct 07 2005 - 11:14:32 EDT