like a user DAO or DTO that might be used in almost all
the features?
I think a core/common feature would be a great place to put it. To not
expose dependencies of core to other features I'd also introduce a common
feature that all features can depend on, then common can be implemented
Maybe User is just overloaded with meaning and should really be
split up into multiple classes (or traits if you have them) each
focused on their role in their respective package?
Or maybe User shouldn't be in any of them, maybe User is just the
mechanics to implement a specific feature which
I like the idea of organizing the packages by feature, but I wonder
where you put the common code, or code that is used in a couple of
places? For example, the domain objects might not fit exclsuvely in
one feature - like a user DAO or DTO that might be used in almost all
the features?
I guess I
This sort of thing is terribly difficult to discuss without concrete
examples. For shared domain stuff, you can usually still identify an
intersecting level higher up in the hierarchy no and aim to have these
as abstract as possible no? In some ways it reminds me of the hard
part of doing REST,
Here is an interesting real-life experience regarding this topic,
although C# was used :)
http://richarddingwall.name/2009/08/08/real-life-ddd-organise-code-by-responsibility-layers-not-repositories-and-services/
--~--~-~--~~~---~--~~
You received this message
On Jun 13, 1:15 pm, Christian Beil christian.a.b...@gmail.com wrote:
What is your opinion on that? I'm especially interested in what you
think about structuring packages? Do youpackageby layer (ie
dao,service,controller,...) or do youpackagebyfeature?
I think the IDE should let you tag stuff,
The thing is, NetBeans (and even Java itself) is no longer just used
for imperative programming where you can simply agree to conform to a
120 character line. Just staying with JEE technologies, we require
editing files full of Facelet/XML, JavaScript, SQL/JPQL annotation
etc. It's particular
I suppose it is too much of a religious war but I would love more
discussion of code style. You will have to gauge other fans but I
like to hear it hashed out. Pick a coding practice of the week (good
or bad) and riff on it for 5 minutes. I now am an anti-tab
evangelist! Coding standards are
I recently view the Google Tech Talks on Clean Code, and I hae to say htat
I'm becoming more and more adverse to dereferencing things that are not
either passed into the constructor of the object at hand, or into the mthod
being invoked. (I.e. No calls to singletons)
When combined with Scala's
Just as a side-note, I'm not drunk, my wireless keyboard is just low on
battery...
On Fri, Jun 19, 2009 at 2:50 PM, Viktor Klang viktor.kl...@gmail.comwrote:
I recently view the Google Tech Talks on Clean Code, and I hae to say htat
I'm becoming more and more adverse to dereferencing things
One of thing missing is an Inline Variable refactoring. I use that,
along extract local variable, almost constantly while hacking code
with eclipse.
Also, the code formatter won't format to our exact code style at the
moment either, although can't remember which bit exactly it doesn't
handle.
To get back to the initial topic, Tor, would you discuss 'package by
layer' vs. 'package by feature' on the podcast?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups The
Java Posse group.
To post to this group, send
On Jun 18, 7:23 pm, Peter Becker peter.becker...@gmail.com wrote:
I feel similar. NetBeans is quite nice in many regards, but generally
lacking in terms of code hygiene. Between NetBeans not even
auto-formatting generated code and Eclipse fixing dozens of things as
Save Actions a lot is still
Save Actions. Yeah, I can see that that would be useful. I know the
hard part has already been done (there's a new action for removing
trailing whitespace for modified lines only, and they added some
infrastructure for save-time actions for that) so what's left is an
options panel for letting you
Bill Robertson wrote:
On Jun 18, 7:23 pm, Peter Becker peter.becker...@gmail.com wrote:
I feel similar. NetBeans is quite nice in many regards, but generally
lacking in terms of code hygiene. Between NetBeans not even
auto-formatting generated code and Eclipse fixing dozens of things as
I had the same feeling when reading that article -- but I stopped
arguing about any flavor of hungarian notation a while ago. Unless
someone uses it on projects I work on, that is :-)
But it is good to see I was not the only one offended.
The other things I noticed is that (a) most of the
Don't get me started on the deficiency of Netbeans. This feature is a must
and has been in all others IDEs forever.
Why the hell isn't JAVA a language that needs attention in Netbeans?
Since this is written in Java, why isn't this the main language supported
Java is the LEAST developed language
On Jun 18, 2:18 pm, Erlend Hamnaberg ngar...@gmail.com wrote:
I really like Netbeans. But until you get REAL editor support for JAVA, I
can't use it.
Can't read your mind, so what do you feel is missing?
--~--~-~--~~~---~--~~
You received this message because
Yes NetBeans HAS come a very long way but it's true its not there yet.
For me, one of the few really big things missing now is line wrapping.
I see people requesting this on the bug tracker almost every single
day.
/Casper
On 18 Jun., 20:48, Ryan Waterer aguitadel...@gmail.com wrote:
Erlend,
Casper Bang wrote:
Yes NetBeans HAS come a very long way but it's true its not there yet.
For me, one of the few really big things missing now is line wrapping.
Can you elaborate?
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - We make Java work. Everywhere.
Casper Bang wrote:
Sure, but it really would be faster to just guide you to the top 4'th
voted item on the issue tracker:
http://www.netbeans.org/issues/show_bug.cgi?id=89894
Thanks.
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - We make Java work. Everywhere.
On Jun 18, 11:18 am, Erlend Hamnaberg ngar...@gmail.com wrote:
Don't get me started on the deficiency of Netbeans. This feature is a must
and has been in all others IDEs forever.
Maybe it's been in all other IDEs forever, but I just fired up
Eclipse 3.4 and I can't find it. I'm sure it's
Yeah, NetBeans should add soft word wrapping.
Eclipse doesn't have it either (except for a third party plugin,
currently at version 0.0.2, which doesn't work with some languages and
apparently breaks line numbering) - but people coming to NetBeans from
for example TextMate certainly miss this
On Jun 18, 4:26 pm, TorNorbye tor.nor...@gmail.com wrote:
On Jun 18, 11:18 am, Erlend Hamnaberg ngar...@gmail.com wrote:
Don't get me started on the deficiency of Netbeans. This feature is a must
and has been in all others IDEs forever.
Maybe it's been in all other IDEs forever, but I
I like this comment from the bug report;
This feature is necessary, for simple usability because is impossible
read a line code with thousands columns.
A line of code should never have thousands of columns.
On Jun 18, 7:49 pm, TorNorbye tor.nor...@gmail.com wrote:
On Jun 18, 4:26 pm,
I feel similar. NetBeans is quite nice in many regards, but generally
lacking in terms of code hygiene. Between NetBeans not even
auto-formatting generated code and Eclipse fixing dozens of things as
Save Actions a lot is still to be done.
Let me elaborate. The premise is that I'm a bloody
maybe the were entering a one-line-coding-contest? i used to type
those as a kid in the back of Nibble and Byte magazine (in apple soft
basic with a ton of semicolons :)
On Jun 18, 2009, at 5:49 PM, Augusto wrote:
I like this comment from the bug report;
This feature is necessary, for
Thanks Tor for pointing out Ctrl-Shift-Cmd-O, didn't know of that one.
I didn't even think of this feature. I use Eclipse most of the time,
and I don't think Eclipse has this feature. I only know of Open Type
(Ctrl-Shift-T) and Open Resource (Ctrl-Shift-R).
Hi Christian,
In addition, there is an article on javapractices.com on the same
issue:
http://www.javapractices.com/topic/TopicAction.do?Id=205
My overall feeling is that package-by-layer is a wide habit, but one
that is often worth breaking.
In addition, a problem seems to be example code.
I think at a point, where packaging by layer starts to become a
serious handicap is where real modularity needs to come in. In most
cases, even now in Java, it doesn't have to take much effort to make
an application extensible via some sort of simple plug-in/module
architecture. If you have
I agree with the semantics of package-by-feature. In Robert Martin's
Agile Software Development: Principles, Patterns, and Practices
book, he has a very big section on packaging and how it affects
coupling and reuse. I do see that many projects tend to ignore this
and package by layer (and I've
31 matches
Mail list logo
