> I would suggest
org.aerogear.android.net (and if you move Scan
et all to .reflection then .impl.core and become .impl.net)
-1 maybe org.aerogear.android.http ?
That works better +1.
> I don't think we should have an exception package. 1) There
isn't one in the JDK and 2) it breaks the organizational connections between classes
and the types of exceptions they can throw
why not? Just because JDK doesn't have it? I can't see any problems on having
org.jboss.aerogear.exception package.
Other than both being exceptions, what relationship do HttpException and PropertyNotFound
exception have with each other? It makes much more sense for them to be group with things
that functionally depend on them than group with things they inherit from. If an
exception is moved to an exception package then the only other hint the user will have as
to where it is used would be in method signatures in different packages or in the javadoc
comments.
----- Original Message -----
From: "Bruno Oliveira" <bruno(a)abstractj.org>
To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org>
Cc: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org>
Sent: Tuesday, November 20, 2012 12:18:28 PM
Subject: Re: [aerogear-dev] Aerogear Android Packages
- Bruno
On Nov 20, 2012, at 1:58 PM, Summers Pittman <supittma(a)redhat.com> wrote:
> Working to make id configurable I created two classes Scan (to
search for a annotation) and Property (to encapsulate reflection property calls) where I
should put these classes? I created some exceptions. We should >have a package for
exceptions?
If Property and Scan and their exceptions are available on an api or meant to be used by
the user directly, I would say put them in org.aerogear.android.reflection. If not,
org.aerogear.android.impl.reflection
+1
> Also I was in doubt whether the classes HeaderAndBody and HttpException should not be
moved to the package impl
I don't think we should have an exception package. 1) There isn't one in the JDK
and 2) it breaks the organizational connections between classes and the types of
exceptions they can throw
why not? Just because JDK doesn't have it? I can't
see any problems on having org.jboss.aerogear.exception package.
----- Original Message -----
From: "Daniel Passos" <daniel(a)passos.me>
To: "AeroGear Developer Mailing" <aerogear-dev(a)lists.jboss.org>
Sent: Tuesday, November 20, 2012 10:49:19 AM
Subject: [aerogear-dev] Aerogear Android Packages
Hi Guys,
I'm having some doubts about where to put some classes.
Working to make id configurable I created two classes Scan (to search for a annotation)
and Property (to encapsulate reflection property calls) where I should put these classes?
I created some exceptions. We should have a package for exceptions?
Also I was in doubt whether the classes HeaderAndBody and HttpException should not be
moved to the package impl
wdyt?
Att,
Daniel Passos
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev