Skip to main content

Home/ Groups/ SoftwareEngineering
3More

Chapter 5. Basic O/R Mapping - 0 views

  • 5.1.6.2. Joined subclass strategy
  • A discriminator column is not required for this mapping strategy
  •  
    "5.1.6.2. Joined subclass strategy"
3More

dbdeploy.com » News - 0 views

  • May 4th, 2009
    • kuni katsuya
       
      dead project(?)
  •  
    "May 4th, 2009"
2More

dbdeploy.com - 0 views

  • dbdeploy is a Database Change Management tool
  • using version-controlled SQL delta scripts
5More

Flyway: the agile database migration framework for Java - 0 views

1More

Welcome to Migrate4j - 0 views

  •  
    meh
2More

Agile database schema management with Liquibase - BEKK Open - 0 views

  • Agile database schema management with Liquibase
  • easily be set up to integrate with Ant, Maven, Spring or even directly in a Java Servlet container
2More

ISO 3166-2 - Wikipedia, the free encyclopedia - 0 views

  • ISO 3166-2
  • defines upper-case alphabetic codes for the names of the principal subdivisions (e.g., provinces or states) of all countries coded in ISO 3166-1
1More

Dell PC Diagnostics | Dell Canada - 0 views

  • Dell PC Diagnostics
2More

E6530 owners thread - 0 views

  • E6530 owners thread
  • Thread: E6530 owners thread
10More

Temporary Documentation - 0 views

  • Low-level configurations
  • ConfigResolver
  • ConfigResolver.getPropertyValue
  • ...7 more annotations...
  • ConfigSource
  • A ConfigResolver uses all configured implementations of ConfigSource to lookup the property in question.
  • Custom Config-Sources
  • interface ConfigSourceProvider
  • ConfigSource
  • DeltaSpikeConfig (CDI based config)
  • application scoped CDI beans
41More

Security Module Drafts - Apache DeltaSpike - Apache Software Foundation - 0 views

  • Authorization
  • Impersonalization
    • kuni katsuya
       
      impersonation
  • authenticates “as a user” or access application imitating his identity - without knowing his password
  • ...36 more annotations...
  • elements of the user interface are displayed to the user based on the user's privilege level
  • assign permissions to individual objects within the application’s business domain
    • kuni katsuya
       
      individual objects == instances
  • Permissions
  • Permissions assigned to user for a given resource in the tree are inherited by other resources
  • Permissions are inherited
  • persist user, group and role information in database. JPA implementation is his dream
  • Security Module Drafts
  • Identity
  • interface Identity
  • login()
  • logout()
  • getUser()
  • Events LoggedInEvent LoginFailedEvent AlreadyLoggedInEvent PreLoggedOutEvent PostLoggedOutEvent PreAuthenticateEvent PostAuthenticateEvent
  • Object level permission
  • Grant or revoke permissions
  • Group management
  • User/Identity management
  • identity.hasRole
  • identity.hasPermission
  • Permissions model
  • Identity Management (IDM)
  • User, Group and Role
  • Events
  • hooks for common IDM or Security operations
  • Audit and logging for permission and IDM related changes
  • Event API.
  • Impersonalization
  • Impersonalization
  • control which elements of the user interface are displayed to the user based on their assigned permissions
  • ask for permission
  • without need to obtain object from DB
  • String resourceId
  • structure of resources
  • more advanced security resolution mechanisms
  • Rules based engine
  • external services - XACML
1More

Git - SVN Crash Course - 0 views

  • Git - SVN Crash Course
21More

Java API Design Checklist « The Amiable API - 0 views

  • Java API Design Checklist
  • Do not use
  • marketing
  • ...18 more annotations...
  • project
  • organizational
  • names
  • Do not move or rename the package of an
  • already released public API
  • Begin with a short, one sentence summary of the API
  • Provide enough details
  • Include the API version number
  • Ensure each type has a single, well-defined purpose
  • Type Design Checklist
  • Ensure types represent domain concepts, not design abstractions
  • Follow consistent design patterns when designing related types
  • Favor enumeration types over constants
  • Consider generic types
  • Avoid deep inheritance hierarchies
  • Do not use public nested types
  • Do not declare public or protected fields
  • Do not expose implementation inheritance to the client
« First ‹ Previous 321 - 340 of 1272 Next › Last »
Showing 20 items per page