Blog

Integrating With WCS Is Easy As Ever

Obviously, you can still use the GSF from your Java code.

Very Cool Annotations

class SomeTypicalController extends InjectingController {
        
        (...)
 
        @CurrentAsset(attributes=["title", "subtitle", "body"]) TemplateAsset theAsset;
 
        protected void handleRequest() {
                String headline = theAsset.asString("headline");
                
                (...)
        }
        
        (...)
 
}

• The @ServiceProducer annotation (tools.gsf.config.ServiceProducer) allows your defining ServiceProducer methods inside your Factory classes.

(...)

@ServiceProducer(cache = true, name="someCustomBean")
public MyCustomBean newCustomBean() {
    return MyCustomBean.getInstance();
}

(...)

• The @InjectForRequest annotation (tools.gsf.config.inject.InjectForRequest) allows your injecting a ServiceProducer-produced bean into your own Java class, Groovy controller or even JSP / Groovy Template.

(...)

@InjectForRequest(value="sitePlanNavService")
protected NavService myNavService;

(...)

• The @Bind annotation (tools.gsf.config.inject.Bind) will look for a given variable in the specified scope ("ics", "request" or "session") and, if found, it will inject the value into the annotated field (plus, it handles automatic type conversion for you too)!

(...)

@Bind(value="rendermode")
protected String currentRenderMode;

(...)

• The @Mapping annotation (tools.gsf.mapping.Mapping) will look up a MAP entry (AssetType:AssetName, AssetType:AssetId, etc...) matching the specified key in the Template / CSElement being executed (for the current site) and, if found, it will inject the mapped value into the annotated field. Yes, it supports AssetId and left/right selection!

@Mapping(value="myMappedAssetIdKey")
protected AssetId mappedAssetId;