Download [#CDV-13] Configure using Java Annotations

[CDV-13] Configure using Java Annotations Created: 30/Nov/06
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Closed
Community Development (Terracotta Server)
X-Common Code
None
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
New Feature
Issue Review Board
Fixed
None
Not Specified
Updated: 27/Jul/12 Resolved: 17/Sep/07
None
Priority:
Assignee:
Votes:
3 Minor
Product Management
0
Not Specified
Not Specified
Description
Support a DSO programming model based on JSR 175 annotations as an alternative
configuration mechanism for DSO metadata. Instead of writing tc-config.xml, DSO developers
would declare metadata inline in their code using the standard Java mechanism for Java code
metadata.
For example:
import com.terracotta.annotations.Root;
public class ECommerceClient
{ @Root public static Inventory; }
And:
import com.terracotta.annotations.Shareable;
import com.terracotta.annotations.WriteLock;
@Shareable(honorTransient=true) public class Inventory {
@WriteLock public void doImportantUpdateStuff()
{ ... }
}
Note that annotations would be supported in addition to the existing XML configuration. XML
will always be required for operational settings (e.g. listen ports, logs, and so forth). Plus, we
need to continue to support the drop-in use case which can only be accomplished via an external
configuration file.
Reasons:






Developers like annotations
It's low-hanging fruit
Pretty much every framework that manages POJOs works this way
JBoss Cache AOP does this (PojoCache)
Demos involving code will be 10x more clear and powerful
This is where the money is
Reference - Support JSR 175 annotations for DSO meta data: LKC-451 (Terraotta internal
development Jira issue)
Comments
Comment by Taylor Gautier [ 17/Sep/07 ]
Most functionality for annotations is implemented.
Generated at Thu May 11 07:14:32 PDT 2017 using JIRA 6.2.4#6261sha1:4d2e6f6f26064845673c8e7ffe9b6b84b45a6e79.