{"id":8337,"date":"2012-09-25T00:43:46","date_gmt":"2012-09-24T19:13:46","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=8337"},"modified":"2012-09-25T02:17:44","modified_gmt":"2012-09-24T20:47:44","slug":"gdsl-awesomeness-setting-a-global-context","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/gdsl-awesomeness-setting-a-global-context\/","title":{"rendered":"GDSL Awesomeness – Setting a global context"},"content":{"rendered":"

Hi,<\/p>\n

Sometimes we need to set the context for the GDSL contributor to all the possible files and scripts in the project scope.
\nThis is a rare case scenario, but could be handy on some implementations. <\/p>\n

 <\/p>\n

This can be done by two techniques:<\/p>\n

    \n
  1. Ignoring all filters passed to the “context” method.<\/li>\n
  2. Setting the “ctype” parameter to “java.lang.Object” class.<\/li>\n<\/ol>\n

     <\/p>\n

    It is illustrated as follows:
    \n[java]
    \n\/\/To set the global context
    \ndef globalContext = context() \/\/ No need to provide any filters.<\/p>\n

    \/\/Alternate method
    \ndef globalContext = context(ctype: "java.lang.Object") \/\/ Contribute to Object class<\/p>\n

    [\/java]<\/p>\n

     <\/p>\n

    Read Further in the “GDSL AWESOMENESS” Series<\/h1>\n
      \n
    1. GDSL Awesomeness – Introduction to GDSL in IntelliJ Idea<\/a><\/li>\n
    2. GDSL Awesomeness – Understanding Context And Contributors in Detail<\/a><\/li>\n
    3. GDSL Awesomeness – Defining dynamic property in a class<\/a><\/li>\n
    4. GDSL Awesomeness – Defining dynamic method in a class<\/a><\/li>\n
    5. GDSL Awesomeness – Adding Hinting for missingMethod implementation<\/a><\/li>\n
    6. GDSL Awesomeness – Setting a global context<\/a><\/li>\n
    7. GDSL Awesomeness – Delegating Closure Calls<\/a><\/li>\n
    8. GDSL Awesomeness – Defining methods in a closure passed to method of particular name<\/a><\/li>\n
    9. GDSL Awesomeness – Defining Properties in a closure passed to method of particular name<\/a><\/li>\n
    10. GDSL Awesomeness – Contributing to classes which match a path\/name pattern<\/a><\/li>\n
    11. GDSL Awesomeness – contributing methods with current class return types or parameters<\/a><\/li>\n
    12. GDSL Awesomeness – AutoComplete Script for grails-Mail-Plugin “sendMail” closure<\/a><\/li>\n
    13. GDSL Awesomeness – Getting Code of a method or Field in GDSL Script<\/a><\/li>\n
    14. GDSL Awesomeness – Advanced Example showing domain properties implementation<\/a><\/li>\n<\/ol>\n

       <\/p>\n

      Hope it helps<\/p>\n

      Kushal Likhi<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

      Hi, Sometimes we need to set the context for the GDSL contributor to all the possible files and scripts in the project scope. This is a rare case scenario, but could be handy on some implementations.   This can be done by two techniques: Ignoring all filters passed to the “context” method. Setting the “ctype” […]<\/p>\n","protected":false},"author":28,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":49,"footnotes":""},"categories":[7],"tags":[1057,9,692,691,1059,1060,1058],"class_list":["post-8337","post","type-post","status-publish","format-standard","hentry","category-grails","tag-gdsl","tag-groovy","tag-intellij","tag-intellij-idea","tag-program-syntax-interface","tag-psi","tag-syntax-highlighting"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t