- The opinions expressed here are my personal opinions. Content published here is not read or approved in advance by EMC and does not necessarily reflect the views and opinions of EMC.
Tags
agile aix ant automation bug tracking convention data dependency injection design pattern eclipse encapsulation eXtreme Programming factory fix gnu/linux gwt html java javafx jsp jvm log mvc osgi parameter object perforce performance pipe refactoring reflection regexp service strange struts subversion TDD tennis tomcat visitor vpn webapp xacml xml xp studio xsltTwitter
- RT @macgirlsweden #XACML engine evaluates the policy & w/ low risk level allows edit but w/ higher level removes edit or hides doc #mmtm12 1 day ago
- RT @johjak #mmtm12 Jeroen starting demo of #xacml policy-based security; risk-adative security. Interesting! #emcworld #documentum 1 day ago
- RT @macgirlsweden #XACML Components being shown #mmtm12 #documentum http://t.co/Va6uqdIq 1 day ago
- RT @turnerkid #mmtm12 reactive dynamic adaptive security model being discussed. Been working with RSA #XACML 1 day ago
- RT @macgirlsweden Argues for a need for dynamic security models - shows off the #XACML engine #mmtm12 #documentum 1 day ago
Tag Archives: perforce
The verdict on Perforce
At work, I’m now forced to use the Perforce version control system, since that’s what our company has standardized upon. I’ve had some bad feelings about that from the start (based on reading about it), but I’ve hold off on … Continue reading
Root Cause Analysis
I’ve moved on to a new project recently. It’s quite different from the previous one. Before I worked on a monolythic web application, now we’re using OSGi. As a result, our project consists of a lot of sub-projects (OSGi bundles) … Continue reading
Posted in process
Tagged ant, cause effect diagram, gradle, groovy, osgi, perforce, root cause analysis, subversion
2 Comments