Hello all,
I'm getting an exception in code
java.lang.ClassCastException: java.lang.ClassCastException:
java.lang.String cannot be cast to java.math.BigDecimal
at
org.apache.commons.beanutils.BeanComparator.compare(BeanComparator.java:
155)
I'm using BeanUtils 1.7.0 but when
Perhaps the annotation could be extended in some way to permit mappings of
Throwable types to Handler types. This would (a) allow different handlers to
be used for the same method, and (b) allow the exception to be thrown as normal
when no matching handler was found.
Just thinking,
Matt
---
I agree with you in some points. Maybe it is better to return inside
exceptions to the caller instead of catch them locally.
The problem, for me, remains in this part: "see if we have a method to
handle such an exception by checking if a method
handleIllegalArgumentException exists"
I believe tha
Hi Jorg,
Thank you again for your comments. I believe you are partially right, let me
explain...
Using Jeha it is possible to specify blocks where you'd like to use handle()
method. Other blocks always can have different strategies, for example:
try {
doSomethingRisky();
}
catch (NamingExcep
I agree with you that there is no elegant way to say what can and cannot
be handled by the handler so what I suggest is let the handler decide what
it can and cannot handle. Looking at the handler should give one a clear
picture of what its equipped to handle.
Here's what I mean with an example:
Hi Andre,
Andre Dantas Rocha wrote at Mittwoch, 8. April 2009 15:17:
> Hi Jorg,
>
> I understand your point, and maybe the framework need some improvement.
> Today it's only an initial code (any help and ideas are welcome).
>
> In my opinion handleException() must handle the original exception
Hi Gurav,
The weaving could be accomplished statically using ASM, BCEL, Javassist or
any similar tool. In my opinion, a bytecode library must be used only during
compilation process; it's better (and cleaner) if the program does not need
it to work.
Personally, I think that attach handlers with s
For example, I think the ideas in Jeha could also be applied to
Commons-Validator. In my opinion, the examples of Commons-Validator could be
more simple and readable with using Annotation.
I don`t have many ideas yet but I see the potent possibility of Annotation
as I can see through Jeha. :)
I th
I just want to take the discussion towards converting compile time weaving
to load time weaving for a second here. Please feel free to correct me if
I have gone off the wrong path here.
My idea is to simply have something like this:
1. apply throws advice on every method which has the annotation
2.
Oops...
Where you see:
throw handleException(e)
replace with:
throw new RuntimeException(handleException(e));
Andre
-Mensagem original-
De: Andre Dantas Rocha [mailto:andre.dantas.ro...@uol.com.br]
Enviada em: quarta-feira, 8 de abril de 2009 10:18
Para: 'Commons Developers List'
Ass
Hi Jorg,
I understand your point, and maybe the framework need some improvement.
Today it's only an initial code (any help and ideas are welcome).
In my opinion handleException() must handle the original exception and all
exceptions that occurs inside it, so the code ever stops in this method:
/
On 08/04/2009, Mladen Turk wrote:
> sebb wrote:
>
> >
> > > +SYSDLL_JVM = 6,// jvm From our own jvm.dll
> > > +SYSDLL_defined = 6 // must define as last idx_ + 1
> > >
> >
> > Shouldn't that be 7 then? Or does the JVM value not count?
> >
> >
>
> Yes. Thanks f
sebb wrote:
+SYSDLL_JVM = 6,// jvm From our own jvm.dll
+SYSDLL_defined = 6 // must define as last idx_ + 1
Shouldn't that be 7 then? Or does the JVM value not count?
Yes. Thanks for keeping an eye ;)
However this is still in early stage of merging
few e
On 08/04/2009, Andre Dantas Rocha wrote:
> Jorg,
>
> I don't agree with this point at all: "having a method call in a catch block
>
> is
> likely to cause problems for code analysis tools - as well as humans -
> as one cannot immediately tell if the code continues or not"
>
>
> I believe it is
Jorg,
I don't agree with this point at all: "having a method call in a catch block
is
likely to cause problems for code analysis tools - as well as humans -
as one cannot immediately tell if the code continues or not"
I believe it is possible to know if the code continues or not, for example,
if
On 08/04/2009, mt...@apache.org wrote:
> Author: mturk
> Date: Wed Apr 8 11:48:56 2009
> New Revision: 763196
>
> URL: http://svn.apache.org/viewvc?rev=763196&view=rev
> Log:
> Use APR late dll macros and extend them with defalt return value
>
> Modified:
>
> commons/sandbox/runtime/tr
It sounds interesting to me. Do you already have any ideas of new domains?
-Mensagem original-
De: Min Cha [mailto:minslo...@gmail.com]
Enviada em: quarta-feira, 8 de abril de 2009 07:03
Para: Commons Developers List
Assunto: Re: Possible incubation?
Hi, Andre.
I think that many legacy
You're right. Today Transform task put the handler code in all catch blocks,
regards type of exception. You have to do the calls manually if you what to
be more precise.
The improvement suggested by Gaurav is very useful and can be done in the
task (or even a Mojo).
Andre
-Mensagem original
Hi Jorg,
Actually you can declare handlers in methods and/or class and use a special
invocation in your catch block -- HandlerUtil.handle(e) -- to tell it you want
to use the declared exception. This is the more flexible approach, because you
can handle only what you want.
The other option is
Hi Gaurav,
gauravar...@codercorp.com wrote at Mittwoch, 8. April 2009 12:30:
> I think it's more valid to look at Jeha as a framework that only handles
> what you ask to handle. In the case you describe, if you don't ask Jeha to
> handle a certain type of exception, then that exception is simply
sebb wrote:
Any plans to add OpenVMS to the list?
Since there is no Runner project, I suppose you meant [Runtime] :)
Short answer - No.
Let's try not to introduce the esoteric OS's
APR-2 broke the support for many OS's like Netware, OS/2,
historic Solaris releases, etc...
In general OS can
That may be well the case, the need for such flexibility in images is
probably there, however if this would be adopted it really need
appropriate names, something of the sort BigString.
paul
Le 08-avr.-09 à 11:36, Jörg Schaible a écrit :
Have a look at the different ImageInputStream/Image
Any plans to add OpenVMS to the list?
I can help with that - if I can still get access to the HP test boxes.
S
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache
On 08/04/2009, gauravar...@codercorp.com wrote:
> I think it's more valid to look at Jeha as a framework that only handles
> what you ask to handle. In the case you describe, if you don't ask Jeha to
> handle a certain type of exception, then that exception is simply
> propagated up the stack.
Hi
I applied to ASF as a part of Google Summer of Code program for a project -
"Implementation of SSH in Java" , and this implementation may be added to
commons net.
I have an idea on how to start-off with this. Although I consulted my mentor
with this idea, i'm posting this idea here to get an i
Hi,
I tried searching the list to read up on the work to make the commons
libraries use generics but didn't really come across any direct posts.
Since i'm new to the list I figured i'd just ask for a thread or a link to
help me with my reading. Also, am I correct in understanding that the
commons
I think it's more valid to look at Jeha as a framework that only handles
what you ask to handle. In the case you describe, if you don't ask Jeha to
handle a certain type of exception, then that exception is simply
propagated up the stack. I don't think it interferes with the method
signature, unles
On 08/04/2009, Jörg Schaible wrote:
> Hi Andre,
>
> Andre Dantas Rocha wrote at Dienstag, 7. April 2009 14:38:
>
>
> > Hi all,
> >
> > This message was originally sent to incubator list, but they suggest to
> > post it here because *maybe* the idea can fit in Commons project.
> >
> > I'm de
Hi, Andre.
I think that many legacy codes could be improved by Annotation.
In this aspect, your idea seems like good.
How do you think about expending the core idea of Jeha to other domains as
well as exception handling?
In my opinion, there might be many domains which can be improved though the
Paul Libbrecht wrote at Mittwoch, 8. April 2009 11:17:
>
> Hello commons list,
>
> one thing I keep seeing around is people exchanging either too big
> strings, byte-arrays, or stringbuffers. It looks like, they one has
> still not found something sensible that describes something close to
> an
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 gene...@gump.apache.org.
Project commons-configuration-test has an issue affecting its community
integrati
Hello commons list,
one thing I keep seeing around is people exchanging either too big
strings, byte-arrays, or stringbuffers. It looks like, they one has
still not found something sensible that describes something close to
an array of characters so:
- that can give its length
- that can
I have been seeing his activity in Commons so I think he will be a good
committer for Commons.
Congratulation, Christian!
On Wed, Apr 8, 2009 at 2:34 PM, Stefan Bodewig wrote:
> Christian Grobmeier has been elected as a new Commons committer about
> two weeks ago and this has been his first co
33 matches
Mail list logo
