The Java RIA Framework

David,

I can see at least 2 solutions to achieve what you want.

The first one consists in making the selected record the model of a bean sub-module. This can be easily done using the built-in addAsChildModuleFrontAction as described in this post. Here is the SJS version adapted (and tested) in the HR sample application (installed on the department teams table to edit a team as a sub-module in the workspace tree) :

form ('Team.pane') // The view we want to use for the team edition  

action('yourCustomAction', parent:'addAsChildModuleFrontAction') { //define a top-level, referenceable action
  wrapped(class:'org.jspresso.framework.application.backend.action.module.AddBeanAsSubModuleAction',
    custom:['childModuleProjectedViewDescriptor_ref':'Team.pane']) // and customize it to display the view defined above
}

table('Department-teams.table', // we install it on the department teams table view 
  columns:['ouId','name','manager'],
  readOnly:true, // we make the table read-only so that we can install a row double-click action
  rowAction:'yourCustomAction') { // We install our action as the row double-click action
    actionMap (parents:['masterDetail']) { // but we can also complement the standard master-detail action map
      actionList('View') { // by adding a new action list (i.e. toolbar section)
        action ref:'yourCustomAction'
    }
  }
}

The second option is to use a dialog poping-up for editing the selected team. This one needs a few lines of code using the 3.5.0 release, but I've just deployed a new snapshot that makes the stuff really straightforward. So if you change your project root pom.xml to bind to 3.5-SNAPSHOT instead of 3.5.0, you will be able to replace the action in the snippet above by the following lines :

action'yourCustomAction',
  parent:'editSelectedComponentAction',
  custom:['viewDescriptor_ref':'Team.pane']

Could hardly be shorter, right ? BTW, one difference with the previous action, is that this one uses Jspresso "Unit of Work" mechnism that allows to work transactionally in memory, i.e. the dialog actually displays a deep copy of the selected team so that clicking "Ok" actually commits the modification in the session entity and clicking "Cancel" rolls back the modifications.

As for your second point, you can easily pre-load a filter module by registering a startup action (that gets trigerred when the module is first displayed), e.g. (taken from HRsample snapshot) :

action 'filterModuleStartup',
  class:'org.jspresso.framework.application.frontend.action.FrontendAction',
  wrapped:'initModuleFilterAction',
  next:'queryModuleFilterAction'

workspace('organization.workspace',
  icon:'structure-48x48.png',
  grantedRoles:['administrator','organization-manager']) {
    filterModule('companies.module',
      icon:'company-48x48.png',
      component:'Company',
      detailView:'Company.module.view',
      startup:'filterModuleStartup')
}

more generaly , the groovy dsl is very nice,

Thanks!

but it's hard to visualize all the options available when you describe a view, a module or an actionMap

 We are working hard on doc, but the key will surely be SJSPlug (and contextual doc).

Best,

Vincent

Hi David

I will try to help you... can you zip and attach your SJS groovy files (or all the "core" directory if you added java files to you Jspresso project) ?

I will come back from holiday on Sunday... I will answer you by Monday evening...

Regards,

Maxime

Hi, i've tried the Vincent solution, and it works fine. Althought, when the Team.pane view is showed, we don't have any toolbar (at least with a back button, for exeample). How can this be achieved? The same happens on this quite similar case - http://www.jspresso.org/forum/add-button-open-entity.

Thanks,
Carlos V.