2012/6/18 Simone Tripodi :
> +1 to 'of'
>
> short to type and intuitive!
>
> Thanks Matt for the valuable feedbacks!
>
I'll implement that after I'm finished with replacing the exceptions.
Benedikt
> best,
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.co
+1 to 'of'
short to type and intuitive!
Thanks Matt for the valuable feedbacks!
best,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
---
Just for the sake of multiple choice, what about:
- keyedBy
- keyedTo
- withKey
- of
- at
?
Matt
On Mon, Jun 18, 2012 at 7:19 AM, Simone Tripodi
wrote:
> LOL indeed :)
>
> go for your proposed solution, sounds nice anyway :)
>
> alles gute,
> -Simo
>
> http://people.apache.org/~simonetripodi/
LOL indeed :)
go for your proposed solution, sounds nice anyway :)
alles gute,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Mon, Jun 18, 2012 at 11:10 AM, Benedikt Ritter
wrote:
> I just realize
I just realized, that we cannot call a method
MappedPropertyAccessor.for(String key) - "for" is a reserved keyword
;-)
How about:
MappedPropertyAcessor.forKey(String key) and
ArgumentsAcessor.with(Argument... Arguments)
Benedikt
2012/6/16 Simone Tripodi :
> +1 to James for both topics,
>
> let's
+1 to James for both topics,
let's start from a basic exception - naming proposals are welcome.
I'll create the wiki page later after dinner - that WE is too much
sunny to stay at home ;)
best,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.co
It shouldn't. If you're catching the superclass (for instance
BeanUtilsReflectionException) and later we start to throw
BeanUtilsInstantiationException which extends
BeanUtilsReflectionException, I don't think you'll run into problems.
On Fri, Jun 15, 2012 at 10:26 AM, Benedikt Ritter
wrote:
> 2
2012/6/15 James Carman :
> On Fri, Jun 15, 2012 at 9:39 AM, Benedikt Ritter
> wrote:
>> - Wrapper Exceptions: I thing we should discuss, how a exception
>> hierarchy could look like. I'll make a suggestion ASAP.
>>
>
> I don't want to duplicate the hierarchy. I would say start with a
> generic ex
On Fri, Jun 15, 2012 at 9:39 AM, Benedikt Ritter
wrote:
> - Wrapper Exceptions: I thing we should discuss, how a exception
> hierarchy could look like. I'll make a suggestion ASAP.
>
I don't want to duplicate the hierarchy. I would say start with a
generic exception type for now. If folks ask f
Hi,
I agree with what you said.
- Annotation processing: let's keep that in mind, and come back to it
later. Simo, can you create the wiki page for us?
- Renaming methods: I hope that I get the time to create a patch this weekend
- Wrapper Exceptions: I thing we should discuss, how a exception
Thanks a lot for monitoring BU2 James, and thanks for the feedbacks!
this sounds to be the way to go!
now waiting for patches from Benedikt :)
best,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On F
On Fri, Jun 15, 2012 at 1:50 AM, Simone Tripodi
wrote:
>
>
> > 2. Wrap checked exceptions into RuntimeExceptions. The question is,
> > what a user can do to recover from one of those exceptions. Only if
> > there is something the user can do, it would make sense to throw a
> > checked exception.
>
Hi Bene,
> Hi,
>
> while working on BU2, I was thinking about the API and what may be improved.
>
great! :)
> Exceptions:
> Right now a lot of API methods just populate the checked reflection
> exceptions like InvocationTargetException from the native java
> reflection API. This dooms Java 6 use
Hi,
while working on BU2, I was thinking about the API and what may be improved.
Exceptions:
Right now a lot of API methods just populate the checked reflection
exceptions like InvocationTargetException from the native java
reflection API. This dooms Java 6 users to write code like:
try {
Bea
14 matches
Mail list logo