Persistence unit properties
Group items matching
in title, tags, annotations or urlBruce Phillips Blog on Java, ColdFusion, Flex and Spry: Java EE 6 Example Projects For ... - 0 views
1More
1. Project Overview - Confluence - 0 views
-
just stumbled across an important link to 'developer guide' docs on this page, which isn't referenced anywhere from the main documentation page! (http://www.graniteds.org/confluence/display/DOC)
17More
shared by kuni katsuya on 14 Jun 12
- No Cached
JPA Reference Guide - JBoss AS 7.0 - Project Documentation Editor - 0 views
docs.jboss.org/...JPA+Reference+Guide
jbossas7 jpa reference documentation persistence-unit jpaprovider
shared by kuni katsuya on 14 Jun 12
- No Cached
-
-
Should be hibernate3-bundled if Hibernate 3 jars are in the application archive (adapterModule and adapterClass will automatically be set for hibernate3-bundled).
-
org.jboss.as.jpa.hibernate:3 (Hibernate 3 integration classes)
- ...14 more annotations...
-
jboss.as.jpa.adapterModule
-
jboss.as.jpa.adapterClass
-
org.jboss.as.jpa.hibernate3.HibernatePersistenceProviderAdaptor
-
Working with other persistence providers
-
A project to build integration for persistence providers like EclipseLink, is here.
-
Troubleshooting
-
“org.jboss.as.jpa” logging can be enabled to get the following information: INFO - when persistence.xml has been parsed, starting of persistence unit service (per deployed persistence.xml), stopping of persistence unit service DEBUG - informs about entity managers being injected, creating/reusing transaction scoped entity manager for active transaction TRACE - shows how long each entity manager operation took in milliseconds, application searches for a persistence unit, parsing of persistence.xml
-
To enable TRACE, open the as/standalone/configuration/standalone.xml (or as/domain/configuration/domain.xml) file. Search for <subsystem xmlns="urn:jboss:domain:logging:1.0"> and add the org.jboss.as.jpa category
-
Packaging the Hibernate 3.5 or greater 3.x JPA persistence provider with your application
-
jboss.as.jpa.providerModule needs to be set to hibernate3-bundled.
-
<property name="jboss.as.jpa.providerModule" value="hibernate3-bundled" />
-
Sharing the Hibernate 3.5 or greater JPA persistence provider between multiple applications
-
Applications can share the same Hibernate3 (for Hibernate 3.5 or greater) persistence provider by manually creating an org.hibernate:3 module (in the AS/modules folder). Steps to create the Hibernate3 module:
-
<property name="jboss.as.jpa.providerModule" value="org.hibernate:3" />
6More
ActionScript, NetBeans and FlexBean (PROTIP included) « Greymatter.pl - 0 views
-
it’s much less bloated and much snappier than Eclipse
-
ActionScript, NetBeans and FlexBean
-
basic MXML templating and project make support (through Ant)
- ...3 more annotations...
-
open an .as file as a JS script
-
you can get basic code highlighting and formatting
-
right/command click an .as file in the project pane and select ‘Open As..’, then select text/javascript MIME type
Mavenizing Javascript Projects « akquinet-blog - 0 views
intellij-java-google-style.xml - google-styleguide - Style guides for Google-originated... - 1 views
/trunk/ - google-styleguide - Style guides for Google-originated open-source projects -... - 0 views
11More
Generic CRUD Service aka DAO - EJB 3.1/0 Code - Only If You Really Needed : Adam Bien's... - 0 views
-
Generic CRUD Service
-
The term Data Access Object (DAO)
-
is actually wrong
-
- ...7 more annotations...
-
easy with generics
-
create
-
find(
-
update(
-
delete(
-
CrudService
-
@TransactionAttribute(TransactionAttributeType.MANDATORY)
19More
log4jdbc - JDBC proxy driver for logging SQL and other interesting information. - Googl... - 0 views
-
for prepared statements, the bind arguments are automatically inserted into the SQL output
-
SQL timing information can be generated to help identify how long SQL statements take to run
-
included tool to produce profiling report data for quickly identifying slow SQL in your application
- ...16 more annotations...
-
SQL connection number information is generated
-
change the driver class name to net.sf.log4jdbc.DriverSpy
-
"jdbc:log4"
-
jdbc.sqlonly
-
jdbc.sqltiming
-
jdbc.audit
-
jdbc.resultset
-
jdbc.connection
-
only SQL
-
the SQL
-
timing statistics
-
ALL JDBC calls
-
very voluminous output
-
all calls to ResultSet objects
-
connection open and close events
-
useful for hunting down connection leak problems
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
10More
VineetReynolds / Java EE 6-Galleria / wiki / Home - Bitbucket - 0 views
-
Java EE 6-Galleria
-
Java EE 6-Galleria
-
captures various project design decisions to aid in understanding the design choices made during the design and construction of the application.
- ...7 more annotations...
-
Overall Application Architecture
-
Data Model
-
Domain Model
-
Testing the Domain Layer
-
Testing the Application Layer
-
Testing the Presentation Layer
-
Overview Source
7More
TH02-EP02-US003 - VFML Admin, Org Mgmt, Create Organization - Projects - Confluence - 0 views
-
Org Mgmt
-
create a new organization
-
onboard a new client
-
- ...1 more annotation...
-
VFML user
-
8More
TH02-EP02-US004 - VFML Admin, Org Mgmt, Sync Properties - Projects - Confluence - 0 views
-
using EXCC
-
-
sync properties
-
sync meaning: a. ensuring that chain-hotel relationships based on icpm data is represented the same way in the cube node structure? (eg. which hotels belong under which chains, and to keep dynamically/automatically updated as hotels are added/removed from chains) 2. or...?
-
-
As a VFML user
-
implies restriction of this action via authorization controls (ie. required vs granted permissions)
-
- ...1 more annotation...
-
maintain an accurate listing of properties in an org
-
2More
TH01-EP03-US001 - Property Mgmt, Edit Location & Directions, Location Type and Descript... - 0 views
-
LOC code
-
31More
TH01-EP03-US004 - Property Mgmt, Edit Location & Directions, Content Mgmt - Projects - ... - 0 views
-
Property Mgmt
-
Property Mgmt
-
Property Mgmt
- ...18 more annotations...
-
Property Mgmt
-
Property Mgmt
-
Property Mgmt
-
As a user
-
-
ability to see
-
-
Location Type
-
Description
-
Airports
-
belonging to other organizations
-
-
clone this information
-
clone = retrieve, then create ie. required permissions: {retrieve,create:}
-
-
have the rights
-
generally speaking, there can be a few independent but overlapping mechanism that will control who is allowed to do what with content: 1. any subject's access to the content itself can be controlled via authorization rules (ie. required vs granted permissions) enforced via system-wide resource-based access control 2. content licensors (~content owners) can restrict the usage of their content by: * whom - ie. content licensee (legally/commercially represented by an organization) * how - eg. reuse as unmodified, create derivatives, composite, redistribute, etc * where - ie. distribution channels their content can be used (eg. only on hotel's vbrochure site, but not in any ids/gds channels) * when - temporal restrictions may limit scope of content license grant by: start, end, duration, season, etc 3. content licensees can further filter or funnel content available to them (resulting from a combination of license granted to them and access control) based on their own criteria (eg. generate a templated hotel presentation only if: at least 1 textual description, 5 photos and 1 video for a hotel is available with a license to combine them (composite content)
-
-
see how other organizations describe the property
-
permission required: retrieve hotel descriptive content(?) owned by independent organization
-
-
Property Mgmt
-
which textual information
-
displayed
-
-
ECM will ask user to confirm that the user has rights to use that content
-
if ecm/vfml is to manage content licensing as a third party between organizations (content licensors & licensees) shouldn't ecm *know* if the user('s organization) has rights to use the content in question? is this question posed to the user (with required explicit acknowledgement) purely to absolve vfml from liability issues that may result from licensing disagreements?
-
-
property’s
-
this being the user's (organization's) 'version'or 'view'of the hotel, since this user normally wouldn't/shouldn't be granted permissions to replace content for a hotel on a different organization's 'view'or 'version' of the same hotel
-
-
to see the user’s original content
-
this implies that *at least* one version of such (temporarily) replaceable content needs to be managed/maintaned to allow reverting what if, deliberately, ignorantly or maliciously, a user replaces the same piece of--textual or any type, really--content for this hotel n times? will all n versions be required to be managed as an undo history? the user's ''original content'' might have been version 1, but equally might have been 1 mean: - previous version of the content, regardless of which user - initial version of that content attached to the hotel regardless of which user created/updated it and ignoring which organization owns it?, or, -
-
4More
TH03-EP01-US001 - Media Management, Media Upload, Media Item Fields (Groomed BE21, FE8)... - 0 views
-
Associated with
-
-
viewed by users
-
and available to all legacy content distribution services (eg. oms, viewers, vscape, etc)
-
21More
Top 10 Lessons Learned From 10 Years in Agile | Agile Zone - 0 views
-
Top 10 Lessons Learned From 10 Years in Agile
-
1. Simplicity is Sophistication.
-
2. Define your Rhythm.
- ...18 more annotations...
-
start cutting down on wasted meeting time
-
3. Agile is Fundamentally About Discipline.
-
areas of planning, unit testing, test driven development, continuous integration, and test automation.
-
4. Software is Hard to Scale, Agile is Not.
-
Focus on business goals
-
5. Think of the Big Picture.
-
success requires a
-
consideration of the system as a whole
-
before making changes to its parts, or else the change will likely be fraught with risk.
-
6. Lose the Religion
-
adapt agile to your need.
-
7. Continuous Focus on Business Value.
-
get caught in the weeds of a technical story's delivery and velocity at the expense of overall business value, company and project goals
-
8. Agile - It's Not Just For Software Anymore.
-
9. Continuous Planning.
-
Plan on a daily basis if possible
-
Keep your focus on maximizing value
-
10. Doing agile and being agile aren’t the same.
51More
shared by kuni katsuya on 15 Mar 13
- No Cached
Preemptive commit comments | Arialdo Martini - 0 views
arialdomartini.wordpress.com/...pre-emptive-commit-comments
BDD BehaviorDrivenDevelopment CommitComment BestPractices SoftwareEngineering
shared by kuni katsuya on 15 Mar 13
- No Cached
-
Tell me what the software does
-
tell me how the software should *behave*, not how the behavior was *implemented* ie. describe the changes in this commit from the behavioral perspective rather than implementation details
-
-
What is the project behavior, in this snapshot?
-
What did the programmers, in order to produce this snapshot?
- ...43 more annotations...
-
committing comments describing the
-
behavior of the software,
-
rather than the
-
implementation or a description of what we did
-
commits’ comments started to look like BDD’s methods name: a description of a behavior.
-
principles
-
Talk about the feature, not about yourself
-
Don’t refer to the past
-
I know it’s now
-
list of benefits
-
More focus while developing
-
Commit review is much easier
-
Less cognitive load
-
You learn commenting much more precisely
-
commit comment becomes a
-
declaration of intent
-
like a BDD method name
-
No more “Just a fix“, “Improvements” or “I made this, this, this and also this” comments.
-
BDD/TDD or any methodology aside, these are the worst commit comments as they are as useless as empty commit comments
-
-
Each preemptive comment triggers a micro design session
-
A preemptive comment sets a micro goal
-
which also aligns well with the 'micro goal' or incremental deliverables approaches of most agile methodologies
-
-
helps to focus a goal to be reached
-
Without preemptive comments, I often went on coding, always asking myself: “Should I commit now? Have I reached a stable state which I could consider a good commit?“
-
define micro-goals through preemptive comments
-
macro-goal through the feature branch name
-
A preemptive comment creates a little timebox
-
-
Writing comments preemptively puts the agreement between the pair members to a test
-
-
commit history gains a very balanced granularity
-
feature branch becomes a collection of evolutionary commits each of which has usually a 1:1 binding with tests
-
very easy to find which commit introduced a bug, since each commit is related to a single new goal/feature
-
Preemptive commit comments
-
Rule #2: write what the software
-
I started taking a lot of care of the words I was using in comments, commits, test names and classes/variables/methods’ names
-
be supposed to do,
-
not what you did
-
should
-
Introducing BDD
-
began with the simple attempt to replace the world
-
“should“
-
“test”
-
with the world
-
Rule #1: write commit comments before coding
-
use the same criteria for my commits’ comments as well.
-
(not what you did)