[jira] Commented: (JELLY-85) TagScript doesn't clear its cached tags after run()

[ http://nagoya.apache.org/jira/browse/JELLY-85?page=comments#action_56756 ] dion gillard commented on JELLY-85: --- Hans and Paul, 'The attached pair of scripts seems to constantly raise the exception "Attempt to use a script that has been garbage col

[jira] Updated: (JELLY-166) Intermittent error with weak reference wrapper

[ http://nagoya.apache.org/jira/browse/JELLY-166?page=history ] dion gillard updated JELLY-166: --- Fix Version: 1.0 > Intermittent error with weak reference wrapper > -- > > Key: JELLY-166 > URL:

Re: [logging] Enterprise Common Logging... dare we say 2.0?

Response below... Simon Kitching wrote: On Thu, 2004-12-16 at 13:53, Matt Sgarlata wrote: Simon Kitching wrote: I think this demonstrates a major issue. When using logging in an "enterprise" situation, the logging can be considered a critical part of the application. If you have heavy-duty monitori

Re: [logging] Enterprise Common Logging... dare we say 2.0?

On Thu, 2004-12-16 at 13:53, Matt Sgarlata wrote: > Simon Kitching wrote: > > I think this demonstrates a major issue. > > > > When using logging in an "enterprise" situation, the logging can be > > considered a critical part of the application. If you have heavy-duty > > monitoring systems watchi

[jira] Commented: (JELLY-85) TagScript doesn't clear its cached tags after run()

[ http://nagoya.apache.org/jira/browse/JELLY-85?page=comments#action_56751 ] Hans Gilde commented on JELLY-85: - this is a problem with code introduced in the patch for JELLY-148 > TagScript doesn't clear its cached tags after run() > --

[jira] Commented: (JELLY-148) Huge memory leak resulting from the use of ThreadLocal

[ http://nagoya.apache.org/jira/browse/JELLY-148?page=comments#action_56749 ] Hans Gilde commented on JELLY-148: -- There's some problem with the patch for this issue, see JELLY-85 I'm looking into it. > Huge memory leak resulting from the use of Threa

Re: [logging] Enterprise Common Logging... dare we say 2.0?

Simon Kitching wrote: I think this demonstrates a major issue. When using logging in an "enterprise" situation, the logging can be considered a critical part of the application. If you have heavy-duty monitoring systems watching for alerts from the software, and have sysadmins on call 24x7 to deal

Re: [logging] Enterprise Common Logging... dare we say 2.0?

On Thu, 2004-12-16 at 10:21, Richard Sitze wrote: > "Henning P. Schmiedehausen" <[EMAIL PROTECTED]> wrote on 12/15/2004 > > ...byte-code engineering contradict each other. One of the really, > > really strong things of c-l is, that it needs no additional jars. Just > > drop commons-logging in, de

Re: [logging] Enterprise Common Logging... dare we say 2.0?

On 15 Dec 2004, at 21:06, Henning P. Schmiedehausen wrote: robert burrell donkin <[EMAIL PROTECTED]> writes: the passivity is a symptom of commons logging being too big, too complex and too tightly coupled to the needs of applications run in containers and yet not sophisticated enough. IMO the comm

Re: [logging] Enterprise Common Logging... dare we say 2.0?

"Henning P. Schmiedehausen" <[EMAIL PROTECTED]> wrote on 12/15/2004 03:06:41 PM: > robert burrell donkin <[EMAIL PROTECTED]> writes: > > >the passivity is a symptom of commons logging being too big, too > >complex and too tightly coupled to the needs of applications run in > >containers and ye

Re: [logging] Enterprise Common Logging... dare we say 2.0?

robert burrell donkin <[EMAIL PROTECTED]> writes: >the passivity is a symptom of commons logging being too big, too >complex and too tightly coupled to the needs of applications run in >containers and yet not sophisticated enough. IMO the commons logging >API could and should be reduced to one

Re: [logging] Enterprise Common Logging... dare we say 2.0?

robert burrell donkin <[EMAIL PROTECTED]> wrote on 12/15/2004 01:44:47 PM: > On 11 Dec 2004, at 02:24, Noel J. Bergman wrote: > > > It disturbs me that what seems to me to be a reasonable and small set > > of > > requirements --- along with what appears to have been considerable > > forethought

Re: [logging] Enterprise Common Logging... dare we say 2.0?

robert burrell donkin <[EMAIL PROTECTED]> wrote on 12/15/2004 01:39:57 PM: > On 10 Dec 2004, at 01:42, Charles Daniels wrote: > > > 8< > > 8< > > >> Regardless of the performance, though, there is still the matter of > >> exactly where the messagekey+params gets converted to a > >> message str

Re: [logging] Enterprise Common Logging... dare we say 2.0?

Glad you made it Robert, was starting to feel that this was getting snubbed by the core logging advocates ;-)! robert burrell donkin <[EMAIL PROTECTED]> wrote on 12/15/2004 01:39:12 PM: > > On 10 Dec 2004, at 00:40, David Graham wrote: > > > > > --- simon <[EMAIL PROTECTED]> wrote: > > > >

Re: [logging] Enterprise Common Logging... dare we say 2.0?

On 11 Dec 2004, at 02:24, Noel J. Bergman wrote: It disturbs me that what seems to me to be a reasonable and small set of requirements --- along with what appears to have been considerable forethought based upon real world issues, and experiences supporting many developers --- appears to be disco

[jira] Created: (JELLY-177) In JellyServlet, the procedure used to determine the script's location is too simplistic

In JellyServlet, the procedure used to determine the script's location is too simplistic Key: JELLY-177 URL: http://nagoya.apache.org/jira/browse/JELLY-177 Project: jelly Type:

Re: [logging] Enterprise Common Logging... dare we say 2.0?

On 10 Dec 2004, at 19:06, Richard Sitze wrote: "Henning P. Schmiedehausen" <[EMAIL PROTECTED]> wrote on 12/10/2004 04:34:07 AM: Richard Sitze <[EMAIL PROTECTED]> writes: - Utility function to support formatting for other purposes (exception strings): formatMessage(S

Re: [logging] Enterprise Common Logging... dare we say 2.0?

On 10 Dec 2004, at 01:42, Charles Daniels wrote: 8< 8< Regardless of the performance, though, there is still the matter of exactly where the messagekey+params gets converted to a message string. Having a user-provided Message object do it delegates the responsibility of locating the i18n resource b

Re: [logging] Enterprise Common Logging... dare we say 2.0?

On 10 Dec 2004, at 01:23, Simon Kitching wrote: On Fri, 2004-12-10 at 13:20, Charles Daniels wrote: Since all of the logging methods (fatal, error, etc.) accept a message of type Object, you could support i18n/l10n by doing something like the following: log.warn(new Message("key", params)); wher

Re: [logging] Enterprise Common Logging... dare we say 2.0?

On 10 Dec 2004, at 00:40, David Graham wrote: --- simon <[EMAIL PROTECTED]> wrote: Regarding the addition of "entry/exit" logging APIs, I'm also in favour. The code seems trivial, and it can be mapped to "TRACE" level for logging implementations that don't provide "FINER" equivalents. It also se

Re: [logging] Enterprise Common Logging... dare we say 2.0?

On 9 Dec 2004, at 23:18, simon wrote: On Fri, 2004-12-10 at 11:52, Martin Cooper wrote: This sure doesn't sound like Commons Logging would be "an ultra-thin bridge between different logging libraries" any more. http://jakarta.apache.org/commons/logging/ This sounds more like a different package alt

Re: AW: [logging] Enterprise Common Logging... dare we say 2.0?

On 9 Dec 2004, at 22:52, Richard Sitze wrote: I'm very interested in any insight into how to leverage the existing i18n project... that said, I have no interest in mandating use of i18n. Commons logging is lightweight, needs to remain as lightweight as possible. For i18n, my perspective is that

DO NOT REPLY [Bug 32723] - [transaction] Add full file management capabilities to the FileResourceManager

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: [logging] Enterprise Common Logging... dare we say 2.0?

On 9 Dec 2004, at 20:21, Richard Sitze wrote: The fundamental problem with the current factory is that it is dependent on "passively" identifying a logging implementation. We propose one solution below, but would ask a more general question: any ne

DO NOT REPLY [Bug 32723] New: - Add full file management capabilities to the FileResourceManager

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 32720] - [jelly] in JellyServlet, the procedure used to determine the script's URL is too simplistic.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 32720] New: - in JellyServlet, the procedure used to determine the script's URL is too simplistic.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

[ANNOUNCE] Commons Transaction 1.0 final released

The Commons Community is proud to announce the the final release of Commons Transaction 1.0. Commons Transaction has recently been promoted from the Commons Sandbox and provides utility classes commonly used in transactional Java programming. Download page: http://jakarta.apache.org/commons/trans

cvs commit: jakarta-commons/transaction/xdocs downloads.xml

ozeigermann2004/12/15 09:30:10 Modified:transaction/xdocs downloads.xml Log: Added commons transaction releases Revision ChangesPath 1.3 +3 -16 jakarta-commons/transaction/xdocs/downloads.xml Index: downloads.xml ==

cvs commit: jakarta-commons/transaction/src/test/org/apache/commons/transaction/locking GenericLockTest.java

ozeigermann2004/12/15 09:36:35 Modified:transaction/src/test/org/apache/commons/transaction/locking GenericLockTest.java Log: Added restart synchronizer to assure a full test run has been completed before starting a new one Revision ChangesPath 1

Handling of validation of indexed properties: Change proposal

Hi, in my current project I had to meet the two following requirements: - Validation of indexed properties has to be done for all the beans in a collection, even if one failes - The validation result of an indexed property has to contain the index also, e.g. masterbean.detailbean[1].property T

[jira] Updated: (JELLY-85) TagScript doesn't clear its cached tags after run()

[ http://nagoya.apache.org/jira/browse/JELLY-85?page=history ] Paul Libbrecht updated JELLY-85: Attachment: includeAndDefineExample.zip The attached pair of scripts seems to constantly raise the exception "Attempt to use a script that has been garbage c

Re: [doc] First attempt at update to release.html

Rory Winston wrote: Hmm, Or even (given that 1.3.0 is the version number): $ for f in $(ls -d *1.3.0*); do if [[ -f $f ]]; then md5sum $f > $f.md5; fi;done I think if you use md5sum you need to strip off the file name appended after the hash (per the release.html instructions). The script below

Beanutils: cannot copy a Timestamp attribute when it is null

Hi, I have a bean with an attribute with java.sql.Timestamp type. Using BeanUtils.copyProperties method I get org.apache.commons.beanutils.ConversionException: No value specified at org.apache.commons.beanutils.converters.SqlTimestampConverter.convert(SqlTimestampConverter.java:103) at org.a

Fw: Beanutils: cannot copy a Timestamp attribute when it is null

I made more investigations and found out that the PropertyUtils.copyProperties is working fine even when the Timestamp attribute has the null value. Alin. Hi, I have a bean with an attribute with java.sql.Timestamp type. Using BeanUtils.copyProperties method I get org.apache.commons.beanu

RE: [VOTE][EMAIL] Release Commons-Email 1.0

I checked a couple other of the mavenized projects, and they didn't seem to put NOTICE.txt in the distribution. Primarily because the primary distribution method seems to by just putting out a jar file and syncing that to ibiblio. Dion, I did try to get NOTICE.TXT in the dist, instead of putting

[Jakarta Commons Wiki] Updated: Betwixt/FrequentlyAskedQuestions

Date: 2004-12-15T01:37:40 Editor: 82.38.65.173 <> Wiki: Jakarta Commons Wiki Page: Betwixt/FrequentlyAskedQuestions URL: http://wiki.apache.org/jakarta-commons/Betwixt/FrequentlyAskedQuestions no comment Change Log: --

[Jakarta Commons Wiki] Updated: Betwixt

Date: 2004-12-15T01:39:42 Editor: 82.38.65.173 <> Wiki: Jakarta Commons Wiki Page: Betwixt URL: http://wiki.apache.org/jakarta-commons/Betwixt no comment Change Log: -- @@ -19,7 +19,7 @@ Documentation

[Jakarta Commons Wiki] Updated: Betwixt/FrequentlyAskedQuestions

Date: 2004-12-15T01:37:23 Editor: 82.38.65.173 <> Wiki: Jakarta Commons Wiki Page: Betwixt/FrequentlyAskedQuestions URL: http://wiki.apache.org/jakarta-commons/Betwixt/FrequentlyAskedQuestions no comment Change Log: --

[GUMP@brutus]: Project commons-resources (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-resources has an issue affecting its community integration. This issue af

[GUMP@brutus]: Project commons-jelly-tags-jsl (in module jelly-tags) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-jelly-tags-jsl has an issue affecting its community integration. This iss

Re: [Vote] Moving commons-sql to db.apache.org (repost)

Martin van den Bemt wrote: +1.. Although I hope I can still have karma on it.. I am pretty much moving towards a big dependency on commons sql, with almost all my projects. Since sql is a far from finished item, I only chose it because I had the karma to actually change things that were not finishe

DO NOT REPLY [Bug 31286] - [logging] Memory leaks in JBoss due to LogFactory cache

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

cvs commit: jakarta-commons/logging/optional/src/java/org/apache/commons/logging/impl WeakHashtable.java

rdonkin 2004/12/15 02:35:19 Modified:logging/optional/src/java/org/apache/commons/logging/impl WeakHashtable.java Log: Improved housekeeping and simplified code for WeakHashTable. Issue#31286. Submitted by Brian Stansberry. Revision ChangesPath 1.

[Jakarta Commons Wiki] Updated: Betwixt/FrequentlyAskedQuestions

Date: 2004-12-15T01:38:19 Editor: 82.38.65.173 <> Wiki: Jakarta Commons Wiki Page: Betwixt/FrequentlyAskedQuestions URL: http://wiki.apache.org/jakarta-commons/Betwixt/FrequentlyAskedQuestions no comment Change Log: --

[Jakarta Commons Wiki] Updated: Betwixt/TipAndHints

Date: 2004-12-15T01:35:54 Editor: 82.38.65.173 <> Wiki: Jakarta Commons Wiki Page: Betwixt/TipAndHints URL: http://wiki.apache.org/jakarta-commons/Betwixt/TipAndHints no comment Change Log: -- @@ -3,3 +

[Jakarta Commons Wiki] New: Betwixt/TipAndHints

Date: 2004-12-15T01:34:58 Editor: 82.38.65.173 <> Wiki: Jakarta Commons Wiki Page: Betwixt/TipAndHints URL: http://wiki.apache.org/jakarta-commons/Betwixt/TipAndHints no comment New Page: = Betwixt Tip And Hints = * using the same IntrospectionConfiguration instance for the r

cvs commit: jakarta-commons/net KEYS

rwinston2004/12/15 02:07:30 Modified:net KEYS Log: Add key Revision ChangesPath 1.2 +43 -0 jakarta-commons/net/KEYS Index: KEYS === RCS file: /home/cvs/jakarta-commons/net/KEYS,v ret

[PROPOSAL][betwixt] Release 0.6.1

in the months since Betwixt 1.6 was released, an important bug has been fixed and several useful features added. therefore, i'd like to propose a 0.6.1 release and will volunteer to act as release manager. i've added a preliminary outline plan to the wiki (http://wiki.apache.org/jakarta-commons

cvs commit: jakarta-commons/net project.xml

rwinston2004/12/15 01:45:18 Modified:net project.xml Log: Update for new release Revision ChangesPath 1.57 +1 -1 jakarta-commons/net/project.xml Index: project.xml === RCS file: /home/

[Jakarta Commons Wiki] New: Betwixt/0.6.1ReleasePlan

Date: 2004-12-15T01:50:20 Editor: 82.38.65.173 <> Wiki: Jakarta Commons Wiki Page: Betwixt/0.6.1ReleasePlan URL: http://wiki.apache.org/jakarta-commons/Betwixt/0.6.1ReleasePlan no comment New Page: = Betwixt 0.6.1 Release Plan = This is a point release which fixes an important

[Jakarta Commons Wiki] Updated: Betwixt

Date: 2004-12-15T01:46:25 Editor: 82.38.65.173 <> Wiki: Jakarta Commons Wiki Page: Betwixt URL: http://wiki.apache.org/jakarta-commons/Betwixt no comment Change Log: -- @@ -45,6 +45,7 @@ * [:/0.5Rel

[Jakarta Commons Wiki] Updated: Betwixt/TipsAndHints

Date: 2004-12-15T01:41:16 Editor: 82.38.65.173 <> Wiki: Jakarta Commons Wiki Page: Betwixt/TipsAndHints URL: http://wiki.apache.org/jakarta-commons/Betwixt/TipsAndHints no comment Change Log: -- @@ -6,4

[Jakarta Commons Wiki] Updated: Betwixt/FrequentlyAskedQuestions

Date: 2004-12-15T01:38:54 Editor: 82.38.65.173 <> Wiki: Jakarta Commons Wiki Page: Betwixt/FrequentlyAskedQuestions URL: http://wiki.apache.org/jakarta-commons/Betwixt/FrequentlyAskedQuestions no comment Change Log: --

[Jakarta Commons Wiki] Updated: Betwixt/TipsAndHints

Date: 2004-12-15T01:40:51 Editor: 82.38.65.173 <> Wiki: Jakarta Commons Wiki Page: Betwixt/TipsAndHints URL: http://wiki.apache.org/jakarta-commons/Betwixt/TipsAndHints no comment Change Log: -- @@ -6,4

[Jakarta Commons Wiki] New: Betwixt/TipsAndHints

Date: 2004-12-15T01:40:28 Editor: 82.38.65.173 <> Wiki: Jakarta Commons Wiki Page: Betwixt/TipsAndHints URL: http://wiki.apache.org/jakarta-commons/Betwixt/TipsAndHints no comment New Page: = Betwixt Tips And Hints = * using the same IntrospectionConfiguration instance for th

[Jakarta Commons Wiki] Updated: Betwixt/FrequentlyAskedQuestions

Date: 2004-12-15T01:37:07 Editor: 82.38.65.173 <> Wiki: Jakarta Commons Wiki Page: Betwixt/FrequentlyAskedQuestions URL: http://wiki.apache.org/jakarta-commons/Betwixt/FrequentlyAskedQuestions no comment Change Log: --

[Jakarta Commons Wiki] Updated: Betwixt/FrequentlyAskedQuestions

Date: 2004-12-15T01:36:54 Editor: 82.38.65.173 <> Wiki: Jakarta Commons Wiki Page: Betwixt/FrequentlyAskedQuestions URL: http://wiki.apache.org/jakarta-commons/Betwixt/FrequentlyAskedQuestions no comment Change Log: --

[Jakarta Commons Wiki] Updated: Betwixt

Date: 2004-12-15T01:33:50 Editor: 82.38.65.173 <> Wiki: Jakarta Commons Wiki Page: Betwixt URL: http://wiki.apache.org/jakarta-commons/Betwixt no comment Change Log: -- @@ -19,6 +19,7 @@ Documentation

[ANNOUNCEMENT] Commons-Net 1.3.0 released

The Jakarta Commons Net team is pleased to announce the release of version 1.3.0. This version contains many fixes and enhancements, and includes a new NTP component. The full list of changes can be found at http://jakarta.apache.org/commons/net/changes-report.html The binary releases can be fo

Re: [doc] First attempt at update to release.html

Another way of creating the links in one shot: export VERSION=1.3.0 # or whatever # Create the links, substituting "current" for the version number $ for f in $(ls -d binaries/*$VERSION*); do NEWFILE=${f##binaries/}; NEWFILE=${NEWFILE/$VERSION/current}; ln -s $f $NEWFILE; done Cheers, Rory Rory

DO NOT REPLY [Bug 32240] - [configuration] XMLConfiguration.save() does not keep element hierarchy

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 32240] - [configuration] XMLConfiguration.save() does not keep element hierarchy

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu