The name of the class that implements
java.sql.Driver in MySQL Connector/J is
com.mysql.jdbc.Driver
Group items matching
in title, tags, annotations or url
6More
MySQL :: MySQL 5.1 Reference Manual :: 21.3.5.1 Driver/Datasource Class Names, URL Synt... - 0 views
-
-
JDBC URL Format The JDBC URL format for MySQL Connector/J is as follows, with items in square brackets ([, ]) being optional: jdbc:mysql://[host][,failoverhost...][:port]/[database] » [?propertyName1][=propertyValue1][&propertyName2][=propertyValue2]... If the host name is not specified, it defaults to 127.0.0.1. If the port is not specified, it defaults to 3306, the default port number for MySQL servers. jdbc:mysql://[host:port],[host:port].../[database] » [?propertyName1][=propertyValue1][&propertyName2][=propertyValue2]... Here is a sample connection URL: jdbc:mysql://localhost:3306/sakila?profileSQL=true
-
Initial Database for Connection If the database is not specified, the connection is made with no default database
- ...2 more annotations...
-
fully specify table names using the database name (that is, SELECT dbname.tablename.colname FROM dbname.tablename...) in your SQL
-
work with multiple databases
-
2More
MySQL :: MySQL 5.1 Reference Manual :: 21.3.5.2 JDBC API Implementation Notes - 0 views
-
Connection
-
If you need to determine if the connection is still valid, issue a simple query, such as SELECT 1. The driver will throw an exception if the connection is no longer valid.
11More
Appendix C. Spring Security Dependencies - 0 views
-
Spring Security Dependencies
-
This appendix provides a reference of the modules in Spring Security and the additional dependencies that they require in order to function in a running application
-
C.1 spring-security-coreThe core module must be included in any project using Spring Security.
- ...8 more annotations...
-
DependencyVersionDescriptionaopalliance1.0Required for method security implementation.
-
spring-aop Method security is based on Spring AOP
-
spring-beans Required for Spring configuration
-
spring-expression Required for expression-based method security (optional)
-
spring-jdbc Required if using a database to store user data (optional).
-
spring-tx Required if using a database to store user data (optional).
-
C.6 spring-security-aclThe ACL module.
-
spring-jdbc Required if you are using the default JDBC-based AclService (optional if you implement your own).spring-tx Required if you are using the default JDBC-based AclService (optional if you implement your own).
Index of /seam/3/security/latest/reference/en-US - 0 views
18More
Seam - Contextual Components - 0 views
-
15.6. Authorization
-
Seam Security is built around the premise of users being granted roles and/or permissions, allowing them to perform operations that may not otherwise be permissible for users without the necessary security privileges
-
15.6.1. Core concepts
- ...15 more annotations...
-
15.6.1.1. What is a role? A role is a group, or type, of user that may have been granted certain privileges for performing one or more specific actions within an application
-
used to create logical groups of users for the convenient assignment of specific application privileges
-
15.6.1.2. What is a permission? A permission is a privilege (sometimes once-off) for performing a single, specific action. It is entirely possible to build an application using nothing but permissions, however roles offer a higher level of convenience when granting privileges to groups of users
-
consisting of three "aspects";
-
a target
-
an action
-
a recipient
-
An empty @Restrict implies a permission check of componentName:methodName
-
implied permission required to call the delete() method is account:delete
-
equivalent of this would be to write @Restrict("#{s:hasPermission('account','delete')}")
-
@Restrict annotation may reference any objects that exist within a Seam context. This is extremely useful when performing permission checks for a specific object instance.
-
selectedAccount
-
selectedAccount
-
Identity.instance().checkRestriction
-
If the expression specified doesn't evaluate to true, either if the user is not logged in, a NotLoggedInException exception is thrown or if the user is logged in, an AuthorizationException exception is thrown.
7More
MySQL :: MySQL 5.7 Reference Manual :: 5.1.4 Server System Variables - 0 views
-
autocommit
-
auto_increment_offset
-
auto_increment_increment
- ...4 more annotations...
-
init_connect
-
init_connect
-
executed by the server for each client that connects
-
one or more SQL statements, separated by semicolon characters
3More
Seam Cron Module - 0 views
-
Seam Cron is a CDI portable extension for scheduled and asynchronous method invocation
-
It wraps common scheduling and backgrounding tasks in an intuitive, type-safe, event driven API
-
Seam Cron Module
4More
JBoss Seam 3 JMS Module - 0 views
-
Bridging the Gap
-
Routing CDI Events to JMS
-
CDI Events from JMS Messages
3More
Seam International Module - 0 views
-
3. Locales
-
3.2. User Locale
-
4. Messages4.1. Message Creation4.2. Properties Files
5More
OpenTravel Forum - 0 views
-
OpenTravel Codes in Schema
-
If you are an inventory supplier, you would reference a rate plan code known to your system, such as “DELUXE” or “Deluxe Room”
-
RoomTypeCode
- ...2 more annotations...
-
assigned by the inventory supplier
-
If you are not a supplier, you need to work with your supplier trading partners to get a list of room types supported by their CRS (central reservation system) or PMS (property management system.)
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)
42More
Login for Server-side Apps - Facebook Developers - 0 views
-
compare it to the same state variable stored client-side in the session
-
-
If the user decided to decline to authorize your app
-
YOUR_REDIRECT_URI
- ...38 more annotations...
-
error_reason=user_denied
-
Handling Revoked Permissions to see how best to proceed
-
Step 6. Exchange the code for an Access Token
-
exchange it for a User access token that can then be used to make API requests
-
/oauth/access_token
-
server-side request to the following OAuth endpoint:
-
client_secret
-
code=CODE_GENERATED_BY_FACEBOOK
-
body of the response
-
access_token
-
USER_ACCESS_TOKEN
-
persist this User access token in your database or in a session variable
-
must have the same base domain as that specified in the App Domain property of your app's settings
-
URL of the form https://apps.facebook.com/YOUR_APP_NAMESPACE
-
scope=user_birthday,read_stream
-
Step 4. Add Permissions to Login Dialog request
-
comma-separated list of any of the Permissions available
-
Step 5. Handle the response from the Login Dialog
-
Step 5. Handle the response from the Login Dialog
-
Step 5. Handle the response from the Login Dialog
-
Step 5. Handle the response from the Login Dialog
-
YOUR_REDIRECT_URI
-
Step 3. Redirect the user to the Login Dialog
-
Login for Server-side Apps
-
Login for Server-side Apps
-
Login for Server-side Apps
-
Login for Server-side Apps
-
Login for Server-side Apps
-
Login for Server-side Apps
-
way to authenticate users in situations where the use of client-side Javascript is not appropriate.
-
Login for Server-side Apps
-
received an access token for them and can make API calls on their behalf
-
Step 5. Handle the response from the Login Dialog
-
include CSRF protection using the state parameter
-
if the user has authorized the app, they will be redirected to:
-
YOUR_REDIRECT_URI
-
code=CODE_GENERATED_BY_FACEBOOK
-
redirect_uri as the same URL that redirect the user to the Login Dialog
5More
tiainen: Easy OAuth using DaliCore and Glassfish: the service provider - 0 views
-
Easy OAuth using DaliCore and Glassfish: the service provider
-
CDI configuration
-
use CDI to inject a reference to the UserBean and the OAuthBean
- ...2 more annotations...
-
JPA configuration
-
dalicore-oauth persistently stores its request and access tokens, its users and its list of service consumers
43More
TH03-EP01-US001 - Media Management, Media Upload, Media Item Fields (Groomed BE21, FE8)... - 0 views
-
Media Management,
-
upload a new media item
-
syndication and encoding - not part of this user story
- ...26 more annotations...
-
definition
-
-
Owner
-
Rights of owner
-
dependent on implementation of licensing/rights management system which is tbd, so these will be best guess stubs for now
-
-
Rights expiry date
-
dependent on implementation of licensing/rights management system which is tbd, so these will be best guess stubs for now
-
-
Syndication
-
dumbed down, feature parity implementation is just a list of idss allowed distribution (i believe) use existing legacy infrastructure? ultimate syndication system will depend on: - licensing - explicit list of syndication channels (much like legacy) - rule-based routing
-
-
Caption
-
Category
-
-
Seasonality display rules
-
this is one (simple) example of rule-based syndication: rule type: temporal (which could include: time range, recurrence, end time, etc) rule: syndicate while startDate>=now() and endDate<=now()
-
-
Short description
-
Long description
-
Search keywords
-
Associated with
-
-
in the media library
-
can be viewed by users
-
not only new ecm users, but legacy viewers as well ie. content uploaded via ecm must be available for display in legacy viewers, at least until legacy system is replaced and shutdown for good
-
-
Uploaded by
-
Date uploaded
-
Date modified
-
Last modified by
-
Status
-
TO DO: for new domain model, should define explicit content life cycle with state diagram
-
-
File type
-
Media type
-
Dimensions
-
Aspect ratio
-
aspect ratio doesn't need to be stored in db as metadata, since it can be calculated cheaply based on the dimensions
-
-
File size
-
-
File name
-
is this the original name of the file that was uploaded? if not, and it supposed to be the medlib file name, imho, should not be exposed. the medlib file name should be immaterial to the ecm user and generally, vfml should treat them as opaque to allow future changes without customer dependencies the only time an ecm user should care about a 'file name' is when they're uploading or downloading. but... once the file is uploaded, who cares what the original file name was? it will be recorded, but should be inconsequential to anything since it would never, ever be referred to again on download, (save as...) the original file name *could* be used, but any file name is just as good, since the downloader would also be given the option to rename the file
-
-
Media units consumed
-
calculated/cached value pull from legacy system in future sprints, could start to build phased shell of the marketing xxx system 1. getMediaUnits()
-
TODO: confirm with david and/or henry.wu where/how to obtain 'media units consumed' for a media item
-
17More
Chapter 14. Tide client framework - 0 views
-
14.3. Contexts and Components
-
core concepts
-
component
- ...14 more annotations...
-
context
-
unique context that exists during the whole lifetime of the Flex application. It can be compared to to the server-side session
-
Components
-
two main kinds of contexts:
-
stateful objects that can be of any ActionScript 3 class with a default constructor
-
global context
-
temporary contexts that can be created and destroyed at any time during the lifetime of the application
-
conversation contexts
-
conversation context always has an identifier
-
usually tied to a particular use case in the application
-
three available scopes:
-
session scope
-
conversation scope
-
event scope
4More
Chapter 2. Mapping Entities - 0 views
-
2.2.3. Mapping identifier properties
-
@Id annotation lets you define which property is the identifier of your entity
-
can be set by the application itself
- ...1 more annotation...
-
or be generated by Hibernate (preferred)
12More
Page - Facebook Developers - 0 views
-
photos
-
Create
-
HTTP POST request to PAGE_ID/photos
- ...9 more annotations...
-
publish_stream and manage_pages permissions
-
source
-
multipart/form-data
-
videos
-
Create
-
HTTP POST request to https://graph-video.facebook.com/PAGE_ID/videos
-
publish_stream and manage_pages permissions
-
source
-
multipart/form-data
2More
Page - Facebook Developers - 0 views
-
picture
-
are these params mutually exclusive? ie. provide source photo's url (image that exists on the interweb) OR form-data (uploading from desktop)
-
2More
FB CMS (DMS) User Stories - Projects - Confluence - 0 views
-
Sequence Diagrams (Upload):
-
sequence diagrams for initial, cdms implementation, *not* cube implementation (see only as reference)
-