Skip to main content

Home/ SoftwareEngineering/ Group items tagged code

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
kuni katsuya

Interface naming in Java - Stack Overflow - 0 views

stackoverflow.com/...interface-naming-in-java

java Interface NamingConvention BestPractices

shared by kuni katsuya on 19 Dec 12 - No Cached
  • interfaces define
  • capabilities
    • kuni katsuya
      kuni katsuya on 19 Dec 12
       
      this is one sensible interface naming option, if the interface encapsulates a cohesive set of behaviors and yes, compared to blindly following the meaningless I+ convention, it requires some thought, but thinking of an appropriate name also forces you to (re)consider the interface's primary responsibility and how it fits into the overall design imho, a class diagram for a domain model should be almost fluently readable english
  • not types
  • ...16 more annotations...
  • Comparable
  • Runnable
  • Serializable
  • Sometimes an Adjective doesn't make sense, but I'd still generally be using interfaces to model behavior, actions, capabilities, properties, etc,... not types.
  • Also, If you were really only going to make one User and call it User then what's the point of also having an IUser interface?
    • kuni katsuya
      kuni katsuya on 19 Dec 12
       
      another anti-pattern... blindly create an interface for every class, even if there's only one implementation!! arrgghhhh! consider introducing an interface when there are 2-3 well-distinguished, concrete implementations required
  • if you are going to have a few different types of users that need to implement a common interface, what does appending an "I" to the interface save you in choosing names of the implementations?
  • prefer not to use a prefix on interfaces:
  • hurts readability.
  • interfaces names should be as short and pleasant as possible
  • Implementing classes should be uglier to discourage their use.
    • kuni katsuya
      kuni katsuya on 19 Dec 12
       
      but they don't *have* to be ugly, like BlahImpl for specialized implementations, use descriptive adjective-noun combos
  • Code using an instance of some type should never, ever care if that type is an interface or a class
  • exposing such a detail in the name of the type is pointless and harmful to understanding
  • several reasons Java does not generally use the IUser convention.
  • should not have to know whether the client is using an interface or an implementation class
  • Java naming convention prefers longer names with actual meanings to Hungarian-style prefixes
  • Interface naming in Java [closed]
  • kuni katsuya on 19 Dec 12
     
    "have interfaces define"
kuni katsuya

JPA implementation patterns: Retrieving entities | Xebia Blog - 0 views

blog.xebia.com/...n-patterns-retrieving-entities

java JPA patterns retrieve NamedQuery find

shared by kuni katsuya on 04 Nov 12 - No Cached
  • JPA implementation patterns: Retrieving entities
  • two ways to retrieve an entity with JPA:
  • EntityManager.find
  • ...2 more annotations...
  • Query object that can then be executed to return a list of entities or a single entity.
  • Keeping the query and the code that sets these parameters together makes them both easier to understand
kuni katsuya

JPA implementation patterns: Bidirectional assocations | Xebia Blog - 0 views

blog.xebia.com/...erns-bidirectional-assocations

shared by kuni katsuya on 04 Nov 12 - No Cached
  • JPA implementation patterns: Bidirectional assocations
  • it gets interesting when we make this association bidirectional
  • But there is a catch!
  • ...2 more annotations...
  • if you run them within one transaction like the code below does, you will find that the item list while be empty:
  • to keep bidirectional associations in sync, JPA leaves more up to the developer.
kuni katsuya

Why you should never use getSingleResult() in JPA | Sysout.be - 0 views

sysout.be/...ver-use-getsingleresult-in-jpa

database JPA EntityManager.getSingleResult() EntityManager.getResultList()

shared by kuni katsuya on 07 Oct 12 - No Cached
  • The only use for getSingleResult() is when we are
  • executing a scalar (count, sum, avg) query
  • query wich will
  • ...8 more annotations...
  • alway
  • return a row
  • 3 ways to do this
  • EntityManger.find()
  • returns a typed instance of the entity when it is found, null when it is not found
  • But what if the row isn’t in the database (anymore)?
  • We get an unchecked exception: NoResultException
  • We never know for sure what we can expect from our database, so throwing an unchecked exception seems the wrong choice for this use-case
    • kuni katsuya
      kuni katsuya on 07 Oct 12
       
      thinking defensively, in a pathological scenario, the data and/or schema of the database could be corrupt eg. using a named query that should return a single entity based on a unique constraint of a table: - what if the unique constraint was implemented incorrectly in the ddl? (too relaxed or too strict) - what if the data became inconsistent as a result of some external process? => should always code defensively, especially at integration points to anything external to the jvm 
kuni katsuya

Adobe Community: Updated Groovy template for GraniteDS Builder (gas3) - 0 views

forums.adobe.com/4410894

graniteds flex java type conversion

shared by kuni katsuya on 01 Nov 12 - No Cached
  • Updated Groovy template for GraniteDS Builder (gas3)
  • also stripped out the specialized GraniteDS datatypes in favor of the LCDS serialization convention that Adobe uses (i.e. a Java map should translate to an 'Object' type, a Java enum should translate to a 'String', and Java collections should always serialize as 'ArrayCollection')
  • didn't do a 'base' version and a version that doesnt get touched by the code generator, but you could easily do so by modifying this template
  • ...3 more annotations...
  • two versions
  • for Managed entities:
  • meant for non managed entities:
kuni katsuya

JPA/Hibernate Ternary Association « Fulvio Di Marco: just a personal code not... - 0 views

fdimarco.wordpress.com/...ahibernate-ternary-association

java JPA ternary n-ary association relationships

shared by kuni katsuya on 23 Oct 12 - No Cached
  • JPA/Hibernate Ternary Association
  • kuni katsuya on 23 Oct 12
     
    "JPA/Hibernate Ternary Association"
kuni katsuya

Needle - Effective Unit Testing for Java EE - Overview - 0 views

needle.spree.de/overview

java javaee6 testing

shared by kuni katsuya on 24 Oct 12 - No Cached
  • Test Java EE applications effectively
  • Needle is a lightweight framework for testing Java EE components
  • outside of the container in isolation
  • ...3 more annotations...
  • reduces the test setup code by
  • analysing dependencies
  • automatic injection of mock objects
kuni katsuya

Introduction - 0 views

maven.apache.org/...index.html

java code analysis pmd maven plugin

shared by kuni katsuya on 09 May 12 - No Cached
kuni katsuya

Software Quality Environment: Wiki: Home - Project Kenai - 0 views

kenai.com/Home

code analysis netbeans plugin

shared by kuni katsuya on 09 May 12 - Cached
  • SQE attempts to provide first-class NetBeans IDE integration for different software quality tools.
  • Currently supported tools: FindBugs PMD CheckStyle Dependency Finder
kuni katsuya

Best Practices - 0 views

pmd.sourceforge.net/...bestpractices.html

java code analysis best practices

shared by kuni katsuya on 09 May 12 - No Cached
  • Best Practices
  • start with some of the obvious rulesets - just run unusedcode and fix any unused locals and fields. Then, run basic and fix all the empty if statements and such-like. Then peruse the design and controversial rulesets and use the ones you like via a custom ruleset
  • Using PMD within your IDE is much more enjoyable than flipping back and forth between an HTML report and your IDE
kuni katsuya

From Spring to Java EE 6 - Java Code Geeks - 1 views

www.javacodegeeks.com/...from-spring-to-java-ee-6.html

spring javaee6

shared by kuni katsuya on 10 May 12 - No Cached
  • prototyped application was designed as a standalone pure Spring applicatio
  • Spring v3
  • analyzed the interest of switching to a Java EE 6
  • ...9 more annotations...
  • can we do in Java EE 6 everything we can do in Spring ? can we do that as easy as in Spring ?
  • yes we can !
  • I am still - a real Spring fanboy (which I, historically speaking, discovered after having been literally disgusted by EJB's 1.0)
  • Contexts & Dependency Injection Messaging Transaction management Web services
  • Spring has an outstanding JMS support
  • Conclusion
  • Arguing that things are in Spring much simpler, much lighter than in Java EE is not - more exactly, no more – true
  • booting really fast
  • From Spring to Java EE 6
kuni katsuya

Why I will use Java EE instead of Spring in new Enterprise Java Projects in 2012 - Java... - 0 views

www.javacodegeeks.com/...ll-use-java-ee-instead-of.html

javaee vs spring

shared by kuni katsuya on 10 May 12 - No Cached
  • J2EE was horrible
  • This is why the Spring framework was created
  • It was lightweight, easy to use, and applications could be deployed in a web container (such as Tomcat) instead of a heavy J2EE application server
  • ...5 more annotations...
  • Pros and Cons of JEE and Spring
  • Advantages of JEE
  • set of standard specifications, thus it is vendor-independent
  • testing is possible!
  • Lightweight application servers and frameworks such as Arquillian arrived
« First ‹ Previous 161 - 180 of 248 Next › Last »
Showing 20▼ items per page