to PropertyUtilsBean exceptions -
as patched by Erik Meade in #BEANUTILS-207
Sendingsrc/java/org/apache/commons/beanutils/PropertyUtilsBean.java
Transmitting file data .
Committed revision 472361.
[beanutils][PATCH] Include bean getClass in PropertyUtilsBean Exceptions
[ http://issues.apache.org/jira/browse/BEANUTILS-207?page=all ]
Niall Pemberton updated BEANUTILS-207:
--
Bugzilla Id: (was: 20968)
Component/s: Bean / Property Utils
[beanutils][PATCH] Include bean getClass in PropertyUtilsBean Exceptions
repeat using Eclipse etc.
[beanutils][PATCH] Warning fixes, are these a good idea?
Key: BEANUTILS-55
URL: http://issues.apache.org/jira/browse/BEANUTILS-55
Project: Commons BeanUtils
within Eclipse.
[beanutils][PATCH] Larger warning fixes.
Key: BEANUTILS-22
URL: http://issues.apache.org/jira/browse/BEANUTILS-22
Project: Commons BeanUtils
Issue Type: Bug
Environment
[ http://issues.apache.org/jira/browse/BEANUTILS-121?page=all ]
Henri Yandell updated BEANUTILS-121:
Bugzilla Id: (was: 32230)
Fix Version/s: 1.8.0
Apply to 1.8.0 - or repeat using Eclipse if the source is too changed.
[beanutils][PATCH
-warning-fix.patch was already fixed.
I'm punting the unnecessary-else fix. I'm not a huge fan of the style of ending
with an if/else, but I do think it's a style thing rather than something that
can be considered wrong.
[beanutils][PATCH] Easy warning fixes
[ http://issues.apache.org/jira/browse/BEANUTILS-22?page=all ]
Henri Yandell resolved BEANUTILS-22.
Resolution: Fixed
r469737 - unnecessary-semicolon-fix-test.patch
Punting on the unnecessary else fix.
[beanutils][PATCH] Larger warning fixes
...
Committed revision 469743.
[beanutils][PATCH] Warning fixes, are these a good idea?
Key: BEANUTILS-55
URL: http://issues.apache.org/jira/browse/BEANUTILS-55
Project: Commons BeanUtils
Hi,
I have found that running maven test for beanutils reports a failure
of 3 test cases.
(a) BeanificationTestCase and LocaleBeanificationTestCase both fail to
load a test class using the code:
ClassLoader loader = new ClassLoader() {};
Class myClass = loader.loadClass(
/show_bug.cgi?id=20968
[EMAIL PROTECTED] changed:
What|Removed |Added
Summary|[PATCH] Include bean|[beanutils][PATCH] Include
|getClass
/show_bug.cgi?id=32233
[EMAIL PROTECTED] changed:
What|Removed |Added
Summary|[PATCH] BeanUtils |[beanutils][PATCH] Warning
|(CurrentCVS): Warning fixes
/show_bug.cgi?id=32232
[EMAIL PROTECTED] changed:
What|Removed |Added
Summary|[PATCH] BeanUtils |[beanutils][PATCH] Larger
|(CurrentCVS): Larger warning
/show_bug.cgi?id=23669
[beanutils][PATCH] LICENSE.txt: acknowledgement(s) typo
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Ref:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg28389.html
I sent a patch in a while back to allow mapping specific interface
definitions to resultsets so that the returned dynabeans don't necessarily
100% map to the resulset metadata. It's useful when you have a service
layer that needs
: Tuesday, October 28, 2003 9:07 AM
To: Jakarta Commons Developers List
Subject: [BEANUTILS] patch for resultset
Ref:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg28389.html
I sent a patch in a while back to allow mapping specific interface
definitions to resultsets so that the returned
I've seen the hint many times in the Jakarta lists, that it is better
to post patches into bugzilla. there each issue is tracked, listed
weekly and requires an explicit handling, closing. It is less likely
that a patch in bugzilla gets lost as in the high volume commons-dev
list.
You got already a
: Tuesday, October 28, 2003 11:27 AM
To: Jakarta Commons Developers List
Subject: Re: [BEANUTILS] patch for resultset
I've seen the hint many times in the Jakarta lists, that it is better to
post patches into bugzilla. there each issue is tracked, listed weekly and
requires an explicit handling
/show_bug.cgi?id=23669
[beanutils][PATCH] LICENSE.txt: acknowledgement(s) typo
Summary: [beanutils][PATCH] LICENSE.txt: acknowledgement(s) typo
Product: Commons
Version: Nightly Builds
Platform: Other
OS/Version: Other
Status: NEW
/show_bug.cgi?id=23669
[beanutils][PATCH] LICENSE.txt: acknowledgement(s) typo
--- Additional Comments From [EMAIL PROTECTED] 2003-10-08 09:54 ---
Created an attachment (id=8490)
patch showing two typos in LICENSE.txt
In order to facilitate it getting checked in soon, I separated out the changes to
existing classes as a separate patch. These very few changes will make the
BeanUtilsBean, etc. extensible so that the rest of the original patch could be a
commons extension. Someone *please* take a moment to
Eric Pabst submitted a patch attached at the end of the following bug
report http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10319. the
fundamental idea is that we allow subclasses of BeanUtilsBean to offer
variations on the basic behaviours. it seems to me that this should allow
the novel
: BeanUtils patch
|
---|
hi eric
i've taken a quick look and i quite like the sound of this solution. the
problem
On Wednesday, June 18, 2003, at 03:59 PM, [EMAIL PROTECTED]
wrote:
Thanks for looking at it, Robert. Is there anything you (anyone?) noticed
that was unnecessarily complex?
I tried (and am open for suggestions) to make it as simple as possible
while still being powerful.
it didn't look
hi eric
i've taken a quick look and i quite like the sound of this solution. the
problem is that i'd have analysis the patch in depth (due to it's size and
complexity) before i could commit it. i can't speak for the others but i'm
don't have the cycles right now for this. maybe someone else
I don't know why, but I submitted a patch for bug #10319
(http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10319), and I didn't see
it on the commons-dev list. Anyone know why?
Would anyone be willing to commit this? It passes all current tests, and
has some new ones. It also fixes at least
Seems like your attachment got stripped from the mail. Amybe wrong
extension or too big, don't know..
Mvgr,
Martin
On Mon, 2003-02-03 at 19:22, LOX wrote:
I'm sorry, I'm relly new to the Apache lists..
Could somebody explain me what happened?
First I sent a mail containing the patch, a
Have a go with the txt extension (the headers still showed the
mixed/multipart, so that's why I think it was stripped out of the mail).
Don't know if it makes any difference though :)
Mvgr,
Martin
On Mon, 2003-02-03 at 19:48, LOX wrote:
Seems like your attachment got stripped from the mail.
here we go again...
Index: ConstructorUtils.java
===
RCS file:
/home/cvspublic/jakarta-commons/beanutils/src/java/org/apache/commons/beanutils/ConstructorUtils.java,v
retrieving revision 1.2
diff -u -r1.2 ConstructorUtils.java
---
Applied thanx !
Mvgr,
Martin
On Mon, 2003-02-03 at 20:58, LOX wrote:
here we go again...
Index: ConstructorUtils.java
===
RCS file:
A recent name change in the license file breaks
build.xml. Here is a patch to fix this problem. Also
included is an optional target that will add
platform specific source to the distribution jar.
Please consider adding this enhancment along with the
fix.
Thanks,
David Morris
Index:
As I had promised a couple weeks ago, attached is the diff for build.xml and
a testcase for the current BeanComparator. I left in the comparator test
for Booleans with the expectation that it will fail.
I will post in a seperate email my MakeComparableComparator that forces
objects to be
31 matches
Mail list logo
